[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [bt-spec] Relationship: Composer:Participant
-----Original Message-----
From: Sazi Temel [mailto:sazi.temel@bea.com]
Sent: Monday, December 31, 2001 8:20 PM
To: Sanjay Dalal
Cc: Peter Furniss; OASIS BTP (Main List)
Subject: RE: [business-transaction] FW: diagrams
At 11:47 PM 12/30/01 -0800, Sanjay Dalal wrote:
Peter,
Thanks for the reply and comments. I have made changes as per your comments. Please see inline for other comments. Let me know if you have any suggestion for more diagrams too.
Wish you and BTPers a happy, healthy and peaceful new year.
thanks,
sanjay
- ----Original Message-----
- From: Peter Furniss [mailto:peter.furniss@choreology.com]
- Sent: Tuesday, December 18, 2001 10:10 AM
- To: OASIS BTP (Main List)
- Subject: RE: [business-transaction] FW: diagrams
- Sanjay,
- Sorry I didn't comment on your diagrams earlier - I think they will be really helpful, and some at least will get into the intended model section.
- thanks. I hope these are also useful for primer apart from the specifications.
- [peter] Composer and Coordinator have direct S:I relation to sub-coordinator, to sub-composer and to participant
- [sanjay] Sazi tells me that this was not resolved in f2f, esp. Composer-Participant and Composer-Sub-composer relationships. I understand your thinking too. I have kept the relationships at abstract level i.e. one can implement such that the same entity can play the roles of Composer and Coordinator. It means, that entity can directly talk to the Participant. In the same way Sub-coordinator and Sub-composer can be played by another entity. That way Composer-Coordinator entity can talk directly to Sub-composer-Sub-Coordinator entity.
- <snip>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC