[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: ebBP 1/11/2005: Reminder Today's TC Call
Remember Dale's words last week....just do it! It's time to get in gear for 2005 and move to formal review 24 January 2005. Comments are requested on: * BT patterns: http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/event.php?event_id=6481 * Technical specification: http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/event.php?event_id=6481 * Pre-notification list: http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/email/archives/200501/msg00005.html * CPPA v2.1/ebBP v2.0 alignment: http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/email/archives/200501/msg00011.html A clarification was raised when Hima, Dale and I met yesterday on CPPA v2.1/ebBP v2.0 alignment regarding the ComplexBTA. Initially, I had thought we limited the CBTA as a mechanism for status visibility of sub-parties visible but not part of the business collaboration. Reference from the editors' F2F this last summer: /Clearly state that the party, with visibility to other sub-parties, has the responsibility for the performance of the sub-parties (who are not first class citizens of the business collaboration), who are not specifically constrained by the business collaboration. Sub-parties are identified in the complexBTA. However, they are not parties to the binary collaboration. Another business collaboration may exist elsewhere that defines the interaction of the parties that are sub-parties visible in this business collaboration. / Dale has asked if this can apply to any collaboration: MPC, Binary or Business. Comments welcome. We will discuss today in addition to the alignment recommended by Dale yesterday (see: above). We will start with the update from Sacha Schlegel and the jBPM team. Thanks.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]