At 00:21 00/03/15 +0900, MURATA Makoto wrote:
>> - XML sent as application/xml (or equivalent):
>> - Charset parameter is strongly recommended, and if present,
>> it takes precedence.
>
>Charset parameter is *disallowed*.
I'm not sure it makes sense to disallow it, but discouraging
it might be fine.
You might think that we can avoid bad WWW servers by this change. But
we cannnot. We have to handle a collection of XML, XSL, CSS, VBScript,
JavaScript, etc. We need a solution that works for every format.
Otherwise, data will corrupt.
CSS is served as text/css. XSL is XML. VBScript and JavaScript may be
served as application/... If they don't have a 'charset' parameter,
and they don't have any internal way to indicate the encoding,
that's the problem of these registrations, not our problem.
Regards, Martin.
#-#-# Martin J. Du"rst, I18N Activity Lead, World Wide Web Consortium
#-#-# mailto:duerst(_at_)w3(_dot_)org http://www.w3.org/People/D%C3%BCrst