- From: Markus Lanthaler via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Mar 2017 18:47:44 +0000
- To: public-hydra-logs@w3.org
A list may be an option but would likely break clients that don't expect it. What would definitely work though is to express it explicitly as a linked list. Something like
```
"view": [
{
"@id": "http://api.example.com/an-issue/comments?page=1",
"@type": "PartialCollectionView",
"first": "/an-issue/comments?page=1",
"next": "/an-issue/comments?page=2",
"last": "/an-issue/comments?page=4"
},
{
"@id": "http://api.example.com/an-issue/comments?page=2",
"@type": "PartialCollectionView",
"previous": "/an-issue/comments?page=1",
"next": "/an-issue/comments?page=3",
},
{
"@id": "http://api.example.com/an-issue/comments?page=3",
"@type": "PartialCollectionView",
"previous": "/an-issue/comments?page=2",
"next": "/an-issue/comments?page=4",
},
{
"@id": "http://api.example.com/an-issue/comments?page=4",
"@type": "PartialCollectionView",
"previous": "/an-issue/comments?page=3"
}
]
```
Whether you include first/last in all views or just one shouldn't matter too much.
An alternative we discussed on the mailing list if I remember correctly would be to describe these relationships with an `IriTemplate`.
--
GitHub Notification of comment by lanthaler
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/112#issuecomment-290187885 using your GitHub account
Received on Wednesday, 29 March 2017 18:47:50 UTC