Re: Browsers breaking content negotiation

OK, I omitted an implementation detail that Linked Data is always
supported for all URIs that have a description, and dct:format adds
support for some extra media types.

So a more explicit (but not practical) example would be something like:

  <http://some.com/img/19f87c54-bb97-4aa7-8163-166e3858f45e>
dct:format "image/jpeg", "application/xhtml+xml",
"application/rdf+xml", "application/n-quads", "text/rdf+n3",
"application/n-triples", "application/ld+json", "application/rdf+xml",
"application/rdf+thrift", "text/turtle", "text/trig" .

Do your arguments still hold?


On Thu, Feb 9, 2017 at 8:07 PM, Ruben Verborgh <Ruben.Verborgh@ugent.be> wrote:
>> why are you inferring the format from the URI?
>
> I didn't, I inferred it from the triple.
>
>>  <http://some.com/img/19f87c54-bb97-4aa7-8163-166e3858f45e>
>> dct:format "image/jpeg" .
>>
>> It identifies a resource which may have multiple representations:
>> JPEG, RDF, HTML etc.
>
> It does not, because of dct:format "image/jpeg"
>
> Ruben

Received on Thursday, 9 February 2017 19:15:43 UTC