Issue 15065: definitionalCollaborationRef should be 0..* (bpmn2-rtf) Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com) Nature: Uncategorized Issue Severity: Summary: Table 10.1, definitionalCollaborationRef includes the phrase “For Processes that interact with other Participants,” which implies that Processes *are* Participants. In fact they are distinct elements in the metamodel. More significantly it states “The definitional Collaboration specifies the Participants the Process interacts with, and more specifically, which individual service, Send or Receive Task, or Message Event, is connected to which Participant through Message Flow.” However a Process could be linked to Participants in many Collaborations and so the multiplicity of [0..1] seems over-limiting. Resolution: Revised Text: Actions taken: February 18, 2010: received issue Discussion: The same process can appear in multiple collaborations, and must be consistent with all them, so it is unclear why definitional collaboration are any different the others a process appears in. One possibility is to limit correlation to the definitional collaboration. If processes can have multiple definitional collaborations, it needs to be decided which applies when the process is called. This is deferred for more discussion in RTF. Disposition: Deferred End of Annotations:===== iler: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 19 Feb 2010 13:43:48 -0500 To: bpmn2-ftf@omg.org From: Juergen Boldt Subject: OMG Issue Created 15065 This is issue # 15065 From: "Pete Rivett"