Re: Browsers breaking content negotiation

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.

Jeff

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.
    
    Best,
    
    Ruben

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