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

On May 24, 2005, at 4:47 PM, Jonathan Marsh wrote:
> The split between Core and SOAP specs of the definition of a single  
> namespace also causes some unfortunate consequences.  Since the  
> mapping of spec to namespace isn’t 1-1, some questions are left  
> unanswered - is the namespace open, and each of these specs stakes  
> out a few terms inside it, leaving the possibility that other specs  
> to define additional terms?  Or is the namespace closed, and  
> versions or extensions need to be expressed through a different  
> namespace?  Having two specs implies it’s open (unless you tie  
> those two specs even further together by specifying cross- 
> dependencies).  But the wsaw:UsingAddressing extension makes a  
> strong implication that the namespace is closed, because it is  
> insufficient to indicate where the definition of new terms might be  
> found. Resolving this contradiction might have impact throughout  
> the spec family.  Merging the Core and SOAP Binding specs would  
> reduce the implication of openness, and be consistent with the WSDL  
> Binding.  Adding text to the Core and SOAP Binding stating the  
> namespace policy and making the cross-dependencies more explicit,  
> is also possible.
>
>

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.

Marc.

>
>
> From: public-ws-addressing-request@w3.org [mailto:public-ws- 
> addressing-request@w3.org] On Behalf Of Prasad Yendluri
> Sent: Friday, April 15, 2005 11:28 AM
> To: public-ws-addressing@w3.org
> Subject: NEW ISSUE: Splitting semantics of namespace across  
> multiple WS-A specs inhibits independent versioning
>
>
>
> Title:
> Splitting the semantics of a (e.g. WSAW) namespace across multiple  
> WS-A specs inhibits independent versioning of the specifications
>
> Description:
> The proposed resolution for issue i021 plans to use a marker  
> defined in the WSAW namespace introduced by one of the WS-A  
> specifications to flag the use of WS-Addressing in a WSDL  
> description.  The intent is to use the WSAW namespace to identify  
> the WS-Addressing specification and the version of it. However  
> given WS-A is now split into three separate specifications the  
> chosen namespace where this marker is defined needs to identify  
> this group of specifications and their "common" version, there by  
> inhibiting independent versioning of the specifications. Hence this  
> brings up a generic issue with splitting semantics of a namespace  
> across multiple specifications inhibiting the ability to versioning  
> those specifications independently.
>
> Target:
> Core, WSDL Binding and SOAP Binding
>
> Justification:
> Given the WS-Addressing comprises three coupled but independent  
> specification, it is highly desirable not to inhibit independent  
> versioning of the constituent specifications, as each specification  
> will need to change based on the issues and functionality changes  
> pertinent to that specification.
>
> Ref: Action item, http://www.w3.org/2005/04/11-ws-addr- 
> minutes.html#action03
>
>

---
Marc Hadley <marc.hadley at sun.com>
Business Alliances, CTO Office, Sun Microsystems.