Re: Hydra metadata for non-RDF resources

Hi, 

What exactly do you mean by hydra metadata for a collection resource which is also represented as a vnd mime type? Are you maybe looking for http://www.hydra-cg.com/spec/latest/core/#discovering-a-hydra-powered-web-api? 

Best regards, 
Dietrich 

Am 11.11.2015 15:15 schrieb Maik Riechert <m.riechert@reading.ac.uk>:

Hi all,

I was wondering, can I make Hydra metadata available for non-RDF 
resources? As an example, I'm thinking of some non-RDF binary collection 
format which would have a mime type of "application/vnd.whatever". Does 
it make sense to make Hydra metadata available via content negotiation 
under the "application/ld+json" mime type? Or does the metadata only 
"count" for the same representation that it is returned for? I guess an 
analogy would be if you have a resource which delivers HTML but then you 
like to include hydra metadata. Of course, you can include that directly 
inside the HTML with an inline json-ld block (as schema.org does), but 
would it be also right to again do that via content negotiation?

Cheers
Maik