W3C home > Mailing lists > Public > www-ws-arch@w3.org > June 2003

FW: Picking up the "WSDL conceptual model" discussion

From: Champion, Mike <Mike.Champion@SoftwareAG-USA.com>
Date: Wed, 11 Jun 2003 21:30:11 -0400
Message-ID: <9A4FC925410C024792B85198DF1E97E405E499FB@usmsg03.sagus.com>
To: www-ws-arch@w3.org


[sent to admin list by mistake ... reposting here]

We were having a good discussion of the "UML diagram" of the WSDL 
conceptual model on the telcon 2 weeks ago.
http://www.w3.org/2002/ws/arch/3/05/2003-05-29-ws-arch.htm
Toward the end, Chris said (as I scribed it anyway) "we need to identify 
what needs to be identified ... one is clearly wsdl:service, but we need to 
identify other things, like deployed service, and sort out which have which 
URIs ... we may need to be able to identify SPECIFIC deployed services, 
having scenarios would help."

I'd like to see some discussion of:
- What needs to be identified (i.e., usefully has a separate identity) 
inside the little cloud we call "service".
- How do these abstractions relate to physical "things" like printers?
- How do these relate to the WSDL "targetResource" discussion?

Here's a strawman list of things we might want to identify.  Based on
subsetquent discussion on and off the list, the only thing
I think we've agreed to is that the WSDL targetResource does not identify
any particular concept in the WSA side of things, but is something for 
WSDL authors to use to identify whatever some particular application thinks
of as the "resource" in the background.  Also, I do not advocate adding
all these concepts to the WSA document, just some minimal set of them; I 
throw out the whole list just to make sure we don't miss anything.

A) The identifier of the unique object (physical or software object with 
identity) that the service operates on.  In the printer example, it's a 
physical printer.  In the ERP example, it's not clear.
B) The actual code that does something in the real world.  In the printer 
scenario, it's a printer driver.  In the ERP scenario, it's the various 
bits of code that handle the purchase order approval process.  In general 
this code will expose proprietary APIs to 3rd parties.  This is what we 
called the "turtle" in Rennes.
C) The code that implements the SOAP interface to B).  This is what we 
called the "agent" in Rennes.
D) The targetResource, whatever that URI in a wsdl:service identifies.  It 
may correspond to A), B) or C), or it may be an abstraction that is useful 
only in the context of a specific application.
E) A wsdl:service element
F) A wsdl:endpoint
G) A soap:ultimateReceiver (?)
H) a managed / deployed service from the management point of view.  I think 
this is probably equivalent to C) but I'm not sure.

There was one response, and I clarified as follows:
Received on Wednesday, 11 June 2003 21:30:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:21 GMT