Legacy Issue Number: 14070
Source: Thematix Partners LLC ( Edward Barkmeyer)
The use of "Actual" on both sides of the ActualAggregateType to ActualStructure relationship, and the ActualGenericType and ActualDataType relationship is confusing and makes it seem that one pair of those classes is redundant. And ActualStructure and ActualDataType are subtypes of "GenericElement", but they have no common words in the names. GenericElements are some kind of "type parameter" (which is what the association end is called). So ActualStructure should be StructureParameter, or GenericStructure, or something like that, shouldn't it?
Rename GenericElement, ActualDataType, ActualStructure to make the naming consistent and make it clear that they are "type parameters".
Reported: EXPRESS 1.0b2 — Fri, 10 Jul 2009 04:00 GMT
Disposition: Resolved — EXPRESS 1.0
The designation GenericElement suggests that it is some general class of model element. "Actual" is overloaded - here it refers to elements taken from ActualParameters, while the "ActualTypes" are derived from them. The classes will be renamed: ParametricElement, ParametricStructure, ParametricType.
The resolution to Issue 14194 moves the section of text that defines these concepts to the Core package. So these changes are made in that text.
The text changes are incorporated into the model changes in issue 14194.
Disposition: Merged into Issue 14194
Updated: Fri, 6 Mar 2015 21:48 GMT
EXPRESS_ — EXPRESS MM Issue: Rename GenericElements
- Key: EXPRESS_-10
- OMG Task Force: 2nd EXPRESS Metamodel FTF