My +1 to Anne's +1 comes with annotations to the original diagram :-)
(Apologies to Paul for the modifications to his diagram)
> -----Original Message-----
> From: Anne Thomas Manes [mailto:anne@manes.net]
> Sent: Tuesday, November 04, 2003 6:34 PM
> To: Mark Baker; paul.downey@bt.com
> Cc: www-ws-desc@w3.org
> Subject: Re: What WSDL defines - the diagram!
>
>
> +1.
>
> WSDL explicitly does not define client or service behaviour. It
describes
> syntax of messages and protocols used to exchange those messages.
>
> Anne
>
> 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.
> >--
> >Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca
>
