Knowledge Discovery Metamodel Avatar
  1. OMG Specification

Knowledge Discovery Metamodel — Open Issues

  • Acronym: KDM
  • Issues Count: 2
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

Inconsistent naming of the property "taggedValue" in ModelElement

  • Key: KDM15-17
  • Status: open  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    ModelElement taggedValue association has the ExtendedValue type instead of the taggedValue as specified in the KDM spec.

  • Reported: KDM 1.3 — Sun, 18 Jan 2015 16:37 GMT
  • Updated: Tue, 29 Mar 2016 15:21 GMT

Merge ClassUnit and InterfaceUnit

  • Key: KDM15-16
  • Status: open  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    This issue is related to KDM14-20

    Problem: During the code model generation for Java we want to identify which class are in fact interfaces. Problem is that we basically need to identify which classes are interfaces upfront or have the ability to convert KDM "class unit" to "interface unit". However, both the objects presenting these both inherit from datatype but at the java code level one can't convert (i.e.) cast from ClassUnit to InterfaceUnit.

    Question: from an implementation point of view would it better to have a class object with an Interface attribute? For example the ClassUnit object has isAbstract. Can we implement isInterface to ClassUnit?

    This change will make it easier to change the type of a given KDM object.

    Note: Java 1.8 will start to allow code in interface specifications which will blur the lines between interface/class specifications.

  • Reported: KDM 1.3 — Fri, 16 Jan 2015 23:44 GMT
  • Updated: Tue, 29 Mar 2016 15:21 GMT