Specification Common Elements Avatar
  1. OMG Specification

Specification Common Elements — Closed Issues

  • Acronym: SCE
  • Issues Count: 2
  • Description: Issues resolved by a task force and approved by Board
Open Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
SDMN-116 Acknowledgements for SDMN 1.0 contributors needed SCE 1.0b1 SDMN 1.0b2 Resolved closed
SDMN-43 Incorrect Mapping from Metamodel to XSD SCE 1.0b1 SDMN 1.0b2 Resolved closed

Issues Descriptions

Acknowledgements for SDMN 1.0 contributors needed

  • Key: SDMN-116
  • Status: closed  
  • Source: BPM Advantage Consulting ( Dr. Stephen White)
  • Summary:

    The acknowledgement section contains information from the RFP, but not the FTF
  • Reported: SCE 1.0b1 — Mon, 15 Jan 2024 18:29 GMT
  • Disposition: Resolved — SDMN 1.0b2
  • Disposition Summary:

    Update Acknowledgements

    Add acknowledgements for SDMN 1.0 contributors from FTF Participation
  • Updated: Mon, 17 Jun 2024 13:39 GMT

Incorrect Mapping from Metamodel to XSD

  • Key: SDMN-43
  • Status: closed  
  • Source: BPM Advantage Consulting ( Dr. Stephen White)
  • Summary:

    The current SDMN XSDs were developed with a faulty translation of UML class relationships to the XSD elements.
    To resolve this issue we need to specify the XSD patterns that correspond to the UML class relationships and then update the XSDs.
  • Reported: SCE 1.0b1 — Tue, 17 Jan 2023 22:56 GMT
  • Disposition: Resolved — SDMN 1.0b2
  • Disposition Summary:

    Use same MM-XSD Mapping as in BPMN, CMMN & DMN

    Use the MM-XSD mapping approach that BPMN pioneered has since been used for all other languages of the BPM+ ecosystem, e.g. DMN & CMMN, to remain backwards compatible and allow vendors to reuse their existing language tooling based on that mapping.
    This also follows the decision of SCE-81.
  • Updated: Mon, 17 Jun 2024 13:39 GMT