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

Satisfying WSDL-related charter requirements

From: Mark Nottingham <mark.nottingham@bea.com>
Date: Fri, 1 Apr 2005 15:16:10 -0800
Message-Id: <2447cc0a543d55afb4ee89bea1ea0982@bea.com>
To: public-ws-addressing@w3.org

To assure that we're on track for satisfying our charter when we go to 
LC on the WSDL document, and to stimulate discussion on the WSDL 
binding, since it's been a little while, I thought it would be good to 
revisit the requirements our charter places on it.

The deliverable itself is defined as:

> - A W3C  Recommendation for the Web Services Addressing WSDL 1.1 and 
> WSDL 2.0 Binding specification, defining the use of Web Services 
> Addressing components in WSDL 1.1 and WSDL 2.0 message exchange 
> patterns and providing the mechanisms for defining Web Services 
> Addressing property  values in WSDL 1.1 and WSDL 2.0 service 
> descriptions;

A cursory look shows only two explicit requirements;

>  B. The use of these abstract message properties in the context of all 
> WSDL 1.1 or WSDL 2.0 Message Exchange Patterns, including the 
> asynchronous use of these MEPs. In particular, the relationship 
> between message properties  and WSDL 1.1 and WSDL 2.0 service 
> descriptions will be provided if applicable.

which seems to refine the requirements implied by the definition above, 

> The deliverables for the SOAP 1.1 and WSDL 1.1 bindings must include 
> language that the bindings are defined for backward compatibility 
> only.

which I believe we've already covered.

Does anyone see other relevant requirements?

How do these requirements affect what we're looking for from our two 
main avenues of enquiry, the WSDL extension (i021) and the Async TF?


Mark Nottingham   Principal Technologist
Office of the CTO   BEA Systems
Received on Friday, 1 April 2005 23:22:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:09 UTC