BPMN 2.0 FTF Avatar
  1. OMG Issue

BPMN2 — Section 8.3.15 [Choreo] ParticipantMultiplicity must allow to specify 1..2, possibly also 0..1

  • Key: BPMN2-214
  • Legacy Issue Number: 14804
  • Status: closed  
  • Source: International Business Machines ( Mr. Matthias Kloppmann)
  • Summary:

    Description of issue: The attributes minimum and maximum are mandated to have a min value of 2. Why would multiplicities such as 1..2 be excluded? Couldn't there even be optional participants?

    Proposal: At the very least, the minimum attribute should allowed to have a minimum of 1. Possibly, minimum should be allowed to start at 0, and maximum at 1.

    Comments:
    From: wstephe created: Fri, 11 Sep 2009 13:19:42 -0500 (CDT)
    The section, table, and page numbers were updated to match the Beta 1 Spec.

  • Reported: BPMN 2.0b1 — Tue, 24 Nov 2009 05:00 GMT
  • Disposition: Resolved — BPMN 2.0
  • Disposition Summary:

    8.3.15 Participants
    p94
    "When the minimum attribute of the ParticipantMultiplicty element has been set by the modeler, then the multiinstance
    marker will be displayed in bottom center of the Pool (Participant - see Figure 8-41) or the Participant Band
    of a Choreography Activity (see page 356)."
    change to:
    "The multi-instance marker will be displayed in bottom center of the Pool (Participant - see Figure 8-41), or the Participant Band of a Choreography Activity (see page
    356), when the ParticipantMultiplicity is associated with the Participant, and the maximum attribute is either not set, or has a value of two (2) or more."
    Table 8.56 ParticipantMultiplicity attributes
    Change from "minimum: integer [0..1] = 2" to "minimum: integer = 0" - mandatory with default value of 0
    with suitable update to schema.
    "The minimum attribute defines minimum number of Participants that
    MUST be involved in the Collaboration. The value of minimum MUST be
    two (2) or greater."
    change to:
    "The minimum attribute defines minimum number of Participants that
    MUST be involved in the Collaboration. If a value is specified in the
    maximum attribute, it MUST be greater or equal to this minimum value."
    Change from "maximum: integer [0..1] = 2" to "maximum: integer [0..1] = 1" - optional with default value of 1.
    "The maximum attribute defines maximum number of Participants that
    MAY be involved in the Collaboration. The value of maximum MUST be
    two (2) or greater."
    change to:
    "The maximum attribute defines maximum number of Participants that
    MAY be involved in the Collaboration. The value of maximum MUST be
    one (1) or greater, AND must be equal or greater than the minimum value."
    Disposition: Resolved

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