W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > April to June 2002

Re: Y5 Exclusive C145n interop; was Re: c14n/exc-c14n interop samples

From: Aleksey Sanin <aleksey@aleksey.com>
Date: Tue, 04 Jun 2002 09:10:32 -0700
Message-ID: <3CFCE678.10001@aleksey.com>
To: merlin <merlin@baltimore.ie>
CC: w3c-ietf-xmldsig@w3.org


>No, the Specification I mention is the normative Specification
>of Exclusive XML Canonicalization:
>  http://www.w3.org/Signature/Drafts/xml-exc-c14n.html
>  Section 3, the first numbered list.
>  
>
Ops, sorry I missed it.

>This is the definition of exc-c14n. The Method that follows
>is "non-normative", which means that it is not the official
>definition. In case of an inconsistency between the normative
>Specification and the non-normative Method, the Specification
>takes precedence.
>
>If you consider the Method to be normative, then the following
>document:
>  <A xmlns="http://example.org/"><B xmlns=""/ ></A>
>Will be rendered by exc-c14n as:
>  <A xmlns="http://example.org/"><B></B></A>
>  
>
I am sorry but this document will be rendered correctly:

  <A xmlns="http://example.org/"><B xmlns=""/ ></A>

because when we are processing element <B> ns_rendered has default 
namespace
with a *different* value (href). By this xmlns="" will be rendered for 
element <B>

>Similarly, the Method does not handle namespace nodes in
>the InclusiveNamespaces.PrefixList correctly when some are
>omitted from the namespace axis, nor does it render such
>namespace nodes if their parent element is absent. 
>
It does! The only thing is that in this case namespace node is not added 
to ns_rendered list.

Aleksey
Received on Tuesday, 4 June 2002 12:11:41 GMT

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