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

RE: [i60] Splitting semantics of namespace across multiple WS-A specs inhibits independent versioning

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Sun, 29 May 2005 15:55:04 -0700
Message-ID: <7DA77BF2392448449D094BCEF67569A507B4A39D@RED-MSG-30.redmond.corp.microsoft.com>
To: "Sanjiva Weerawarana" <sanjiva@opensource.lk>, "Marc Hadley" <Marc.Hadley@Sun.COM>
Cc: <public-ws-addressing@w3.org>

No, it doesn't make sense.  The SOAP headers are defined in the wsa
namespace (from the Core).  To have such closely related features as the
SOAP fault codes associated with those headers defined in a different
namespace is sure to cause way more confusion than it's worth.

-1.  WS-A and WSDL are different in this regard.

I am however at a bit of a loss to propose very complete solutions that
don't involve merging documents.

> -----Original Message-----
> From: Sanjiva Weerawarana [mailto:sanjiva@opensource.lk]
> Sent: Sunday, May 29, 2005 8:48 AM
> To: Marc Hadley
> Cc: Jonathan Marsh; public-ws-addressing@w3.org
> Subject: Re: [i60] Splitting semantics of namespace across multiple
> WS-A specs inhibits independent versioning
> 
> On Fri, 2005-05-27 at 12:05 -0400, Marc Hadley wrote:
> > Would it make sense to split the namespace and have a separate one
> > for Core and SOAP then ? This seems like a simple way to alleviate
> > the problem.
> 
> +1.
> 
> This is what WSDL has always had and appears to have worked just fine.
> 
> Sanjiva.
> 
Received on Sunday, 29 May 2005 22:55:30 GMT

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