Issue 6457: Abandon the OMGS4LMMA (uml2-superstructure-ftf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: If the so-called OMGS4LMMA is accepted, it is not possible that an InformationFlow could connect both Classes and Instance Specifications. ... Suggested resolution: Abandon the OMGS4LMMA. Apply InstanceSpecification uniformly (for example, an informationFlow is used to connect classes and an instanceSpecification of an informationFlow is used to connect instanceSpecifications of classes, that is, to connect objects. Resolution: Revised Text: Actions taken: November 7, 2003: received issue March 9, 2005: closed issue Discussion: The issue is not clear what document changes are required to ‘abandon the OMGS4LMMA’: in general in the past restrictions claimed as a result of the 4 layer metadata architecture were based on a misunderstanding rather than anything documented in an adopted specification. There is nothing (e.g. in section 7.2 of Superstructure, in particular 7.2.8) to stop linking of classes at different meta-levels: indeed this is used in Profiles. With respect to the example of InformationFlows these do not in fact cross meta- levels since an instance of InstanceSpecification is at the same level (M1) as an instance of Class: as section 7.2.9 of Superstructure states “The instances, which are sometimes referred to as “run-time” instances, that are created at M0 from for example Person should not be confused with instances of the metaclass InstanceSpecification that are also defined as part of the UML metamodel“ Disposition: Closed, no change End of Annotations:===== f the so-called OMGS4LMMA is accepted, it is not possible that an InformationFlow could connect both Classes and Instance Specifications. ... Suggested resolution: Abandon the OMGS4LMMA. Apply InstanceSpecification uniformly (for example, an informationFlow is used to connect classes and an instanceSpecification of an informationFlow is used to connect instanceSpecifications of classes, that is, to connect objects.