W3C home > Mailing lists > Public > public-ldp-wg@w3.org > October 2012

ldp-ISSUE-18 (container membership): container membership and robust pagination [Use Cases and Requirements]

From: LDP <sysbot+tracker@w3.org>
Date: Fri, 05 Oct 2012 13:53:18 +0000
Message-Id: <E1TK8L8-0005U9-3C@tibor.w3.org>
To: public-ldp-wg@w3.org
ldp-ISSUE-18 (container membership): container membership and robust pagination [Use Cases and Requirements]

http://www.w3.org/2012/ldp/track/issues/18

Raised by: Steve Battle
On product: Use Cases and Requirements

Issues relating to use-case UC-BPC1: List resources within a container

http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements#UC-BPC1:_List_resources_within_a_container

* Should there be a guaranteed way to get the full container membership without pagination. ie. Should GET on <containerURL> ''ever'' be redirected to the paginated <containerURL>?firstpage ?

* The current approach to paging is not robust to deletions and insertions of container members. Insertions/deletions will have the side effect of moving page boundaries. This could be detected by qualifying the request with 'If-match'. The ?firstPage still lists the full membership so this can be correlated with the results, however, a page boundary change makes it hard to recover resources that have 'fallen through the cracks.

* Should the number of resources per page be an explicit property of the container?

* Why do we have different query syntaxes for accessing the first and subsequent pages (e.g. why not p=1): <URI>?firstpage, <URI>?p=2, ... ?

* Is it best to use 'p' or something more descriptive like 'page'?
Received on Friday, 5 October 2012 13:53:19 UTC

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