Re: Pagination (ISSUE-42)

Sure. I'm no expert, though - beware.

GET /alice

{
  "@id": "http://example.com/alice#person",
  "collection": [
    {
      "@id": "/alice/friends",
      "@type": "Collection",
      "manages": {
         "subject": "http://example.com/alice#person",
        "predicate": "foaf:knows"
      }
      "search" : ... an iritemplate,
      "operation" : ... supportedOperations on /alice/friends
    }
  ]
}

GET /alice/friends
Link:

[
  {
    "@id": "http://example.com/bob#person",
    "@reverse": {
      "foaf:knows": "http://example.com/alice#person"
    }
  },
  {
    "@id": "http://example.com/linda#person",
    "@reverse": {
      "foaf:knows": "http://example.com/alice#person"
    }
  }
]

Point is to keep your description-based approach while also not having to
deal with foaf:knows pointing to a document rather than a person. Next step
in my tinkering is trying to give a URI to the collection's description.






--

Jacopo Scazzosi
Developer
http://www.jacoscaz.com

On Mon, Feb 23, 2015 at 4:26 PM, Dietrich Schulten <ds@escalon.de> wrote:

> Hi,
>
> Am 23.02.2015 um 11:40 schrieb Jacopo Scazzosi:
>
> > what about going back to the hydra:manages block and @reverse foaf:knows
> > but using them in the descriptor and each item of the array
> > respectively? It might make for a nice compromise.
> >
>
> Could you please write up a short example? It would help me understand
> what you mean. My imaginative power for json-ld is quite limited :)
>
> Best regards,
> Dietrich
>
>
>