> > Brendan has made the point that MNG needs to be in there; we also need
> > application/xml and application/xml+xhtml too.
>
> I think you mean application/xhtml+xml and probably text/xhtml+xml.
Yes :-) Those two, and also application/xml and text/xml.
RFC 2616 (HTTP) seems unclear on whether "*/xml" or "*/xhtml+xml" would be
a valid thing to send in an Accept header (to keep the size down.) Does
anyone have any idea whether this would work? Would it be sensible?
> > Eric, Philipp - who exactly do we have to ask or where to we have to post
> > to get W3C input on a suggested header? We need to bear in mind the
> > requirement to keep it short.
>
> The IETF is responsible for "registering" MIME headers (like
> Content-length) and HTTP headers (like Connection or Server). I
> beleive the authoritative list is the RFCs; all you need is grep (for
> no particular string). You may want to investigate HTTP Extensions [3]
> which provides a mechanism to uniquely identify headers that have not
> been "registered" in this fashion.
Sorry, I should have been more clear. I means "Who exactly do we ask to
get W3C input on a suggested _value_ for our Accept: header" (not a new
header as such.) But you seem to have sorted this out already :-)
> I think RFC 3023 provides the answer, which is that */*+xml, text/xml,
> application/xml (like text/xml except that the content provider
> requests that the data not be presented to the user as text),
> text/xml-external-parsed-entity (DTD subset), and
> application/xml-external-parsed-entity (DTD subset) all represent XML
> MIME entities. From RFC 3023 section 7:
>
> [*/*+xml] will allow applications that can process XML generically
> to detect that the MIME entity is supposed to be an XML document,
> verify this assumption by invoking some XML processor, and then
> process the XML document accordingly.
We need to note, though, that putting */*+xml in an Accept: header is
specifically disallowed by RFC 3023 in section 7 (because HTTP[RFC 2616]
does not allow it).
Therefore, we need to enumerate all specific "+xml" types we support in
the Accept: header.
Current candidate:
Accept: text/xml, application/xml, text/xhtml+xml, application/xhtml+xml,
text/html;q=0.9, image/png, image/mng, image/jpeg,
image/gif;q=0.9, text/plain;q=0.8, text/css, */*;q=0.01
(default q value is 1, so these have been removed to save space.)
The other question is:
Do we need to specify image/gif and text/plain at all? If q values are
relative, not absolute, these will be caught by "*/*;q=0.01" anyway.
However, if logic somewhere exists of the form "If q value > 0.5 then do
foo" then this might not work.
Gerv
