DMN 1.1 RTF Avatar
  1. OMG Issue

DMN11 — DMN XSD, MM, Attribute/Association Tables, and spec text are not consistent

  • Key: DMN11-146
  • Status: closed  
  • Source: Oracle ( Gary Hallmark)
  • Summary:

    XSD must use names derived in a consistent way from MM names. XSD types should be used everywhere. Spec text descriptions must agree in name and concept with the MM. XSD must use containment and references in the same way as the MM. For example, DMN11-81 removes references and uses containment for the entries in a DT. But XSD still has lingering ID/IDREFs that must be removed and aligned with current MM.

  • Reported: DMN 1.0 — Thu, 8 Oct 2015 16:10 GMT
  • Disposition: Resolved — DMN 1.1
  • Disposition Summary:

    Align XSD, MM and spec text as described

    Make following changes to XSD:
    1. Relation.column in XSD should have type tInformationItem, not tContextEntry
    2. Invocation.calledFunction is missing in the XSD
    3. KnowledgeSource.type: change anyType to string
    4. tInvocation/@calledFunction is of type="xsd:string", but in MM it aggregates an Expression => Change XSD to reference abstract element Expression.

    Make following changes to MM:
    1. MM ImportedValues does not contain importedElement, but XSD does. Add attribute to MM
    2. Collapse the classes that are not essential in each diagram, e.g. DMNElement and NamedElement should show attributes only in the DMN Element diagram
    3. Use xsd types (instead of String) for ID, anyURI, QName
    4. rename OrganisationalUnit into OrganizationUnit in MM and spec text.
    5. name association from Decision to InformationRequirement "informationRequirement"
    6. add attribute importedElement : String[1] to ImportedValues in MM
    7. remove attribute "name" from InformationItem in MM
    8. Make NamedElement abstract in MM and XSD

  • Updated: Tue, 29 Mar 2016 15:07 GMT
  • Attachments: