- From: Steve Speicher <sspeiche@gmail.com>
- Date: Wed, 29 Oct 2014 10:16:14 -0400
- To: John Arwe <johnarwe@us.ibm.com>
- Cc: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
- Message-ID: <CAOUJ7JpuF2aw6gB20PRMiDJuQtvRN_SAU3jyLP63BZoY=qLrig@mail.gmail.com>
John, Yes, I know what Ashok is asking for and is in our wish list. I'm not denying there are other needs around client-directed paging, filter and inlining. The point being, the bullet I reference in the proposed charter is already covered in the paging spec as it is written. I don't think we'd agree that paging can already answer this question: "How can a client specify the size of a page when paging?" If there are additional needs or a stronger requirement that the server MUST supply the exact size, etc. then those questions should be added. As written, we already cover it. I'm not sure what Arnaud (or who ever added this) was thinking was missing from current paging spec as to why this question can't be answered. - Steve Speicher On Wed, Oct 29, 2014 at 10:07 AM, John Arwe <johnarwe@us.ibm.com> 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 14:16:41 UTC