-
Key: DMN11-26
-
Status: closed
-
Source: Bruce Silver Associates ( Mr. Bruce Silver)
-
Summary:
If a DMN engine wants to provide a history of executed rules and clauses it needs to be able to reference them explicitly and have a human-readable label for them.
-
Reported: DMN 1.0 — Mon, 9 Mar 2015 19:37 GMT
-
Disposition: Resolved — DMN 1.1
-
Disposition Summary:
Add ID & label attributes by inheriting DMNElement
Spec text, MM and XSD should be changed to...
1. Let DecisionRule, InputClause and OutputClause inherit DMNElement.
2. Add an attribute label to DMNElement -
Updated: Tue, 30 Apr 2024 23:19 GMT
-
Attachments:
- DMN11-154-Proposal.png 82 kB (image/png)
- Fig15_DMNElement_proposal.png 44 kB (image/png)
- Fig17_Decision_proposal.png 76 kB (image/png)
- Fig18_BusinessContext_proposal.png 35 kB (image/png)
- Fig19_BusinessKnowledgeModel_proposal.png 36 kB (image/png)
- Fig20_InputData_proposal.png 24 kB (image/png)
- Fig21_KnowledgeSource_proposal.PNG 37 kB ()
- Fig26_Expression_proposal.png 74 kB (image/png)
- Fig44_DecisionTable_proposal.png 82 kB (image/png)
- Fig60_All_Expressions_proposal.PNG 38 kB ()
- Table27.png 51 kB (image/png)
DMN11 — DecisionRule, InputClause & OutputClause should have ID and label for referencing in execution logs
- Key: DMN11-26
- OMG Task Force: Decision Modeling and Notation 1.1 RTF
