W3C home > Mailing lists > Public > public-ws-chor@w3.org > March 2003

Re: More about the patient/receptionist/doctor use case.

From: Assaf Arkin <arkin@intalio.com>
Date: Wed, 26 Mar 2003 12:11:00 -0800
Message-ID: <3E820954.1030306@intalio.com>
To: Stephen White <swhite@SeeBeyond.com>
CC: Ricky Ho <riho@cisco.com>, edwink@collaxa.com, jdart@tibco.com, public-ws-chor@w3.org

Awesome!

arkin

Stephen White wrote:

>I was having trouble following the use case as a text description, so I made up a couple of diagrams to help me follow the example. There is a diagram with a 3-party choreography (3Part_Pat-Recp-Doc.jpg) and three separate diagrams of the individual 2-party choreographies (within 3_2Part_Pat-Recp-Doc.jpg). I am sending in the diagrams to help those like me who need to see pictures. 
>
>A note about the diagrams: The activities of the three parties are separated by swimlanes. The solid lines between activities indicate the sequence of activities for each party. The dashed lines show the flow of messages between the parties. I numbered the messages as was presented in the example. The activities within the swimlanes represent only the interface for that party. Presumably, there are activities that go on behind the scenes, but are not modeled in the choreography.
>
>-Steve
>
>-----Original Message-----
>From: Ricky Ho [mailto:riho@cisco.com]
>Sent: Tuesday, March 25, 2003 1:46 PM
>To: edwink@collaxa.com; jdart@tibco.com
>Cc: public-ws-chor@w3.org
>Subject: RE: More about the patient/receptionist/doctor use case.
>
>
>Edwin,
>
>  
>
Received on Wednesday, 26 March 2003 15:15:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 01:00:07 GMT