Issue 14699: Multiple PartnerEntities per Participant (bpmn2-ftf)
Source: NIST (Mr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Critical
Summary: Collaborations and other C models might be in reusable libraries, but
currently their participants cannot be linked to multiple entities, and
cannot be linked with modifying the C model.  For example, a
collaboration might describe a contract that many entities can enter
into.  This contract might be in a library and not be modifiable.
Entities should still be able to refer to participants in it to indicate
they commit to the contract.  This commitment is made jointly by
multiple entities, each linked to their own participants.

Resolution: The associations from Participant to PartnerEntity and PartnerRole
should be unidirectional from PartnerEntity and PartnerRole, rather than
Participant, and have unbounded multiplicity on both ends. This enables
modelers to assign entities and roles to interaction models in libraries
without modifying the library.
The resolution assumes the resolution of 14654.
In the Collaborations chapter, Participants section, figure The
Participant Class Diagram, on the partnerRoleRef and partnerEntityRef
associations from Participant:
- Change the 0..1 multiplicities to *.
- Insert a "/" just before the association end names (but not part of
the names).
- Reverse the navigation direction of the associations (leaving the
association end names where they are).
- Name the unamed association ends "participantRef".
In the Collaborations chapter, Participants section, in the table
Participant attributes and model associations:
- In the partnerRoleRef row, right column, at the end, add the
sentence, "This attribute is derived from the participantRefs of
Partner Roles."
- In the partnerEntityRef row, right column, at the end, add the
sentence, "This attribute is derived from the participantRefs of
Entity Roles."
In the Collaborations chapter, Participants section, PartnerEntity
subsection, in the table PartnerEntity attributes, add a row at the end:
- participantRef [0..*]
Specifies how the Partner Entity participates in collaborations
and choreographies.
In the Collaborations chapter, Participants section, PartnerRole
subsection, in the table PartnerEntity attributes, add a row at the end:
- participantRef [0..*]
Specifies how the Partner Role participates in collaborations
and choreographies.
In the Collaborations chapter, Collaboration Package XML Schemas
section, in table Participant XML schema, remove:
<xsd:attribute name="partnerRoleRef" type="xsd:QName" use="optional"/>
<xsd:attribute name="partnerEntityRef" type="xsd:QName" use="optional"/>
Disposition: Resolved
Revised Text: 
Actions taken:
November 19, 2009: received issue
October 21, 2010: closed issue
Discussion: 

End of Annotations:=====
s is issue # 14699

[OMG 14699] Multiple PartnerEntities per Participant

##Source: NIST (Conrad Bock, conrad.bock@nist.gov)
##Original Issue: http://www.osoa.org/jira/browse/BPMN-533
##Original Info: (Severity: Critical - Nature: Revision)

Collaborations and other C models might be in reusable libraries, but
currently their participants cannot be linked to multiple entities, and
cannot be linked with modifying the C model.  For example, a
collaboration might describe a contract that many entities can enter
into.  This contract might be in a library and not be modifiable.
Entities should still be able to refer to participants in it to indicate
they commit to the contract.  This commitment is made jointly by
multiple entities, each linked to their own participants.