Edit comment LC-2484 for XML Security Working Group

Quick access to LC-2484 LC-2486

Comment LC-2484

Comment Shortname:

Commenter: Pratik Datta <pratik.datta@oracle.com>

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeCanonical XML Version 2.0 /**/ /**********************... Canonical XML Version 2.0 W3C Working Draft 21 April 2011 Abstract Canonical XML Version 2.0 is canonicalization algo... Status of This Document This section describes the status o... Table of Contents 1. Introduction 1.1 Terminology 1.2 App... 1. Introduction 1.1 Terminology The key words "must", "mus... 1.1 Terminology The key words "must", "must not", "required... 1.2 Applications Since the XML 1.0 Recommendation [XML10] a... 1.3 Limitations Two XML documents may have differing inform... 1.4 Requirements for 2.0 Canonical XML 2.0 solves many of t... 1.4.1 Performance A major factor in performance issues note... 1.4.2 Streaming A streaming implementation is required to b... 1.4.3 Robustness Whitespace handling was a common cause of... 1.4.4 Portability It should be possible to canonicalize a s... 1.4.5 Simplicity C14N 1.x algorithms are complex and depend... 2. Canonical XML 2.0 2.1 Data Model The input to the canon... 2.1 Data Model The input to the canonicalization algorithm... 2.2 Parameters Instead of separate algorithms for each vari... 2.3 Processing Model The basic canonicalization process con... 2.4 The Need for Exclusive XML Canonicalization In some cas... 2.4.1 A Simple Example As a simple example of the type of p... 2.4.2 General Problems with re-Enveloping As a more complet... 2.5 Namespace Processing As part of the canonicalization pr... 2.5.1 Namespace concepts The following concepts are used in... 2.5.2 Namespace processing algorithm Step 1: At first deter... 2.5.3 Example of exclusive canonicalization with prefix rew... 2.5.3.1 With PrefixRewrite="none" <wsse:Security xmlns:ws... 2.5.3.2 With PrefixRewrite="sequential" <n0:Security xmlns... 2.6 Attribute processing Note: namespace declarations are n... 3. Use of Canonical XML 2.0 in XML Security 3.1 Use of Can... 3.1 Use of Canonical XML 2.0 in XML Signature 2.0 Canonical... 3.2 Use of Canonical XML 2.0 in XML Encryption 1.1 Canonica... 4. Pseudocode This section presents the entire canonicaliza... 4.1 canonicalize() Top level canonicalize function.... 4.2 canonicalizeSubtree() Canonicalize an individual subtre... 4.3 processNode() Redirect to appropriate node processing f... 4.4 processDocument() Process the Document Node.... 4.5 processElement() Process an Element Node. pr... 4.6 processText() Process an Text Node. processT... 4.7 processPI() Process an Processing Instruction (PI) Node... 4.8 processComment() Process an Comment Node. pr... 4.9 addNamespaces() Add namespaces from this element to the... 4.10 processNamespaces() Process the list of namespaces for... 4.11 addXMLAttributes() Combine/modify the 3 special xml at... 5. Output rules The document is encoded in UTF-8. Line bre... 6. Processing model for Streaming XML parsers Unlike DOM p... A. References Dated references below are to the latest know... A.1 Normative references [RFC2119] S. Bradner. Key words f... [RFC2119] [XML-NAMES] [XML10] [XMLDSIG-CORE2] A.2 Informative references [DOM-LEVEL-2-CORE] Arnaud Le Ho... [DOM-LEVEL-2-CORE] [URI] [XML-C14N] [XML-C14N11] [XML-EXC-C14N] [XML-PARSER-STAX] [XMLBASE] [XMLDSIG-XPATH-FILTER2] [XMLENC-CORE1]
or

Refinement of the section concerned:

Status:

open proposal pending resolved_yes resolved_no resolved_partial other assigned to Nobody

Type: substantive editorial typo question general comment undefined

Resolution status:

Response drafted Resolution implemented Reply sent to commenter

Response status:

No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):

Comment:

In C14N 2.0, the TrimTextNodes parameter removes leading and trailing whitespace, but we haven't precisely defined what whitespace is.



I propose that we define it the same that the XML spec defines it, which is space character, carriage return, line feed or tab.



Here is the excerpt from XML specification http://www.w3.org/TR/xml/#NT-S



----------------------------------------------------------------

S (white space) consists of one or more space (#x20) characters, carriage returns, line feeds, or tabs.



White Space

[3] S ::= (#x20 | #x9 | #xD | #xA)+



Note:



The presence of #xD in the above production is maintained purely for backward compatibility with the First Edition. As explained in 2.11 End-of-Line Handling, all #xD characters literally present in an XML document are either removed or replaced by #xA characters before any other processing is done. The only way to get a #xD character to match this production is to use a character reference in an entity value literal.

-----------------------------------------------------------



Pratik

Related issues: (space separated ids)

WG Notes: WG resolution to accept changes to close issue: http://lists.w3.org/Archives/Public/public-xmlsec/2011Jun/att-0010/minutes-2011-06-07.html#item03

Resolution: http://lists.w3.org/Archives/Public/public-xmlsec/2011Jun/0002.html In Section 2.3, added this line into "Text Nodes" - Whitespace consists of space (#x20) characters, carriage returns, line feeds, or tabs. reference to XML 1.0 also added to this text

(Please make sure the resolution is adapted for public consumption)