A language for describing resource-oriented APIs & turning them into Swagger or resource diagrams. Oriented around the concepts we want to expose in the APIs.
The description of representation parameters is unclear.
The responsibilities between the service and the framework need to be clearly defined. The documentation's example seems to mix things defined by reslang and things that must be implemented by the service. The boundary is pretty fuzzy.
The text says such parameters turn into query parameters, but it seems more likely the parameters are queryonly. I suspect the parameters do not appear as resource attributes.
What is the difference between queryonly and representation? Why wouldn't one simply use queryonly? Unclear what functionality representation adds.
The description of
representationparameters is unclear.queryparameters, but it seems more likely the parameters arequeryonly. I suspect the parameters do not appear as resource attributes.queryonlyandrepresentation? Why wouldn't one simply usequeryonly? Unclear what functionalityrepresentationadds.