W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > July to September 2001

RE: Question: Base64 Transform Nodeset Input

From: John Boyer <JBoyer@PureEdge.com>
Date: Tue, 31 Jul 2001 10:17:14 -0700
Message-ID: <7874BFCCD289A645B5CE3935769F0B520C343B@tigger.PureEdge.com>
To: "Christian Geuer-Pollmann" <geuer-pollmann@nue.et-inf.uni-siegen.de>, <w3c-ietf-xmldsig@w3.org>

Hi Christian,

The inserted <comment> element (which is not an XML comment, but rather
an XML element like any other) would cause a problem for base-64
decoding.  The behavior to mimic is XPath string(), which  concatenates
all descendant text nodes.

John Boyer
Senior Product Architect, Software Development
Internet Commerce System (ICS) Team
PureEdge Solutions Inc. 
Trusted Digital Relationships
v: 250-708-8047  f: 250-708-8010
1-888-517-2675   http://www.PureEdge.com <http://www.pureedge.com/>  	

-----Original Message-----
From: Christian Geuer-Pollmann
Sent: Tuesday, July 31, 2001 5:55 AM
To: w3c-ietf-xmldsig@w3.org
Subject: Question: Base64 Transform Nodeset Input

What does section "6.6.2 Base64" mean whan it states:

"If an XPath node-set (or sufficiently functional alternative) is given
input, then it is converted to an octet stream by performing operations 
logically equivalent to 1) applying an XPath transform with expression 
self::text(), then 2) taking the string-value of the node-set."

Is the following fragment valid input which decodes to "The URI of the 
transform is http://www.w3.org/2000/09/xmldsig#base64"

VGhlIFVSSSBvZiB0aGUgdHJhbn<comment>Inserting this comment should not
anything for processing</comment>

Received on Tuesday, 31 July 2001 13:17:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:21:36 UTC