- From: Jim Hendler <hendler@cs.umd.edu>
- Date: Mon, 7 Jul 2003 12:21:39 -0400
- To: "Martin Chapman" <martin.chapman@oracle.com>, "Champion, Mike" <Mike.Champion@SoftwareAG-USA.com>, <public-ws-chor@w3.org>
At 9:04 AM -0700 7/7/03, Martin Chapman wrote: >I think Mike has made a good point here. If a composition presents a new >wsdl, it has to be hosted somewhere, even if its job is just to delegate out >to the parties (Yaron made a similar point the other week). I thought we had >ruled out this sort of central controller, for autonomous peer-peer >environments. >Thinking about this a little more, the only way I can see nesting of >choreographies is for one choreography to take on the role(s) defined in >another choreography. Something like: > >Choreo 1: pay > role payer > role payee > role cardagency > > payer sends payment details to cardagency > //cardagency verifies and does stuff > cardagency deposits money from payers card > cardagency credits money (minus fee) to payees account > >Choreo 2: Purchase goods > role buyer > role seller > reuses Choreo 1: buyer=payer, seller=payee > > buyer submits PO > seller checks warehouse > seller send invoice to buyer > buyer submits payment details (kicks off choreo 1) > > blah, blah > >Something like that anyway. > >Martin. I think this is the correct way to do this sort of thing -- assuming the choreographies are able to be designated with a URI or with some other namespace type trick, then I think there is tremendous strength in one choreography being able to use another by pointing (and setting variables) -JH -- Professor James Hendler hendler@cs.umd.edu Director, Semantic Web and Agent Technologies 301-405-2696 Maryland Information and Network Dynamics Lab. 301-405-6707 (Fax) Univ of Maryland, College Park, MD 20742 *** 240-277-3388 (Cell) http://www.cs.umd.edu/users/hendler *** NOTE CHANGED CELL NUMBER ***
Received on Monday, 7 July 2003 12:21:57 UTC