Consensus has been reached to pursue the operations extension proposal. We would like to have a single recommended path for multi-operation support, and the operations extension has proven to be the most flexible. It supports all the use cases thus far, including streaming.
Further work needed:
How to parallelize requests? Suggestion: servers can look to usage of
pointerreferences to determine when it’s feasible.
Mappings for all possible query params to attributes of an operation.
How to allow for greater response customizability (e.g. different fields used for resources of the same type, depending on their relationships)? This could be achieved using multiple
How to truncate or eliminate response payloads for certain operations?
Extensions are the other major issue to tackle in 1.1.
@ethanresnick will review his WIP proposals from May re: extension negotiation.