1、INCITS/ISO/IEC 19502:20052009 (ISO/IEC 19502:2005 , IDT) Information technology Meta Object Facility (MOF)INCITS/ISO/IEC 19502:20052009(ISO/IEC 19502:2005, IDT)INCITS/ISO/IEC 19502:20052009 ii ITIC 2009 All rights reserved PDF disclaimer This PDF file may contain embedded typefaces. In accordance wi
2、th Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing
3、policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Eve
4、ry care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. Adopted by INCITS (InterNational Committee for Information Technology Standards) as
5、 an American National Standard. Date of ANSI Approval: 3/23/2009 Published by American National Standards Institute, 25 West 43rd Street, New York, New York 10036 Copyright 2009 by Information Technology Industry Council (ITI). All rights reserved. These materials are subject to copyright claims of
6、International Standardization Organization (ISO), International Electrotechnical Commission (IEC), American National Standards Institute (ANSI), and Information Technology Industry Council (ITI). Not for resale. No part of this publication may be reproduced in any form, including an electronic retri
7、eval system, without the prior written permission of ITI. All requests pertaining to this standard should be submitted to ITI, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of America INCITS/ISO/IEC 19502:20052009 ITIC 2009 All rights reserved iiiContentsForeword viiiIntrodu
8、ction ix1 Scope .12 Normative references .12.1 Identical Recommendations | International Standards 12.2 International Standards . 13 Abbreviations and Conventions .24 List of Documents 25 MOF Usage Scenarios .35.1 Overview . 35.2 Software Development Scenarios . 45.3 Type Management Scenarios . 55.4
9、 Information Management Scenarios . 65.5 Data Warehouse Management Scenarios 76 MOF Conceptual Overview 96.1 Overview . 96.2 Metadata Architectures . 96.2.1 Four Layer Metadata Architectures. 96.2.2 The MOF etadata Architecture . 106.2.3 MOF Metamodeling Terminology 126.3 The MOF Model - Metamodelin
10、g Constructs 136.3.1 Classes .136.3.2 Associations 166.3.3 Aggregation . 176.3.4 References 186.3.5 DataTypes . 206.3.6 Packages . 206.3.7 Constraints and Consistency 236.3.8 Miscellaneous Metamodeling Constructs 246.4 Metamodels and Mappings . 256.4.1 Abstract and Concrete Mappings 256.4.2 he MOF M
11、etamodel IDL Mapping . 266.4.3 he MOF Metamodel XML Mapping 266.4.4 Mappings of the MOF Model. 277 MOF Model and Interfaces 297.1 Overview . 297.2 How the MOF Model is Described 297.2.1 Classes .30INCITS/ISO/IEC 19502:20052009 iv ITIC 2009 All rights reserved7.2.2 Associations 347.2.3 DataTypes . 35
12、7.2.4 Exceptions . 357.2.5 Constants 367.2.6 Constraints 367.2.7 UML Diagrams 367.3 The Structure of the MOF Model . 367.3.1 The MOF Model Package . 367.3.2 The MOF Model Service IDL. 387.3.3 The MOF Model Structure . 387.3.4 The MOF Model Containment Hierarchy . 407.4 OF Model Classes 417.4.1 Model
13、Element (abstract) 417.4.2 Namespace (abstract) 457.4.3 GeneralizableElement (abstract) 487.4.4 TypedElement (abstract) 527.4.5 Classifier (abstract) 537.4.6 Class . 547.4.7 DataType (abstract) 557.4.8 PrimitiveType 567.4.9 CollectionType 577.4.10 EnumerationType 587.4.11 AliasType . 597.4.12 Struct
14、ureType 597.4.13 StructureField 607.4.14 Feature. (abstract) 607.4.15 StructuralFeature . (abstract) 627.4.16 Attribute (idl_substitute_name “MofAttribute”) 637.4.17 Reference 647.4.18 BehavioralFeature (abstract) 667.4.19 Operation 677.4.20 Exception .(idl_substitute_name “MofException”) 687.4.21 A
15、ssociation 697.4.22 AssociationEnd . 717.4.23 Package 747.4.24 Import 767.4.25 Parameter . 787.4.26 Constraint 797.4.27 Constant 827.4.28 Tag 837.5 MOF Model Associations 857.5.1 Contains 857.5.2 Generalizes . 867.5.3 RefersTo . 877.5.4 Exposes (derived) 887.5.5 IsOfType 907.5.6 CanRaise 907.5.7 Ali
16、ases. 917.5.8 Constrains. 927.5.9 DependsOn . (derived) 93INCITS/ISO/IEC 19502:20052009 ITIC 2009 All rights reserved v7.5.10 AttachesTo 957.6 MOF Model Data Types 967.6.1 PrimitiveTypes used in the MOF Model 967.6.2 MultiplicityType 967.6.3 VisibilityKind 977.6.4 DirectionKind. 987.6.5 ScopeKind .
17、987.6.6 AggregationKind . 987.6.7 EvaluationKind 987.7 MOF Model Exceptions. 997.7.1 NameNotFound. 997.7.2 NameNotResolved 997.8 MOF Model Constants . 997.8.1 Unbounded . 1007.8.2 The Standard DependencyKinds 1007.9 MOF Model Constraints 1017.9.1 MOF Model Constraints and other M2 Level Semantics .
18、1017.9.2 Notational Conventions . 1017.9.3 OCL Usage in the MOF Model specification. 1037.9.4 The MOF Model Constraints . 1057.9.5 Semantic specifications for some Operations, derived Attributes and Derived Associations 1257.9.6 OCL Helper functions 1317.10 The PrimitiveTypes Package 1347.10.1 Boole
19、an 1357.10.2 Integer . 1357.10.3 Long 1357.10.4 Float 1357.10.5 Double . 1357.10.6 String .1357.10.7 IDL for the PrimitiveTypes Package 1367.11 Standard Technology Neutral Tags 1368 The MOF Abstract Mapping. 1398.1 Overview . 1398.2 MOF Values 1398.3 Semantics of Data Types . 1398.4 Semantics of Equ
20、ality for MOF Values . 1408.5 Semantics of Class Instances . 1418.6 Semantics of Attributes . 1418.6.1 Attribute name and type 1428.6.2 Multiplicity 1428.6.3 Scope 1438.6.4 Is_derived . 1448.6.5 Aggregation. 1448.6.6 Visibility and is_changeable. 1448.7 Package Composition 1448.7.1 Package Nesting .
21、 1448.7.2 Package Generalization 1458.7.3 Package Importation . 145vi ITIC 2009 All rights reserved8.7.4 Package Clustering . 1458.8 Extents 1458.8.1 The Purpose of Extents . 1468.8.2 Class Extents 1478.8.3 Association Extents . 1478.8.4 Package Extents . 1478.9 Semantics of Associations 1498.9.1 MO
22、F Associations in UML notation . 1498.9.2 Core Association Semantics . 1508.9.3 AssociationEnd Changeability . 1528.9.4 Association Aggregation . 1528.9.5 Derived Associations . 1528.10 Aggregation Semantics . 1528.10.1 Aggregation “none” . 1528.10.2 Aggregation “composite” . 1538.10.3 Aggregation “
23、shared” 1538.11 Closure Rules 1538.11.1 The Reference Closure Rule 1538.11.2 The Composition Closure Rule . 1558.12 Recommended Copy Semantics . 1568.13 Computational Semantics . 1578.13.1 A Style Guide for Metadata Computational Semantics . 1578.13.2 Access operations should not change metadata 158
24、8.13.3 Update operations should only change the nominated metadata . 1588.13.4 Derived Elements should behave like non-derived Elements . 1588.13.5 Constraint evaluation should not have side-effects . 1588.13.6 Access operations should avoid raising Constraint exceptions 1599 MOF to IDL Mapping 1619
25、.1 Overview . 1619.2 Meta Objects and Interfaces . 1619.2.1 Meta Object Type Overview 1619.2.2 The Meta Object Interface Hierarchy 1639.3 Computational Semantics for the IDL Mapping . 1659.3.1 The CORBAIdl Types Package 1659.3.2 Mapping of MOF Data Types to CORBA IDL Types 1699.3.3 Value Types and E
26、quality in the IDL Mapping 1709.3.4 Lifecycle Semantics for the IDL Mapping 1709.3.5 Association Access and Update Semantics for the IDL Mapping . 1739.3.6 Link Addition Operations . 1739.3.7 Attribute Access and Update Semantics for the IDL Mapping 1769.3.8 Reference Semantics for the IDL Mapping .
27、 1819.3.9 Cluster Semantics for the IDL Mapping 1829.3.10 Atomicity Semantics for the IDL Mapping 1829.3.11 The Supertype Closure Rule . 1829.3.12 Copy Semantics for the IDL Mapping . 1839.4 xception Framework 1839.4.1 Error_kind string values 1859.4.2 Structural Errors 1859.4.3 Constraint Errors .
28、188ISO/IEC 19502:2005(E) ITIC 2009 All rights reserved vii9.4.4 Semantic Errors 1889.4.5 Usage Errors. 1899.4.6 Reflective Errors 1909.5 Preconditions for IDL Generation 1929.6 Standard Tags for the IDL Mapping 1949.6.1 Tags for Specifying IDL #pragma directives 1949.6.2 Tags for Providing Substitut
29、e Identifiers . 1959.6.3 Tags for Specifying IDL Inheritance 1969.7 Generated IDL Issues . 1989.7.1 Generated IDL Identifiers 1989.7.2 Generation Rules for Synthesized Collection Types . 2009.7.3 IDL Identifier Qualification . 2029.7.4 File Organization and #include statements . 2029.8 IDL Mapping T
30、emplates 2029.8.1 Template Notation. 2039.8.2 Package Module Template . 2039.8.3 Package Factory Template . 2059.8.4 Package Template 2069.8.5 Class Forward Declaration Template 2099.8.6 Class Template . 2099.8.7 Class Proxy Template . 2109.8.8 Instance Template . 2129.8.9 Class Create Template . 21
31、39.8.10 Association Template 2149.8.11 Attribute Template . 2229.8.12 Reference Template 2319.8.13 Operation Template 2409.8.14 Exception Template 2429.8.15 DataType Template . 2439.8.16 Constraint Template 2459.8.17 Annotation Template . 24510 The Reflective Module 24710.1 Introduction . 24710.2 Th
32、e Reflective Interfaces 24810.2.1 Reflective Argument Encoding Patterns . 24810.2.2 Reflective:RefBaseObject . (abstract) 25010.2.3 Reflective:RefObject . (abstract) 25410.2.4 Reflective:RefAssociation . (abstract) 26510.2.5 Reflective:RefPackage (abstract) 26910.3 The CORBA IDL for the Reflective I
33、nterfaces . 27010.3.1 Introduction . 27010.3.2 Data Types 271Annex A (normative) Conformance Issues .273Annex B (normative) Legal Information.275INDEX .279INCITS/ISO/IEC 19502:20052009 viii ITIC 2009 All rights reservedForeword ISO (the International Organization for Standardization) and IEC (the In
34、ternational Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular
35、 fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have establishe
36、d a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical c
37、ommittee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC
38、shall not be held responsible for identifying any or all such patent rights. ISO/IEC 19502 was prepared by the Object Mangement Group (OMG) and was adopted, under the PAS procedure, by Joint Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its approval by national bodies o
39、f ISO and IEC. ISO/IEC 19502 is related to ISO/IEC 19501, Information technology Open Distributed Processing Unified Modeling Language (UML) Version 1.4.2 ISO/IEC 19503, Information technology XML Metadata Interchange (XMI) ISO/IEC 14769, Information technology Open Distributed Processing Type Repos
40、itory Function INCITS/ISO/IEC 19502:20052009 ITIC 2009 All rights reserved ixIntroductionThis International Standard defines a metamodel (defined using MOF), a set of interfaces (defined using ODP IDL (ITU-T Recommendation X.920 (1997) | ISO/IEC 14750:1999), that can be used to define and manipulate
41、 a set of interoperable metamodels and their corresponding models. It also defines the mapping from MOF to ODP IDL (ITU rec X920|ISO 14750). These interoperable metamodels include the Unified Modeling Language (UML) metamodel (ISO/IEC 19501:2005), the MOF meta-metamodel, as well as future standard t
42、echnologies that will be specified using metamodels. The MOF provides the infrastructure for implementing design and reuse repositories, application development tool frameworks, etc. The MOF specifies precise mapping rules that enable the CORBA interfaces for metamodels to be generated automatically
43、, thus encouraging consistency in manipulating metadata in all phases of the distributed application development cycle. Mappings from MOF to W3C XML and XSD are specified in the XMI (ISO/IEC 19503) specification. Mappings from MOF to Java are in the JMI (Java Metadata Interchange) specification defi
44、ned by the Java Community Process.In order to achieve architectural alignment considerable effort has been expended so that the UML and MOF share the same core semantics. This alignment allows the MOF to reuse the UML notation for visualizing metamodels. In those areas where semantic differences are
45、 required, well-defined mapping rules are provided between the metamodels. The UML has been the subject of a separate PAS submission.The OMG adopted the MOF (version 1.0) in November 1997. It was developed as a response to a request for proposal, issued by the OMG Analysis and Design Task Force, for
46、 Metadata repository facility (http:/www.omg.org/cgi-bin/doc?cf/96-05-02). The purpose of the facility was to support the creation, manipulation, and interchange of meta models. The most recent revision of MOF, 1.4 was adopted in April 2002, and includes corrections and clarifications to the origina
47、l 1.3 version, and minor modeling feature additions.The rapid growth of distributed processing has led to a need for a coordinating framework for this standardization and ITU-T Recommendations X.901-904 | ISO/IEC 10746, Open Distributed Processing Reference Model (RM-ODP) provides such a framework.
48、It defines an architecture within which support of distribution, interoperability, and portability can be integrated. RM-ODP Part 2 (ISO/IEC 10746-2) defines the foundational concepts and modeling framework for describing distributed systems. RM-ODP Part 3 (ISO/IEC 10746-3) specifies a generic archi
49、tecture of open distributed systems, expressed using the foundational concepts and framework defined in Part 2. While not limited to this context, this International Standard is closely related to work on the standardization of Open Distributed Processing (ODP). In particular, the ODP Type Repository Function (ISO/IEC 14769 | Rec. X.960) references the OMG Meta Object Facility, version 1.3. This function specifies how to use the OMG MOF as a repository for ODPtypes. AMERICAN NATIONAL STANDARD
