1、BSI Standards Publication BS ISO/IEC 19763-12:2015 Information technology Metamodel framework for interoperability (MFI) Part 12: Metamodel for information model registrationBS ISO/IEC 19763-12:2015 BRITISH STANDARD National foreword This British Standard is the UK implementation of ISO/IEC 19763-12
2、:2015. The UK participation in its preparation was entrusted to Technical Committee IST/40, Data management and interchange. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of
3、 a contract. Users are responsible for its correct application. The British Standards Institution 2015. Published by BSI Standards Limited 2015 ISBN 978 0 580 78361 6 ICS 35.040 Compliance with a British Standard cannot confer immunity from legal obligations. This British Standard was published unde
4、r the authority of the Standards Policy and Strategy Committee on 31 March 2015. Amendments/corrigenda issued since publication Date T e x t a f f e c t e dInformation technology Metamodel framework for interoperability (MFI) Part 12: Metamodel for information model registration Technologies de linf
5、ormation Cadre du mtamodle pour linteroprabilit (MFI) Partie 12: Mtamodle pour lenregistrement du modle dinformation INTERNATIONAL STANDARD ISO/IEC 19763-12 Reference number ISO/IEC 19763-12:2015(E) First edition 2015-03-15 ISO/IEC 2015 BS ISO/IEC 19763-12:2015ii ISO/IEC 2015 All rights reserved COP
6、YRIGHT PROTECTED DOCUMENT ISO/IEC 2015 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written
7、permission. Permission can be requested from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ISO/I
8、EC 19763-12:2015(E)BS ISO/IEC 19763-12:2015ISO/IEC 19763-12:2015(E)Foreword iv Introduction v 1 Scope . 1 2 Conformance . 2 2.1 General . 2 2.2 Degree of conformance 2 2.2.1 General 2 2.2.2 Strictly conforming implementation 2 2.2.3 Conforming implementation . 2 2.3 Implementation Conformance Statem
9、ent (ICS) . 2 3 Normative references 2 4 T erms, definitions, and abbr e viat ed t erms . 3 4.1 Terms and definitions . 3 4.2 Terms for concepts used in this part of 19763 3 4.3 Abbreviated terms . 8 5 Structure of MFI Information model registration 9 5.1 Overview of MFI Information model registrati
10、on 9 5.2 Association between MFI Information model registration and MFI Core and mapping 10 5.3 Metaclasses in MFI Information Model Registration 12 5.3.1 Attribute .12 5.3.2 Attribute_Unique_Identifier_Element .13 5.3.3 Described_Domain 13 5.3.4 Diagram.14 5.3.5 Domain 14 5.3.6 Entity_Specialisatio
11、n_Hierarchy 15 5.3.7 Entity_Specialisation_Hierarchy_Foreign_Key_Attribute .16 5.3.8 Entity_Type 16 5.3.9 Enumerated_Domain .18 5.3.10 Foreign_Key_Attribute 18 5.3.11 General_Constraint . .18 5.3.12 Information_Model .19 5.3.13 Information_Modelling_Language .19 5.3.14 Key_Attribute .19 5.3.15 Nativ
12、e_Key_Attribute .20 5.3.16 Non_Key_Attribute.20 5.3.17 Relationship 20 5.3.18 Relationship_End 21 5.3.19 Relationship_End_Foreign_Key_Attribute .22 5.3.20 Relationship_End_Group 23 5.3.21 Relationship_End_Unique_Identifier_Element 23 5.3.22 Unique_Identifier 24 5.3.23 Unique_Identifier_Element 24 5.
13、3.24 Valid_Value .25 Annex A (informative) Description of the metamodel 26 Annex B (informative) Relationship of metaclasses to the MDR Metamodel 33 Annex C (informative) Applicability of information modelling concepts to techniques .34 Annex D (informative) Examples of information model registratio
14、n .36 Bibliography .61 ISO/IEC 2015 All rights reserved iii Contents PageBS ISO/IEC 19763-12:2015ISO/IEC 19763-12:2015(E) Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardizatio
15、n. 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 fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual i
16、nterest. 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 established a joint technical committee, ISO/IEC JTC 1. The procedures used to develop this document and th
17、ose intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of document should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see
18、www.iso.org/directives). Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of th
19、e document will be in the Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents). Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement. For an explanation on the meaning of ISO specific te
20、rms and expressions related to conformity assessment, as well as information about ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information The committee responsible for this document is ISO/IEC JTC 1, Information techn
21、ology, SC 32, Data management and interchange. ISO/IEC 19763 consists of the following parts, under the general title Information technology Metamodel framework for interoperability (MFI): Part 1: Framework Part 3: Metamodel for ontology registration Part 5: Metamodel for process model registration
22、Part 6: Registry Summary Part 10: MFI Core model and basic mapping Part 12: Metamodel for information model registration The following parts are under preparation: Part 7: Metamodel for service registration Part 8: Metamodel for role and goal registration Part 9: On demand model selection Part 13: M
23、etamodel for forms registrationiv ISO/IEC 2015 All rights reservedBS ISO/IEC 19763-12:2015ISO/IEC 19763-12:2015(E) Introduction There is an increasing demand for systems to interoperate by exchanging data. For these data exchanges to be meaningful, it is essential that the business information requi
24、rements that are met by the data stored in these systems are understood so that suitable data exchange mechanisms can be developed. Business information requirements, including the semantic meaning of the information, are often represented by information models before the databases that are an integ
25、ral part of the systems are designed. These models are often called logical models. The subsequent design of the database structure can also be considered to be another form of information model. Where there is an overlap of the universe of discourse of two systems, the information models for these
26、two systems can be registered using the facilities specified by this part of ISO/IEC 19763. The mappings between these two models can then be registered using the facilities specified by ISO/IEC 19763-10. An interface between the two systems can then be designed, enabling the two systems to interope
27、rate by exchanging information. ISO/IEC 2015 All rights reserved vBS ISO/IEC 19763-12:2015BS ISO/IEC 19763-12:2015Information technology Metamodel framework for interoperability (MFI) Part 12: Metamodel for information model registration 1 Scope The primary purpose of the multipart standard ISO/IEC
28、19763 is to specify a metamodel framework for interoperability. This part of ISO/IEC 19763 specifies a metamodel for registering information models. This metamodel was developed taking into account two distinct types of information models such as those that are used to document the information requi
29、rements of a particular area of interest, and those that represent the structure of a database which are often expressed using a Database Definition Language (DDL). Information models that represent information requirements can be developed using a number of different common diagramming techniques a
30、nd notations. The metamodel specified in this part of ISO/IEC 19763 was developed to cover the registration of models expressed using the following techniques and notations: Express-G, an ISO standard entity-relationship modelling notation, as described in Reference 8; IDEF1X, a US Federal standard
31、entity-relationship modelling notation, as described in References 6 and 12; the entity-relationship modelling notation first developed by Harry Ellis and Richard Barker and later adopted by Oracle for its CASE*Method and by the UKs CCTA for SSADM (Structured Systems Analysis and Design Method), as
32、described in Reference 2; the UML Class Diagram notation, as described in References 13 and 14; the original entity-relationship modelling notation proposed by Peter Chen, as described in Reference 4; the Information Engineering entity-relationship modelling notation, as described in Reference 11. I
33、t is understood that these selected techniques represent all of the essential features of all information modelling techniques used to represent information requirements. The registration of information models that represent the structure of a database is limited in the metamodel specified in this p
34、art of ISO/IEC 19763 to those database structures that conform to the Core SQL specification. Core SQL is the set of features defined in the conformance requirements specified in ISO/IEC 9075-2 and ISO/IEC 9075-11. The registration of information models that are expressed using notations such as Obj
35、ect Role Modeling (ORM) and “Natural language Information Analysis Method” (NIAM), collectively known as fact-based models, is out of scope for this part of ISO/IEC 19763. INTERNATIONAL ST ANDARD ISO/IEC 19763-12:2015(E) ISO/IEC 2015 All rights reserved 1BS ISO/IEC 19763-12:2015ISO/IEC 19763-12:2015
36、(E) 2 Conformance 2.1 General An implementation claiming conformance with this part of ISO/IEC 19763 shall support the metamodel specified in Clause 5 depending on the degree of conformance as described below. 2.2 Degree of conformance 2.2.1 General The distinction between “strictly conforming” and
37、“conforming” implementations is necessary to address the simultaneous needs for interoperability and extensions. This part of ISO/IEC 19763 describes specifications that promote interoperability. Extensions are motivated by the needs of the users, vendors, institutions, and industries, but are not s
38、pecified by this part of ISO/IEC 19763. A strictly conforming implementation could be limited in usefulness, but is maximally interoperable with respect to this part of ISO/IEC 19763. A conforming implementation can be more useful, but could be less interoperable with respect to this part of ISO/IEC
39、 19763. 2.2.2 Strictly conforming implementation A strictly conforming implementation a) shall support the metamodel specified in Clause 5, and b) shall not use, test, access, or probe for any extension features nor extensions to the metamodel specified in Clause 5. 2.2.3 Conforming implementation A
40、 conforming implementation a) shall support the metamodel specified in Clause 5, and b) as permitted by the implementation, can use, test, access, or probe for any extension features or extensions to the metamodel specified in Clause 5. NOTE 1 All strictly conforming implementations are also conform
41、ing implementations. NOTE 2 The use of extensions to the metamodel could cause undefined behaviour. 2.3 Implementation Conformance Statement (ICS) An implementation claiming conformance with this part of ISO /IEC 197 63 shall include an Implementation Conformance Statement stating a) whether it is a
42、 strictly conforming implementation (2.2.2) or a conforming implementation (2.2.3), and b) what extensions, if any, are supported or used if it is a conforming implementation. 3 Normative references The following documents, in whole or in part, are normatively referenced in this document and are ind
43、ispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. NOTE One or more terms and definitions of the referenced International Standards listed below are used in Cl
44、ause 4 Terms and definitions.2 ISO/IEC 2015 All rights reservedBS ISO/IEC 19763-12:2015ISO/IEC 19763-12:2015(E) ISO/IEC 9075-1:2011, Information technology Database languages SQL Part 1: Framework (SQL/Framework) ISO/IEC 9075-2:2011, Information technology Database languages SQL Part 2: Foundation (
45、SQL/Foundation) ISO/IEC 11179-3, Information technology Metadata registries (MDR) Part 3: Registry metamodel and basic attributes ISO/IEC 19763-10, Information technology Metamodel framework for interoperability (MFI) Part 10: MFI Core model and basic mapping 4 T erms, d efinitions , and abbr e viat
46、 ed t erms 4.1 T erms and definiti ons For the purposes of this document, the following terms and definitions apply. 4.2 Terms for concepts used in this part of 19763 4.2.1 aggregation special form of relationship (4.2.37) that specifies a whole-part relationship between the aggregate (whole) and a
47、component part Note 1 to entry: Adapted from ISO/TS 19103:2005, 4.2.2. 4.2.2 association semantic relationship (4.2.37) between two object classes (4.2.35) Note 1 to entry: Adapted from ISO/IEC 11179-3:2013. 4.2.3 associative entity type information model element (4.2.25) that has both relationship
48、(4.2.37) and entity type (4.2.21) properties Note 1 to entry: May also be known as an association class. Note 2 to entry: An associative entity type can be seen as a relationship that also has entity type properties or as an entity type that also has relationship properties. Note 3 to entry: Adapted
49、 from ISO/IEC 19501:2005, 5.46.1. 4.2.4 attribute named characteristic of an entity type (4.2.21) whose values serve to qualify, identify, classify, quantify or express the state of an instance of an entity type 4.2.5 at t r ibu t e u n ique ide nt i f ie r e le me nt unique identifier element (4.2.45) that is a statement that a particular attribute (4.2.4) is part of a particular unique identifier (4.2.44) 4.2.6 cardinalit
