-
Key: DMN17-36
-
Status: open
-
Source: Red Hat ( Matteo Mortari)
-
Summary:
Since DMNv1.2 the spec dropped the equivalence of:
[a] = a
because it does not apply to the statement that
a singleton list L, when used in an expression where a list is not expected, behaves as if L[1] is written.
So the expression
[a] = a
on DMNv1.2 is expected to return false.
However, in section 10.3.2.6 Context of the spec, it provides the following statement for the get entries function:
To retrieve a list of key,value pairs from a context m, the following built-in function may be used: get entries(m).
For example, the following is true:get entries({key 1 : "value 1 "})[key="key 1 "].value = "value 1 "
BUT
get entries({key1 : "value1"})[key="key1"].value = "value1" by substitution: [ { key : "key1", value : "value1" } ][key="key1"].value = "value1" [ { key : "key1", value : "value1" } ].value = "value1" [ "value1" ] = "value1"
according to DMNv1.2 should be false
By the same principle that the DMNv1.2 for the following literal expression:
[123] = 123
on DMNv1.2 is expected to be false
-
Reported: DMN 1.2b1 — Wed, 30 Jan 2019 14:43 GMT
-
Updated: Fri, 21 Jun 2024 17:56 GMT
DMN17 — Inconsistency DMNv1.2 dropping [a]=a and get entries example
- Key: DMN17-36
- OMG Task Force: Decision Model and Notation 1.7 RTF