Review of WS-A WSDL Binding

As per my action item, here are my comments on [1].

1. Section 2 introduces some elements, <wsaw:InterfaceName>, 
<wsaw:ServiceName> for refering to WSDL Interface, Service, and Endpoint 
components. The same result could be achieved by using the IRI-reference 
component designators defined in WSDL 2.0 Part 1, Appendix A.

2. Section 2 also defines the use of embedding WSDL in <wsa:Metadata> 
which indicates that people think it's useful to embed WSDL in other XML 
documents. This raises a question about WSDL 2.0. In <include>, <import>, 
and @wsdlLocation a location is specified. The spec says this location 
should dereference to a WSDL 2.0 document. Should it also be allowed to 
derefence to an element in an XML document, e.g. via a fragment id? This 
is the case for XML Schema.

3. Section 3.1 defines the <wsaw:UsingAddressing> Extension Element. I 
have a question about terminology. Our spec is inconsistent. Sometimes we 
say Extensibility element and sometimes Extension element. I suggest we 
use Extension element and attribute throughout, rather than Extensibility. 
 I think this is purely editorial. I'll make the change if no one objects.

4. The XML example 4-1 is wrong since it uses <definition> as the root 
element. It should use <description>

5. Section 4.3 defines the use of <wsa:ReferenceParameters> but does not 
say how this affects the WSDL 2.0 component model. Does this add a 
property to Endpoint?

[1] http://www.w3.org/TR/2006/WD-ws-addr-wsdl-20060216/

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca