- From: Ruben Verborgh <Ruben.Verborgh@UGent.be>
- Date: Thu, 9 Feb 2017 19:40:25 +0000
- To: Martynas Jusevičius <martynas@graphity.org>
- CC: public-lod <public-lod@w3.org>, "public-rww@w3.org" <public-rww@w3.org>
> 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:40:59 UTC