-
Key: DMN13-65
-
Status: closed
-
Source: Goldman Sachs ( Octavian Patrascoiu)
-
Summary:
None of the metamodels contain logic constraints. For example, the name of a decision table is the same with the name of the variable defined inside of the decision table tag (invariant at decision table level).
Ideally these constrains would be used to validate the diagrams before execution (e.g. generating code from Java). Bruce Silver's already covers some of the. We should add them and more in the spec.
I think the metamodel constraints should be described with OCL – see the UML metamodels. There should be constraints for CL1, CL2 and CL3. It’s very likely the CL3 constraints will be a superset of CL2 constraints.
-
Reported: DMN 1.1 — Sun, 30 Oct 2016 11:45 GMT
-
Disposition: Deferred — DMN 1.3
-
Disposition Summary:
RTF 1.3 is ending
Thank you for reporting the issue; it is likely valid but unfortunately the DMN 1.3 revision task force ran out of time before a member was able to resolve it. The issue will be deferred to the next revision task force.
-
Updated: Mon, 30 Mar 2020 19:50 GMT
DMN13 — Metamodel constraints & validation
- Key: DMN13-65
- OMG Task Force: Decision Model and Notation 1.3 RTF