W3C home > Mailing lists > Public > public-xmlsec@w3.org > June 2010

RE: C14N2.0: ugly little details

From: Pratik Datta <pratik.datta@oracle.com>
Date: Tue, 29 Jun 2010 09:32:30 -0700 (PDT)
Message-ID: <2b293106-0d51-41de-a4dc-f5515586ab97@default>
To: Scott Cantor <cantor.2@osu.edu>, Meiko Jensen <Meiko.Jensen@ruhr-uni-bochum.de>, XMLSec WG Public List <public-xmlsec@w3.org>
Yes that is right, the current proposal prevents selecting text nodes.

See Section 2.1 of C14N 2.0
http://www.w3.org/TR/xml-c14n2/#sec-Data-Model

It says:

* Some examples of subsets that were were permitted in the Canonical XML 1.x mode but not in this new model: 
  - A subset consisting of a single attribute all by itself. 
  - A subset consisting of an attribute without its owner element. 
  - A subset consisting of a text node all by itself. 
  - A subset consisting of a text node without its parent node. 
  - A subset consisting of an element without some of its text node children.



So it is not possible to have give two text nodes as input to C14N 2.0. You would have to give the text node along with the parent element, I.e. <A>1  </A> and <B>  2</B>


Pratik

-----Original Message-----
From: Scott Cantor [mailto:cantor.2@osu.edu] 
Sent: Tuesday, June 29, 2010 7:06 AM
To: Meiko Jensen; XMLSec WG Public List
Subject: RE: C14N2.0: ugly little details

> Note the whitespace behind 1 and before 2. DSIG2-Selection includes the
> XPaths /X/A/text() and /X/B/text(), hence the C14N2.0 gets an input made
> up by two text nodes: "1 " and " 2".

I had thought that the current proposal precluded selecting only text nodes.
This is perhaps yet another reason to preclude that.

-- Scott
Received on Tuesday, 29 June 2010 16:33:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 29 June 2010 16:33:56 GMT