[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: multiparty (was) Fwd: Re: message routing
From: John Yunker: > This issue gets really thorny unless you keep two concepts front and center: > Any one "transaction" is between two parties, and a party's responsibilities > and capabilities are specified in the protocol in which they "agree" to > participate. I fully agree. Moreover, when it comes to dependencies between transactions in a collaboration, many (if not most) of them will also be between two parties, because they will be commitment-fulfillment relationships and commitments are (usually?always?) between two parties. In other words, many (all?) multi-party collaborations can be resolved to a group of two-party dialogs. In still other words, the complexities of workflow models with splits and joins etc may be avoidable in many cases. -Bob Haugen
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC