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

Re: ldp-ISSUE-33 (pagination): how to structure functionality

From: Ashok Malhotra <ashok.malhotra@oracle.com>
Date: Mon, 12 Nov 2012 08:09:16 -0800
Message-ID: <50A11F2C.9080906@oracle.com>
To: public-ldp-wg@w3.org
FWIW, Odata has a different approach to pagination.

LDP suggests a separate URI for each page, for example .../#n

OData give you a pointer at the bottom of each page to the next page.
Not sure if there is a pointer to the previous page.  Need to check the spec.
All the best, Ashok

On 11/12/2012 7:36 AM, Wilde, Erik wrote:
> hello all.
>
> i agree with ISSUE-33 that pagination should be functionality that can be
> reused. maybe it's helpful to look at how it's done elsewhere:
>
> - rfc4287 is atom, the "container format". it defines what a container
> looks like, what entries look like, and thus mostly defines the data model
> of containers and entries.
>
> - rfc5023 is atompub. it defines the interactions for creating new entries
> i have recently described in longish emails.
>
> - rfc5005 is feed paging and describes link relations that can be used in
> *any resource* (that works within the framework of rfc5988) to expose
> links to first, next, previous, and last pages.
>
> this means it's perfectly fine to implement atompub without paging, but it
> probably would not be very helpful to do so.
>
> cheers,
>
> dret.
>
>
Received on Monday, 12 November 2012 16:09:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:42 UTC