Yeah sure. You can use resource expansion and also field targeting (to only get fields you need), add some typesystem on top of it, make sub-resource-expansion

Yeah sure. You can use resource expansion and also field targeting (to only get fields you need), add some typesystem on top of it, make sub-resource-expansion look a bit nicer by... I don't know, creating a small DSL for it. And then standardize documentation and tooling around it. Voila, now you have your own implementation of GraphQL that might even be better than the original one, who knows. Only one way to find out! Until then I will continue to use GraphQL wherever it works well. :)