Core issue 164, OSLC paging should support POST with an application/x-www-form-urlencoded body

[David Honey1 <DavidHoney@uk.ibm.com>]

Issue https://issues.oasis-open.org/browse/OSLCCORE-164
relates to OSLC paging should support POST with an application/x-www-form-urlencoded
body.

Jim, the core spec at https://tools.oasis-open.org/version-control/browse/wsvn/oslc-core/trunk/specs/oslc-core.html#resourcePaging
and the responseInfo shape at https://tools.oasis-open.org/version-control/browse/wsvn/oslc-core/trunk/specs/core-vocab.html#responseInfo
doesn't address this issue. I think we agreed that we would include an
oslc:postBody in the responseInfo.

I also think we have the emphasis of
the following the wrong way round:
4.11.1 OSLC Services SHOULD support [LDPPaging]
to enable clients to retrieve large LDP resources (LDPRs) a page at a time.

4.11.2 OSLC Services MAY support a Resource
Paging Capability as defined in [OSLCCore2]
to enable clients to retrieve large resources a page at a time. This capability
is included to preserve compatibility with [OSLCCore2].


I think 4.11.2 should be a SHOULD, and
4.11.1 should be a MAY. I know of no query capabilities that implement
LDP paging. All the ones I have seen that support paging use 4.11.2. So
clients consuming query capabilities are likely to only support 4.11.2.

David.
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU