Issue 15143: Outdated descriptions (mof2core-rtf) Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com) Nature: Uncategorized Issue Severity: Summary: The document still contains large chunks of introductory material that date from the original MOF 2.0 submission and no longer apply. They should be deleted or updated as appropriate. Resolution: Revised Text: General: Replace all usages of MOF 2.0 and UML 2.0 with MOF 2 and UML 2 Section 1: replace the following: This MOF 2.0 Core specification is in response to the Object Management Group Request For Proposals ad/01-11-14 (MOF 2.0 Core RFP). This MOF 2.0 specification is based on the following OMG Specifications: • MOF 1.4 Specification -- MOF 2.0 is a major revision of the MOF 1.4 Specification. MOF 2.0 addresses issues deferred to MOF 2.0 by the MOF 1.4 RTF. For information on migration from MOF 1.4 to MOF 2.0 please refer to the “Migration from MOF 1.4” chapter. • UML 2.0 Infrastructure Convenience Document: ptc/04-10-14 -- MOF 2.0 reuses a subset of the UML 2.0 Infrastruc- ture Library packages. • MOF 2.0 XMI Convenience document: ptc/04-06-11 -- Defines the XML mapping requirements for MOF 2.0 and UML 2.0. With the following: This MOF 2 Core specification provides the basis for metamodel definition in OMG’s family of MDA languages and is based on a simplification of UML2’s class modeling capabilities. In addition to providing the means for metamodel definition it adds core capabilities for model management in general, including Identifiers, a simple generic Tag capability and Reflective operations which are generically defined and can be applied regardless of metamodel. MOF 2 Core is built on by other OMG MOF specifications, including the following (in this list ‘MOF based model’ means any model that instantiates a metamodel defined using MOF, which includes metamodels themselves): • MOF 2 XMI – for interchanging MOF-based models in XML • MOF 2 IDL – defines a platform-specific API for MOF Core operations for OMG’s CORBA platform • MOF 2 Facility and Object Lifecycle – for connecting to and managing collections of MOF-based model elements • MOF 2 Versioning and Development Lifeycle – for managing versions and configurations of MOF-based models • MOF Queries Views and Transformations – for transforming MOF-based models • MOF Models to Text – for generating text, such as programs, from MOF-based models • Object Constraint Language – for specifying constraints on MOF-based models Section 2: Replace the following: Compliant products shall support one or more of the following technology mappings: MOF 2.0 XMI ( ptc/04-06-11), MOF 2.0 IDL, and MOF 2.0 Java binding. Additional conformance rules based on MOF 2.0 IDL and MOF 2.0 Java binding will be specified in separate specifications. With: Compliant products shall support one or more of the following technology mappings: MOF 2 XMI, MOF 2.0 IDL. Additional conformance rules based on are specified in these specifications. Section 3: Replace the following: Readers of this MOF 2.0 specification are expected to be familiar with the UML Infrastructure V 2.0 specification. The MOF 2.0 model packages Essential MOF (EMOF) and Complete MOF (CMOF) are constructed by merging the UML2 Infrastructure Library packages. The main body of the document describes the technical specification itself. This specification references the following documents: • UML 2.0 Infrastructure Convenience Document: ptc/04-10-14 • MOF 2.0 XMI Convenience document: ptc/04-06-11 With: Readers of this MOF 2 specification are expected to be familiar with the UML Infrastructure specification. The MOF 2 model packages Essential MOF (EMOF) and Complete MOF (CMOF) are constructed by merging the UML2 Infrastructure Library packages. The main body of the document describes the technical specification itself. This specification references the following documents: • UML 2.4 Infrastructure (provide up to date reference) • MOF 2.4 XMI (provide up to date reference) Part I – Introduction: In para 3 replace the following: The Meta Object Facility (MOF), an adopted OMG standard, (latest revision MOF 1.4) With: The Meta Object Facility (MOF) In para 5 replace the following: This collaboration continues to this day as the vendors working on UML 2.0 Infrastructure and MOF 2.0 are attempting even greater reuse (as required by the OMG RFPs) With: This collaboration continues to this day as the vendors working on UML 2 and MOF 2 are attempting even greater reuse Delete the following para: Since then, MOF Revision Task Forces have produced several minor revisions, the most recent being the MOF 1.4 specification, which was adopted in October 2001. In para 7 replace the following: The use of MOF and XMI over the last few years has raised numerous application and implementation issues by vendors. As of the time of this writing over 150 formal usage and implementation issues have been submitted to the OMG for consideration. While a vast majority of these issues have been addressed by MOF 1.4, some are considered too major to be addressed by a Revision Task Force (RTF), and therefore, a series of MOF 2.0 RFPs (seven so far: MOF 2.0 Core, MOF 2.0 IDL Mapping, MOF 2.0 XMI Mapping, MOF 2.0 Versioning and MOF 2.0 Query/View/Transformations, MOF 2.0 Facility RFP, MOF 2.0 Facility RFP) have been issued. With: MOF 2 is represented by a set of specifications: MOF 2 Core, MOF 2 IDL Mapping, MOF 2 XMI Mapping, MOF 2 Facility and Object Lifecycle, MOF 2 Versioning and Development Lifecycle, MOF 2 Query/View/Transformations, MOF Model to Text. In para 8 replace the following: The reader must keep in mind that the individual RFPs and the proposals can be used incrementally and independently, and this modularity is a design goal of MOF 2.0. For example, vendors can implement the MOF 2.0 Model as a framework for metamodeling and metadata representation and management without using MOF 2.0 IDL or MOF 2.0 Java mapping. This was considered very important to provide more choice for MOF implementers. With: The reader must keep in mind that the individual specifications can be used incrementally and independently, and this modularity was a design goal of MOF 2. For example, vendors can implement the MOF 2 Core as a framework for metamodeling and metadata representation and management without using MOF 2 IDL or MOF 2 Facility. This was considered very important to provide more choice for MOF implementers. In para 9 replace the following: This MOF 2.0 specification integrates and reuses the complementary UML 2.0 Infrastructure submission to provide a more consistent modeling and metadata framework for OMG’s Model Driven Architecture. UML 2.0 provides the modeling framework and notation, MOF 2.0 provides the metadata management framework and metadata services. The manner in which the specification addresses individual RFP requirements is explained in the Scope of this specification. Considerable progress has been made in eliminating overlapping modeling constructs in UML 1 and MOF 1 specifications (for example, the confusion between MOF References and UML AssociationEnds has been eliminated). More importantly the modeling constructs from the UML2 Infrastructure Library are reused (using import) by both the MOF 2, UML2 Infrastructure, and UML2 Superstructure specifications. With: This MOF 2 specification integrates and reuses the complementary UML 2 Infrastructure submission to provide a more consistent modeling and metadata framework for OMG’s Model Driven Architecture. UML 2 provides the modeling framework and notation, MOF 2 provides the metadata management framework and metadata services. Considerable progress has been made in eliminating overlapping modeling constructs in UML 1 and MOF 1 specifications (for example, the confusion between MOF References and UML AssociationEnds has been eliminated). Delete the following paragraph: One of the challenges the MOF 2.0 Core and MOF 2.0 XMI Mapping submissions face is to maintain a stable interchange model (XMI) while MOF 2 and UML 2 are changing quite significantly. To accomplish this, we have begun applying the design principles that have been used in the XMI for XML Schemas and now the MOF 2.0 XMI mapping submission. This is to use a very small subset of the modeling concepts in MOF. We call this Essential MOF or EMOF which basically models simple classes with attributes and operations to fix the basic mapping from MOF to XML and Java. Additional mapping rules are provided in a manner consistent with XMI 2.0 for more complex modeling constructs. Please refer to the MOF 2.0 XMI Convenience document: ptc/04-06-11 for more details. Section 7.1: Delete the following paragraph: While much progress has been made in unification of the modeling concepts in MOF 2 and UML 2, the goal of reuse of meta model packages across object and non-object systems continues to be challenging. To address this the initial MOF 2.0 Core submission included a chapter titled “Common Concepts.” In the revised submission (in part to meet current submission deadlines and because this task proved to be more difficult than anticipated) we have scaled back these goals to focus on reuse between just UML and MOF. The MOF2 submission team recommends additional OMG RFPs be issued to address this broader reuse of metamodel packages between object and non-object systems. Section 7.2: Replace the following: The MOF 1.4 Reflection interfaces allow traversal across any number of metalayers recursively. With: The MOF 2 Reflection interfaces allow traversal across any number of metalayers recursively. Section 7.3: Replace the following: The UML 2.0 Infrastructure Library uses fine grained packages to bootstrap the rest of UML 2.0. A design goal (and RFP Requirement) is to reuse this infrastructure in the definition of the MOF 2.0 Model. In MOF 2.0 this reuse is simply accomplished by using a standard CMOF extensibility mechanism -- importing, combining, and merging existing MOF 2.0 compliant packages. Importing packages makes model elements contained in the imported package visible in the importing package. Merging packages extends model elements in the merging package with new feature deltas from the merged package. The details are covered in the UML 2.0 Infrastructure Convenience document in the section on PackageMerge. Note that we have designed both the UML 2.0 model and the MOF 2.0 model to be compliant to MOF 2.0 and be instantiable from MOF 2.0. With: The UML 2 Infrastructure Library uses fine grained packages to bootstrap the rest of UML 2. A design goal is to reuse this infrastructure in the definition of the MOF 2 Model. In MOF 2 this reuse is simply accomplished by using a standard CMOF extensibility mechanism - merging existing MOF 2.0 compliant packages. Merging packages extends model elements in the merging package with new feature deltas from the merged package. The details are covered in the UML 2 Infrastructure Convenience document in the section on PackageMerge. Note that both the UML 2 model and the MOF 2 model are designed to be compliant to MOF 2 and be instantiable from MOF 2. Section 8.1: Replace the following: Please refer to the chapter “Language Formalism” in the UML 2.0 Infrastructure Convenience document. With: Please refer to the chapter “Language Formalism” in the UML 2 Infrastructure specification. Section 9: Delete the following: Note – The Factory class has some overlap with the MOF Life cycle RFP and will need to be reconciled when submissions for that RFP are adopted. Actions taken: March 24, 2010: received issue April 25, 2011: closed issue Discussion: End of Annotations:===== ubject: Issue on MOF 2.0 Core Date: Wed, 24 Mar 2010 00:40:58 -0700 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issue on MOF 2.0 Core Thread-Index: AcrLJVhQQQ53UphxSAevnDXQ3E+Rvw== From: "Pete Rivett" To: Outdated descriptions ------------------------- The document still contains large chunks of introductory material that date from the original MOF 2.0 submission and no longer apply. They should be deleted or updated as appropriate. Pete -- Pete Rivett (pete.rivett@adaptive.com) CTO, Adaptive Inc 65 Enterprise, Aliso Viejo, CA 92656 tel: +1 949 330 7677, cell: +1 949 338 3794 Follow me on Twitter @rivettp or http://twitter.com/rivettp