Re: Pagination (ISSUE-42)

• From: Thomas Hoppe <thomas.hoppe@n-fuse.de>
• Date: Tue, 03 Feb 2015 06:36:17 +0100
• To: public-hydra@w3.org
• Message-ID: <54D05E51.2000700@n-fuse.de>

Hi Markus,

On 02/02/2015 11:48 PM, Markus Lanthaler wrote:
>
> Another design I have been tinkering with was to rename PagedCollection to
> something like PartialCollection and *perhaps* move the pagination controls
> into a separate resource or blank node:
>
>    {
>      "@id": "http://api.example.com/an-issue/comments?page=3",
>      "@type": "PartialCollection",
>      "pagination": {
>        "firstPage": "/an-issue/comments",
>        "previousPage": "/an-issue/comments?page=2",
>        "nextPage": "/an-issue/comments?page=4",
>        "lastPage": "/an-issue/comments?page=498"
>      },
>      "member": [ ...]
>    }
>
>
>

Correkt me if I'm wrong, the `PartialCollection`  type should address 
the problem Ruben discovered
by having exactly the semantics of a single page.
What I don't get is the benefit of introducing a bnode for the
pagination controls. Can you please explain that?

Thanks

Received on Tuesday, 3 February 2015 05:36:46 UTC