BPSS 2.0 Role fixups: discussion topic Nov 17 teleconference for CPPA

["Dale Moberg" <dmoberg@us.axway.com>]

A CollaborationRole groups together all of a party’s actions within a service and with a given role. And since there was only one service in a BPSS process specification and roles were not rebound during activities, this approach was adequate for BPSS 1.x.

 

BPSS 2.0, however, allows toplevel (external “roles” or party types) to be bound to each BusinessCollaboration in the BPSS instance. The BusinessCollaboration/@name is the new Service value. The problem is how to describe a Recommended way of connecting BPSS values with CPPA values given the new flexibility in BPSS 2.0.

 

I am going to propose a “straw man” proposal that involves some changes in the current draft. This proposal can serve to start discussion on the BPSS 2.0 Role issue set this Friday, Nov. 17 (this will be our last November 2006 teleconference).

 

1. When ExternalRole values are present and bound (by means of a Performs construct) to Role values in BusinessCollaborations, it is Recommended that the CollaborationRole/Role value be the ExternalRole/BusinessPartnerRole/@name value.

2.  When ExternalRole/BusinessPartnerRoles are absent or are not bound to a BusinessCollaboration’s Role values, then the CollaborationRole/Role value Should be that of the BusinessCollaboration/Role/@name value.

3. When BTAs are present, then the value for Role should derive from the value associated with the @currentRoleRef in the BTAs Performs construct.

a. When the BTA/Performs/@currentRoleRef refers to a BC/Role whose @name value is the same as CollaborationRole/Role, then it is not Required that there be any ActionContext2 information about Role to indicate the Role value in context. The implementation Should, however, supply the (unchanged) value within an ActionContext2 element.

b. When the BTA/Performs/@currentRoleRef refers to a BC/Role whose @name value that differs from the CollaborationRole/Role, then it is Required that there be any ActionContext2 information about Role to indicate the Role value in context.

4. When CollaborationActivities are present within a BC, we need to decide what to do Friday:

Here are some directions:

(1) mainly ignore the intermediate reassignments in Role values, and always follow rule 3b. In other words, identify the role value “operative” in the final BTA/Performs/@currentRoleRef and supply it to the ActionContext2 element.

(2) Add on some listing of intermediate role values to the ActionContext2

(3) something else

 

 

I hope this can serve to help focus discussion for the CPPA talk. It may be necessary to set up a call with a webex so that we can share a visual representation of the schemas involved.