-
Key: DMNFTF-13
-
Status: closed
-
Source: Oracle ( Gary Hallmark)
-
Summary:
last paragraph of 6.1 of the alpha spec says:
Using a value expression of type invocation is never required, even when possible: FEEL specifies its own invocation mechanism for more complex usages, and a FEEL literal expression can always be used instead of a value expression of type invocation.
I would like this to say instead:
A boxed invocation SHOULD be used instead of a literal FEEL invocation when possible. In general, a boxed expression SHOULD be used instead of a literal FEEL expression when possible. Note that Conformance Level 3 specifies additional boxed expressions.
Because 'boxed expression' isn't defined until 6.2, the rewritten para should be moved to the end of 6.2 (or even 6.3)
Also, I notice that 6.1 defines a decision table to be a tabular representation of decision logic. Would it be a good idea to do a global replace of 'boxed expression' with 'tabular expression'?
-
Reported: DMN 1.0b1 — Wed, 7 Aug 2013 22:36 GMT
-
Disposition: Resolved — DMN 1.0
-
Disposition Summary:
Define boxed expressions available at each conformance level, and recommend their use over equivalent literal expressions.
-
Updated: Tue, 21 Apr 2015 01:19 GMT
DMNFTF — boxed (tabular) expressions should be encouraged
- Key: DMNFTF-13
- OMG Task Force: Decision Model And Notation 1.0 FTF