- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Fri, 18 Apr 2014 08:39:21 +0200
- To: Markus Lanthaler <markus.lanthaler@gmx.net>
- Cc: Gregg Kellogg <gregg@greggkellogg.net>, public-hydra@w3.org
Hi Markus,
> The reason why it is called PagedCollection and not CollectionPage is that I
> see a PagedCollection as the sum of all the pages it consists of.
That would be cool indeed, but this is contradicted by the example:
{
"@context": "http://www.w3.org/ns/hydra/context.jsonld",
"@id": "http://api.example.com/an-issue/comments?page=3",
"@type": "PagedCollection",
"totalItems": "4980",
"itemsPerPage": "10",
"firstPage": "/an-issue/comments?page=1",
"nextPage": "/an-issue/comments?page=4",
"previousPage": "/an-issue/comments?page=2",
"lastPage": "/an-issue/comments?page=498",
"member": [
... the members of this PagedCollection ...
]
}
Note how "?page=3" is called a PagedCollection (but is a single page)
or how "?page=4" is the "next page" of the PagedCollection (only pages have a next page).
or how "?page=1" is the "firstPage" of "?page=3".
> Well... this certainly looks tidy but do you really need an "entry point"
> which just links to the first and last page but doesn't give you any
> members?
No, not an entry point, but it should be possible to refer to the collection as a whole.
So think identifier (URI), not URL per se.
>> In other words, the representations of
>> - http://data.linkeddatafragments.org/dbpedia
>> and
>> - http://data.linkeddatafragments.org/dbpedia?page=1
>> would be the same, even though the first identifies the entire dataset
>> and the second only identifies the first page.
>
> That's how a PagedCollection is supposed to be used in general.
Yes, but in my example, they are separate entities (see remark above this one).
Cheers,
Ruben
Received on Friday, 18 April 2014 06:39:59 UTC