-
Key: KERML-89
-
Status: closed
-
Source: Model Driven Solutions ( Mr. Ed Seidewitz)
-
Summary:
In subclause 8.4.4.11 Feature Values Semantics, it states that
The checkFeatureValuationSpecialization constraint requires that, if the featureWithValue has no explicit ownedSpecializations and is not directed, then it subsets the result parameter of the value Expression.
However, the specification of checkFeatureValuationSpecialization in subclause 8.3.3.3.3 only requires
If a Feature has a FeatureValue, then it must specialize the result of the value Expression of the FeatureValue.
without the limitation that "the featureWithValue has no explicit ownedSpecializations and is not directed" (and the OCL is consistent with the textual description of the constraint).
-
Reported: KerML 1.0a1 — Sun, 11 Jun 2023 22:18 GMT
-
Disposition: Resolved — KerML 1.0b2
-
Disposition Summary:
Update the checkFeatureValuationSpecialization constraint
As discussed in 8.4.4.11 Feature Values Semantics, if a Feature is directed or has ownedSpecializations, it is desirable not to have it implicitly specialize the result of the value Expression, but, rather, to have it's type checked against the type of the result. Therefore, the checkFeatureValueSpecialization constraint should be updated to reflect the description in 8.4.4.11.
-
Updated: Tue, 1 Jul 2025 15:00 GMT
KERML — The checkFeatureValuationSpecialization constraint is incorrect
- Key: KERML-89
- OMG Task Force: Kernel Modeling Language (KerML) 1.0 FTF