BPMN 2.0 FTF Avatar
  1. OMG Issue

BPMN2 — [Section 10.2.3] Editorial

  • Key: BPMN2-189
  • Legacy Issue Number: 14750
  • Status: closed  
  • Source: Object Management Group ( Mariano Benitez)
  • Summary:

    [OMG 14750] [Section 10.2.3] Editorial: protocol attribute on the transaction subprocess class seems to have a wrong description - TransactionMethod values not explained
    This is the description Transaction->protocol attribute in 0.9.2 (page 156):

    The elements that make up the internal Sub-Process flow.
    This association is only applicable when the XSD Interchange is used. In the case
    of the XMI interchange, this association is inherited from the
    FlowElementsContainer class.

    Also, the TransactionMethod values are not fully explained. I can infer compensate, but I don't understand Store or Image.

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

    Clarification: Attribute "protocol" is not needed as Transaction Sub-Process has attribute "flowElements" inherited from class Sub-Process.
    Proposal for 14335 resolves the second part of the issue.
    The proposal is to make the following changes in Beta 1:
    (1) Section 10.2.5
    Table 10.21: Remove attribute "protocol" (the complete row).
    (2) Update the XSD, so that Transaction inherits from SubProcess as stated in the specification text and MM:
    Add
    <xsd:complexType name="tTransaction">
    <xsd:complexContent>
    <xsd:extension base="tSubProcess"/>
    ...
    </xsd:complexContent>
    </xsd:complexType>
    instead of
    <xsd:complexType name="tTransaction">
    <xsd:complexContent>
    <xsd:extension base="tActivity"/>
    ...
    </xsd:complexContent>
    </xsd:complexType>
    Disposition: Resolved

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