Hi, thanks for your comments.
The idea of standarization has certainly been one of the big parts of the successes of relational databases. Though, as you point out relational databases aren’t actually compatible, they just follow the same ideas - and even there it took years from the original ideas in the 70’s until the first standards in the mid-late 80s.
The idea of ‘I could change’ is very powerful, even when, as you point out, it still takes some grunt to actually do.
I think, for us, GraphQL is now widely accepted and used. Indeed, there’s a number of products now that use GraphQL as the data access interface, so you can see your database as a GraphQL database.
GraphQL itself also now has a guiding federation, backed by many vendors, so there’s a really good signs there that GraphQL is fast becoming something more than the single vendor languages you mention in for graph databases. There’s also a growing ecosystem of tools. So. I think there’s good signs that GraphQL is moving in the kind of direction that you are looking for.