- From: John Arwe <johnarwe@us.ibm.com>
- Date: Mon, 30 Sep 2013 09:21:14 -0400
- To: public-ldp-wg@w3.org
- Message-ID: <OF7B2FB5FE.8BD87402-ON85257BF6.0048CEDB-85257BF6.00495B5E@us.ibm.com>
> > Container sort criteria are far less obvious however, and was the sticky > > part when we discussed the proposal at the F2F. Those currently require > > the presence of a ldp:Page resource in the triples regardless of whether > > or not the particular resource supports paging. > > Aren't they only in LDPCs? I'm just trying to get the LDP footprint > out of the LDPRs (per TimBL's request, but it also makes sense to me). Sort criteria only exist on LDPCs, yes. LDPCs are also LDPRs. So is it your contention then that, by omission, the representation of an LDPC where the server wishes to expose the sort criteria it used includes a ldp:Page (describing the sort criteria)? Thus, if a sorted LDPC is also paged, the GET response message conveying said representation ALSO has (in paging headers) Link: http://www.w3.org/ns/ldp/Resource; rel=type Link: <resourceURL>?page2; rel=next Link: <resourceURL>; rel=collection Best Regards, John Voice US 845-435-9470 BluePages Tivoli OSLC Lead - Show me the Scenario
Received on Monday, 30 September 2013 13:21:52 UTC