Git Product home page Git Product logo

omg-dmn-spec's People

Contributors

brsilver avatar falko avatar jamet123 avatar menski avatar opatrascoiu avatar simonringuette avatar sringuette avatar tarilabs avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

omg-dmn-spec's Issues

Missing property "id" in the DC::Style in XMI file

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>

How to model a Decision Service?

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?

Missing properties for di:DiagramElement in the XMI file

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.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.