DMN 1.3 RTF Avatar
  1. OMG Issue

DMN13 — Spaces and additional characters in names / identifiers

Open Closed All
  • Key: DMN13-58
  • Status: closed  
  • Source: Goldman Sachs ( Octavian Patrascoiu)
  • Summary:

    Having spaces and additional characters in useful from a user / BA perspective. However, is not good practice when it comes to implementing / designing programming languages / DSL. That's mainly due to ambiguities introduced by this approach. This is the reason none of the main stream PL do not support this feature.

    I suggest the following approach:

    • use spaces and additional characters in labels to improve the usability of FEEL (display labels in DRD diagrams)
    • if the name of a DMN entity (e.g. decision) contains a a space of additional character, use ' as delimiters. For example, 'A nice decision name ?'
    • reference ItemDefinitions by id and not by name to avoid ambiguities.
    • use the same delimiters to handle FEEL keywords as names (e.g. an OutputClause has name/label date)

    The same approach has been used successfully for SQL and OCL. OCL 2.4. specification is here
    http://www.omg.org/spec/OCL/2.4/
  • Reported: DMN 1.1 — Wed, 23 Nov 2016 10:58 GMT
  • Disposition: Closed; Out Of Scope — DMN 1.3
  • Disposition Summary:

    non-backward compatible change to FEEL and metamodel

    would need to wait for 2.0 RFP
  • Updated: Mon, 30 Mar 2020 19:50 GMT