W3C home > Mailing lists > Public > public-ws-addressing@w3.org > January 2005

RE: Action related to i043

From: Martin Gudgin <mgudgin@microsoft.com>
Date: Mon, 31 Jan 2005 12:39:16 -0800
Message-ID: <DD35CC66F54D8248B6E04232892B633804A02DCB@RED-MSG-43.redmond.corp.microsoft.com>
To: "Rich Salz" <rsalz@datapower.com>
Cc: <public-ws-addressing@w3.org>

Err, 1 and 2 won't match because the string value "bar:x1" doesn't match
"baz:x1", surely? I can't see how EXCC14N would give the same octet
stream for 1 and 2. Surely 1 and 3 WILL match because the bar nsdecl
will be discarded as not visibly utilized...

I'm confused.

Gudge

> -----Original Message-----
> From: Rich Salz [mailto:rsalz@datapower.com] 
> Sent: 31 January 2005 20:35
> To: Martin Gudgin
> Cc: public-ws-addressing@w3.org
> Subject: Re: Action related to i043
> 
> > 	Comparison of Reference Parameters should be performed using
> > EXCC14N. However, EPR issuers and comparators need to be aware that
> > EXCC14N might yield false positives in cases where 
> reference parameters
> 
> 	Replace "false positives" with "errors", I think, since 
> the three 
> following fragments will/wont' compare correctly:
> (1)	<foo xmlns:bar="x1">bar:x1</foo>
> (2)	<foo xmlns:baz="x1">baz:x1</foo>
> (3)	<foo xmlns:bar="x2">bar:x1</foo>
> 
> That is, 1 and 2 will match, but shouldn't, and 1 and 3 won't 
> match but 
> should.
> 
> 	/r$
> 
> 
> -- 
> Rich Salz, Chief Security Architect
> DataPower Technology                           
> http://www.datapower.com
> XS40 XML Security Gateway   
> http://www.datapower.com/products/xs40.html
> XML Security Overview  
> http://www.datapower.com/xmldev/xmlsecurity.html
> 
Received on Monday, 31 January 2005 20:39:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:01 GMT