My suggestion 2013 was a limited but important missing “middleware” for building/editing CONTRIBUTIONs consisting of one or several COMPOSITIONs so I called it “Contribution builder” as described in the thread CONTRIBUTION builder supporting collaborative (multi user, multi device) editing? GraphQL? Operational Transformation?
In 2013 I did not think of providing simplified formats/paths or GraphQL (not published by then), but accessing the contribution builder via GraphQL would be one of the obvious alternatives that should be provided today.
And now, future speculations:
Another piece of, partly related, middleware could be an AQL result* parser that could be accessed via GraphQL. If it is combined with the contribution builder in smart ways I think that would cover most “simplifying” middelware needs.
*) Perhaps a GraphQL-accessible AQL result parser is not very useful for all kinds of AQL query results, some are really simple enough already, but it would likely be useful at least for certain (stored?) queries that return either:
- entire templated compositions (naturally containing “template_id” - see class “ARCHETYPED”) or
- lists of subtrees of content extracted from parts inside templated compositions. Perhaps one would need to include the template IDs (+path?) in a response column always named “template_id” - or have some other way to make life easier for the template-based model-translating result parser.