TL;DR: An argument for (with an included example spec) a protocol that solves many of the problems that graphql solves but at the REST layer (e.g. rather than o

TL;DR: An argument for (with an included example spec) a protocol that solves many of the problems that graphql solves but at the REST layer (e.g. rather than ontop of the REST layer). (As a personal aside: The difference between this spec and GraphQL is relatively minor, they seem equally complex in implementation details (e.g. correctly implementing a graphql server/resolvers is no cakewalk; and correctly implementing either in a less-programming-time way would require a large amount of meta-programming; something that this spec doesn't necessarily solve, or even seem to hint at, yet uses as an argument for it), the only real improvement is that this one is a layer lower (theoretically one less layer of abstraction/indirection improves performance and simplicity) and is not owned by Facebook).