Re: [Specifications] Linking to multiple PartialCollectionView from Collection

I second Markus on discouraging `@list`. It may make sense to keep the structure as an ordered list but the underlying RDF model is awkward at best.

My question is, how are you intending to consume it? As JSON or RDF? If you expect a nice JSON structure, which wouldn't affect the RDF I could suggest `"@container": "@index".

``` json
{
  "@context": [ 
    "http://www.w3.org/ns/hydra/context.jsonld",
    { 
      "view": { "@id": "hydra:view", "@container": "@index" }
    }
  ],
  "view": {
      "1": {
        "@id": "http://api.example.com/an-issue/comments?page=1",
        "@type": "PartialCollectionView"
      },
      "2": {
        "@id": "http://api.example.com/an-issue/comments?page=2",
        "@type": "PartialCollectionView"
      },
      "3": {
        "@id": "http://api.example.com/an-issue/comments?page=3",
        "@type": "PartialCollectionView"
      }
  }
}
```

This way you don't change the RDF representation but give your client simpler navigation of the JSON structure.

-- 
GitHub Notification of comment by tpluscode
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/112#issuecomment-290213681 using your GitHub account

Received on Wednesday, 29 March 2017 20:21:16 UTC