Hydra metadata for non-RDF resources from Maik Riechert on 2015-11-11 (public-hydra@w3.org from November 2015)

From: Maik Riechert <m.riechert@reading.ac.uk>
Date: Wed, 11 Nov 2015 14:13:48 +0000
To: Hydra <public-hydra@w3.org>
Message-ID: <56434D1C.4060605@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

Received on Wednesday, 11 November 2015 14:14:17 UTC