representation parameter description unclear

[j-q-arnold]

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.