b3tt3rw0rs3
b3tt3rw0rs3 on Hacker News
Composeability is front and center in GQL, so you may want to consider it.
How would you think anyone should call a graph query language done by the SQL committee?
Many standards are also available via the national standards body of your locale (e.g. ANSI), often at a cheaper rate.
Just looking at
https://db-engines.com/en/ranking/graph+dbms clearly shows Neo4j as the most prominent graph db.
I think even Cosmos as number 2 might be misleading here, as Cosmos is a multi-model product and db engines doesn't distinguish between graph and non-graph use in the ranking.
(Same for ArangoDB)
AQL is a vendor-specific multi model language that lately has picked up some ideas from openCypher, like pattern matching.
GQL is a project for creating an International Standard language in the process of being created by experts from many countries that represent the interests of multiple vendors.
SPARQL requires buy-in into the world of the semantic web even when all you want to do is store and query graph data.
Also, property graphs wouldn't have managed to get the traction they have if SPARQL would have been sufficient. SPARQL simply suffers from being designed in a way that does not sufficiently address the needs of application developers, in expressivity, ease of use, let alone allowing easy migration of existing relational data by sharing the same type system with SQL.
Standards happen when the time is right. Property graphs have been in the making and matured for the last 10+ years, driven by Neo4j, other vendors, and the community and are going to stay. It's a sign of success that the SQL standards committee recognized this development by starting the GQL project.
The GQL project just started. Since it is going to be an ISO standard, the specification is only available for members while under development but may be purchased from ISO once final (Same as for SQL, though you can find copies on the internet).
GQL will be a declarative language in the spirit of existing property graph query languages like Cypher, so that gives you an idea. I'm sure as the project proceeds, various artefacts (software or otherwise) will become freely available.
If you want to dig deeper, gqlstandards.org links to some documents that are copyright Neo4j and have been submitted to the standards process.
https://drive.google.com/drive/folders/16CUhVI1PQ4hBlhD80_Ys...