- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Tue, 18 Aug 2015 19:27:36 +0200
- To: Dimitri van Hees <info@dimitrivanhees.com>
- Cc: "public-hydra@w3.org" <public-hydra@w3.org>
Hi Dimitri, > Problems arise when we also want to add hypermedia to the response. In my opinion, one of the hypermedia versions of my the JSON response is HAL, returned when application/hal+json is being requested. The hypermedia version of the JSON-LD response should be Hydra, but as far as I know Hydra doesn't have it's own media type because it's in fact just valid application/ld+json. However, JSON-LD is also in fact just valid application/json, yet still has it's own media type. Just like HAL by the way, which is also just valid application/json. I think what you are looking for is profiles: https://tools.ietf.org/html/rfc6906 They enable indicating the type of content beyond the content type. We could imagine using this for negotiation as well. At the same time, this is why I think self-descriptiveness is important: as a client, use what you understand and ignore what you do not. That applies only to LD, however. Best, Ruben
Received on Tuesday, 18 August 2015 17:28:10 UTC