RE: What does WSDL describe?

Paul:

> To me this is really a service design issue: If 'foo' simply 
> secures, rather than process the document, then i'd call it 
> 'submitOrder' and expect to have to call other foos before i 
> actually bought a motorbike.
> 
> I'd accept calling it messageExchange so long as continuing 
> to generate code from WSDL or WSDL from code isn't treated as heresy.

What is heresy is generating stub code like you would against CORBA IDL. I
like the idea of generating code that binds to messages (described in WSDL).
I rather less like the idea of "binding to a Web Service" which seems far
too tightly coupled.

Jim