Response Description of resolution. (TackTong, 04/25/2010)
Query
RESOLVED In the current OSLC Reporting spec, you have the statement: "An OSLC Service MUST support paging and include oslc:responseInfo as required in the response of a query." However, note that the core spec says "The server MAY return the logical response as sequence of physical responses, referred to as pages." What is the reason for the MUST in the Reporting spec? Do you mean that if a response is paged, it must be done as per the core spec? Or do you mean that the server must really break down a response into pages? If you mean the former, I'm not sure the statement is necessary - all OSLC specs from here on are supposed to be compliant with the core spec, so if paging is performed, that is how it must be done. If you mean the latter, why? What is the maximum size of a reportable response? If a provider decided to page after 100 petabytes, is that compliant? If no maximum size is defined, a client has to handle a response of an arbitrary size, and therefore will be able to handle a response from a provider that does not page. Of course, a provider that does not implement paging might not be able to return a very large query result, so support for paging is recommended - but perhaps a given provider knows it's database is not that large. It seems to me the statement should probably use SHOULD rather than MUST. (TackTong for NickCrossley, 04/28/2010)
Response Specification updated from "MUST support paging ....." to "SHOULD support paging....". (TackTong, 04/30/2010)
Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Contributions are governed by our Terms of Use Ideas, requests, problems regarding this site? Send feedback