Issue 13127: Section 9.1: paragraph needs clarification (mof2core-rtf) Source: Model Driven Solutions (Mr. Cory B. Casanave, cory-c(at)modeldriven.com) Nature: Clarification Severity: Significant Summary: The following paragrph is not stated clearly and can cause an improper interpretation of the MOF object model: Class Element is the superclass of all model elements in MOF, and is the superclass of all instances of MOF model elements. Each element can access its metaClass in order to obtain a Class that provides a reflective description of that element. By having both MOF and instances of MOF be rooted in class Element, MOF supports any number of meta layers as described in Chapter 7, “MOF Architecture.” A better way to say it may be: Class Element is the superclass of all classes defined in MOF, and is a superclass of the metaclass of all MOF model elements. Each element can access its metaClass in order to obtain a Class that provides a reflective description of that element. By having both MOF and instances of MOF be rooted in class Element, MOF supports any number of meta layers as described in Chapter 7, “MOF Architecture.” Resolution: Further description would be useful than suggested in the issue Revised Text: Replace the quoted paragraph in section 9.1 Semantics with the following: Class Element is the superclass of all classes defined in MOF, and is an implicit superclass of all metaclasses defined using MOF: this superclass relationship to Element does not need to be explicitly modeled in MOF-compliant metamodels, and if implicit in this way Element is not included in the list of superclasses. By creating Properties with type Element it is possible to reference elements in any MOF-compliant model, similar to the use of xsd:any in XML Schemas. Each element can access its metaClass in order to obtain a Class that provides a reflective description of that element. By having both MOF and instances of MOF be rooted in class Element, MOF supports any number of meta layers as described in Chapter 7, “MOF Architecture.” Actions taken: November 26, 2008: received issue April 25, 2011: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 26 Nov 2008 11:39:50 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Cory Casanave Company: Model Driven Solutions mailFrom: cory-c@modeldriven.com Notification: No Specification: MOF Core Section: 9.1 FormalNumber: formal/06-01-02 Version: 2.0 RevisionDate: 1/1/06 Page: 88 Nature: Clarification Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727) Description The following paragrph is not stated clearly and can cause an improper interpretation of the MOF object model: Class Element is the superclass of all model elements in MOF, and is the superclass of all instances of MOF model elements. Each element can access its metaClass in order to obtain a Class that provides a reflective description of that element. By having both MOF and instances of MOF be rooted in class Element, MOF supports any number of meta layers as described in Chapter 7, .MOF Architecture.. A better way to say it may be: Class Element is the superclass of all classes defined in MOF, and is a superclass of the metaclass of all MOF model elements. Each element can access its metaClass in order to obtain a Class that provides a reflective description of that element. By having both MOF and instances of MOF be rooted in class Element, MOF supports any number of meta layers as described in Chapter 7, .MOF Architecture..