- From: Ashok Malhotra <ashok.malhotra@oracle.com>
- Date: Wed, 29 Oct 2014 11:06:50 -0400
- To: public-ldp-wg@w3.org
- Message-ID: <5451028A.8020601@oracle.com>
Yes, I would like something stronger than a hint. How about a bullet that says o Ability for a client to specify the size and content of pages. where content could mean items 11 to 20 or, if the items are ordered, keys 100 to 110, etc. On a different point, I was struck by the line "must provide paging-related hints" <https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpp-client-advertise> Clearly a hint is something that can be ignored. So why the "must"? All the best, Ashok On 10/29/2014 10:07 AM, John Arwe wrote: > Steve, IIRC Ashok was after something stronger than a "hint" ... hence 'specify'. > > At least in discussions, that was my sense ... and it tended to extend into use cases like "give me 11-20th &things from the container, sorted &thisway". Like what almost any UI wants to do. > > IIRC Sandro suggested that we could re-use the current response assertions about sorting as inputs to deal with the "sorted &thisway" piece, which made sense to me. > > Best Regards, John > > Voice US 845-435-9470 BluePages <http://w3.ibm.com/jct03019wt/bluepages/simpleSearch.wss?searchBy=Internet+address&location=All+locations&searchFor=johnarwe> > z/VM OpenStack Enablement and KVM >
Received on Wednesday, 29 October 2014 15:07:23 UTC