-
Key: DMN12-101
-
Status: closed
-
Source: Camunda Services GmbH ( Mr. Falko Menge)
-
Summary:
The classes InformationRequirement, KnowledgeRequirement and AuthorityRequirement do not have an ID. But, they need one in order to reference them in Diagram Interchange.
-
Reported: DMN 1.1 — Thu, 20 Oct 2016 17:36 GMT
-
Disposition: Resolved — DMN 1.2
-
Disposition Summary:
Make InformationRequirement, KnowledgeRequirement and AuthorityRequirement inherit from DMNElement
Update MM figures:
- Figure 20: Decision Class Diagram
- Figure 22: BusinessKnowledgeModel class diagram
XSD Diff: https://github.com/omg-dmn-taskforce/omg-dmn-spec/commit/fabefaf02122f449d50a235ddc3d8f016202c1b0
Argument for backward compatibility
All added attributes are optional. Thus, a valid DMN 1.1 model, lacking all these new optional attributes, is also a valid DMN 1.2 model. -
Updated: Wed, 3 Oct 2018 14:17 GMT
-
Attachments:
- DMN12-10-KnowlegeSource.PNG 46 kB ()
- DMN12-102-BKM.PNG 36 kB ()
- DMN12-102-DecisionPNG.PNG 77 kB ()
DMN12 — Requirements don't have an ID (needed for DI)
- Key: DMN12-101
- OMG Task Force: Decision Modeling and Notation 1.2 RTF