CMMN 1.1 RTF Avatar
  1. OMG Issue

CR — CMMN needs to provide a standard way for vendors to serialize extensions (Vendor Extensions)

  • Key: CR-20
  • Legacy Issue Number: 19506
  • Status: closed  
  • Source: Trisotech ( Mr. Denis Gagne)
  • Summary:

    CMMN nees to provide a standard way for vendors to serialize extensions (Vendor Extensions)

    It is proposed that a schema resembling what was done in BPMN be used

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

    Add new extension capability to CMMN as per that of BPMN

    1. Add two rows to table 5.1
    -. Add a new figure of the meta model showing the relation between CMMNElement and extension in section 5.1.1 (This figure comes from resolution CR-71)
    2. Add two rows to table 5.2 after imports line
    3. Add a row at the end of table 5.2
    4. Figure 5.1 – Definitions class diagram need to be updated with Extensions depiction.
    5. A complete new section 5.1.5 Extesibility need to be added. This will have a ripple effect on table and figure numbering
    6. Figure of the meta model should be inserted after first para of section 5.1.5, in the meta model we need to add the four classes described
    7. Figure of the meta model should be inserted at the end of section 5.1.5 just before talking about Relationship. Relationship is a new class that extends CMMNElement and is related to the Definition
    8. Some changes needed to CMMN.xsd
    9. Some changes needed to CMMNCaseModel.xsd

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