[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: ebBP 5/23/2005: Comment re: Attribute reference without a name in3.4.10.11 (wd-2-0-1-03)
To fix this editorial omission, we need to specify what role is identified in this section on Business Collaboration. Please review the schema and technical specification v2.0 for any further details (that explains where attributes became elements, for example). Note, with the enhancements for role and the addition of perform, more detail is required in this reference. Thanks. Comments welcome and appreciated. Change from: One of the roles is initiating the Business Collaboration. This is the role, which sends the first message (i.e. Request) of the first BTA. This attribute is used to “bind” the roles of an inner Collaboration Activity to the parent Business Collaboration roles (i.e. the initial abstract partner roles). Even if this role is not known until run-time, we can still specify a “logical” initiating role. In that case, the initiating role of the parent Binary (Business) Collaboration will be bound to the initiating role of the inner Binary (Business) Collaboration definition. Change from: One of the roles is initiating the Business Collaboration. This is the role (or may be associated with the role that performs the activity) that sends the first message (i.e. Request) of the first BTA. The initial abstract partner roles of the parent Business Collaboration are bound to the roles of an inner Collaboration Activity, when there is an inner Collaboration Activity. The abstract partner roles, the roles bound and performed (such as the initiating RoleRef), and how they relate are described in detail in Section 3.4.1.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]