On Wednesday, October 22, 2003, 2:42:51 PM, MURATA wrote: MM> Please follow RFC 3023 and provide the charset parameter. If your applications are tested with multiple charsets, and you can demonstrate that your applications interoperably: a) give the charset parameter precedence over what the XML declaration says b) correctly re-write the XML when saving to disk so that the encoding parameter in the XML declaration is altered to what the MIME charset parameter said (if they differ, thus ensuring that the XML remains well formed when read from disk) then please feel free to add the charset parameter. If, on the other hand, - you would rather avoid this extra level of implementation burden - you would like consistent behavior when reading from local disk as well as from the network, - you are uncomfortable about the possibility of having allegedly XML content on your server which is not well formed in the absence of HTTP headers - you want to simplify the deployability of this media type across Web servers from different vendors then I urge you to *not* add a charset parameter but instead, to add the sentence: "There is no charset parameter. Character handling has identical semantics to the case where the charset parameter of the "application/xml" media type is omitted, as described in [RFC3023]." -- Chris mailto:chris@w3.org