Re: Browsers breaking content negotiation

I agree with Ruben.

Representation specific IRIs are a requirement for a linked data/semweb server.
1 IRI for a concept can content negotiate to multiple representations
that have their own IRI.
Server side it makes sense to prefer sending the most logical
representation of a concept if the client has no preference.
Which for images is the highest quality image format, not their metadata.

So practically for me I actually prefer if browsers send accept: */*
it is better than what they did before e.g. chrome used to prefer xml
over html.
e.g. for http://purl.uniprot.org
if the client has no preference we send HTML.
else if the client wants RDF/XML we send that.
else we send HTML because that's what we got ;)

Regards,
Jerven





On Thu, Feb 9, 2017 at 9: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
>



-- 
Jerven Bolleman
me@jerven.eu

Received on Thursday, 9 February 2017 20:33:30 UTC