SMOF 1.0 FTF Avatar
  1. OMG Issue

SMOF_ — Extended element semantics complicates common use case

  • Key: SMOF_-9
  • Legacy Issue Number: 17150
  • Status: closed  
  • Source: NIST ( Conrad Bock)
  • Summary:

    Section (Element, as extended), Semantics, first sentence, says reclassification is constrained by Compatibility elements, but this would mean an instances of a type cannot be reclassified as one of its subtypes without using compatibility, see AspectOf example in the previous issue. This is such a typical use case that it would be significant burden to require modelers to explicitly define compatibility for it.

  • Reported: SMOF 1.0b2 — Wed, 22 Feb 2012 05:00 GMT
  • Disposition: Resolved — SMOF 1.0
  • Disposition Summary:

    Metaclasses will be considered compatible by default and without need for specific marking, unless explicitly marked disjoint. There will no longer be any Compatibility elements. This will also resolve issue 17152. The required model changes are addressed by the resolution to issue 17163, which becomes a prerequisite to this resolution

  • Updated: Sat, 7 Mar 2015 08:56 GMT