W3C home > Mailing lists > Public > public-xmlsec@w3.org > March 2013

Proposed changes to XML Normalization 1.0

From: Jim Dovey <jdovey@kobo.com>
Date: Mon, 25 Mar 2013 16:17:28 +0000
To: "public-xmlsec@w3.org" <public-xmlsec@w3.org>
Message-ID: <C267696EE6755D4F8C95779465BB88C027F52F@koboexch1>
Editorial changes:
==============

§1.5.1 ¶1: "Canonicalization will be slow if the implementation uses the Canonical XML 1.1 specification as a formula…"
Change to "Normalization will be slow if the implementation uses the algorithm specified in [[XML-C14N11]] as the basis for its own implementation…"

§1.6 Test Cases for Canonical XML 2.0
Remove/replace (new test cases will be required if replaced).

§2.1.2 ¶7 (Note) "…since the canonicalization algorithm…"
Change to "…since the normalization algorithm…"

§2.2, ¶2 following IDL in §2.2.6, beginning "In the XML Canonicalization space…"
Replace last sentence:
"But in the current version of Canonical XML 2.0, Inclusive canonicalization has been removed completely."
with
"The XML Normalization algorithm removes the concept of Inclusive canonicalization completely."

§2.4.3 Step 3.2: "…during the canonicalization of…"
Replace with "…during the normalization of…"

§4.3.2 ¶1 "As per XML Canonicalization…"
Replace with "As per [[!XML-C14N11]]…" (normative reference— or is that inappropriate within an informative section?)



Editor-wants-it-to-look-purdy changes:
==============================

Rewrite pseudocode with nested <li> elements similar to Shadow DOM specification at <https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html#composition>


Algorithmic Changes:
=================

Should the algorithm emit pushed-down' namespaces in a different manner for event/stream parsers? For example, rather than emit them as attributes, should they only be reported through e.g. SAX2 beginNamespaceMapping and endNamespaceMapping at the point at which they become visibly utilized, and include no xmlns attributes? Perhaps both?

Also, we could do with describing a version of the algorithm for pull parsers e.g. StAX in detail I think.

_________________________________________
Jim Dovey
Digital Content Format Evangelist | Kobo Inc.
jdovey@kobo.com<mailto:jdovey@kobo.com>
C: (416) 716-0413
135 Liberty St. | Suite 101 | Toronto, ON  | M6K 1A7

[cid:image001.png@01CD8762.BDA95B70]




image001.png
(image/png attachment: image001.png)

Received on Monday, 25 March 2013 16:18:06 GMT

This archive was generated by hypermail 2.3.1 : Monday, 25 March 2013 16:18:07 GMT