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

RE: Two logical WSDL documents describing the same service

From: Champion, Mike <Mike.Champion@SoftwareAG-USA.com>
Date: Thu, 18 Dec 2003 11:35:46 -0500
Message-ID: <BDD579D96530CA4BAAAD5D9549BDE779F8CDDC@resmsg01.sagus.com>
To: Amelia A Lewis <alewis@tibco.com>, "Champion, Mike" <Mike.Champion@SoftwareAG-USA.com>
Cc: www-ws-desc@w3.org


> -----Original Message-----
> From: Amelia A Lewis [mailto:alewis@tibco.com] 
> Sent: Thursday, December 18, 2003 11:16 AM
> To: Champion, Mike
> Cc: www-ws-desc@w3.org
> Subject: Re: Two logical WSDL documents describing the same service
> In WSDL terms, a service is the thing in the 
> definitions/service element.  It does not correspond with the 
> common conception of a service as a bag of state out there 
> somewhere with (potentially many, mutually
> incompatible) exposed endpoints.

Yep, I'd say this is the question you want to focus on.  If a WSDL <service>
element does not correspond to the common conception of a "service", things
are going to get ugly.  I'm not so sure that what people think of as the
"service" is the bag of state rather than a specific interface for
manipulating that bag of state, but I haven't thought hard about it.  Worse,
there seem to be two inconsistent sources of information on what "people
think of as a service" -- common SOAP/WSDL 1.1 practice, and the theorizing
about Service Oriented Architectures that one sees everywhere these days.
I'm inclined to think that the SOA theorizing is the better source of
inspiration, but I can *easily* imagine that companies with shipping
products and real WSDL 1.1 customers would disagree!
Received on Thursday, 18 December 2003 11:41:27 UTC

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