OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-bp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: ebBP 2/10/2005: Role Editorial Clarifications (multiple sections)


Again, as a part of our TC call Tuesday, we discussed how to effectively 
communicate roles, role changes and partners. Here is some simple 
proposed text. We will need to go through the specification to ensure we 
are clear on this point throughout. Note that changes are either shown 
by [add]...[end-add] or by UPPER CASE where the changes are incremental 
to a particular sentence. The goal was to differentiate the roles that 
apply and any feedback would be greatly appreciated. Whether this has 
been accomplished, I'll leave for the team to answer. Thank you!

Assumptions:
Party or trading partner: Assumes abstract partner or top-level role in 
a business collaboration
Business Transaction: Abstract role
Business Transaction Activity: Specific role assumed and occupied by an 
abstract partner. Specific role occupies a role in the activity.
Business Collaboration (any type): Involves abstract partners or 
top-level roles (2 or more)
Collaboration activity: External role maps to other top-level roles in 
business collaborations
=================================
Section 4.5.1:
FROM:

When specialized, Binary (Business) Collaborations are between two roles 
only. Multiparty (Business) Collaborations involve more than two roles. 
Binary (Business) Collaborations are expressed as a set of Business 
Activities between the two roles. The Business Activity can be a 
Business Transaction Activity, i.e. the activity of conducting a single 
Business Transaction, or a Collaboration Activity, i.e. the activity of 
conducting another Binary (Business) Collaboration. An example of the 
former is the activity of “process purchase order”. An example of the 
latter is the activity of “negotiating a contract”. In either case the 
activities can be choreographed relative to other activities as per below.

The ability of a Binary (Business) Collaboration to have activities that 
in effect are executing others is the key to recursive compositions and 
re-use of Binary (Business) Collaborations. For example, an activity, 
whether it is a Business Transaction Activity or a Collaboration 
Activity MAY represent the usage of a definition within a Binary 
(Business) Collaboration Specification. For instance, a Business 
Transaction is defined once. However, the BT could appear many times as 
different Business Transaction Activities, where the roles change within 
the same Binary (Business) Collaboration such as for an Offer and 
Counter Offer. In that case, either partner may assume the initiating role.

In essence each Business Collaboration is a re-useable protocol between 
two or more agreeable parties.

TO: When A BUSINESS COLLABORATION IS SPECIALIZED, a Binary (Business) 
Collaboration INVOLVES two TOP-LEVEL OR ABSTRACT PARTNER roles only. 
THESE ROLES ARE SOMETIMES CALLED TOP-LEVEL ROLES. Multiparty (Business) 
Collaborations involve more than two ABSTRACT PARTNER OR TOP-LEVEL 
roles. BUSINESS Collaborations are expressed as a set of Business 
Activities between THESE roles. [add] EACH ABSTRACT PARTNER OR TOP-LEVEL 
ROLE OCCUPIES A SPECIFIC ROLE WHEN ASSOCIATED WITH A BUSINESS ACTIVITY. 
[end-add]

The Business Activity can be a Business Transaction Activity, i.e. the 
activity of conducting a single Business Transaction, or a Collaboration 
Activity, i.e. the activity of conducting another BUSINESS Collaboration 
SUCH AS A BINARY (BUSINESS) COLLABORATION WITHIN ANOTHER BINARY 
(BUSINESS) COLLABORATION. An example of the former is the activity of 
“process purchase order”. An example of the latter is the activity of 
“negotiating a contract”. In either case the activities can be 
choreographed relative to other activities as per below.

The ability of a Binary (Business) Collaboration to have activities that 
in effect are executing others is the key to recursive compositions and 
re-use of BUSINESS Collaborations. For example, an activity, whether it 
is a Business Transaction Activity or a Collaboration Activity MAY 
represent the usage of a definition within ANOTHER BUSINESS 
COLLABORATION. For instance, a Business Transaction is defined once. 
However, the BT could appear many times as different Business 
Transaction Activities SUCH AS FOR AN OFFER AND COUNTER OFFER. IN THE 
BUSINESS TRANSACTION ACTIVITIES, THE ABSTRACT ROLE IN THE BUSINESS 
TRANSACTION BECOMES A SPECIFIC ROLE, THAT MAY change within the same 
Binary (Business) Collaboration. In that case, either ABSTRACT role IN 
THE BUSINESS TRANSACTION may assume the initiating role IN THE BUSINESS 
TRANSACTION ACTIVITY.

In essence each Business Collaboration is a re-useable protocol between 
two or more agreeable parties THAT MAY ASSUME AND OCCUPY DIFFERENT ROLES 
AT VARIOUS STEPS IN THE PROCESS.

Section 4.5.2:
FROM: A Business Transaction is conducted between two parties playing 
opposite roles in that transaction. The top-level roles are always 
generic and labeled as requesting and responding roles. The specific 
roles (e.g. buyer, seller) will be specified at the Business Transaction 
Activity level, when the Business Transaction definition is used for a 
distinct purpose.

Like a Binary (Business) Collaboration, a Business Transaction is a 
re-useable protocol between two roles. The way it is re-used is by 
referencing it from a Binary (Business) Collaboration through the use of 
a Business Transaction Activity as per above. In a Business Transaction 
Activity the roles of the Binary (Business) Collaboration are assigned 
to the execution of the Business Transaction......

TO: A Business Transaction is conducted between two parties playing 
opposite ABSTRACT roles in that transaction. EACH PARTY, AS AN ABSTRACT 
PARTNER, ASSUMES AN ABSTRACT ROLE IN A BUSINESS TRANSACTION. THOSE roles 
are always generic and labeled as requesting and responding roles. The 
specific roles (e.g. buyer, seller) will be specified at the Business 
Transaction Activity level, when the Business Transaction definition is 
used for a distinct purpose. AT THAT POINT, THE ABSTRACT PARTNER ASSUMES 
AND OCCUPIES A SPECIFIC ROLE , AS A ROLE OCCUPANT. ONLY TWO ROLE 
OCCUPANTS MAY BE ACTIVE AT ONE TIME IN A BUSINESS TRANSACTION ACTIVITY.

Like a Binary (Business) Collaboration, a Business Transaction is a 
re-useable protocol between two ABSTRACT roles. The way it is re-used is 
by referencing it from a Binary (Business) Collaboration through the use 
of a Business Transaction Activity as per above. In a Business 
Transaction Activity the SPECIFIC roles of the Binary (Business) 
Collaboration are assigned to the execution of the Business Transaction. 
[add] AS INDICATED IN THE PREVIOUS SECTION, A BUSINESS COLLABORATION MAY 
BE COMPOSED WITHIN ANOTHER BUSINESS COLLABORATION VIA A COLLABORATION 
ACTIVITY. EACH ABSTRACT PARTNER PARTICIPATES IN THE BUSINESS 
COLLABORATION AND ASSUMES DIFFERENT ROLE OCCUPANTS IN THE INCLUDED 
BUSINESS TRANSACTION ACTIVITIES. HOW THE EXTERNAL ROLE IN AN ACTIVITY 
MAPS TO THE ROLES DEFINED WITHIN THE ENCLOSED ACTIVITIES IS MAPPED TO 
SHOW A TREE OF ROLE RELATIONSHIPS. HOW THIS IS ACCOMPLISHED USING THE 
PERFORMS ELEMENT AND EXTERNAL ROLE MAPPING IS FOUND LATER IN SECTIOND 
4.6.2 and 4.6.7.1. [end-add].......

Section 4.6.2
FROM: When performing a /collaboration/ activity within a /collaboration 
/there is an implicit relationship between the roles at the two levels. 
Assume that a /Binary (Business) Collaboration /Firm Order is performing 
/Binary (Business) Collaboration /Product Fulfillment through 
/Collaboration Activity/ Drop Ship. Binary (Business) Collaboration Firm 
Order has the following roles: Customer and Retailer. In Collaboration 
Activity Drop Ship we assign Customer to be the initiator, and Retailer 
to be the responder. Binary (Business) Collaboration Product Fulfillment 
has the following roles: Buyer and Seller and a Business Transaction 
Activity where Buyer is the initiator and Seller the responder. We have 
now established a role relationship between the roles Customer and Buyer 
because they are both initiators in activities in the related performing 
and performed /Binary (Business) Collaborations/.

TO: When performing a /collaboration/ activity within a /collaboration 
/there is an implicit relationship between the roles at MULTIPLE levels 
(TWO AT A MINIMUM). FOR EXAMPLE, assume that a /Binary (Business) 
Collaboration /Firm Order is performing /Binary (Business) Collaboration 
/Product Fulfillment through /Collaboration Activity/ Drop Ship. Binary 
(Business) Collaboration Firm Order has the following roles: Customer 
and Retailer. In Collaboration Activity Drop Ship we assign Customer to 
be the initiator, and Retailer to be the responder. Binary (Business) 
Collaboration Product Fulfillment has the following roles: Buyer and 
Seller and a Business Transaction Activity where Buyer is the initiator 
and Seller the responder. We have now established a role relationship 
between the roles Customer and Buyer because they are both initiators in 
activities in the related performing and performed /Binary (Business) 
Collaborations/.




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]