Issue 13856: Section: 18.3.6 (uml2-rtf) Source: (, ) Nature: Clarification Severity: Significant Summary: Figure 18.8 includes a Metamodel formalism which has never been introduced, in particular with respect to customized metamodels. The presentation as a package with a triangle is new at this point. Although the concept of a metamodel is verbally explained in the Infrastructure, there is no abstract syntax. It becomes implicitly clear that a metamodel is a package. I suggest to insert a definition of a Metamodel as a subclass of Package in the Infrastructure document or in the Profiles chapter of this document. This also allows to explain what is meant by "applying a metamodel". Also, the term "a UML2 metamodel" (p. 666) is unclear, taking into account that UML2 itself is a metamodel. This all should be clarified due to the importance of the metamodel concept in this chapter. The same applies to the respective chapter of the Infrastructure document. Resolution: Revised Text: Actions taken: April 9, 2009: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 09 Apr 2009 06:18:50 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Michael Zapf Company: University of Kassel mailFrom: Michael.Zapf@uni-kassel.de Notification: Yes Specification: OMG Unified Modeling Language (OMG UML), Superstructure Section: 18.3.6 FormalNumber: formal/2009-02-03 Version: 2.2 RevisionDate: Feb 2009 Page: 665, 666 Nature: Clarification Severity: Significant HTTP User Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.3) Gecko/2008092416 Firefox/3.0.3 Description Figure 18.8 includes a Metamodel formalism which has never been introduced, in particular with respect to customized metamodels. The presentation as a package with a triangle is new at this point. Although the concept of a metamodel is verbally explained in the Infrastructure, there is no abstract syntax. It becomes implicitly clear that a metamodel is a package. I suggest to insert a definition of a Metamodel as a subclass of Package in the Infrastructure document or in the Profiles chapter of this document. This also allows to explain what is meant by "applying a metamodel". Also, the term "a UML2 metamodel" (p. 666) is unclear, taking into account that UML2 itself is a metamodel. This all should be clarified due to the importance of the metamodel concept in this chapter. The same applies to the respective chapter of the Infrastructure document.