Quantcast

Errata: “or by the Byte Order Mark” lackign in section 4.3.3.

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Errata: “or by the Byte Order Mark” lackign in section 4.3.3.

Leif Halvard Silli-4
In section 4.3.3. of XML 1.0 fifth edition[1], please add ”or by the
Byte Order Mark” in the following passage, as illustrated by the <INS>
element:

  ]]In the absence of information provided by an external transport
protocol (e.g. HTTP or MIME) <INS>or by the Byte Order Mark</INS>, it
is a fatal error for an entity including an encoding declaration to be
presented to the XML processor in an encoding other than that named in
the declaration,[[

The purpose of this error fix is
a) to take the consequence of the fact that the BOM is a method
   of setting the encoding that is *external* to the XML document
   production (it is a encoding signature and not part of the
   document production.)
b) that it makes sense to treat all external methods for setting
   the encoding the same way. That is: They should all be able to
   override the internal encoding without causing fatal error.
   Currently, it is only external *transport* protocols that have
   that privilege.
c) that Web browsers and a number of other parses already *do*
   ignore the XML encoding declaration whenever there is a BOM.
d) Given that the spec already says the BOM can override the
   XML encoding declaration *and* the new information that
   3023bis is going to say that the BOM takes precedence over
   the charset parameter of MIME/HTTP,[2] it would be odd if
   the feature (BOM) that have higher precedence than the
   charset parameter would not be have the same ”privilege”
   with regard to making parsers *ignore* the XML encoding
   declaration.

[1] http://www.w3.org/TR/REC-xml/#charencoding
[2]
http://lists.w3.org/Archives/Public/www-international/2013OctDec/0086.html
--
leif halvard silli
Loading...