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

Re: What WSDL defines - the diagram!

From: David Booth <dbooth@w3.org>
Date: Wed, 05 Nov 2003 13:10:36 -0500
Message-Id: <>
To: Anne Thomas Manes <anne@manes.net>, Mark Baker <distobj@acm.org>,
Cc: www-ws-desc@w3.org, paul.downey@bt.com

Mark & Anne,

Certainly, a WSDL document does not *fully* define client or service 
behavior, but it does *partially* define their behavior.  That's what MEPs 
are all about.  When a WSDL document specifies a message exchange pattern, 
that pattern partially defines the behavior of the interacting parties -- 
not their internal behavior, but their externally observable behavior, 
i.e., what messages they send and receive and in what sequence.

The labels on the diagram were somewhat abbreviated, and omitted the word 
"partially".  A clearer diagram is at

At 01:34 PM 11/4/2003 -0500, Anne Thomas Manes wrote:

>WSDL explicitly does not define client or service behaviour. It describes 
>syntax of messages and protocols used to exchange those messages.
>At 10:41 AM 11/4/2003, Mark Baker wrote:
>>Cool, thanks for tackling that at the f2f.
>>But I disagree with the diagram.  As it was explained to me, a WSDL 2.0
>>document could be said to "describe the syntax" of client and service
>>("schema in, schema out"), rather than "define the behaviour", which
>>would require defining what in/out means in relation to any requested
>>semantics (aka the protocol).
>>WSDL 1.1 describes the protocol in that it suggests that a successful
>>response to a message means that the requested operation in the message
>>was successfully invoked.  WSDL 2.0 is ambiguous.
>>Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca

David Booth
W3C Fellow / Hewlett-Packard
Telephone: +1.617.253.1273
Received on Wednesday, 5 November 2003 13:11:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:06:36 UTC