DMN 1.2 RTF Avatar
  1. OMG Issue

DMN12 — Allow DMN DI to provide an alternative notation for Input Data (DMN 1.2)

  • Key: DMN12-272
  • Status: closed   Implementation work Blocked
  • Source: BPM Advantage Consulting ( Dr. Stephen White)
  • Summary:

    More and more, DMN is being used in conjunction with BPMN and CMMN. The recent work of the OMG BPM Healthcare initiative is a prime example. The Healthcare Field Guide being developed is anchored with the three standards as the way forward for developing healthcare clinical pathways. Feedback from this work and work being done for the VHA using all three standards, is that data notation should be consistent across all three specifications. Thus, the BPMN Data Object, the CMMN Case File, and the DMN Data Input should all look the same since they represent the same general concept to the people creating the models. Further, it will help readers of the models, who don't create them, but are responsible for their implementation within the organization, to understand how the three models work together. Such readers could be hospital clinical informatists.
    While there may be technical differences between the data representations among the three standards, these differences are not important to the business analysts who are using the models nor the readers of the models. The general concept of data used within a process, case, or decision is common across the three specs.
    Thus, the proposal for this issue is to allow modeling tools to provide an alternative notation for DMN Data Inputs that matches the notation found for BPMN Data Objects and CMMN Case Files.

  • Reported: DMN 1.1 — Tue, 3 Apr 2018 18:24 GMT
  • Disposition: Duplicate or Merged — DMN 1.2
  • Disposition Summary:

    duplicate of dmn12-44

    close as duplicate. Note that dmn12-44 is deferred.

  • Updated: Wed, 3 Oct 2018 14:17 GMT