W3C home > Mailing lists > Public > public-ws-addressing@w3.org > November 2004

RE: i034: computing default Action value for WSDL 2.0

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Wed, 17 Nov 2004 16:30:10 -0800
Message-ID: <7DA77BF2392448449D094BCEF67569A505AEE4D7@RED-MSG-30.redmond.corp.microsoft.com>
To: "Rich Salz" <rsalz@datapower.com>
Cc: <public-ws-addressing@w3.org>

WSDL 2.0 restricts target namespaces to be an absolute URI - not an
absolute URI _reference_ as Namespaces in XML does.  I'm trying to
remember if this was intentional or not, but the effect is that WSDL
target namespaces are a subset of XML namespaces and thus the issue of
"#" appearing in a target namespace doesn't come up.  Looks like the
same is true of WSDL 1.1.

Whether using # in a namespace is clever or not I'll pass on.  You can
probably tell that I'm a reformed fragment enthusiast.

> -----Original Message-----
> From: Rich Salz [mailto:rsalz@datapower.com]
> Sent: Wednesday, November 17, 2004 3:51 PM
> To: Jonathan Marsh
> Cc: public-ws-addressing@w3.org
> Subject: Re: i034: computing default Action value for WSDL 2.0
> 
> > [target namespace] is the {target namespace} of the interface. If
> > {target namespace} ends with a "/" an additional "/" is not added.
> 
> How about "If {tns} does not end with a / or #, add a /."  xml dsig
and
> xml-enc namespaces end with the fragment-start, which is kinda clever.
> 
> 	/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 Thursday, 18 November 2004 00:31:16 GMT

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