BPMN 2.0 FTF Avatar
  1. OMG Issue

BPMN2 — Clarification on relationship between MEP and Choreography Task in BPMN2

  • Key: BPMN2-95
  • Legacy Issue Number: 14548
  • Status: closed  
  • Source: Red Hat ( Gary Brown)
  • Summary:

    PDF page 337, page 307:
    "A single MEP is defined as a BPMN Choreography Task (see page 350). Thus, a Choreography defines the order
    in which Choreography Tasks occur. Choreography Sub-Processes allow the composition/decomposition of
    Choreographies."

    If the MEP has a request, response and multiple faults how will the choreography identify which subsequent path based on a decision relates to each response.

    Would propose changing wording to "A single MEP can be defined ..." - allowing an MEP to be defined across separate Choreography Tasks, enabling the decision point and relevant paths based on each response type to be explicitly defined in the choreography. However this may require some additional mechanism to correlate the separate choreography tasks as belonging to the same MEP.

  • Reported: BPMN 2.0b1 — Fri, 9 Oct 2009 04:00 GMT
  • Disposition: Resolved — BPMN 2.0
  • Disposition Summary:

    PDF page 337, page 307:
    Change: "A single MEP is defined as a BPMN Choreography Task"
    To: "A single MEP can be defined as a BPMN Choreography Task"
    Disposition: Resolved

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