W3C home > Mailing lists > Public > public-ldp-wg@w3.org > November 2013

Re: paging in editor's draft

From: John Arwe <johnarwe@us.ibm.com>
Date: Wed, 6 Nov 2013 11:59:16 -0500
To: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
Message-ID: <OF6FB82CAE.27C699F6-ON85257C1B.005CC1F8-85257C1B.005D5184@us.ibm.com>
> >LDP sorting only describes the relationship between (sub)sets (wrt the
> >entire collection) of members on *different* pages, it does not say
> >anything about the order of members on a single page (nor would saying
> >that really make much sense
> > when dealing with RDF).
> 
> not sure why that wouldn't make much sense. wouldn't it actually make a
> lot of sense, if i am building a UI that tried to list 100 entries, i 
can
> get sorted pages of 10, but then i have no idea how the 10 are sorted on
> each page? sequences are not such a great thing to express in RDF, but
> it's possible, and it seems to me that sorted pages may be a more useful

Erik, what I had in mind when I wrote the final parenthetical was someone 
believing that the order of "members" in the *serialization* of a single 
page carries significance.  That's what doesn't make much sense in the 
same breath as RDF (or Jena as the common implementation).  Certainly one 
can add it to the RDF content if the usage scenario warrants it.


Best Regards, John

Voice US 845-435-9470  BluePages
Tivoli OSLC Lead - Show me the Scenario
Received on Wednesday, 6 November 2013 16:59:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:17:46 UTC