W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > October to December 2000

Re: Call for Implementation: Canonical XML Becomes a W3C Candidate Recommendation

From: Joseph M. Reagle Jr. <reagle@w3.org>
Date: Tue, 31 Oct 2000 09:46:06 -0500
Message-Id: <4.3.2.7.2.20001031094043.00b9add0@rpcp.mit.edu>
To: TAMURA Kent <kent@trl.ibm.co.jp>, "Merlin Hughes" <merlin@baltimore.ie>, "Petteri Stenius" <Petteri.Stenius@done360.com>
Cc: w3c-ietf-xmldsig@w3.org

At 15:35 10/31/2000 +0900, TAMURA Kent wrote:
> > [1] http://www.w3.org/Signature/2000/10/10-c14n-interop
>
>Add IBM implementation, and fill "Y" for all items, please.

Done. A couple of questions, the first of which is mine, and the latter is 
something Boyer asked:

1. Is the requirement with respect to parsing and relative-URI-ns (reporting 
it as an error and not expanding) already implemented in the parser, or 
logic you had to add on for the time being?
2. <Boyer>One of the final editorial tweaks that Joseph asked me to make was 
to amend the beginning of section 2.1 to make it clear that document 
subsetting and node-set input meant the same thing.  When I say node-set 
input is recommended (as opposed to required), I'm saying that a conformant 
implementation should but is not required to do document subsetting as 
described in Section 2.4 and exemplified in Section 3.7. Since ... you have 
working code for example 3.7, I am just writing to ask whether this does 
indeed mean you created your implementation using XPath node-sets. </Boyer>




__
Joseph Reagle Jr.
W3C Policy Analyst                mailto:reagle@w3.org
IETF/W3C XML-Signature Co-Chair   http://www.w3.org/People/Reagle/
Received on Tuesday, 31 October 2000 09:48:24 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.29 : Thursday, 13 January 2005 12:10:11 GMT