Legacy Issue Number: 14069
Source: Thematix Partners LLC ( Edward Barkmeyer)
Clause 188.8.131.52 and Figure 32 says that ActualTypes have a namespace. As Figure 33 shows, the GenericElements are the objects that define the type_labels within the Algorithm; the ActualTypes don't. The ActualGenericType and ActualAggregateType just have identifiers that refer to these. If the same ActualStructure is used for ActualAggregateTypes with different member types, the ActualTypes are different, but the type labels – the names in the namespace – are the same, which violates the uniqueness rule for namespaces.
So ActualTypes don't have ScopedIds, and they don't have a namespace.
(It may be that they must be "owned by" the Algorithm for CMOF purposes, but that should be a separate concern.)
Delete the :namespace association for ActualType.
Reported: EXPRESS 1.0b2 — Fri, 10 Jul 2009 04:00 GMT
Disposition: Resolved — EXPRESS 1.0
The name of the issue is misleading. The text of 184.108.40.206 AssociationEnd: scope is clear on this point:
"An ActualType does not really have a namespace; the GenericElement to which it refers is a LocalElement whose namespace is the Algorithm. The .scope of the ActualType does, however, represent the ownership of the ActualType as a LocalElement and the lifetime of the ActualType. "
The problem is that no ActualType has a ScopedId - an ActualType is not a NamedElement, and its 'scope' relationship does not subset the LocalElement:namespace relationship. The model will be corrected.
Updated: Fri, 6 Mar 2015 21:48 GMT
EXPRESS_ — EXPRESS MM Issue: ActualType doesn't have a namespace
- Key: EXPRESS_-9
- OMG Task Force: 2nd EXPRESS Metamodel FTF