Shared Data Model and Notation Avatar
  1. OMG Specification

Shared Data Model and Notation — Open Issues

  • Acronym: SDMN
  • Issues Count: 29
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Summary

Key Issue Reported Fixed Disposition Status
SDMN-137 XML Namespace URI needs updating SDMN 1.0b1 open
SDMN-135 There are Connection Errors in the SDMN Diagram Example SDMN 1.0b1 open
SDMN-133 MultiplicityKind attribute is redundant in ItemDefinition SDMN 1.0b1 open
SDMN-130 ItemKind is in the Wrong Location SDMN 1.0b1 open
SDMN-129 Additional Editorial Issues SDMN 1.0b1 open
SCE-109 XSD Chapter Outdated with incorrect text. SDMN 1.0b1 open
SCE-107 Annotation class provides no value and conflicts with downstream languages SDMN 1.0b1 open
SCE-103 Some SCE Elements are concrete instead of abstract SDMN 1.0b1 open
SCE-101 importType Property description obsolete and too restrictive SDMN 1.0b1 open
SDMN-125 Labels are not needed for SDMN Connectors SDMN 1.0b1 open
SDMN-121 Notation Depiction Definitions for ItemComponents is not clear SDMN 1.0b1 open
SDMN-119 SDMN XSD has a redundant Import element SDMN 1.0b1 open
SDMN-115 Copyright section needs update SDMN 1.0b1 open
SDMN-113 SDMN has too many layers of abstraction for packaging models SDMN 1.0b1 open
SDMN-93 There are SCE Structural changes that affect the structure SDMN SDMN 1.0b1 open
SDMN-69 There are editorial issues in the Specification SDMN 1.0b1 open
SDMN-81 Create Capability of Data Associations across multiple Data Items - not just one to one SDMN 1.0b1 open
SDMN-74 Integration from SDMN to BPMN, CMMN, and DMN is not clear SDMN 1.0b1 open
SCE-53 SCEDI cannot be directly re-used as-is SDMN 1.0b1 open
SDMN-109 There are no semantics defined for some of the DataItem markers SDMN 1.0b1 open
SDMN-103 ReferenceConnector for DataItems does not match the semantics of ItemDefinition reference relationships SDMN 1.0b1 open
SDMN-88 The Legend in the DataItem Diagram Example is not necessary SDMN 1.0b1 open
SDMN-50 No Notation for Item Definitions SDMN 1.0b1 open
SDMN-83 Add arrowhead to Containment Connector SDMN 1.0b1 open
SDMN-44 Clarify constraints on SDMN Import inherited from SCE SDMN 1.0b1 open
SDMN-49 Containment Connector SDMN 1.0b1 open
SDMN-62 Remove Item Format from SDMN SDMN 1.0b1 open
SDMN-45 Fig 1 does not render properly in PDF SDMN 1.0b1 open
SDMN-41 Add BPMN Messages to SDMN SDMN 1.0b1 open

Issues Descriptions

XML Namespace URI needs updating

  • Key: SDMN-137
  • Status: open  
  • Source: Camunda Services GmbH ( Mr. Falko Menge)
  • Summary:

    The XML namespace URI of the original SDMN submission uses a dated version stamp, which if changed with each revision could lead to model interchange issues, i.e. different tools supporting different versions with incompatible XML namespaces (see also SCE-117).

    In addition, the following sentence about imports was accidentally copied from DMN is invalid for SDMN:

    SDMN files MAY import non-SDMN files (such as XSDs and PMMLs) if the contained elements use external
    definitions.

  • Reported: SDMN 1.0b1 — Tue, 6 Feb 2024 22:42 GMT
  • Updated: Sat, 10 Feb 2024 01:21 GMT

There are Connection Errors in the SDMN Diagram Example

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

    In the diagram, it looks like some of connectors provide inconsistent or conflicting relationships.

  • Reported: SDMN 1.0b1 — Tue, 6 Feb 2024 22:02 GMT
  • Updated: Sat, 10 Feb 2024 01:21 GMT


ItemKind is in the Wrong Location


Additional Editorial Issues

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

    The application of resolutions for previous issues missed a few things and there are some general editorial problems that still need fixing.

  • Reported: SDMN 1.0b1 — Tue, 6 Feb 2024 16:49 GMT
  • Updated: Sat, 10 Feb 2024 01:21 GMT
  • Attachments:

XSD Chapter Outdated with incorrect text.

  • Key: SCE-109
  • Status: open  
  • Source: BPM Advantage Consulting ( Dr. Stephen White)
  • Summary:

    XSD Chapter Outdated with incorrect text that was copied from the DMN specification.

  • Reported: SDMN 1.0b1 — Wed, 31 Jan 2024 23:42 GMT
  • Updated: Fri, 9 Feb 2024 01:16 GMT

Annotation class provides no value and conflicts with downstream languages

  • Key: SCE-107
  • Status: open  
  • Source: BPM Advantage Consulting ( Dr. Stephen White)
  • Summary:

    The Annotation class, an abstract class, is no longer necessary since Documentation and Category are no longer subclassing it. With only Attachment subclassing Annotation, it provides no value. It also adds additional structural overhead that is not needed. Further, using the name "Annotation" conflicts with downstream language PPMN that want to use it for an unrelated language element.

  • Reported: SDMN 1.0b1 — Wed, 31 Jan 2024 17:52 GMT
  • Updated: Fri, 9 Feb 2024 01:16 GMT
  • Attachments:

Some SCE Elements are concrete instead of abstract


importType Property description obsolete and too restrictive

  • Key: SCE-101
  • Status: open  
  • Source: BPM Advantage Consulting ( Dr. Stephen White)
  • Summary:

    The description of the import element was copied from BPMN and contains information that are not appropriate to SCE, which is an infrastructure specification and not specific to any modeling language.
    Note that this text was updated by SCE-36, but the update was not comprehensive enough

  • Reported: SDMN 1.0b1 — Mon, 29 Jan 2024 20:29 GMT
  • Updated: Fri, 9 Feb 2024 01:16 GMT

Labels are not needed for SDMN Connectors


Notation Depiction Definitions for ItemComponents is not clear

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

    In the specification section for Edge Resolutions, the two entries for the connections for ItemDefinitions does not provide enough detail to for the identification of the proper elements to be depicted.

  • Reported: SDMN 1.0b1 — Wed, 24 Jan 2024 17:38 GMT
  • Updated: Fri, 9 Feb 2024 01:15 GMT

SDMN XSD has a redundant Import element

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

    SDMN inherits the import element from SCE, but it also contains its own copy of import. This is probably a left over from an earlier version of the XSD.

  • Reported: SDMN 1.0b1 — Tue, 16 Jan 2024 17:29 GMT
  • Updated: Fri, 9 Feb 2024 01:15 GMT

Copyright section needs update

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

    Update copyright section
    Update the years of contribution based on OMG-recognized contributors and taskforce membership.

  • Reported: SDMN 1.0b1 — Mon, 15 Jan 2024 18:28 GMT
  • Updated: Fri, 9 Feb 2024 01:15 GMT

SDMN has too many layers of abstraction for packaging models


There are SCE Structural changes that affect the structure SDMN


There are editorial issues in the Specification


Create Capability of Data Associations across multiple Data Items - not just one to one

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

    The current Data Associations (as well as those in BPMN) allow mapping between two data structures. But there are situations where 2 or more structures should be mapped to another structure. This capability should be added to SDMN. This may involve some signification metamodel adjustments.

  • Reported: SDMN 1.0b1 — Tue, 28 Nov 2023 18:46 GMT
  • Updated: Fri, 2 Feb 2024 00:21 GMT

Integration from SDMN to BPMN, CMMN, and DMN is not clear

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

    The spec should have more descriptions of how SDMN can be used by the other languages. This might affect some SDMN structures.

  • Reported: SDMN 1.0b1 — Tue, 7 Nov 2023 15:59 GMT
  • Updated: Fri, 2 Feb 2024 00:21 GMT

SCEDI cannot be directly re-used as-is


There are no semantics defined for some of the DataItem markers


ReferenceConnector for DataItems does not match the semantics of ItemDefinition reference relationships

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

    For ItemDefinitions, the reference relationship affects the content (structure) of the source ItemDefinition. For DataItems, the ReferenceConnector does not affect the structure of the source DataItem. The proposal for the graphical elements for ItemDefinition modeling plans on re-using the ReferenceConnector line. Thus, there is a conflict.
    Either the ItemDefinition should use a different line style or the ReferenceConnector should be redefined.
    However, based on an analysis of the definition of the ReferenceConnector it could be argued that the basic Association connector (inherited from SCE) provides the same semantic capability. Thus, the ReferenceConnector would be better to be redefined to match the semantics of the ItemDefinition reference relationship.

  • Reported: SDMN 1.0b1 — Thu, 28 Dec 2023 19:38 GMT
  • Updated: Sat, 27 Jan 2024 01:16 GMT
  • Attachments:

The Legend in the DataItem Diagram Example is not necessary


No Notation for Item Definitions


Add arrowhead to Containment Connector


Clarify constraints on SDMN Import inherited from SCE

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

    The spec doesn't clearly specify the constraints on the types of items that can be imported for an SDMN model.

  • Reported: SDMN 1.0b1 — Sat, 28 Jan 2023 00:02 GMT
  • Updated: Fri, 29 Dec 2023 00:43 GMT

Containment Connector

  • Key: SDMN-49
  • Status: open  
  • Source: Trisotech ( Mr. Denis Gagne)
  • Summary:

    The notion of Containment Connector is not needed if the Notion of Parent DataItem is not needed. If needed it should be aligned with that of UML

  • Reported: SDMN 1.0b1 — Mon, 3 Apr 2023 18:47 GMT
  • Updated: Thu, 21 Dec 2023 00:01 GMT

Remove Item Format from SDMN

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

    As part of the simplification of SDMN, remove this class. This is in line with removing DataState and Location.

  • Reported: SDMN 1.0b1 — Mon, 2 Oct 2023 16:58 GMT
  • Updated: Thu, 21 Dec 2023 00:01 GMT

Fig 1 does not render properly in PDF

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

    Both background and some arrows (e.g. BPMN -> DMN) are black or near black.

  • Reported: SDMN 1.0b1 — Tue, 7 Mar 2023 18:37 GMT
  • Updated: Wed, 18 Oct 2023 00:52 GMT
  • Attachments:

Add BPMN Messages to SDMN

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

    BPMN Messages are similar to Data Objects. In a sense, they are the Data Objects between Pools. And they can have data structures as well.

  • Reported: SDMN 1.0b1 — Wed, 21 Sep 2022 18:12 GMT
  • Updated: Wed, 18 Oct 2023 00:52 GMT