Re: Paging

Hi, Elli.

It doesn't look like anybody has responded to you yet, so, I will at least
acknowledge that we've got the message. We still have a heavy focus on a
handful of other issues right now, but the group will be visiting your
feedback soon; I'll make sure of it.

Your active participation is much appreciated.

- Cody



On Thursday, June 6, 2013, Elli Schwarz wrote:

> LDP Working Group:
>
> In section 5.1.3 Paging, and specifically in 5.3.6.3, you describe that
> for the last page of a container (or resource after adoption of ISSUE-33)
> should contain a value of rdf:nil for the ldp:nextPage attribute. By the
> way, thank you for allowing paging for LDPRs as well!
>
> In my scenario, I have a set of SPARQL CONSTRUCT queries that I use to
> create the RDF data when the user does a GET on an LDPC or LDPR URL. (I use
> URL path parameters as parameters in my SPARQL query to get specific
> results.) Due to my use of SPARQL CONSTRUCT, I have no way of knowing
> whether I'm serving the last page or not. I use LIMIT and OFFSET with ORDER
> BY in my SPARQL query to get back a certain number of query solution sets
> per page, but there's no way to know if the next offset will produce more
> data. Because of this, there's no way for me to know the last page.
>
> Since my system directly returns the SPARQL CONSTRUCT results, I would
> prefer that I wouldn't have the server perform other queries to determine
> if there's more data, nor would I want to cache a somewhat larger result
> set so I can see if there's more data. I understand that LDP isn't
> tied directly to using SPARQL, so the fact that I can't get this info
> from SPARQL isn't a problem for LDP per se. However, I would suspect that
> my case is a typical use case. I don't think people are storing ldp:
> predicates directly in their data, so one way to add it is to use SPARQL
> CONSTRUCT queries to return their data in a format conforming to the LDP
> spec. Is there something else we can do instead of requiring rdf:nil as a
> pointer to the last page?
>
> Thank you,
> Elli Schwarz
>


-- 
Cody Burleson
Enterprise Web Architect, Base22
Mobile: +1 (214) 702-6338
Skype: codyburleson
Email: cody@base22.com
Blog: codyburleson.com

* <http://base22.com>*
*
*
*Check my free/busy
time.<http://www.google.com/calendar/embed?src=cody.burleson%40base22.com&ctz=America/Chicago%20>
*