W3C home > Mailing lists > Public > www-xml-xinclude-comments@w3.org > December 2004

Re: The encoding attr should trigger Accept-Charset

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Mon, 13 Dec 2004 16:04:22 +0100
To: Elliotte Rusty Harold <elharo@metalab.unc.edu>
Cc: www-xml-xinclude-comments@w3.org
Message-ID: <41c1aaad.32515906@smtp.bjoern.hoehrmann.de>

* Elliotte Rusty Harold wrote:
>>   In order to minimize encoding errors for parse="text" processing,
>>please change the definition of the encoding attribute to include a
>>requirement that if the attribute has a legal value and the encoding is
>>supported and the protocol supports such action, that the server is
>>informed of the encoding attribute value, e.g. for encoding="iso-8859-2"
>>and a HTTP request, that the request includes
>>
>>   Accept-Charset: iso-8859-2
>>
>>such that the server has a chance to provide a proper representation.
>
>This seems like a good idea for implementers. I'm considering adding 
>it to my implementations. However, I'm not sure this really needs to 
>be a requirement of the specification. For instance, some people 
>might be implementing XInclude in an environment where it's difficult 
>or impossible to set a specific HTTP header.

The requirement should have the same requirement level as processing of
the accept and accept-language attributes. The document currently ack-
nowledges that there may exist valid reasons in particular circumstances
to ignore the item; I did not mean to suggest that adding Accept-Charset
was more important than the other headers.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Monday, 13 December 2004 15:04:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:58:57 UTC