Re: Hypermedia and media types

<snip>
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.
</snip>

unless otherwise instructed (by specs, local design specifics), i write my 
clients/consumers to default to MUST-IGNORE and my servers/providers to 
default to MUST-UNDERSTAND. 



mamund
+1.859.757.1449
skype: mca.amundsen
http://amundsen.com/blog/
http://twitter.com/mamund
https://github.com/mamund
http://linkedin.com/in/mamund

On Tue, Aug 18, 2015 at 1:27 PM, Ruben Verborgh <ruben.verborgh@ugent.be> 
wrote:

> 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
>