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

Use case for the deployedService / targetService issue

From: Ugo Corda <UCorda@SeeBeyond.com>
Date: Thu, 29 May 2003 14:42:57 -0700
Message-ID: <EDDE2977F3D216428E903370E3EBDDC90811D9@MAIL01.stc.com>
To: <www-ws-arch@w3.org>
Here is the example I gave during today's call.

I have a Buyer Web service and a Seller Web service that interact according to a choreography. The choreography happens to be an executable process (a la BPEL) and to be represented as a Web service itself: let's call it BuySellChor.

In the same WSDL file I describe the three services. I have three wsdl:service definitions with corresponding names BuyerS, SellerS, BuySellChorS.

I also have:

deployedService behind BuyerS (the agent implementing the buyer), with URI=http://BuyerDS
deployedService behind SellerS (the agent implementing the seller), with URI=http://SellerDS
deployedService behind BuySellChorS (the agent implementing the choreography, e.g. a BPEL executable process), with URI=http://BuySellChorDS

Now I want to use a URI to indicate that BuyerS, SellerS and BuySellChorS are related (they are a service group). Let's say that this URI is http://BuySellChorTR (but I could have reused http://BuySellChorDS as well). This would be the URI corresponding to targetResource as described by the WSD group.

Clearly http://BuySellChorTR is not the same as http://BuyerDS or http://SellerDS. In fact, http://BuySellChorTR can hardly be identified with the concept of a targetResource associated with BuyerS or SellerS.

Received on Thursday, 29 May 2003 17:43:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:05:52 UTC