omg-dmn-taskforce / omg-dmn-spec Goto Github PK
View Code? Open in Web Editor NEWOMG Decision Model and Notation specification
Home Page: https://www.omg.org/spec/DMN/
OMG Decision Model and Notation specification
Home Page: https://www.omg.org/spec/DMN/
DC::Style
(which should be DI::Style
BTW) in the DMNDI13.xmi
file does not contain any properties:
<packagedElement xmi:type="uml:Class" xmi:id="_18_1_f7a0369_1441612964861_428140_5975"
name="DC::Style"
isAbstract="true"/>
While in the DI.xsd
it has an id
:
<xsd:complexType name="Style" abstract="true">
<xsd:annotation>
<xsd:documentation>Style contains formatting properties that affect the appearance or style of diagram elements, including diagram themselves.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="extension" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>
Line 9: the schema location for DMNDI is DMNDI15.xsd and not DMNDI13.xsd as the file has been renamed.
DMN 1.1 states the following:
"An instance of Definitions is composed of [...] zero or more decisionServices,
which are instances of DecisionService [...]"
However i did not find a way to properly model a Decision Service that is compliant with the provided XSD. A decisionService
element is not allowed inside the definitions
element:
<xsd:element name="definitions" type="tDefinitions" substitutionGroup="namedElement" />
<xsd:complexType name="tDefinitions">
<xsd:complexContent>
<xsd:extension base="tNamedElement">
<xsd:sequence>
<xsd:element name="import" type="tImport" minOccurs="0" maxOccurs="unbounded" />
<xsd:element name="itemDefinition" type="tItemDefinition" minOccurs="0" maxOccurs="unbounded" />
<xsd:element ref="drgElement" minOccurs="0" maxOccurs="unbounded" />
<xsd:element ref="artifact" minOccurs="0" maxOccurs="unbounded" />
<xsd:element name="elementCollection" type="tElementCollection" minOccurs="0" maxOccurs="unbounded" />
<xsd:element ref="businessContextElement" minOccurs="0" maxOccurs="unbounded" />
</xsd:sequence>
<xsd:attribute name="expressionLanguage" type="xsd:anyURI" use="optional" default="http://www.omg.org/spec/FEEL/20140401" />
<xsd:attribute name="typeLanguage" type="xsd:anyURI" use="optional" default="http://www.omg.org/spec/FEEL/20140401" />
<xsd:attribute name="namespace" type="xsd:anyURI" use="required" />
<xsd:attribute name="exporter" type="xsd:string" use="optional" />
<xsd:attribute name="exporterVersion" type="xsd:string" use="optional" />
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
What is the correct way to model a decision service? Am i missing something?
Currently, the DMNDI13.xmi
file does not specify any properties of the DI::DiagramElement
:
<packagedElement xmi:type="uml:Class" xmi:id="_18_1_f7a0369_1441609962778_700532_4351"
name="DI::DiagramElement"
isAbstract="true"/>
On the other hand, the DI.xsd
file contains multiple properties of that type:
<xsd:complexType name="DiagramElement" abstract="true">
<xsd:annotation>
<xsd:documentation>DiagramElement is the abstract super type of all elements in diagrams, including diagrams themselves. When contained in a diagram, diagram elements are laid out relative to the diagram's origin.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="extension" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element ref="di:Style" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>an optional locally-owned style for this diagram element.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="sharedStyle" type="xsd:IDREF">
<xsd:annotation>
<xsd:documentation>a reference to an optional shared style element for this diagram element.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>
This causes a problem when we try to parse DMN files based on the XMI schema.
There is a typo in the contextEntry
property of dmn:Context
:
<packagedElement xmi:type="uml:Class" name="Context" ...>
...
<ownedAttribute xmi:type="uml:Property" name="contextEnrty"...>
...
</ownedAttribute>
</packagedElement>
See https://github.com/omg-dmn-taskforce/omg-dmn-spec/tree/v1.3/xmi/DMN13.xmi#L1533
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.