SMOF_ — Compatiblity constraints and instances

Section 9.1.2.2 (Compatibility), Semantics, should clarify whether
instances can be taken into account when evaluating the constraint
specification (compare to the AspectOf, Attributes, isRequired, next to
last paragraph in the description). If they can, the last sentence
presumably should replace evaluates to true" with "evaluates to true for
all possible instances of either type". My understanding is the
Compatible constraint specification must evaluate to true for an
instance to be classified under both types, so if the constraint spec
can account for instances, then all instances (past, present, and
future) of both types must satisfy the constraint spec for the types to
be equivalent.

Explicit Compatibility has been removed from the metamodel and semantics.
Revised Text:
Resolution for this issue is included in the resolution for issue 17163.
Disposition: Closed – Duplicate / Merged – see issue 17163