DMN 1.0 FTF Avatar
  1. OMG Issue

DMNFTF — Data Input notation specification and useage

  • Key: DMNFTF-94
  • Legacy Issue Number: 19292
  • Status: closed  
  • Source: Knowledge Partners, Inc. ( Paul Vincent)
  • Summary:

    Input Data entity definition appears to be quite sparse versus the data specification requirements likely to be needed in decision modelling. Also not well represented in the ch 11 DMN Example where it is used there for input samples rather than input specifications.

    Example: an end user defined a DRD and labelled the Input Data in their DRD with the name of the XSD of the data source. They then questioned how to annotate an Input Data with a specific named XSD - especially is the input data is constrained to a 3rd party format (such as an industry standard that is specified as an XSD), which they considered (as a tag) a business level concept, even if the details of the XSD might not be.

    Suggestion: Input Data should be more vigorously defined e.g. as a specification of input data / source (message, invocation, etc) associated with Boxed Invocation, maybe renamed Source of Data. Sample Data could be specified as a Knowledge Source for Input Data. Specifications of the format (e.g. industry XSDs) of Input Data could also be Knowledge Sources

  • Reported: DMN 1.0b1 — Wed, 19 Mar 2014 04:00 GMT
  • Disposition: Resolved — DMN 1.0
  • Disposition Summary:

    Distinguish input data from case data.

  • Updated: Tue, 21 Apr 2015 01:19 GMT
  • Attachments: