SDMN 1.0b2 FTF Avatar
  1. OMG Issue

SDMN — Incorrect Mapping from Metamodel to XSD

Open Closed All
  • 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