CMMN 1.1 RTF Avatar
  1. OMG Issue

CR — Incorrect References

  • Key: CR-18
  • Legacy Issue Number: 19503
  • Status: closed  
  • Source: LoQutus nv ( Jochen Firey)
  • Summary:

    In the conformance matrix on page 2, following references should be fixed:
    2.1 --> 2.2
    2.2 --> 2.3
    2.3 --> 2.4
    2.4 --> 2.5
    6.7.2.1 --> 6.8.2.1
    6.7.2.2 --> 6.8.3.1

    On page 55, following reference should be fixed: reference to picture 6.35 should be 6.34

  • Reported: CMMN 1.0 — Mon, 7 Jul 2014 04:00 GMT
  • Disposition: Resolved — CMMN 1.1
  • Disposition Summary:

    Fix references in specification

    a- In the conformance matrix (table 2.1) on page 2, fix following references (column 1):
    2.1 --> 2.2
    2.2 --> 2.3
    2.3 --> 2.4
    2.4 --> 2.5
    6.7.2.1 --> 6.8.2.1
    6.7.2.2 --> 6.8.3.1

    Current conformance matrix (table 2.1) on page 2

    New conformance matrix (table 2.1) on page 2

    b- On page 55, change reference to picture 6.35 to 6.34

    Current text in page 55

    The construct in Figure 6.35 may be considered a “Stage transition,” triggered by a particular event. Stage B is enabled via its entry criterion (depicted on its boundary), the OnPart of which may specify as standardEvent the termination of Stage A, given that it terminates based on the exit criterion (as depicted on its boundary). That exit criterion may itself has an OnPart (not depicted as connector) that refers e.g., to the creation of a document (CaseFileItem instance). So, when an instance of the document is created, Stage A terminates, and Stage B is enabled upon termination of Stage A, given that it terminates based on that document creation event.

    Change text in page 55, as follows:

    The construct in Figure 6.35 6.34 may be considered a “Stage transition,” triggered by a particular event. Stage B is enabled via its entry criterion (depicted on its boundary), the OnPart of which may specify as standardEvent the termination of Stage A, given that it terminates based on the exit criterion (as depicted on its boundary). That exit criterion may itself has an OnPart (not depicted as connector) that refers e.g., to the creation of a document (CaseFileItem instance). So, when an instance of the document is created, Stage A terminates, and Stage B is enabled upon termination of Stage A, given that it terminates based on that document creation event.

  • Updated: Tue, 29 Mar 2016 15:06 GMT
  • Attachments: