-
Key: DMN12-89
-
Status: closed
-
Source: Trisotech ( Mr. Denis Gagne)
-
Summary:
Most element inherit DMNElement which includes a label.
Some elements extends NamedElement that extends DMNElement and adds a required name to it.Some text should be added to the specification to determine how those two attributes should be used.
For example, what should be depicted on a Decision in the diagram?
It’s name or its label?
Is that label really required on all elements?
(please note that a label may contain ctrl char like carriage return where I presume the name would not)NB (This issue also relate to the upcoming Diagram Interchange (DI) capability coming)
-
Reported: DMN 1.1 — Fri, 26 Aug 2016 18:40 GMT
-
Disposition: Resolved — DMN 1.2
-
Disposition Summary:
Clarify role of label
1. Clearly define that the name attribute is displayed in the notation
2. Explain label attributes purpose as an alternative short description and that it is not displayed and not to be confused with names, which are used for referencing
3. Should not be used on elements that already have a name -
Updated: Tue, 30 Apr 2024 23:18 GMT
DMN12 — Label versus name attribute
- Key: DMN12-89
- OMG Task Force: Decision Modeling and Notation 1.2 RTF