- From: Nathan Ridley <axefrog@gmail.com>
- Date: Tue, 17 Mar 2015 11:23:07 +1000
- To: public-linked-json@w3.org
- Message-ID: <CAMKTGkaJvETAVX1Sy=LfwHUy2rY10=ur=C2HBBtbuZqqYpROWA@mail.gmail.com>
Given that the idea of Hypermedia is to also include next steps that a user can take, ala "links", but also the fact that a resource probably only knows about linked data that directly relates to itself, what's the best way to represent a resource *and* linked metadata surrounding the request? For instance, perhaps the resource represents a user on my system, but I also need the user/client to know about general links to other areas of the website, e.g. the "about us" page, the login page, a Hydra entry point, and so forth. If I just return the JSON-LD document representing the requested user, and don't assume that the client has any pre-existing state (as per HATEOAS/REST constraints), then how should that metadata be bundled up in the response? Should I simply be returning a graph instead? Nathan -- *Google*: axefrog@gmail.com *Skype*: axefrog *Twitter*: @NathanRidley *Website*: http://axefrog.com / http://nathanridley.com *Phone: *+61 (0) 475 072789
Received on Tuesday, 17 March 2015 01:23:34 UTC