BPMN 2.0 FTF Avatar
  1. OMG Issue

BPMN2 — A Collaboration should be able to reference more than one Choreography

  • Key: BPMN2-293
  • Legacy Issue Number: 15168
  • Status: closed  
  • Source: BPM Advantage Consulting ( Dr. Stephen White)
  • Summary:

    To support SoaML modeling a Collaboration will need to be able to reference more than one Choreographies. These Choreographies would then be associated with the Conversations of the Collaboration.

  • Reported: BPMN 2.0b1 — Thu, 8 Apr 2010 04:00 GMT
  • Disposition: Resolved — BPMN 2.0
  • Disposition Summary:

    Section 9, Collaboration
    Change the multiplicity of Collaboration's choreographyRef model association from 0..1 to 0..*
    (a) Update Figure 9.1 to reflect this change
    Table 9.1, second row:
    (b) First column: Change "[0..1]" to "[0..*]"
    (c) Second column: change the first sentence to "The choreographyRef model association defines the Choreographies that can be shown between the Pools of the
    (d) Table 9.2, Collaboration XML Schema: change:
    "<xsd:attribute name="choreographyRef" type="xsd:QName" use="optional"/>"
    "<xsd:element ref="choreographyRef " minOccurs="0" maxOccurs="unbounded"/>"
    Disposition: Resolved

  • Updated: Fri, 6 Mar 2015 20:57 GMT