-
Key: DMN15-159
-
Status: closed
-
Source: Camunda Services GmbH ( Mr. Falko Menge)
-
Summary:
For tools to clearly identify the version of a DMN file or FEEL expression, the XML namespaces of DMN, DMN DI, and FEEL should be updated.
Namespace URIs must be backwards compatible with the scheme applied in previous versions for tools that support multiple versions in parallel. See:
- https://issues.omg.org/browse/DMN12-62?focusedCommentId=18500&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-18500
DMN13-191DMN14-166
DI and DC namespaces can stay the same as DMN 1.4 DI is still based on the same DI 1.1 specification and "OMG Policy for Versioning of Specification URIs, File URIs, and XML Namespaces in OMG Specifications", states explicitly:
Note: if a spec has many machine readable files, and only some of them change at a given specification version, then only the changed files should get new URIs. That could mean a mixture of URI date segment values for a given specification version..
-
Reported: DMN 1.4b1 — Tue, 14 Feb 2023 16:15 GMT
-
Disposition: Resolved — DMN 1.5
-
Disposition Summary:
Update Namespace URIs for DMN 1.5
Update namespace URIs with the following values:
XSD: https://www.omg.org/spec/DMN/20230324/MODEL/
XSD DI: https://www.omg.org/spec/DMN/20230324/DMNDI/
FEEL: https://www.omg.org/spec/DMN/20230324/FEEL/
XMI: https://www.omg.org/spec/DMN/20230324/DMN15.xmi
XMI DI: https://www.omg.org/spec/DMN/20230324/DMNDI15.xmiAll URIs conform with the OMG Policy for Specification URIs and Namespaces (smsc/2018-08-01) and are backwards-compatible with the namespace scheme applied in DMN 1.2, 1.3, and 1.4, which is important for vendors supporting multiple versions in parallel.
-
Updated: Fri, 26 Apr 2024 23:37 GMT
DMN15 — New Namespace URIs needed
- Key: DMN15-159
- OMG Task Force: Decision Model and Notation 1.5 RTF