- From: John Boyer <jboyer@PureEdge.com>
- Date: Fri, 14 Apr 2000 09:41:28 -0700
- To: "TAMURA Kent" <kent@trl.ibm.co.jp>, "IETF/W3C XML-DSig WG" <w3c-ietf-xmldsig@w3.org>
Hi TAMURA-san,
The "two digit" meant put a leading 0 for values of 0F and less, but I
should've said 'upper case' for the letters.
Thanks,
John Boyer
Software Development Manager
PureEdge Solutions, Inc. (formerly UWI.Com)
Creating Binding E-Commerce
jboyer@PureEdge.com
-----Original Message-----
From: w3c-ietf-xmldsig-request@w3.org
[mailto:w3c-ietf-xmldsig-request@w3.org]On Behalf Of TAMURA Kent
Sent: Thursday, April 13, 2000 5:57 PM
To: IETF/W3C XML-DSig WG
Subject: Re: XPath transform tweak and Draft before FTF
In message "XPath transform tweak and Draft before FTF"
on 00/04/13, "John Boyer" <jboyer@PureEdge.com> writes:
> <li><b>Namespace and Attribute Nodes-</b> a space, the node's QName, an
equals sign,
> an open double quote, the modified string value, and a close double quote.
> The string value of the node is modified by replacing all ampersands
(&) with <code>&amp;</code>,
> all double quote characters with <code>&quot;</code>, and all
whitespace characters
> (#x9, #xA, #xD, and #x20) with two digit hexadecimal character references
except for #x20
> characters with no preceding #x20.</li>
>
> <li><b>Text Nodes-</b> the string value, except all ampersands are
replaced by <code>&amp;</code>,
> all open angle brackets (<) are replaced by <code>&lt;</code>, and
all #xD characters
> are replaced by <code>&#x0D;</code>.</li>
Clarify how to express hexadecimal character references, please.
- A-F must be capital letters or not.
- Preceding '0' is allowed or not.
--
TAMURA Kent @ Tokyo Research Laboratory, IBM
Received on Friday, 14 April 2000 12:32:54 UTC