Canonical XML

Canonical XML is a <a href="/facts/Canonical_form/K2jhB44k">normal form</a> of <a href="/facts/XML/clNgUfWk">XML</a>, intended to allow relatively simple comparison of pairs of XML documents for equivalence; for this purpose, the Canonical XML transformation removes non-meaningful differences between the documents. Any XML document can be converted to Canonical XML.
For example, XML permits whitespace to occur at various points within start-tags, and attributes to be specified in any order. Such differences are seldom if ever used to convey meaning, and so these forms are generally considered equivalent:

In converting an arbitrary XML document to Canonical XML, attributes are encoded in a normative order (alphabetical by name), and with normative spacing and quoting (though with all namespace declarations placed ahead of regular attributes, and namespaced attributes sorted by namespace rather than prefix or qualified name). Thus, the second form above would be converted to the first.
Canonical XML specifies a number of other details, some of which are:

<ul><li>the <a href="/facts/UTF-8/xlaVHSyf">UTF-8</a> encoding is used</li>
<li>line-ends are represented using the <a href="/facts/Newline/ffeJz4Nn">newline</a> character <a href="/facts/Hexadecimal/02ohQW22">0x</a>0A</li>
<li>whitespace in attribute values is normalized</li>
<li>entity references and non-special character references are expanded</li>
<li><a href="/facts/CDATA/2cndUSMH">CDATA</a> sections are replaced with their character content</li>
<li>empty elements are encoded as start/end pairs, not using the special empty-element syntax</li>
<li>default attributes are made explicit</li>
<li>superfluous namespace declarations are deleted</li></ul>
According to the <a href="/facts/W3C/lGWmhF6M">W3C</a>, if two <a href="/facts/XML/clNgUfWk">XML</a> documents have the same canonical form, then the two documents are logically equivalent within the given application context (except for limitations regarding a few unusual cases).
However, in a special context users might care about special semantics beyond the generic logical equivalence with which Canonical XML is associated. For example, a <a href="/facts/Steganography/RGLdKYcE">steganography</a> system could conceal information in an XML document by varying whitespace, attribute quoting and order, the use of hexadecimal vs. decimal numeric character references, and so on. Obviously converting such a file to Canonical XML would lose those specialized semantics. On the other hand, XML files that differ in their use of upper- vs. lower-case, or that use archaic versus modern spelling, and so on, might be considered equivalent for certain purposes. Such contexts are beyond the scope of Canonical XML.

Canonical XML open-in-new

Canonical XML