FEEL function definitions are defined as lexical closures, which simply means that names in the function body must be in scope, and that scope includes the function parameters and, just like any other decision logic, it includes the information requirements and the knowledge requirements. This is very handy. For example, it allows the logic of a BKM to reference 100 Input Data items by name, without requiring that each invocation pass in 100 parameter bindings.

In order for this to work, the BKM would model 100 Information Requirements on the 100 Input Data items, instead of modeling them as parameters. The boxed invocations would not have 100 rows of repetitive binding information. We must extend the MM and Table 2 to allow a BKM to have information requirements.

Defer to DMN 1.6

Defer to DMN 1.6

The notion of a 'type' or ItemDefinition is in the metamodel (with some pending issues) and in the semantics and concepts, but little is in the notation. Thus, we have notation that allows you to execute an expression with actual arguments, but no notation to allow validation based on type information without actual values.

We have most of the pieces, so it should not be difficult. E.g., individual values can be number, string, date and time, etc. We can allow numeric ranges using our unary tests, e.g. '>0', '[10..30)', etc. We can allow LOVs using "abc", "def", "ghi". These can be 'simple items', and we can also define structures using something similar to boxed contexts.

Defer to DMN 1.6

Defer to DMN 1.6

10.3.2.9.2 says "The global context is a context provided for convenience and 'pre-compilation'. Any number of expressions can be named and represented in a FEEL context m. The syntactic description m of this context can be evaluated once, that is, mapped to the FEEL domain as m, and then re-used to evaluate many expressions." For example, you might want to put a Relation used as a multi-dimensional constant in the global context. Or you might want to put a reusable function definition in the global context. Currently the xsd does not have globals. All expressions are bound to a specific drgElement, not global. The Import element probably needs to be modified to support this also.

Defer to DMN 1.6

Defer to DMN 1.6

in typographic literals, italics are strings and bold italics are date literals, but in 10.3, italics are feel syntactic elements and bold are semantic elements. Better to have different notations

Defer to DMN 1.6

Defer to DMN 1.6

In XSD, business context pointers are duplicated in both directions. E.g. decisionOwner and decisionMaker point to organizationalUnit, which in turns has pointers back the other way. This duplication adds no new information, just potential for internal inconsistency. I suggest omitting one of these directions; the other one is easily extracted from the serialization by XPATH.

Defer to DMN 1.6

Defer to DMN 1.6

Figure 10 on page 25 with text "The encapsulated decisions are therefore

"

Figure 11 on page 26 with text "The encapsulated decisions for this services are

".

Table 20 on page 56:

• "outputDecisions: This attribute lists the instances of Decision required to be output by this DecisionService".
• "encapsulatedDecisions: If present, this attribute lists the instances of Decision to be encapsulated in this DecisionService".

For us it is unclear what decisions should be stored in the DMN model as encapsulated decisions. Must the output decisions also be included in the list of encapsulated decisions (as stated on page 25, 26)? Or does the list of encapsulated decisions only hold the decisions contained in the lower compartment of a decision service (as mentioned on 56 since encapsulatedDecisions seems to be optional)?

Defer to DMN 1.6

Defer to DMN 1.6

literal expression is used in MM, and textual expression is used in grammar. Let's use 1 consistently, but check that they are really the same concept.

`textual expression` does not mean `Literal Expression`

There are no places where `textual expression` refers to the `literal expression` meta model element.

`textual expression` is used only in the FEEL grammar and in the refinement of Decision Tables when using FEEL (10.3.2.10 Decision Table) and it clearly refers to the FEEL grammar in that instance.

Each input expression SHALL be a textual expression (grammar rule 2). Each list of input values SHALL be an instance of unary tests (grammar rule 15).

Clause 10.3.2.9 shows FEEL number values as mapped to XML decimal, integer, and double, but the only mapping to Java is to BigDecimal. The appropriate mapping to Java, like the appropriate mapping to XML, depends on the range and intent of the data element. BigDecimal is rarely used for anything but currency. Java int and double are much more likely to be appropriate for most data items. The mapping of number to Java should be just as flexible as the mapping to XML and PMML.

BigDecimal is not the only mapping of numbers in Java

The use of other number types in Java can be done by implementing engine optimizations, as long as the overall semantics of FEEL numbers is supported.

Figure 10 on page 25 with text "The encapsulated decisions are therefore

"

Figure 11 on page 26 with text "The encapsulated decisions for this services are

".

Table 20 on page 56:

• "outputDecisions: This attribute lists the instances of Decision required to be output by this DecisionService".
• "encapsulatedDecisions: If present, this attribute lists the instances of Decision to be encapsulated in this DecisionService".

For us it is unclear what decisions should be stored in the DMN model as encapsulated decisions. Must the output decisions also be included in the list of encapsulated decisions (as stated on page 25, 26)? Or does the list of encapsulated decisions only hold the decisions contained in the lower compartment of a decision service (as mentioned on 56 since encapsulatedDecisions seems to be optional)?

Defer to DMN 1.5

Defer to DMN 1.5

10.3.2.9.2 says "The global context is a context provided for convenience and 'pre-compilation'. Any number of expressions can be named and represented in a FEEL context m. The syntactic description m of this context can be evaluated once, that is, mapped to the FEEL domain as m, and then re-used to evaluate many expressions." For example, you might want to put a Relation used as a multi-dimensional constant in the global context. Or you might want to put a reusable function definition in the global context. Currently the xsd does not have globals. All expressions are bound to a specific drgElement, not global. The Import element probably needs to be modified to support this also.

Defer to DMN 1.5

Defer to DMN 1.5

FEEL function definitions are defined as lexical closures, which simply means that names in the function body must be in scope, and that scope includes the function parameters and, just like any other decision logic, it includes the information requirements and the knowledge requirements. This is very handy. For example, it allows the logic of a BKM to reference 100 Input Data items by name, without requiring that each invocation pass in 100 parameter bindings.

In order for this to work, the BKM would model 100 Information Requirements on the 100 Input Data items, instead of modeling them as parameters. The boxed invocations would not have 100 rows of repetitive binding information. We must extend the MM and Table 2 to allow a BKM to have information requirements.

Defer to DMN 1.5

Defer to DMN 1.5

in typographic literals, italics are strings and bold italics are date literals, but in 10.3, italics are feel syntactic elements and bold are semantic elements. Better to have different notations

Defer to DMN 1.5

Defer to DMN 1.5

The notion of a 'type' or ItemDefinition is in the metamodel (with some pending issues) and in the semantics and concepts, but little is in the notation. Thus, we have notation that allows you to execute an expression with actual arguments, but no notation to allow validation based on type information without actual values.

We have most of the pieces, so it should not be difficult. E.g., individual values can be number, string, date and time, etc. We can allow numeric ranges using our unary tests, e.g. '>0', '[10..30)', etc. We can allow LOVs using "abc", "def", "ghi". These can be 'simple items', and we can also define structures using something similar to boxed contexts.

Defer to DMN 1.5

Defer to DMN 1.5

In XSD, business context pointers are duplicated in both directions. E.g. decisionOwner and decisionMaker point to organizationalUnit, which in turns has pointers back the other way. This duplication adds no new information, just potential for internal inconsistency. I suggest omitting one of these directions; the other one is easily extracted from the serialization by XPATH.

Defer to DMN 1.5

Defer to DMN 1.5

DMN 1.1 should provide examples of all types of decision model allowed by the standard, both graphically (DRD and decision table, where appropriate) and XML serialization. Currently missing:
1. decision tables with an expression (more than a name) in inputExpression and outputExpression.
2. decision tables with inputEntry or outputEntry referencing a "name" as defined by S-FEEL, i.e. not just a literal.
3. DRD and decision table involving what Vanthienen calls "action subtables". All existing examples are "condition subtables".
4. Serialization of crosstab format tables.
5. Representation of literal values vs names in serialization.
6. Representation of PMML and FEEL in the serialization.

Add second example to Chapter 11

See attached word doc for spec changes. See attached zip file for additions to examples.zip.

If a function definition is the value expression of an information item, then that information item should have an item definition that gives the type of the function definition. E.g., the type of a function of two numeric arguments that returns their sum should be something like function(number, number) returns number but we have no way to express such an item definition

add FunctionItem to ItemDefinition MM, XSD, and spec text

See attached word doc

Group is an unfilled rectangle enclosing various elements in the DRD, with meaning defined by the modeler. It follows the usage defined by BPMN, an “artifact” with no operational semantics, simply an annotation of the model.

Add Group to spec, MM, and XSD fashioned after BPMN

See attached word doc

Clause 10.3.2.9 shows FEEL number values as mapped to XML decimal, integer, and double, but the only mapping to Java is to BigDecimal. The appropriate mapping to Java, like the appropriate mapping to XML, depends on the range and intent of the data element. BigDecimal is rarely used for anything but currency. Java int and double are much more likely to be appropriate for most data items. The mapping of number to Java should be just as flexible as the mapping to XML and PMML.

RTF 1.3 is ending

Thank you for reporting the issue; it is likely valid but unfortunately the DMN 1.3 revision task force ran out of time before a member was able to resolve it. The issue will be deferred to the next revision task force.

in typographic literals, italics are strings and bold italics are date literals, but in 10.3, italics are feel syntactic elements and bold are semantic elements. Better to have different notations

RTF 1.3 is ending

Thank you for reporting the issue; it is likely valid but unfortunately the DMN 1.3 revision task force ran out of time before a member was able to resolve it. The issue will be deferred to the next revision task force.

The notion of a 'type' or ItemDefinition is in the metamodel (with some pending issues) and in the semantics and concepts, but little is in the notation. Thus, we have notation that allows you to execute an expression with actual arguments, but no notation to allow validation based on type information without actual values.

We have most of the pieces, so it should not be difficult. E.g., individual values can be number, string, date and time, etc. We can allow numeric ranges using our unary tests, e.g. '>0', '[10..30)', etc. We can allow LOVs using "abc", "def", "ghi". These can be 'simple items', and we can also define structures using something similar to boxed contexts.

RTF 1.3 is ending

Thank you for reporting the issue; it is likely valid but unfortunately the DMN 1.3 revision task force ran out of time before a member was able to resolve it. The issue will be deferred to the next revision task force.

In XSD, business context pointers are duplicated in both directions. E.g. decisionOwner and decisionMaker point to organizationalUnit, which in turns has pointers back the other way. This duplication adds no new information, just potential for internal inconsistency. I suggest omitting one of these directions; the other one is easily extracted from the serialization by XPATH.

RTF 1.3 is ending

Thank you for reporting the issue; it is likely valid but unfortunately the DMN 1.3 revision task force ran out of time before a member was able to resolve it. The issue will be deferred to the next revision task force.

10.3.2.9.2 says "The global context is a context provided for convenience and 'pre-compilation'. Any number of expressions can be named and represented in a FEEL context m. The syntactic description m of this context can be evaluated once, that is, mapped to the FEEL domain as m, and then re-used to evaluate many expressions." For example, you might want to put a Relation used as a multi-dimensional constant in the global context. Or you might want to put a reusable function definition in the global context. Currently the xsd does not have globals. All expressions are bound to a specific drgElement, not global. The Import element probably needs to be modified to support this also.

RTF 1.3 is ending

Thank you for reporting the issue; it is likely valid but unfortunately the DMN 1.3 revision task force ran out of time before a member was able to resolve it. The issue will be deferred to the next revision task force.

literal expression is used in MM, and textual expression is used in grammar. Let's use 1 consistently, but check that they are really the same concept.

RTF 1.3 is ending

Thank you for reporting the issue; it is likely valid but unfortunately the DMN 1.3 revision task force ran out of time before a member was able to resolve it. The issue will be deferred to the next revision task force.

FEEL function definitions are defined as lexical closures, which simply means that names in the function body must be in scope, and that scope includes the function parameters and, just like any other decision logic, it includes the information requirements and the knowledge requirements. This is very handy. For example, it allows the logic of a BKM to reference 100 Input Data items by name, without requiring that each invocation pass in 100 parameter bindings.

In order for this to work, the BKM would model 100 Information Requirements on the 100 Input Data items, instead of modeling them as parameters. The boxed invocations would not have 100 rows of repetitive binding information. We must extend the MM and Table 2 to allow a BKM to have information requirements.

RTF 1.3 is ending

Thank you for reporting the issue; it is likely valid but unfortunately the DMN 1.3 revision task force ran out of time before a member was able to resolve it. The issue will be deferred to the next revision task force.

Figure 10 on page 25 with text "The encapsulated decisions are therefore

"

Figure 11 on page 26 with text "The encapsulated decisions for this services are

".

Table 20 on page 56:

• "outputDecisions: This attribute lists the instances of Decision required to be output by this DecisionService".
• "encapsulatedDecisions: If present, this attribute lists the instances of Decision to be encapsulated in this DecisionService".

For us it is unclear what decisions should be stored in the DMN model as encapsulated decisions. Must the output decisions also be included in the list of encapsulated decisions (as stated on page 25, 26)? Or does the list of encapsulated decisions only hold the decisions contained in the lower compartment of a decision service (as mentioned on 56 since encapsulatedDecisions seems to be optional)?

RTF 1.3 is ending

Thank you for reporting the issue; it is likely valid but unfortunately the DMN 1.3 revision task force ran out of time before a member was able to resolve it. The issue will be deferred to the next revision task force.

We lack examples of input expressions that are not simple names, input entries that reference variables, and output entries that are more than simple values.
For example, could change fig 67, Eligibility column, from Eligibility||INELIGIBLE|ELIGIBLE to Eligibility=ELIGIBLE||false|true
In Fig 71, add a context entry with name 'Adult' and value '18'. Change the entry <18 to <Adult.
In Fig 83, rename to Adjusted Disposable Income. Add parameter list (Risk Category, Disposable Income). Change output entries to 0.6 * Disposable Income, 0.7 * Disposable Income, 0.8 * Disposable Income, change invocation entry in Fig 82 name to Adjusted Disposable Income and pass Disposable Income. Change Affordability calculation to 'if Adjusted Disposable Income > Required Monthly Installment'

add more examples

more suggested examples

Here is a slight one (typo error) table 6.1, first row: an « e » is missing into « Knowledge ».

N.B. It is more elegant to not cut a table on several pages, as it was done before, but it is another matter.

Unable to find the issue

I do not see a table 6.1 in the spec, nor do I find a 'Knowledge' with missing 'e'.

This may include both the DRD and boxed expressions (decision tables, etc)

Add Diagram Interchange Chapter and XSD

Add DI chapter and necessary changes to existing spec text.

XSD Changes based on CMMN 1.1 DI:
https://github.com/omg-dmn-taskforce/omg-dmn-spec/commit/d0f469e69a12ccd268c0e24e6d278f7dc6ca9ad9

A more detailed changelog can be found in this Git branch:
https://github.com/omg-dmn-taskforce/omg-dmn-spec/commits/fm-dmn12-62-diagram-interchange

It should be possible to re-use a decision subgraph by extracting it to another diagram and replacing it with a reference and an invocation to the extracted decision in the original diagram.

Given the current MM, I see two ways of making that possible:

• introducing a sub-type of BKM that allows referencing a decision in another diagram
• introducing a sub-type of Invocation that allows referencing a decision in another diagram

The attachment illustrates the missing and proposed re-use possibilities of the "affordability calculation" (from the example section). The attached example uses the second option of the two.

Allow Decision Service to be invoked from decision logic in a decision model

Revised text is attached as Invocable (Issue 10) - OMG Proposal (version 14).
XML Schema changes described by: https://github.com/omg-dmn-taskforce/omg-dmn-spec/commit/82d171eafa8be4e5659b6e47b46a76a025f15d0d
All figures will be separately attached in the final report as .svg files

Argument for Backward Compatibility
The newly added class (complexType) Invocable is abstract and thus not in the serialization. Concrete attributes are unchanged (except made optional).
Note that before this change, there was no standard way to serialize a decision model containing a decision service; hence, w.r.t. decision services, there is no compatibility to maintain.

A decision with logic: if x then y else z has an unconditional requirement on x but a conditional requirement on y and z. This is useful to represent in the notation (perhaps as a tick mark on the requirement arc in homage to BPM's unconditional gateway exit arc) and in the MM. It could prove very useful to implementors, who could use data-driven dataflow to activate the decision when x is available, but to produce y or z on demand.

withdrawn - no clear proposal or compelling use case

withdrawn by submitter

a. In clause 9.2, para 5, first sentence, "date and time" should be in italics.
b. Why is date and time type excluded from S-FEEL? This restriction makes XSD mapping problematic.

No SFEEL changes

Not enough usage of SFEEL to justify change at this time.

We have 2 notations for input data

1. an oval shape

2. the name of input data in the requiring decision (so-called Listed Input Data)

As far as I see, there is nothing in the MM to distinguish these cases,

so there is no way to interchange the intended notation.

Proposed: add a new attribute to Decision named listedInputData of type boolean.

DI supports interchange of listed input data on diagrams

this issue subsumed and resolved by diagram interchange (DMN12-20)

The glossary is not only for CL2. CL3 adds contexts, relations, functions, etc. to the repertoire of boxed expressions

enumerate all the expressions

see revised text.

In the metamodel/XSD, decision logic is contained in a decision element, hence not reusable. To reference reusable decision logic, decision invokes BKM, which is reusable. The semantics are clear, but representation of the decision and BKM as separate graphical elements in DRD is visually inefficient. It creates unnecessary clutter in the DRD (Fig 63 is a prime example). BPMN solved this problem in a better way, and I suggest DMN should allow the same. In BPMN a subprocess definition is embedded in the parent process so to reference reusable subprocess, it uses a call activity. The call activity shape is same as subprocess except it has a thick border style. The diagram does not contain both subprocess and call activity, just one or the other. I would like to propose that a decision shape in DRD with a thick border be used to mean the decision invokes a BKM (with name generated from the decision name). No metamodel or schema changes required; this is merely alternative graphical notation. In a DMN tool, typically clicking on the decision will hyperlink to the decision logic (DT or literal expression), whether that logic is embedded in the decision or reusable. This distinction is mostly important to programmers, not modelers, so should not unnecessarily complicate the diagram.

subsumed by invocable decision service

no longer an issue after invocable decision service feature added.

The figure 8.18 is NOT the figure of the DecisionTable class diagram (i.e. metamodel).
This diagram was good into the previous beta versions of DMN specification.
This "wrong" diagram was already used as figure 6.8 on page 32 (Decision class diagram i.e. metamodel).

The issue does not exist in the current specification

The MM, now Figure 51, seems fine in OMG formal/2016-06-01

I am developing an application that imports DMN files generated by http://demo.bpmn.io/dmn, in order to get some information about the descision tables.

But, when I try to use the XSD schema to validate the DMN file, I get some errors, for example:

unexpected element (uri:"http://www.omg.org/spec/DMN/20151101/dmn11.xsd", local:"definitions")

Apparently, the path is no longer available. Instead, the OMG site is using http://www.omg.org/spec/DMN/20141115/dmn.xsd

this appears to be a tool issue. The spec is correct.

see further details in the issue.

FEEL function definitions are defined as lexical closures, which simply means that names in the function body must be in scope, and that scope includes the function parameters and, just like any other decision logic, it includes the information requirements and the knowledge requirements. This is very handy. For example, it allows the logic of a BKM to reference 100 Input Data items by name, without requiring that each invocation pass in 100 parameter bindings.

In order for this to work, the BKM would model 100 Information Requirements on the 100 Input Data items, instead of modeling them as parameters. The boxed invocations would not have 100 rows of repetitive binding information. We must extend the MM and Table 2 to allow a BKM to have information requirements.

No agreement about whether this is a good or bad idea

Defer until we can agree to resolve or close.

If a function definition is the value expression of an information item, then that information item should have an item definition that gives the type of the function definition. E.g., the type of a function of two numeric arguments that returns their sum should be something like function(number, number) returns number but we have no way to express such an item definition

needed, but out of time

Should enhance item definition so it can model function types because that is the type of a BKM's logic

literal expression is used in MM, and textual expression is used in grammar. Let's use 1 consistently, but check that they are really the same concept.

no proposal but possibly still an issue, defer.

Literal expression v. textual expression may be a distinction without a difference.

In XSD, business context pointers are duplicated in both directions. E.g. decisionOwner and decisionMaker point to organizationalUnit, which in turns has pointers back the other way. This duplication adds no new information, just potential for internal inconsistency. I suggest omitting one of these directions; the other one is easily extracted from the serialization by XPATH.

cannot change schema for compatibility reasons

reconsider in 2.0?

DMN 1.1 should provide examples of all types of decision model allowed by the standard, both graphically (DRD and decision table, where appropriate) and XML serialization. Currently missing:
1. decision tables with an expression (more than a name) in inputExpression and outputExpression.
2. decision tables with inputEntry or outputEntry referencing a "name" as defined by S-FEEL, i.e. not just a literal.
3. DRD and decision table involving what Vanthienen calls "action subtables". All existing examples are "condition subtables".
4. Serialization of crosstab format tables.
5. Representation of literal values vs names in serialization.
6. Representation of PMML and FEEL in the serialization.

Need comprehensive set of examples, defer.

Perhaps the next task force can extract some examples from some test cases and add them to the spec.

Clause 10.3.2.9 shows FEEL number values as mapped to XML decimal, integer, and double, but the only mapping to Java is to BigDecimal. The appropriate mapping to Java, like the appropriate mapping to XML, depends on the range and intent of the data element. BigDecimal is rarely used for anything but currency. Java int and double are much more likely to be appropriate for most data items. The mapping of number to Java should be just as flexible as the mapping to XML and PMML.

still no proposals in 4 years, defer.

FEEL chose the simplicity of a single numeric type. Possibly some vendors have extensions, but none has volunteered to make a detailed proposal. There are many numeric builtins and operators; a complete proposal would be somewhat tedious.

Group is an unfilled rectangle enclosing various elements in the DRD, with meaning defined by the modeler. It follows the usage defined by BPMN, an “artifact” with no operational semantics, simply an annotation of the model.

Under discussion but no proposal, defer.

See issue comments.

The notion of a 'type' or ItemDefinition is in the metamodel (with some pending issues) and in the semantics and concepts, but little is in the notation. Thus, we have notation that allows you to execute an expression with actual arguments, but no notation to allow validation based on type information without actual values.

We have most of the pieces, so it should not be difficult. E.g., individual values can be number, string, date and time, etc. We can allow numeric ranges using our unary tests, e.g. '>0', '[10..30)', etc. We can allow LOVs using "abc", "def", "ghi". These can be 'simple items', and we can also define structures using something similar to boxed contexts.

no proposal for this missing feature, defer

Still seems useful.

in typographic literals, italics are strings and bold italics are date literals, but in 10.3, italics are feel syntactic elements and bold are semantic elements. Better to have different notations

editorial only, can defer

we should identify some typographical conventions and use them consistently.

10.3.2.9.2 says "The global context is a context provided for convenience and 'pre-compilation'. Any number of expressions can be named and represented in a FEEL context m. The syntactic description m of this context can be evaluated once, that is, mapped to the FEEL domain as m, and then re-used to evaluate many expressions." For example, you might want to put a Relation used as a multi-dimensional constant in the global context. Or you might want to put a reusable function definition in the global context. Currently the xsd does not have globals. All expressions are bound to a specific drgElement, not global. The Import element probably needs to be modified to support this also.

did not write proposal to remove global context, defer.

Probably global context can/should be removed, but we did not work out the details.

The input and output entries in a decision table are expressions. The expressions are serialized as part of the rule 'clause', with an ID. In the rules, the expressions are represented by IDREF. This level of indirection is undesirable for many reasons:
1. the expressions are small text strings, typically no bigger than an ID
2. copy/paste of rules across decision tables won't work (IDs are different)
3. diff of decision tables is complicated, due to indirection
4. there is no level of indirection in the notation - the rules appear to contain the expressions, not a reference to them.
5. complicates JSON serialization
Proposed: In Figure 44, move Expression ownership from Clause to DecisionRule, and follow logical implications in text and xsd.

remove indirection, split Expression into LiteralExpression and UnaryTests

DecisionRules are ordered in a DecisionTable. By also ordering the inputs and the outputs (requires splitting Clause into InputClause and OutputClause, we can move the inputEntries and outputEntries under DecisionRule and avoid all IDREFs within a decision table, significantly simplifying serialization. Also, we combine a proposal for DMN11-84, which is merged with this issue.

Allow DMN to specify and interchange definitions of decision services, along the lines proposed in Annex B.

Definition, notation and examples for Decision Service

Complete proposal in the attached document

Now that we have decision services, this is a much better and simpler feature for which to define execution semantics. We can simplify and improve the usefulness of 10.4.

replace 10.4 with Execution Semantics of Decision Services

This proposal depends on adoption of DMN11-143. I think we should specify the execution semantics of decision services. This can replace 10.4, which is the execution semantics of DRGs, which is problematic because the InputData doesn't have much meaning except as the parameter of a decision service. No MM or XSD changes.

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.

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.

DMN nees to provide a standard way for vendors to serialize extensions (Vendor Extensions). It is proposed that a schema resembling what was done in BPMN and CMMN be used.

Why DMN should be extensible

The extension mechanism allows adding Custom Metadata to models in a way that it MAY be interchanged between vendors. Concretely this means that it is possible to add custom attributes and elements in a custom namespace to the XML interchange format.

Example of a custom attribute

<DecisionTable id="table1" custom:audit="true" xmlns:custom="http://custom.org/auditing" ...>

Example of a custom element

<DecisionTable id="table1" ...>
  ...
  <extensionElements>
  <custom:audit xmlns:custom="http://custom.org/auditing">
    <custom:audit-level>full</custom:audit-level>
    <custom:retention>unlimited</custom:retention-level>
  </custom:audit>
  </extensionElements>
  ...
</DecisionTable ...>

Vendors need to be able to add custom Metadata

Vendors need to be able to decorate the model with additional metadata. Vendors may implement additional usecases which the standard as such does not address like historization, reporting, fine-grained editing authorizations amd restrictions, ...
Having the possibility to put this directly into the interchange format allows vendors to roundtrip models. If all vendors participating in the roundtrip re-export the other vendor's extensions than they are not lost during roundtrip which leads to a better inter-operatbility experience for the user.

Users need to be able to add custom Metadata

The possibility to extend the model with custom metadata has also proven to be vital to camunda users and customers in the past.
Many users extend the model with their custom attributes and elements to be able to implement custom extensions.
Some have custom metadata for their execution environment others for auditing and reporting.
It is very important at users are able to put custom metadata into the xml file.

FAQ

Is BPMN's extension mechanism perfect?

Probably not. At the XML level it works extremely well. At the Meta Model level it could certainly be improved.
But the question is whether the practical advantages of a "slightly better approach" would outweigh the advantages of consistency among these standards.

Does that mean that Vendors can just ignore the Standard?

No. In order to be compliant, vendors need to implement the standard in the way mandated by the standard.
If they use custom extensions for realizing non-compliant behavior then they are non-compliant.

Do tools need to understand the extensions created by other vendors?

No. Tools do not need to understand extensions created by other vendors. What's more, the specification text explicitly states that tools do not event need to round-trip extension elements by other vendors while still being compliant. There is also no compliance level at which a tool is required to support this. A tool is fully compliant if it is not able to round-trip extension elements.

Has this actually been successful in BPMN?

Yes. Extension mechanisms are heavily used and there is ample empiric evidence of this being a successful concept. To see it in action have a look at the demos and test cases of the BPMN Model Interchange Working Group (MIWG) at the OMG.

For comparison see also the CMMN 1.1 proposal CR-20.

Add new extension capability to DMN as per that of BPMN and CMMN

Based on the extension capabilities of BPMN and CMMN the following changes need to be done:

1. Add two rows to table 3
2. Add a new figure of the metamodel showing the relation between DMNElement and the extension mechanism in section 6.3
3. Figure 15 - DMNElement class diagram needs to be updated with ExtensionElements and ExtensionAttribute depiction.
4. A complete new section 6.3.14 Extensibility needs to be added. This will have a ripple effect on table and figure numbering. Figure of the metamodel should be inserted after the first paragraph of section 6.3.14, in the metamodel we need to add the two classes described
5. Some changes needed to DMN.xsd, which already contains this mechanism

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.

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

Need to reword to use new MM associations

spec text update to decision rule MM in 8.3.3

This issue describes the changes to Decision Rule meta-model from referencing conditions and conclusions to embedding them.

We are required to vote on the beta 1.1 documents, submitted with this report. See "Deliverables" section of this report.

submit attached beta documents to OMG

OMG requires a vote on beta documents.

The reference to classes BMM::Objective, BPMN::Process and BPMN::Task does not seem to work in the metamodel XMI file

unable to find more information about this issue

Did not hear back from Pete and nobody on RTF is an XMI expert. Not even sure if this still applies.

issue 60 has identified 2 critical but easy to fix problems with the beta2 xsds. An even simpler fix is to combine the 2 xsds. Separate xsds invites the problems, and it has been reported that popular XML tools don't like the 2 xsds because it is the included xsd that has the document root. Also, DMN11-89 proposes to use FunctionDefinition (now in dmn3) to consistently serialize all BKM logic.

Merge contents of dmn3.xsd into dmn.xsd

Merge contents of dmn3.xsd into dmn.xsd and delete dmn3.xsd.

The BKM MM defines parameters but has no notation for them. Meanwhile, the FunctionDefinition also defines parameters that duplicate the BKMs. Also, 10.2.1.7 says a BKM's logic must be a FunctionDefinition or a DT, but Table 11 syas a BKM's logic msut be the BODY of the function it defines. To straighten out thsi mess, I propose
1. remove params from BKM MM
2. require BKM to contain a FunctionDefiniition, so that the params will always be defined, and always at the decision logic level
3. allow FunctionDefinition whose body is a DT with simple inputExpressions that reference all parameters, and only parameters, in order, to be denoted using the DT only

BKM value expression is a function definition

change BKM metamodel and XSD to associate BKM to FunctionDefinition instead of separate parameters and body

There are many occurrences of the phrase 'In DMN 1.0'. Now that we are writing DMN 1.1, this phrase is no longer simply tedious and redundant, but now it is also wrong. All occurrences should simply be deleted. And, all occurrences of 'In DMN' should be deleted. They are redundant. This is the DMN specification! Everything described is by default 'in DMN'!

Remove superfluous refs to DMN and all refs to DMN 1.0

Remove all unnecessary use of "In DMN..."
All remaining refs to DMN 1.0 shoul dbe updated to 1.1

In the chapter 11 example, Fig 63 contains an information requirement connector linking Adjudication to Routing. But in reality Routing is not an input to Adjudication. What is meant is that Adjudication is only performed if Routing has certain output value. That relationship is what Vanthienen calls an action subtable, whereas information requirement reflects a condition subtable relationship. Still it is useful to depict such relationships in DRD. I suggest adding a new connector type, association - an artifact as meant by BPMN, i.e. no operational semantics just annotation - to reflect it. A text label could indicate a particular output value that enables the dependent decision.

Close - no change required

Consensus is not to add new type of information requirement connector.

DRD lacks elements to hold modeler-provided annotation in the diagram. These help clarify the meaning of the decision model but otherwise have no operational semantics. In BPMN they are called "artifacts".

Add artifacts textAnnotation and association (connector) to DRD, metamodel, and xsd

See comments on DMN11-42. The proposed annotation elements are essentially copied from BPMN 2.0.

XSD changes:
https://github.com/omg-dmn-taskforce/omg-dmn-spec/commit/489a726acb94837ef9b926c199f31e86e5a71ceb

In the MM, Fig 15, all classes inherit the optional name attribute. Thus, any DMNElement may or may not have a name. What is closer to the truth, is that some DMNElements MUST have a name, and others MUST NOT. Attached is proposed MM that splits the elements into the named and unnamed. There will be numerous text changes, especially to explain that decision tables, being expressions, do not have names. The apparent 'names' of expressions like DTs are really the name of the Information Item that has said expression as its valueExpression. It is dangerous (misleading) to supply a name for an expression, because it may appear that one could refer to the named expression's value by that name. But you cannot. You can only refer to an Information Item by name in an expression.

define NamedElement subclass of DMNElement

Revised text, MM figures, and XSD (github links)

In XSD, top-level element Import is used to make top-level elements in external DMN, XSD, and possibly other types of files visible to the decision model. Import also is part of tLiteralExpression as a way to import value expressions, but it needs additional information. Propose to give this element a different name and type:
In tLiteralExpression, replace Import with importedValues, type tImportedValues. Add tImportedValues as follows:
<xsd:complexType name="tImportedValues">
<xsd:complexContent>
<xsd:extension base="tImport">
<xsd:sequence>
<xsd:element name="importedElement">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="expressionLanguage" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>

replace Import in tLiteralExpression with importedValues, new type

Revise spec, MM Fig 26, and XSD as directed.

These are redundant. InputVariable is a pointer to a variable definition, but any expression MUST only reference a variable with unique name in scope, so the pointer is redundant. An expression referencing a name not defined uniquely in scope is an error.

Similarly, in tExpression, itemDefinition (a pointer to ItemDefinition representing the expression's output datatype) is redundant. The Decision or BKM element also has OutputDefinition, pointer to ItemDefinition that defines the datatype of the output expression. Any variable referenced by an any literal expression also already has a datatype defined by InformationItem.

move inputVariable and itemDefinition from Expression metamodel to InputData and Decision (and correct XSD and explanatory text)

Revise spec, MM, and XSD as indicated.

This issue also relates to isComplete.
Level 3 decision tables may specify a default output entry to be selected if no rules match. I dont believe this is allowed for level 2. In any case, the default output entry is missing from both boxed expression and xsd for decision table, possibly missing from metamodel also.

Add decision table default output

Add attribute defaultOutputEntry of type tLiteralExpression

itemDefinition is referenced to a base type defined by either a typeDefinition or typeRef. 7.3.2 says typeDefinition is "a String that defines the data structure", but it simply names a built-in type, does not define a structure. It also says typeRef is "a String that references a built-in data type... or a data structure defined at the top level in an external document", but those statements are incorrect as well. Built-in types are named by typeDefinition, typeRef is not String. Structured types are defined by itemComponent and referenced by typeRef, usually NOT in an external document. So this text is completely wrong. This issue also affects how external references are defined, via namespace prefix or filename, via ID or element name. Referenced typed by DMNElementReference are ambiguous and inadequate to cover the range of external references required.

simplify and correct MM and XSD for ItemDefinition

Proposal is to Merge and close DMN11-25, 56, 57, 71.

The latest MM diagram (attached) shows ItemDefinition containing itemComponents, which are also tItemDefinition. It also shows ItemDefinition has attribute typeRef and typeDefinition. It is better to have a consistent referencing scheme via typeRef, so typeDefinition should be removed from the MM. Otherwise, the MM is correct, but the XSD is not consistent with this.

The corrected XSD deletes tItemComponent and defines itemComponent as tItemDefinition. This makes ItemComponent recursive, which resolves and closes DMN11-56 and DMN11-71.

Also, to make ItemDefinition consistent with DMN11-67, allowedValue is renamed allowedValues, type tUnaryTests, maxOccurs=1.

It is important that types be referenced consistently via typeRef or itemDefinition, whether the type is:

(1) a base type (without restriction) in the ItemDefinition's typeLanguage; (2) a custom type (including base types with allowed values) defined in the current Definitions; (3) a custom type defined in an imported DMN model; or (4) a type defined in an imported XSD (or WSDL or other type language). Normally types have names unique in their namespace, and outside of DMN they do not have ids. Therefore tDMNElementReference, a pointer to id, will not work; the best way to reference types is by standard QName. This also resolves 11-25, since now Definitions/@namespace has a purpose.

A base type in the specified typeLanguage should not require ItemDefinition, nor should an imported type. ItemDefinition is required only for custom types defined in the current document.

QName is namespace-prefixed pointer to either ItemDefinition/@name (or, for imported XSD type, to xsd:simpleType/@name or xsd:complexType/@name). The prefix must be declared in DMN via xsd:schema/@xmlns:[prefix]="[namespace URI]". This means references to FEEL base types must use prefix for the FEEL namespace, just as references to XSD base types must use prefix for the XSD namespace. For imported DMN documents, the prefix must reference the Definitions/@namespace attribute of the import.

ItemDefinition defines the datatype of each variable used in DMN expression. As currently defined, it "works" for FEEL base types, although inefficiently (since it has both @name and typeDefinition, two strings that both name the type). It "sort of works" for imported XSD complex types, as long as you ensure the FEEL elements have valid XML element names (e.g. no spaces, etc.) In that case ItemDefinition/@name names the FEEL type and typeRef is a QName pointer to complexType defined in imported XSD. In the general case, for FEEL complex types defined inside the DMN model, it doesn't work very well.

It is clumsy for defining data structures more than 2 levels deep. ItemDefinition may contain a list of itemComponents, each with a name and pointer to another ItemDefinition. So to define a type that is 3 levels deep, you would have to define one or more 2-level ItemDefinitions, and then the top-level ItemDefinition would use those as itemComponents and point to their ItemDefinitions. Also, the current schema is missing cardinality information (in xsd, @minOccurs and @maxOccurs), important in the definition of a complex type:

I propose a change to tItemDefinition by changing tItemComponent. Child itemComponents are now contained in a parent itemComponent, not referenced, just like a complexType in XSD. I would like to make ItemDefinition/@name a required attribute, since it names the type, but am unable to do this without making it required for all tDMNElement. So the spec should just say, even though optional in schema, ItemDefinition/@name is required.

See attached doc with diagram. I will provide also revised dmn.xsd.

no longer relevant

no longer relevant

In Chapter 11 examples, most boxed invocations - Fig 76, 78, 80, 81 - have format in which the "tab" names the invoking element and the top line of the box, above the parameter list, names the invoked element. Fig 82 is different. The tab names the invoking element, the top line of the box lists the parameters of the invoking element, then the parameter list, and the bottom row names the invoked element.

That seems inconsistent and a mistake.

issue seeking clarification only

issue was clarified in comments

All reviewers, please log minor typos here.

errata found in review of V4 of clean spec

see revised text. Some of these are clearly more than typos, more like omission of some editing instructions.

The top box of a DT should display the Information Item determined by the table, i.e. the name of the decision or BKM for which the DT is the logic.

In Figs 32, 34 and 36, "table name" should read "information item".

We should also clarify by adding to the first bullet point in 8.1 "Usually this will be the name of the Decision or Business Knowledge Model for which the Decision Table provides the decision logic."

Correct figs 29, 31 & 33 and clarify DT information item

Correct figs 29, 31 & 33 (32, 34 & 36 in v3) by replacing "table name" with "information item name"

Clarify the typical use of this box in the Introduction to Decision Tables (8.1)

Decision table notation has an output name (renamed output label by DMN11-43) but there is no place in the MM for this label. Cannot use output clause name because this is the name of the component in a multiple component output.

add outputLabel attribute to DecisionTable MM (and xsd)

see attached MM

At the decision logic level, one does not 'invoke' a BKM; rather, one invokes the FunctionDefinition that is contained in the BKM. How does one refer to the FunctionDefinition by name? Logic refers to InformationItems by name, it does not refer to the DRGElements directly by name. Therefore, a BKM should contain an InformationItem of the same name whose value expression is the FunctionDefinition contained in the BKM.

Add InformationItem child to BKM

see attached MM figure. Need git pointer to XSD.

when we removed the redundant variable references from Expression, we also removed the redundant InformationItem (now typeRef) reference. The result type of an expression is redundant because you can always compute the result type from the input types, and a good tool will have to perform this computation anyway in order to verify that the redundant value is correct. However, simple tools may benefit from a declaration of the expected type of an expression, and the benefit may outweigh the drawbacks of redundancy, hence the issue.

add typeRef attribute to Expression, and derived association to ItemDefinition

Affects MM, XSD, and spec text

The InformationItem has a typeRef, which may ref ItemDefinition (derived association)

replace associations to InformationItem with typeRef (datatype) and derived associations

This corrects DMN11-86, which is already on ballot 6. Also, replace attached figures, relevant changes highlighted.

section 6.3.10 describes the KnowledgeSource metamodel but has no diagram. KnowledgeSource and AuthorityRequirement is shown in figs 17,19 in a confusing manner and need correction.

Add Knowledge Source diagram and clean up KnowledgeSource in Figs 17 and 19

p38 says "An instance of Definitions has a namespace, which is a String. The namespace identifies the default target namespace for the elements in the Definitions and follows the convention established by XML Schema." I think this is mistaken. The convention established by XML Schema relates to schema/@targetNamespace in the XSD. Definitions/@namespace "follows" (or did in the beta version) the convention established by BPMN 2.0, which is specifically for identifying external references as a variant of QName, using the prefix of the declared target namespace and the ID of the element in that namespace. DMN FTF no longer uses that convention, so Definitions/@namespace has no purpose, although it is a required attribute. I would like to see a return to the beta format of external references (making Definitions/@namespace relevant), since there are explicit pointers from DMN to BPMN processes and tasks, and it makes no sense for DMN to use a different referencing mechanism (based on filename not namespace) than the one BPMN uses to reference other BPMN models.

treat namespace as part of the qualified name for imported elements

presumably if a decision D requires an imported decision E from namespace S, then D's logic can refer to S.E (but where do we say that?)

The S-FEEL and FEEL grammars of chapters 9 and 10 suggest a much wider range of allowed syntax in decision tables than are illustrated in any examples of the spec. For example, input entries and output entries may reference one or more "names" - presumably variables - but in the examples they reference only literal values. Also, all examples of input expressions are simply variable names, not expressions. Additional text is needed to explain what is allowed and not allowed in decision table elements.

Text to explain constraints on decision table elements

These edits reflect grammar rule changes consistent with what is allowed in decision table elements under DMN11-49, resolving ambiguity of the terms "name", "expression", and other inconsistencies. This proposal was reviewed and agreed by Jan Vanthienen and myself and is ready for consideration by RTF.

If a DMN engine wants to provide a history of executed rules and clauses it needs to be able to reference them explicitly and have a human-readable label for them.

Add ID & label attributes by inheriting DMNElement

Spec text, MM and XSD should be changed to...

1. Let DecisionRule, InputClause and OutputClause inherit DMNElement.
2. Add an attribute label to DMNElement

This is related to DMN11-9. Expression class is defined in 7.3 and 7.3.1 as "return a single value when interpreted", but Decision (e.g. DecisionTable, concrete subclass of Expression) may return multiple values, in two ways. Compound output tables, and multi-hit Collect tables. I suggest removing the "single value" comment from definition of Expression, or applying it only to a different class than the superclass of DecisionTable.

Revise text to clarify Expression as "single value".

8.2.3 says "Input expressions are usually simple, for example, a name (e.g. CustomerStatus) or a test (e.g. Age<25)." However, under the S-FEEL grammar of 9.1, Age<25 is not a simple expression.

Revise SFEEL grammar to allow comparison in input expression

The revisions to S-FEEL grammar allow comparison in CL2 input expression. Attachments for discussion only and not part of proposal.

In 6.3.11 it says the notation for an information requirement is a plain arrow (from a required decision or input data). Arrows have no labels. Yet, table 14 shows a 'variable'. Presumably, this variable must be the same as the required decision or input data. Therefore, the variable should be removed from the InformationRequirement class, and the Decision class and InputData class should extend the InformationItem class. Variables are of type InformationItem.

Proposed: remove 'variable' from table 14. Make DRGElement extend InformationItem (figures 15, 17, 19, 20 and supporting text). Remove 'informationRequirement' and 'valueExpression' from table 20. Define the qualified name of an imported DRGElement to be of the form prefix . localPart where prefix must be distinct for each import element.

text changes to support move of InformationItem in MM/xsd

All figures showing decision tables need to be reviewed for correct hit policy and completeness codes. Many examples of UC and HC, which are not allowed in FTF version.

Remove completeness info from model and notation

we can define completeness of decision table rules, so that tools behave consistently, but there seems to be no clear need to model or notate completeness as a separate flag.

Many DT figures have a 'C' meaning Complete - these must all be removed.

FEEL datatypes are listed in 10.3.2.2. There is no such list. They are described below, in numbered sections, but not in a list.

replace ref to 10.3.2.2

rewording in revised text

No idea what the asterisks mean:
FEEL([1+1, 2+2]) *is [2, 4]*.
Proposed: replace with bold text between asterisks and remove asterisks.

Remove extraneous asterisks in 10.3.2.1

In clause 10.3.2.1, the example
FEEL([1+1, 2+2]) is [2, 4]
should not contain the asterisks, which are the result of a copy-paste error from JIRA.

Both dmn.xsd and dmn3.xsd at http://www.omg.org/spec/DMN/1.0/Beta2/ have problems. Two small issues prevent any use of dmn3.xsd. Four occurrences of type="tExpression" must be changed to type="tLiteralExpression" in dmn.xsd before it can be used to serialize decision tables and enumerations.

correct 2 issues in dmn3.xsd and 1 issue (4 occurrences) in dmn.xsd

Note that previous issue DMN11-91 has combined dmn3.xsd into dmn.xsd
2 occurrences of type="tExpression" to type="tLiteralExpression" made by this issue, and
2 occurrences of type="tExpression" to type="tUnaryTests" made for issue DMN11-81.

tAuthorityRequirement is incorrect. This element is contained in a decision, BKM, or KnowledgeSource. It should reference a KnowledgeSource, but in XSD it is a choice between requiredDecisionRef, requiredInputRef, and requiredAuthorityRef. Propose replace that choice with requiredAuthorityRef, pointer to the KnowledgeSource.

issues seeking clarification

issue clarified

I think this attribute is inappropriate. It reflects a model validation condition, not a design-time property. Moreover, it has default value "false", suggesting that any model that omits this attribute is intentionally inconsistent, which makes no sense to me.

This is a bit different from isComplete, where false could possibly be intentional at design time.

*Remove consistency info from model *

we could define the concept of consistency, so that tools will behave consistently, but it does not seem to belong in the model. Rules are either consistent or not, regardless of what some flag might say.

In decision table, Fig 27, 28, and third bullet on p66 refer to output expression. The other figures and the metamodel/schema refer to output name. I don't believe the output column heading can be an expression, just a name. Suggest replace "output expression" with "output name".

correct callouts in Figs 27&28, create additional figures for multiple outputs

attached figures to be replaced/inserted, with indicated revised neighboring text. No MM or XSD change.

For model interchange, BPMN has shown these attributes useful for identifying the tool name and version used to create the serialization. The importing tool may have special mappings for certain exporters.

add Definitions/@exporter, @exporterVersion

optional string attributes used to identify the tool that created the serialization, to aid in model interchange

The syntaxes defined in 9.1 (S-FEEL grammar) and 10.3.1.2 (FEEL grammar) do not permit decision table input entries to contain negative numeric values.

9.4.3: An input entry is a simple unary tests, defined using:

14: simple unary tests

13: simple positive unary tests

7: simple positive unary test

8: interval

18: endpoint

19: simple value

33: simple literal

36: numeric literal: [0-9] & “.”

I suggest a numeric literal should be allowed to start with a minus sign.

allow numeric literal to start with minus sign

according to the current grammar, numeric literals cannot have a minus sign, so neither can range endpoints, which are not arbitrary expressions.

The intent of ItemDefinition and itemComponent was to allow nested structures, such as Order contains a list of items, each item having an ID, Description, and Quantity. This isn't possible without having to create intermediate ItemDefitions and refs.

close as duplicate

close as duplicate

The spec states (8.2.12) "Incomplete tables may specify a default output. The default value is underlined in the list of output values." This needs two points of clarification:

(a) When a default is specified, a decision table is ipso facto complete. I propose we drop the word "incomplete".
(b) The spec does not say how to use defaults when the output is compound. Can we specify defaults for some output columns and not for others? If so, what value would the output take on default, for the columns where no default was specified? If not, we should say that defaults must be specified for all output columns or none.

close, addressed by other proposals

closed, no longer relevant

reference DMN FTF 1.0 Beta 2 with Change Bars.pdf document, OMG Document number dtc/14-11-36

On page 116, in clause 10.2.2.1, the Beta 2 document introduces Table 29, “String, date, time and duration comparisons, which shows one FEEL Expression: “2012-12-31 in (2012-12-25..2013-02-14)”. The example is invalid because FEEL has no literal syntax for dates. This example should use the date() built-in function.

Also, this table should be combined with Table 28, immediately above since they both give examples of the same kind.

Combine tables 28 & 29 and change formatting

revise text as indicated

Reference the DMN FTF 1.0 Beta 2 with Change Bars.pdf document, OMG document number dtc/14-11-36

On page 61, clause 6.3.12 describes the “Knowledge Requirement metamodel”. In the section on well-formed KnowledgeRequirements, the third bullet beginning “if the InformationRequirement element …” should instead read “if the KnowledgeRequirement element ….”

Correct typo in 3rd well-formed requirement of KnowledgeRequirement

On page 51, clause 6.3.12 describes the “Knowledge Requirement metamodel”. In the section on well-formed KnowledgeRequirements, the third bullet beginning “if the InformationRequirement element...” should instead read “if the KnowledgeRequirement element.…..”

reference DMN FTF 1.0 Beta 2 with Change Bars.pdf document, OMG Document number dtc/14-11-36

The bullet at the top of page 64, in clause 7.1, contains the following garbled sentence: “The variables that are used in the body of the function defined by a business knowledge model element in the DRG must be bound to the information sources each of the requiring decision.”

correct the typo

see revised text

I believe the XSDs are seriously messed up. On the surface, this would be apparent to anyone who tried to open the level 3 xsd in an XML editor, since the “include” fails right off the bat and the tool goes ding ding ding. Not only does it point to the wrong filename, but the namespace is different, not allowed with include. You can fix those things by making the namespaces match and fixing the filespec. Actually I don’t care that much about the level 3. I am more concerned with the 14-08-19.xsd, the Level 1 and 2.

That one has an element named ItemDefinition and another one named itemDefinition with different datatype, which is confusing. I believe that the latter is a pointer to the former. If so, you will have a lot less confusion by renaming the latter itemDefinitionRef.

But the problem with the XSD goes a lot deeper. Maybe it is my lack of understanding of the spec, I don’t know. I think the central problem is that tExpression (the datatype for inputExpression, inputEntry, outputEntry, range of allowed values, and many other elements) is just a list of inputVariables and possibly a single itemDefinition(Ref). It is NOT an expression, in natural language, S-FEEL, or anything else. Maybe the intent was to allow literal expressions, but the XSD does not reference tLiteralExpression, just tExpression. Or maybe the intent was to do like BPMN and make tExpression a mixed-content type, where the expression string is the direct content of the element, but the XSD does not say that, either. Or maybe the intent is to put the expression in the any ##other element or attribute? That would work but be very weird. Anyway, without that I think it would be an impossible challenge to serialize even the simplest decision table per the XSD. And maybe that is why there are no serialization examples in the spec.

overall, early list of possible xsd issues subsumed by more focussed issues

All the substantive have been addressed by other issues. This can be closed.

There are some issues with the XMI:

• The top level element should be a uml:Package not a uml:Model

• There is a proprietary namespace at the top of the file which should just be deleted: there is no longer any need for such a profile and it should be removed from the original MagicDraw model xmlns:cmof_Profile="http://www.magicdraw.com/schemas/cmof_Profile.xmi">