-
Key: DMN11-92
-
Status: closed
-
Source: Oracle ( Gary Hallmark)
-
Summary:
In the MM, Fig 15, all classes inherit the optional name attribute. Thus, any DMNElement may or may not have a name. What is closer to the truth, is that some DMNElements MUST have a name, and others MUST NOT. Attached is proposed MM that splits the elements into the named and unnamed. There will be numerous text changes, especially to explain that decision tables, being expressions, do not have names. The apparent 'names' of expressions like DTs are really the name of the Information Item that has said expression as its valueExpression. It is dangerous (misleading) to supply a name for an expression, because it may appear that one could refer to the named expression's value by that name. But you cannot. You can only refer to an Information Item by name in an expression.
-
Reported: DMN 1.0 — Tue, 7 Jul 2015 20:01 GMT
-
Disposition: Resolved — DMN 1.1
-
Disposition Summary:
define NamedElement subclass of DMNElement
Revised text, MM figures, and XSD (github links)
-
Updated: Tue, 29 Mar 2016 15:07 GMT
-
Attachments:
- Fig15Prop105.PNG 54 kB ()
- Fig16Prop105.PNG 50 kB ()
- Fig17Prop105.PNG 115 kB ()
- Fig18Prop105.PNG 41 kB ()
- Fig19Prop105.PNG 59 kB ()
- Fig20Prop105.PNG 27 kB ()
- Fig26Prop105.PNG 89 kB ()
- Fig60Prop105.PNG 48 kB ()
DMN11 — Need to clarify which DMNElements must and must not have names
- Key: DMN11-92
- OMG Task Force: Decision Modeling and Notation 1.1 RTF