Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I wish I had better news for you...</p> <p>Unfortunately, the standard algorithms for XML Signatures (<a href="http://www.w3.org/TR/xmldsig-core/#sec-AlgID" rel="nofollow">http://www.w3.org/TR/xmldsig-core/#sec-AlgID</a>) operate on the canonicalized representation (<a href="http://www.w3.org/TR/2001/REC-xml-c14n-20010315" rel="nofollow">http://www.w3.org/TR/2001/REC-xml-c14n-20010315</a>) of the XML document, <em>not</em> its semantics. Namespace prefixes are, alas, considered part of the signed content of the document.</p> <p>(There are arguments for this involving the possible use of namespace prefixes inside strings with implicit binding from their context, as occurs in XSLT for example. That's actually a bad practice, but the XML Recommendations established it and it has become common... and when this is done, it is impossible to canonicalize reliably without knowing the complete semantics of the particular type of document.)</p> <p>So, despite the original intent that prefixes be nothing but "syntactic sugar" for namespace URIs, in practice changing them incautiously does risk breaking some tools, and in particular changing them will always change the XML Signature.</p> <p>This situation is an artifact of the rapid development of XML in incremental and somewhat unnatural order. Leaving XML Namespaces, the XML Schema, and the XML Infoset as afterthoughts did permit getting XML out to the users much more quickly and helped it gain acceptance... but also made retrofitting these more sophisticated semantics to the existing XML syntax more difficult, and has resulted in a certain amount of impedance mismatch and resulting pain as things don't fit as smoothly as they should. Someday there may be an XML 2.0 which starts with the infoset and derives the syntax and tooling from that, but until that day we're going to be stuck with a few cases where something obviously desirable is either much more work than necessary or simply not possible.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload