KerML 1.0b2 FTF Avatar
  1. OMG Issue

KERML — DataType Disjointness Clarification

  • Key: KERML-174
  • Status: closed  
  • Source: Self ( Jim Ciarcia)
  • Summary:

    First Sentance of Last Paragraph
    "If any of the types of a feature are data types, then all of them must be."
    This is inconsistent with the Abstract Syntax that does not enforce this constraint, it enforces a weaker constraint.
    Features that are types by DataType can legally be typed by Classifiers according to 8.4.4.2 semantics
    8.4.4.2 Data Types Semantics states that DataType is disjoint with Class and Association,
    so a more consistent statement would be that then
    "If any of the types of a feature are DataTypes, then it can't also be typed by Class or Associations.

  • Reported: KerML 1.0b1 — Sat, 16 Sep 2023 18:22 GMT
  • Disposition: Resolved — KerML 1.0b2
  • Disposition Summary:

    Revise the language description

    Agreed.

    In addition, the following statement in 7.4.3 Classes is also incorrect: "If any of the types of a feature are classes, then all of them must be." As noted in 8.4.4.3 Classes Semantics, the base Class Occurrences is disjoint with the base DataType DataValues, but not the base Association Link. So, the correct statement in 7.4.3 is "If any of the types of a feature are classes, then none of its types can be data types."

  • Updated: Tue, 1 Jul 2025 15:01 GMT