W3C home > Mailing lists > Public > public-lod@w3.org > February 2017

Re: Browsers breaking content negotiation

From: Young,Jeff (OR) <jyoung@oclc.org>
Date: Thu, 9 Feb 2017 20:20:41 +0000
To: Ruben Verborgh <Ruben.Verborgh@UGent.be>, Martynas Jusevičius <martynas@graphity.org>
CC: public-lod <public-lod@w3.org>, "public-rww@w3.org" <public-rww@w3.org>
Message-ID: <7B20DFF5-C82B-4B0A-B404-8F5617453088@oclc.org>
Here’s how I imagine splitting the hair using Schema.org:

ex:A0 a schema:ImageObject;
	schema:fileFormat “image/jpeg”, “image/png”;
	schema:contentUrl “http://some.com/img/19f87c54-bb97-4aa7-8163-166e3858f45e”.

That way conneg on the linked data URI (ex:A0) won’t cross wires with conneg on the image URI.


On 2/9/17, 3:04 PM, "Ruben Verborgh" <Ruben.Verborgh@UGent.be> wrote:

    > image content negotiation breaks with Accept: */*, and we
    > cannot control its default value in browsers.
    That's indeed what https://wiki.whatwg.org/wiki/Why_not_conneg means.
    Now the question is for what applications this poses a problem.
    https://bugzilla.mozilla.org/show_bug.cgi?id=1249474 is an example,
    but this is not a Semantic Web application.
    Your original mail seemed to indicate a possibility
    that it breaks Linked Data platforms, but I don't see that yet.

Received on Thursday, 9 February 2017 20:21:19 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 23 February 2017 16:49:10 UTC