1、BSI Standards PublicationBS ISO/IEC 19763-12:2015Information technology Metamodel framework forinteroperability (MFI)Part 12: Metamodel for information modelregistrationBS ISO/IEC 19763-12:2015 BRITISH STANDARDNational forewordThis British Standard is the UK implementation of ISO/IEC 19763-12:2015.T
2、he UK participation in its preparation was entrusted to TechnicalCommittee 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 a contract
3、. Users are responsible for its correct application. The British Standards Institution 2015.Published by BSI Standards Limited 2015ISBN 978 0 580 78361 6 ICS 35.040 Compliance with a British Standard cannot confer immunity from legal obligations.This British Standard was published under the authorit
4、y of the Standards Policy and Strategy Committee on 31 March 2015.Amendments/corrigenda issued since publicationDate T e x t a f f e c t e dInformation technology Metamodel framework for interoperability (MFI) Part 12: Metamodel for information model registrationTechnologies de linformation Cadre du
5、 mtamodle pour linteroprabilit (MFI) Partie 12: Mtamodle pour lenregistrement du modle dinformationINTERNATIONAL STANDARDISO/IEC 19763-12Reference number ISO/IEC 19763-12:2015(E)First edition 2015-03-15 ISO/IEC 2015BS ISO/IEC 19763-12:2015ii ISO/IEC 2015 All rights reservedCOPYRIGHT PROTECTED DOCUME
6、NT ISO/IEC 2015All 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 permission. Permission c
7、an be requested from either ISO at the address below or ISOs member body in the country of the requester.ISO copyright officeCase postale 56 CH-1211 Geneva 20Tel. + 41 22 749 01 11Fax + 41 22 749 09 47E-mail copyrightiso.orgWeb www.iso.orgPublished in SwitzerlandISO/IEC 19763-12:2015(E)BS ISO/IEC 19
8、763-12:2015ISO/IEC 19763-12:2015(E)Foreword ivIntroduction v1 Scope . 12 Conformance . 22.1 General . 22.2 Degree of conformance 22.2.1 General 22.2.2 Strictly conforming implementation 22.2.3 Conforming implementation . 22.3 Implementation Conformance Statement (ICS) . 23 Normative references 24 Te
9、rms, definitions, and abbreviated terms . 34.1 Terms and definitions . 34.2 Terms for concepts used in this part of 19763 34.3 Abbreviated terms . 85 Structure of MFI Information model registration 95.1 Overview of MFI Information model registration 95.2 Association between MFI Information model reg
10、istration and MFI Core and mapping 105.3 Metaclasses in MFI Information Model Registration 125.3.1 Attribute . 125.3.2 Attribute_Unique_Identifier_Element .135.3.3 Described_Domain 135.3.4 Diagram. 145.3.5 Domain 145.3.6 Entity_Specialisation_Hierarchy 155.3.7 Entity_Specialisation_Hierarchy_Foreign
11、_Key_Attribute .165.3.8 Entity_Type 165.3.9 Enumerated_Domain .185.3.10 Foreign_Key_Attribute 185.3.11 General_Constraint 185.3.12 Information_Model .195.3.13 Information_Modelling_Language .195.3.14 Key_Attribute . 195.3.15 Native_Key_Attribute .205.3.16 Non_Key_Attribute.205.3.17 Relationship 205.
12、3.18 Relationship_End 215.3.19 Relationship_End_Foreign_Key_Attribute .225.3.20 Relationship_End_Group 235.3.21 Relationship_End_Unique_Identifier_Element 235.3.22 Unique_Identifier 245.3.23 Unique_Identifier_Element 245.3.24 Valid_Value . 25Annex A (informative) Description of the metamodel 26Annex
13、 B (informative) Relationship of metaclasses to the MDR Metamodel 33Annex C (informative) Applicability of information modelling concepts to techniques .34Annex D (informative) Examples of information model registration .36Bibliography .61 ISO/IEC 2015 All rights reserved iiiContents PageBS ISO/IEC
14、19763-12:2015ISO/IEC 19763-12:2015(E)ForewordISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of In
15、ternational 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 interest. Other international organizations, governmental and non-governmental, in liai
16、son 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 those intended for its further maintenance are described in the ISO/IEC Directives, Part
17、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 www.iso.org/directives). Attention is drawn to the possibility that some of the element
18、s 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 the document will be in the Introduction and/or on the ISO list of patent declarations re
19、ceived (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 terms and expressions related to conformity assessment, as well as information about ISOs
20、adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the following URL: Foreword - Supplementary informationThe committee responsible for this document is ISO/IEC JTC 1, Information technology, SC 32, Data management and interchange.ISO/IEC 19763 consists of the following par
21、ts, 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 Part 6: Registry Summary Part 10: MFI Core model and basic mapping Part 12: Metamodel for
22、information model registrationThe 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: Metamodel for forms registrationiv ISO/IEC 2015 All rights reservedBS ISO/IEC 19763-12:2015I
23、SO/IEC 19763-12:2015(E)IntroductionThere 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 requirements that are met by the data stored in these systems are understood so that suitable data
24、 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 integral part of the systems are designed. These models are often called logical models. The subseq
25、uent 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 two systems can be registered using the facilities specified by this part of ISO/IEC 19763. The
26、 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 interoperate by exchanging information. ISO/IEC 2015 All rights reserved vBS ISO/IEC 19763-12:2015BS IS
27、O/IEC 19763-12:2015Information technology Metamodel framework for interoperability (MFI) Part 12: Metamodel for information model registration1 ScopeThe primary purpose of the multipart standard ISO/IEC 19763 is to specify a metamodel framework for interoperability. This part of ISO/IEC 19763 specif
28、ies 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 requirements of a particular area of interest, and those that represent the structure of a database wh
29、ich 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 and notations. The metamodel specified in this part of ISO/IEC 19763 was developed to cover the reg
30、istration 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 entity-relationship modelling notation, as described in References 6 and 12; the entity-relationsh
31、ip 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 described in Reference 2; the UML Class Diagram notation, as described in References 13 and 14; th
32、e 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.It is understood that these selected techniques represent all of the essential features of all infor
33、mation 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 part of ISO/IEC 19763 to those database structures that conform to the Core SQL specification. Core S
34、QL 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 Object Role Modeling (ORM) and “Natural language Information Analysis Method” (NIAM), collectively known
35、 as fact-based models, is out of scope for this part of ISO/IEC 19763.INTERNATIONAL STANDARD ISO/IEC 19763-12:2015(E) ISO/IEC 2015 All rights reserved 1BS ISO/IEC 19763-12:2015ISO/IEC 19763-12:2015(E)2 Conformance2.1 GeneralAn implementation claiming conformance with this part of ISO/IEC 19763 shall
36、 support the metamodel specified in Clause 5 depending on the degree of conformance as described below.2.2 Degree of conformance2.2.1 GeneralThe distinction between “strictly conforming” and “conforming” implementations is necessary to address the simultaneous needs for interoperability and extensio
37、ns. 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 specified by this part of ISO/IEC 19763.A strictly conforming implementation could be limited in usefulness, b
38、ut 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 19763.2.2.2 Strictly conforming implementationA strictly conforming implementationa) shall support the metamo
39、del specified in Clause 5, andb) shall not use, test, access, or probe for any extension features nor extensions to the metamodel specified in Clause 5.2.2.3 Conforming implementationA conforming implementationa) shall support the metamodel specified in Clause 5, andb) as permitted by the implementa
40、tion, 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 conforming implementations.NOTE 2 The use of extensions to the metamodel could cause undefined behaviour.2.3 Implementation Co
41、nformance Statement (ICS)An implementation claiming conformance with this part of ISO/IEC 19763 shall include an Implementation Conformance Statement statinga) whether it is a strictly conforming implementation (2.2.2) or a conforming implementation (2.2.3), andb) what extensions, if any, are suppor
42、ted or used if it is a conforming implementation.3 Normative referencesThe following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition
43、 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 Clause 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:201
44、1, Information technology Database languages SQL Part 1: Framework (SQL/Framework)ISO/IEC 9075-2:2011, Information technology Database languages SQL Part 2: Foundation (SQL/Foundation)ISO/IEC 11179-3, Information technology Metadata registries (MDR) Part 3: Registry metamodel and basic attributesISO
45、/IEC 19763-10, Information technology Metamodel framework for interoperability (MFI) Part 10: MFI Core model and basic mapping4 Terms, definitions, and abbreviated terms4.1 Terms and definitionsFor the purposes of this document, the following terms and definitions apply.4.2 Terms for concepts used i
46、n this part of 197634.2.1aggregationspecial form of relationship (4.2.37) that specifies a whole-part relationship between the aggregate (whole) and a component partNote 1 to entry: Adapted from ISO/TS 19103:2005, 4.2.2.4.2.2associationsemantic relationship (4.2.37) between two object classes (4.2.3
47、5)Note 1 to entry: Adapted from ISO/IEC 11179-3:2013.4.2.3associative entity typeinformation model element (4.2.25) that has both relationship (4.2.37) and entity type (4.2.21) propertiesNote 1 to entry: May also be known as an association class.Note 2 to entry: An associative entity type can be see
48、n as a relationship that also has entity type properties or as an entity type that also has relationship properties.Note 3 to entry: Adapted from ISO/IEC 19501:2005, 5.46.1.4.2.4attributenamed characteristic of an entity type (4.2.21) whose values serve to qualify, identify, classify, quantify or ex
49、press the state of an instance of an entity type4.2.5attribute unique identifier elementunique 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.6cardinalitynumber of elements in a collection (4.2.8)Note 1 to entry: Adapted from ISO/IEC 9075-2:2011. ISO/IEC 2015 All rights reserved 3BS ISO/IEC 19763-12:2015ISO/IEC 19763-12:2015(E)4.2.7catalognamed collection (4.2.8) of schemas (4.2.42) in a database
