W3C home > Mailing lists > Public > www-ws-desc@w3.org > November 2002

New Issue: Optionality of soap:headers at binding level

From: Prasad Yendluri <pyendluri@webmethods.com>
Date: Wed, 13 Nov 2002 18:27:31 -0800
Message-ID: <3DD30A13.6030802@webmethods.com>
To: www-ws-desc@w3.org
Folks,

I received an action from the recent WS-I meeting to communicate an 
issue identified by the BP team to this group (part of my liaison 
duties:) for potential resolution in WSDL 1.2.

In a nutshell the issue has to do with how can a WSDL mark some of the 
headers at the soap binding level to be optional. WSDL 1.1 specification 
is silent on this and it is not clear if it is an error if some of the 
headers defined in a WSDL document are missing from the SOAP message 
that is generated. WSDL 1.1 spec does not provide a way to mark 
soap:headers "optional".

Current spec for the soap:bind extensions stands as follows:

<soap:header message="qname" part="nmtoken" use="literal|encoded"
                            encodingStyle="uri-list"? namespace="uri"?>*


The WS-I BP team feels it would be desirable to provide a way (an AII?) 
to mark the soap:header elements optional or required. Alternatively all 
headers can be made mandatory unless marked optional via the newly 
defined attribute.

Thoughts?

Regards, Prasad
Received on Wednesday, 13 November 2002 21:24:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:22 GMT