W3C home > Mailing lists > Public > www-validator@w3.org > December 2008

Re: HTML Validator HTTP Accept

From: Sierk Bornemann <sierkb@gmx.de>
Date: Tue, 16 Dec 2008 18:26:44 +0100
Cc: www-validator Community <www-validator@w3.org>
Message-Id: <B5809D58-E70A-4830-A8DD-448DD08EED4C@gmx.de>
To: olivier Thereaux <ot@w3.org>

Hi Olivier!

Am 16.12.2008 um 13:46 schrieb olivier Thereaux:
> Still, let's try and get out of that arguing loop and into problem  
> solving. Sierk, since you've been for the longest time the proponent  
> of adding an Accept: header, can you take charge of finding, if not  
> a perfect candidate, at  least a very, very good candidate?
>
> The candidate accept header should:
> * have text/html and application/xhtml+xml as q=1
> * list accept for all other types supported by the validator (SVG,  
> MATHML, SMIL, MusicXML, plain XML, etc)
> * list accept for all types supported by the other validators  (CSS,  
> Feed, RDF)
> * finish with an *, with a low q factor
> * perhaps also add a few obvious "not supported" with q=0, such as  
> raster images?
>
> If you accept (pun not intended), please reopen http://www.w3.org/Bugs/Public/show_bug.cgi?id=18 
>  and reassign it to you.


I will try, but I have little hope, that it is or should be me of all  
people to do the magic golden section...
Digging into it, I have found http://www.grauw.nl/blog/entry/470 and https://bugzilla.mozilla.org/show_bug.cgi?id=433859 
  with references to
http://lists.w3.org/Archives/Public/public-webapi/2008May/0228.html
http://lists.w3.org/Archives/Public/public-webapi/2008May/0229.html

and the ongoing discussion about that topic there.

Especially the notes on

http://www.w3.org/TR/XMLHttpRequest/#send
http://dev.w3.org/cvsweb/~checkout~/2006/webapi/XMLHttpRequest/ 
Overview.html?rev=1.203&content-type=text/html; 
%20charset=iso-8859-1&only_with_tag=HEAD#setrequestheader
http://dev.w3.org/cvsweb/~checkout~/2006/webapi/XMLHttpRequest-2/ 
Overview.html?rev=1.46&content-type=text/html; 
%20charset=iso-8859-1&only_with_tag=HEAD#setrequestheader

which now clearly state:
"If the user agent implements server-driven content-negotiation it  
should set Accept-Encoding and Accept-Charset headers as appropriate;  
it must not automatically set the Accept. If the Accept-Language  
header is not set using setRequestHeader() user agents should provide  
it. Responses to such requests must have the content-encodings  
automatically decoded. [RFC2616"

Maybe it is useful to use the Accept headers Firefox and Safari  
provide so far (with a slight preference to the way Safari does handle  
it, like Anne v.K. describes it on http://lists.w3.org/Archives/Public/public-webapi/2008May/0355.html) 
.

Currently these browsers do provide the following Accept headers:

Firefox 3.0.4:  text/html,application/xhtml+xml,application/ 
xml;q=0.9,*/*;q=0.8
Safari 3.2.1:  text/xml,application/xml,application/xhtml+xml,text/ 
html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Opera 9.6.3:  text/html, application/xml;q=0.9, application/xhtml+xml,  
image/png, image/jpeg, image/gif, image/x-xbitmap, */*;q=0.1


Maybe this helps a little bit for a beginning, maybe not. I will dive  
into it deeper. I don't know, if I am successful in a manner we could  
be confident of.


Sierk

-- 
Sierk Bornemann
email:            sierkb@gmx.de
WWW:              http://sierkbornemann.de/
Received on Tuesday, 16 December 2008 17:27:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:14:33 GMT