- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Tue, 3 Feb 2015 11:03:52 +0100
- To: Tomasz Pluskiewicz <tomasz@t-code.pl>
- Cc: Markus Lanthaler <markus.lanthaler@gmx.net>, public-hydra@w3.org
> Oh wait, I see it actually addresses my point from the earlier email. Do I understand correctly that the pagination property would belong both to a Page and Collection?
>
> {
> "@id": "/comments?page=3",
> "@type": "Page",
> "pageOf": "/comments",
> "pagination": {
> "firstPage": "/comments/page=1",
> "lastPage": "/comments/page=10"
> }
> }
>
> {
> "@id": "/comments",
> "@type": "Collection",
> "pagination": {
> "firstPage": "/comments/page=1",
> "lastPage": "/comments/page=10"
> }
> }
>
> This way handling of pages and monolithic collections is uniform but the semantics aren't mixed.
I would prefer to only have the second kind;
even though the first is convenient, it's not in line with the logical model.
Collections are paged; paged are not.
Ruben
Received on Tuesday, 3 February 2015 10:04:27 UTC