Re: What does WSDL describe?

An example would be nice, but I have an observation to make that might
be useful.

On Wed, Oct 29, 2003 at 09:04:33PM +0600, Sanjiva Weerawarana wrote:
> > Consider the data "12345", suitably SOAP-ized.  If that is sent
> > to a service, and we get a successful response back, what are the
> > possible interpretations of that success?
> 
> I think we can stop right here - the possible interpretations are
> out of scope for WSDL. Some may want to interpret it as "processed"
> while others may want to interpret it as "success." Not WSDL's role
> to pick one of those interpretations as "it."

Well, WSDL 1.1 picked an interpretation, as did IDL and MIDL and
every other description language I know of.

> WSDL is pretty damn lame really - it just says a document conforming
> to this schema goes in and another conforming to that schema comes
> out. That's it. *Really* lame. :-(.
> 
> Going beyond that is not the job for WSDL. I thought that's what
> the semantic Web was about, but I really don't grok SW stuff yet.

I think it would be a mistake for WSDL 1.2 to require the use of
Semantic Web technology for developers who just want to do what WSDL
1.1 already does without Semantic Web technology.

Do you really want to do that?

Mark.
-- 
Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca

Received on Thursday, 30 October 2003 07:10:38 UTC