- From: elf Pavlik <perpetual-tripper@wwelves.org>
- Date: Wed, 11 Nov 2015 16:13:31 +0100
- To: Maik Riechert <m.riechert@reading.ac.uk>
- CC: Hydra <public-hydra@w3.org>
On 11/11/2015 03:13 PM, Maik Riechert wrote: > Hi all, Hi Maik > > 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? IMO using *describedby* Link in HTTP Header, as in LDP, makes a reasonable approach * http://www.w3.org/TR/ldp/#link-relation-describedby * http://www.w3.org/TR/ldp-primer/#creating-a-non-rdf-binary-resource-post-an-image-to-an-ldp-bc > > Cheers > Maik >
Received on Wednesday, 11 November 2015 15:13:41 UTC