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