- From: Steve Speicher <sspeiche@gmail.com>
- Date: Mon, 25 Mar 2013 09:58:44 -0400
- To: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
My use case is something like this: Bug tracking tools often have thousands of bugs reported. Making a request on these is often filtered down based on the state or project/timeline associated with, but often ordered based on some defined ordering: last modified, highest priority, status, creator, etc. Since RDF is unordered and the response may be split across pages, there needs to be a way to indicate what the order is. Otherwise, the client will have to discover the intended order by other means and also if the response was split across pages responses, it would be preferred to have member resources on the current page based on ordering predicates that occur before those found on the next page. Note this is related to ISSUE-14 [1] and motivates its need. I will leave it to the editor's to tweak as needed, just wanted to get the use case out there. [1] - http://www.w3.org/2012/ldp/track/issues/14 Thanks, Steve Speicher IBM Rational Software OSLC - Lifecycle integration inspired by the web -> http://open-services.net
Received on Monday, 25 March 2013 13:59:15 UTC