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

Action: Review of WSDL SOAP 1.1 binding LC WD, along with the SOAP binding in the Adjuncts.

From: Katy Warr <katy_warr@uk.ibm.com>
Date: Fri, 16 Sep 2005 11:01:49 +0100
To: public-ws-addressing@w3.org
Message-ID: <OF55171108.BE4B21E1-ON8025707D.0037AF31-8025707E.00371A19@uk.ibm.com>
Here are my comments for review of the WSDL soap 1.1 and adjuncts part 5 
wsdl spec for discussion on Monday's call. The majority of my comments 
refer to the WSDL SOAP Header block component section....but I did read 
the rest, honest ;o)
Sorry that this is late,
Katy

o Minor/typos

WSLD Adjuncts Section 5.3 (Default Binding rules)
Minor comment - comma required after the word 'transmitted' aids 
understanding of this sentence.
Payload Construction. When formulating the SOAP envelope to be transmitted 
the contents of the payload (i.e., the contents of the SOAP Body element 
information item of the SOAP envelope) MUST be what is defined by the 
corresponding Interface Message Reference component.
 
WSDL Adjuncts Section 5.10.3 SOAP Header Block component
"{element} REQUIRED. A xs:QName, a reference to an XML element declaration 
in the {element declarations} property of the Description component. This 
element represents a SOAP header block."
replace with?
"{element} REQUIRED. A xs:QName, a reference to an XML element declaration 
in the {element declarations} property of the Description component. This 
element representsTHE QNAME OF a SOAP header block."

WSDL Adjuncts Section 5.10.3 SOAP header block component
The following sentence switches between a SOAP Header Block representing 1 
header and representing multiple headers?
"A SOAP Header Block component describes an abstract piece of header data 
(message headers) that is associated with the exchange of messages between 
the communicating parties. The presence of a SOAP Header Block component 
in a WSDL description indicates that the service supports headers and MAY 
require a Web service consumer/client that interacts with the service to 
use the described header. Zero or more such headers may be used."

o Comment: How does wsoap:header indicate required = true/false?

WSDL Adjuncts Section: 5.10.3 SOAP Header Block component
Does the wsoap:header component require an additional attribute to 
indicate required=true/false?
In other words, there does not appear to be a way to indicate that the 
service 
(a) supports the header and the client may send it     (i.e. a bit like 
UsingWSAddressing required = false)
VS 
(b) supports headers and REQUIRES that the client use the described 
header?   (i.e. a bit like UsingWSAddressing required = true)
The mustUnderstand=true attribute part of <wsoap:header> indicates only 
whether the mustUnderstand attribute must be set on the header (and not 
whether it is mandatory for the client to send the header itself). 
The following text in section 5.3:
"SOAP Header Construction. If the {soap headers} property as defined in 
section 5.10 Declaring SOAP Header Blocks exists and is not empty in a 
Binding Message Reference or Binding Fault component, element information 
item conforming to the element declaration of a SOAP Header Block 
component's {element} property, in the {soap headers} property, MUST be 
turned into a SOAP header block for the corresponding message."
appears to indicate that the sending of the header element is mandatory. 
But, later (section 5.10.3):
"The presence of a SOAP Header Block component in a WSDL description 
indicates that the service supports headers and MAY require a Web service 
consumer/client that interacts with the service to use the described 
header. Zero or more such headers may be used."
appears to suggest that it's up to the client to decide whether or not the 
SOAP headers are sent.

o Comment : Use of wsoap:header Element Information Items

WSDL Adjuncts Section 5.10
What is the intent of the (non-'document') element information items in 
the wsoap:header? 
"Zero or more namespace-qualified element information items amongst its 
[children]. The [namespace name] of such element information items MUST 
NOT be "http://www.w3.org/2005/08/wsdl" and MUST NOT be 
"http://www.w3.org/2005/08/wsdl/soap"."
Section 5.3 (quoted in above comment)  decribed the use of element info 
items in the soap header block in the context of default binding rules. It 
implies that they describe the type of the soap header like this example 
(???).
<wsoap:header element=wsa:replyTo>
      wsa:EndpointReference
</wsa:action>
In summary - the actual description of the element information item 
(5.10.4) is vague - could it be expanded?:

o WS-Addressing WSDL spec ?

wsaw:UsingAddressing appears to be simply a shorthand for wsoap:headers. 
Would it be worth us adding the semantic equivalent to 
wsaw:UsingAddressing in terms of WSDL 2.0 SOAP header blocks as part of 
the WS-A WSDL specification? 
Received on Friday, 16 September 2005 10:02:21 GMT

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