-
Key: DMN18-79
-
Status: open
-
Source: Goldman Sachs ( Dr. Octavian Patrascoiu)
-
Summary:
According to Section 7.3.3, ItemDefinition Metamodel, FEEL types no longer require a prefix (e.g., feel). However, the standard does not define the semantics of type resolution when a user-defined type has the same name as a FEEL type, when the type is defined locally or imported with an empty prefix.
-
Reported: DMN 1.7b1 — Tue, 1 Sep 2026 10:00 GMT
-
Updated: Tue, 1 Sep 2026 16:39 GMT
DMN18 — Unspecified resolution for name clashes of FEEL types
- Key: DMN18-79
- OMG Task Force: Decision Model and Notation 1.8 RTF