Re: Browsers breaking content negotiation

> Even only
> considering image media types, such browser behavior breaks
> applications.

What applications exactly break?

If you are talking about "Web applications", they don't break,
because you can still customize the accept header.

> If for example both image/svg and image/png are supported, and maybe
> SVG is preferred, the server cannot make an informed choice based on
> Accept: */* only.

Representation-specific URLs are possible.

<https://example.org/images/abc> ex:hasRepresentation <https://example.org/images/abc.jpg>.
<https://example.org/images/abc> ex:hasRepresentation <https://example.org/images/abc.svg>.
<https://example.org/images/abc.jpg> dct:format "image/jpeg".
<https://example.org/images/abc.svg> dct:format "image/svg+xml".

Best,

Ruben

Received on Thursday, 9 February 2017 19:41:01 UTC