W3C home > Mailing lists > Public > public-hydra@w3.org > November 2015

Re: Hydra metadata for non-RDF resources

From: Maik Riechert <m.riechert@reading.ac.uk>
Date: Wed, 11 Nov 2015 17:21:04 +0000
To: Ruben Verborgh <ruben.verborgh@ugent.be>, elf Pavlik <perpetual-tripper@wwelves.org>
Cc: Hydra <public-hydra@w3.org>
Message-ID: <56437900.9070109@reading.ac.uk>

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

What if I had a complete RDF representation for the binary thing? Then 
both would live under the same URL via content negotiation, right? I 
feel that sometimes the boundaries blur a bit and it's not always clear 
what a different thing is and what isn't.

Received on Wednesday, 11 November 2015 17:21:35 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 November 2015 17:21:35 UTC