Source: Oracle ( Gary Hallmark)
use <element name=xx, type=tYY/> instead of <element ref=zz/>
This will more consistently name subelements as MM attributed names, not as MM class names. This is a stylistic issue only.
Reported: DMN 1.0 — Tue, 27 Oct 2015 17:21 GMT
Disposition: Resolved — DMN 1.1
Consistently use MM names in XSD
Change XSD to use attribute names as defined in meta model aggregations.
Remove references to global elements where no polymorphism is needed.
In particular the changes are:
1. remove unneeded global elements and refs
2. Revert back to ref="Import" due to polymorphism with ImportedValues
3. Remove unused element text
4. Use attribute names from meta model
5. Consistently prefix type names with t
(This is only XSD cosmetics and does not affect the actual element names in instance documents)
6. Consistently name elements with MM class name with lower-case first letter
(This last change might be a little controversial, as it affects many element names. However, the previous changes result in a mixture of upper and lower case element name, which certainly will be confusing for tool vendors. Especially, since we see in the OMG BPMN Model Interchange Working Group, that many tool vendors are not performing schema validations, we might end up with subtle differences in import/export that prevent interchange. Also when developing tools to analyse or transform DMN files using XSLT or XPath, predictable element names will safe a lot of hassle.)
7. imported values can only be used in literal expression.
Updated: Tue, 29 Mar 2016 15:07 GMT
- AllExpressions.png 62 kB (image/png)
- BusinessContext.png 50 kB (image/png)
- BusinessKnowledgeModel.png 51 kB (image/png)
- Decision.png 109 kB (image/png)
- DecitionTable.png 104 kB (image/png)
- Definitions.png 56 kB (image/png)
- Expression.png 100 kB (image/png)
- InputData.png 28 kB (image/png)
- KnowledgeSource.png 48 kB (image/png)
DMN11 — use refs in XSD only to substitution groups
- Key: DMN11-164
- OMG Task Force: Decision Modeling and Notation 1.1 RTF