Re: Hydra metadata for non-RDF resources

> IMO using *describedby* Link in HTTP Header, as in LDP, makes a
> reasonable approach
> * http://www.w3.org/TR/ldp/#link-relation-describedby

+1 on that

Another option is to negotiate for application/ld+json,
in response to which the server can send a 303 to an about resource.
It is important though that the thing and the description about the thing are different.

> or to send HTTP OPTIONS

I used to do that, but there are good arguments against it:
http://www.mnot.net/blog/2012/10/29/NO_OPTIONS

Best,

Ruben

Received on Wednesday, 11 November 2015 17:12:04 UTC