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

Re: Schema centric canonicalization - Need and status

From: Anders Rundgren <anders.rundgren@telia.com>
Date: Thu, 17 Nov 2005 10:18:24 +0100 (MET)
Message-ID: <1572415.1132219104866.JavaMail.tomcat@pne-ps3-sn2>
To: rsalz@datapower.com
Cc: w3c-ietf-xmldsig@w3.org

r$ (an abbreviation of "rich"?),

I took a deep thought about this and concluded that default values is 
a cute feature but its utility is questionable except for programmers 
(who anyway must know the *entire* input set they will be dealing 
with).

Original schema snippet:
<xs:attribute name="CanonicalizationAlgorithm" type="xs:anyURI" 
default="http://www.w3.org/2001/10/xml-exc-c14n#" use="optional"/>

Revised schema snippet:
<!--default: http://www.w3.org/2001/10/xml-exc-c14n# -->
<xs:attribute name="CanonicalizationAlgorithm" type="xs:anyURI" use="
optional"/>

I guess I saved a few hundred development hours there :-)

/a$

----Original Message----
From: rsalz@datapower.com
Date: Nov 16, 2005 5:35:46 PM
To: Anders Rundgren <anders.rundgren@telia.com>
Cc: "w3c-ietf-xmldsig@w3.org" <w3c-ietf-xmldsig@w3.org>
Subj: Re: Schema centric canonicalization - Need and status


> It is not binding to the schema that is the problem.  It is *using*
> the schema in the canonicalization process.  This is AFAIK currently
> not supported by XML DSig standards.

Sure, the stnadard supports it, by allowing anyone to define a 
transform,
and UDDI's schema-aware transformation is one such transform.

As for implementations that support it, well...  I'm not aware of any.
Of course there are some, but I've never run into any use of it.

	/r$

-- 
SOA Appliance Group
IBM Application Integration Middleware
* This address is going away; please use rsalz@us.ibm.com *
Received on Thursday, 17 November 2005 09:19:36 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 17 November 2005 09:19:36 GMT