ISO/IEC JTC 1/SC 32/WG 2 - MetaData

This document describes TUpper as an ontology that is conformant to the requirements specified for top-level ontologies in ISO/IEC 21838-1. This document describes TUpper as a resource designed to support ontology design, ontology integration, automated reasoning, and semantic integration of heterogeneous information systems. The following are within the scope of this document: — definitions of classes and relations in the signature of TUpper; — axiomatizations of TUpper in OWL 2 and CL; — documentation of the conformity of TUpper to the requirements specified for top-level ontologies in ISO/IEC 21838-1; — documentation of the methodology for specifying domain ontologies that conform to TUpper. The following are outside the scope of this document: — specification of ontology languages, including the languages RDF, OWL and CL standardly used in ontology development; — specification of methods for reasoning with ontologies; — specification of translators between the notations of ontologies developed in different ontology languages.

This document describes descriptive ontology for finguistic and cognitive engineering (DOLCE) as an ontology that is conformant to the requirements specified for top-level ontologies in ISO/IEC 21838-1. This document describes DOLCE as a resource designed to support ontology design, ontology integration, and semantic integration of heterogeneous information systems. The following are within the scope of this document: — definitions of classes and relations in the signature of DOLCE; — axiomatizations of DOLCE in OWL 2 and CL; — documentation of the conformity of DOLCE to the requirements specified for top-level ontologies in ISO/IEC 21838-1; — documentation of the methodology for specifying domain ontologies that conform to DOLCE. The following are outside the scope of this document: — specification of ontology languages, including the languages RDF, OWL, and CL standardly used in ontology development; — specification of methods for reasoning with ontologies; — specification of translators between the notations of ontologies developed in different ontology languages.

This document specifies the information to be recorded in a metadata registry in the form of a conceptual data model: — Clause 5 specifies the approach used to model a metadata registry; — Clause 6 specifies the Core Model of the registry, including basic types and classes to be reused in extending the model. The core model defines a generic “registry item”, from which any type of item that needs to registered can be sub-classed; — Clause 7 specifies the metamodel for Identification of registry items; — Clause 8 specifies the metamodel for Designation and Definition of registry items; — Clause 9 specifies the metamodel for Registration of registry items; — Clause 10 specifies the metamodel for Classification of registry items; — Clause 11 specifies the metamodel for Mapping among registry items.

This document provides a specification for an extension to a metadata registry (MDR), as specified in ISO/IEC 11179-3:2023, in which metadata that describes concept systems can be registered. The specification in this document, together with the relevant clauses of the specification in ISO/IEC 11179-3, provides the ability to record the following metadata: concept systems and associated concepts; relations among concepts in a concept system; assertions about concepts in a concept system. The metamodel in this document is intended to support the full description of a concept system, including ontologies. Where there is a requirement to register an ontology where the details are defined elsewhere, consider using ISO/IEC 19763-3 instead.

This document provides a specification for an extension to a Metadata Registry (MDR), as specified in ISO/IEC 11179-3, in which metadata that describes data elements and associated concepts, such as “data element concepts”, “conceptual domains” and “value domains” can be registered. The specification in this document, together with the relevant clauses of the specification in ISO/IEC 11179-3, provides the ability to record metadata about: a) data elements, units of measure and derivation rules; b) data element concepts and associated object classes and properties; c) conceptual domains, conceptual domain subsets and value meanings; d) value domains, value domain subsets, datatypes and permissible values. This document is applicable to the formulation of data representations, concepts, meanings and relationships to be shared among people and machines, independent of the organization that produces the data. It is not applicable to the physical representation of data as bits and bytes at the machine level.

This document defines the type of information to be specified, the conditions to be met, and the procedure(s) to be followed for each item to be registered in a metadata registry. The requirements and procedures contained herein apply to all types of items specified in ISO/IEC 11179‑3, ISO/IEC 11179‑31, ISO/IEC 11179‑32, ISO/IEC 11179‑33, ISO/IEC 11179‑35 and those specified in ISO/IEC 19763. Some Registration Authorities can use this document to register and manage locally defined metadata item types that are not defined in ISO/IEC 11179 or ISO/IEC 19763. This document addresses the common metadata that is used to document the common facilities of a registry: administration, identification, naming and definition, details that can apply to any and all types of registry items. This document does not address the metadata that is specific to particular types of registry items, such as data elements and value domains. This document does not specify the registry's system design, file organization techniques, storage media, programming languages, etc. to be used in its implementation.

This document provides the means for understanding and associating the individual parts of ISO/IEC 11179 and is the foundation for a conceptual understanding of metadata and metadata registries. This document also describes the relationship of ISO/IEC 11179 to other JTC 1/SC 32 standards, technical specifications and technical reports on metadata. In all parts of ISO/IEC 11179, metadata refers to descriptions of data. It does not contain a general treatment of metadata.

This document provides a possible instantiation of the registry metamodel specified in ISO/IEC 11179-3 using the SQL database language as specified in ISO/IEC 9075-2.

This document describes Basic Formal Ontology (BFO), which is an ontology that is conformant to the requirements specified for top-level ontologies in ISO/IEC 21838‑1. It describes BFO as a resource designed to support the interchange of information among heterogeneous information systems. The following are within the scope of this document: — definitions of BFO-2020 terms and relations; — axiomatizations of BFO-2020 in OWL 2 and CL; — documentation of the conformity of BFO-2020 to the requirements specified for top-level ontologies in ISO/IEC 21838‑1; — specification of the requirements for a domain ontology if it is to serve as a module in a suite of ontologies in which BFO serves as top-level ontology hub by providing a starting point for the introduction of the most general terms in those domain ontologies which are its nearest neighbours within the suite; — specification of the role played by the terms in BFO in the formulation of definitions and axioms in ontologies at lower levels that conform to BFO. The following are outside the scope of this document: — specification of ontology languages, including the languages RDF, OWL, and CL standardly used in ontology development; — specification of methods for reasoning with ontologies; — specification of translators between the notations of ontologies developed in different ontology languages.

The primary purpose of the ISO/IEC 19763 series is to specify a metamodel framework for interoperability. This document specifies a metamodel for registering document models (or schemata). Examples of such document models include: — specifications for XML documents (using XML schema[3]); — specifications for JSON documents (using JSON schema[2]). This metamodel was developed taking into account the requirements for both XML schema and JSON schema, but is applicable to all current specifications for document models.

This document specifies required characteristics of a domain-neutral top-level ontology (TLO) that can be used in tandem with domain ontologies at lower levels to support data exchange, retrieval, discovery, integration and analysis. If an ontology is to provide the overarching ontology content that will promote interoperability of domain ontologies and thereby support the design and use of purpose-built ontology suites, then it needs to satisfy certain requirements. This document specifies these requirements. It also supports a variety of other goals related to the achievement of semantic interoperability, for example, as concerns legacy ontologies developed using heterogeneous upper-level categories, where a coherently designed TLO can provide a target for coordinated re-engineering. This document specifies the characteristics an ontology needs to possess to support the goals of exchange, retrieval, discovery, integration and analysis of data by computer systems. The following are within the scope of this document — Specification of the requirements an ontology needs to satisfy if it is to serve as a top-level hub ontology. — Specification of the relations between a top-level ontology and domain ontologies. — Specification of the role played by the terms in a top-level ontology in the formulation of definitions and axioms in ontologies at lower levels. The following are outside the scope of this document: — Specification of ontology languages, including the languages OWL 2 and CL, used in ontology development with standard model-theoretic semantics. — Specification of methods for reasoning with ontologies. — Specification of translators between notations of ontologies developed in different ontology languages. — Specification of rules governing the use of IRIs as permanent identifiers for ontology terms. — Specification of the principles of ontology maintenance and versioning. — Specification of how ontologies can be used in the tagging or annotation of data.

This document specifies the metamodel that provides a facility to register administrative and evolution information related to ontologies. The metamodel is intended to promote interoperability among application systems, by providing administrative and evolution information related to ontologies, accompanied with standardized ontology repositories that register ontologies themselves in specific languages. This document does not specify the metamodels of ontologies expressed in specific languages and the mappings among them.

This document specifies the message exchange framework for communicating data element definitions with an ISO/IEC 11179-3 metadata registry (MDR). It defines message semantics, protocols and bindings for a set of transactions allowing the exchange of a commonly used subset of data element metadata with an ISO/IEC 11179-3 MDR. This document establishes the following data element message exchange interoperability specifications: — retrieving data element list from an ISO/IEC 11179-3 MDR matching the selection criteria; — retrieving metadata of a selected data element from an ISO/IEC 11179-3 MDR.

This document describes the basic concept of metadata, and its relationship to both data and metamodels.

This document compliments ISO/IEC 11179-3 by describing registration of classification schemes and using them to classify registered items in an MDR. Any metadata item can be made a Classifiable_Item so it can be classified, which can include object classes, properties, representations, conceptual domains, value domains, data element concepts and data elements themselves. This document does not establish a particular classification scheme as pre-eminent. Sanction of a particular taxonomic approach and/or a particular epistemology is also beyond the scope of this document. These are addressed by other standards committees and/or tend to be tailored to a particular domain of discourse. The MDR can establish its own classification schemes, and other standards committees are developing or have developed normative languages for use in classification and/or particular techniques and structures that can be accommodated by this document. Each registration authority, as described and specified in ISO/IEC 11179-6, can classify classifiable items according to the classification schemes, structures and content that it deems appropriate. In documenting the classification aspects of classifiable items, the registration authority can use the principles, methods, procedures and attributes covered in this document.

This document provides a usage scenario that utilizes the facilities defined in ISO/IEC 11179-3, ISO/IEC 19763-5 and ISO/IEC 19763-10 to demonstrate the registration of the mapping between process models. The availability of these registered process model mappings will help to promote the reuse of process models. The scope of this document is limited to a discussion of the process models associated with software development projects and the deliverables produced during these projects. This document describes a scenario that evaluates the combined usage of ISO/IEC 11179-3, ISO/IEC 19763-5 and ISO/IEC 19763-10 to enable the reuse of past knowledge of process models describing project processes and deliverables.

The primary purpose of the ISO/IEC 19763 series is to specify a metamodel framework for interoperability. ISO/IEC TS 19763-13(E) specifies a metamodel for registering form designs. ISO/IEC TS 19763-13(E) provides a metamodel to describe the structure and semantics of an implemented form devoid of any specific, domain semantics, e.g. in healthcare, social science, e-government and e-business, or representation format so that data may be faithfully exchanged between systems and system components, and associations expressed between sets of form designs whose data may be compared, joined or composed for analysis.

ISO/IEC TR 19763-9:2015 specifies a technical guideline on how to use the Role and Goal, Process, and Service (RGPS) metamodels to select appropriate combinations of models and/or services to support user-requests. The scope of ISO/IEC TR 19763-9 is limited to model selection based on ISO/IEC 19763-5, ISO/IEC 19763-7, and ISO/IEC 19763-8.

The primary purpose of the multipart standard ISO/IEC 19763 is to specify a metamodel framework for interoperability. ISO/IEC 19763-7:2015 specifies a metamodel for registering models of services, facilitating interoperability through the reuse of services. ISO/IEC 19763-7:2015 is only applicable to web services whose capabilities are described by some web service description language (see Annex A for examples of such languages). Figure 1 shows the scope of ISO/IEC 19763‑7:2015.

The primary purpose of the multipart standard ISO/IEC 19763 is to specify a metamodel framework for interoperability. ISO/IEC 19763-7:2015 specifies a metamodel for registering models of services, facilitating interoperability through the reuse of services. ISO/IEC 19763-7:2015 is only applicable to web services whose capabilities are described by some web service description language (see Annex A for examples of such languages). Figure 1 shows the scope of ISO/IEC 19763‑7:2015.

The ISO/IEC 19763 family of standards defines normative metamodels for the registration of models (including information models and process models), ontologies, services and roles & goals. Currently a lot of metadata registries or model registries were constructed and utilized in many different business domains, such as e-business, healthcare, automobile, electronics devices and civil construction. One of the key issues for the cross domain data or services integration must be enabling the easy discovery of metadata that are stored in the different registries that were scattered over different domains. Therefore, it is necessary to provide specific metadata that describes the registry itself in order to enable interoperation among different registries that were built following different standards. ISO/IEC 19763:2015 family of standards specifies an information artefact called the Registry Summary. The Registry Summary consists of information that describes administrative aspects, the summary of contents and the technical access method of the registry. A collection of multiple Registry Summary information is called a "Registry of Registries" or RoR, however, this standard does not mandate a particular implementation. Also, any specific protocol between Registry Summaries and RoR, such as creation of RoR and synchronization of RoR, would not be specified in this standard. Those are to be specified by other standards. The Registry Summary and RoR concept should be applied to all Metamodel Framework for Interoperability (MFI) registries, but its use may be applied to any kind of registries.

The primary purpose of the multipart standard ISO/IEC 19763 is to specify a metamodel framework for interoperability. ISO/IEC 19763-5:2015 specifies the metamodel that describes a facility to register administrative information and selected metadata about process models. The metamodel specified in ISO/IEC 19763‑5:2015 is intended to promote semantic discovery and reuse of process models within/across process model repositories. For this purpose, it provides selected metadata and common semantics of process models created with a specific process modelling language, including Business Process Model and Notation (BPMN), UML (Unified Modelling Language) Activity Diagram and EPC (Event-driven Process Chain), etc. The metamodel can help discovery of the function and composition of a process, and promote reuse of its components at different levels of granularity.

ISO/IEC 11179-5:2015 provides instruction for naming of the following items, as defined in ISO/IEC 11179‑3: concept, data element concept, conceptual domain, data element, and value domain. ISO/IEC 11179-5:2015 describes naming in a metadata registries (MDR); includes principles and rules by which naming conventions can be developed; and provides examples of naming conventions.

The ISO/IEC 19763 multipart International Standard specifies a metamodel framework for interoperability. ISO/IEC 19763-12:2015 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 requirements 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).

The ISO/IEC 20944 series of International Standards provides the bindings and their interoperability for metadata registries, such as those specified in the ISO/IEC 11179 series of International Standards. ISO/IEC 20944-2:2013 contains provisions that are common to coding bindings and the coding bindings themselves. The coding bindings have commonality in their conceptualization of data instances and their internal structures. Common features include: using datatypes to characterize the nature and operations upon data; using ISO/IEC 11404 to define and declare datatypes; using common aggregate structures, such as array and record, to describe sets of data; using common navigation descriptions to reference components within a set of data. The individual coding bindings each incorporate a mapping of common data semantics to their individual binding requirements. XML and DIVP (dotted identifier value pair) bindings are provided.

The ISO/IEC 20944 series of International Standards provides the bindings and their interoperability for metadata registries, such as those specified in the ISO/IEC 11179 series of International Standards. ISO/IEC 20944-4:2013 contains provisions that are common to protocol bindings and the protocol bindings themselves. The protocol bindings have commonality in their conceptualization of the services provided. Common features include: common data transfer semantics; harmonized session services for connection-oriented and connection-less protocols. Bindings for HTTP and WebDAV protocols are provided.

The ISO/IEC 20944 series of International Standards provides the bindings and their interoperability for metadata registries, such as those specified in the ISO/IEC 11179 series of International Standards. ISO/IEC 20944-1:2013 contains an overview, framework, common vocabulary, and common provisions for conformance for the ISO/IEC 20944 series of International Standards.

The ISO/IEC 20944 series of International Standards provides the bindings and their interoperability for metadata registries, such as those specified in the ISO/IEC 11179 series of International Standards. ISO/IEC 20944-5:2013 contains provisions that are common to the profiles, and the profiles themselves. A profile of ISO/IEC 11179-3:2003 is included, which maps ISO/IEC 11179 metadata attributes to standardized identifiers for navigation and access of ISO/IEC 11179 metadata.

The ISO/IEC 20944 series of International Standards provides the bindings and their interoperability for metadata registries, such as those specified in the ISO/IEC 11179 series of International Standards. ISO/IEC 20944-3:2013 contains provisions that are common to application programming interface (API) bindings and the API bindings themselves. The API bindings have commonality in their conceptualization of the services provided. Common features include: using a session paradigm to access data; using a parameterized security framework to support a variety of security techniques; using a hierarchical navigation for data access. Bindings for C, Java, and ECMAscript programming languages are provided.

ISO/IEC 19773:2011 specifies small modules of data that can be used or reused in applications. These modules have been extracted from ISO/IEC 11179-3, ISO/IEC 19763, and OASIS EBXML, and have been refined further. These modules are intended to harmonize with current and future versions of the ISO/IEC 11179 series and the ISO/IEC 19763 series. These modules include: reference-or-literal (reflit) for on-demand choices of pointers or data; multitext, multistring, etc. for recording internationalized and localized data within the same structure; slots and slot arrays for standardized extensible data structures; internationalized contact data, including UPU postal addresses, ITU-T E.164 phone numbers, internet E-mail addresses, etc.; generalized model for context data based upon who-what-where-when-why-how (W5H); data structures for reified relationships and entity-person-groups. Conformity can be selected on a per-module basis.

ISO/IEC 14957:2010 specifies the notation to be used for stating the format, i.e. the character classes, used in the representation of data elements and the length of these representations. It also specifies additional notations relative to the representation of numerical figures. For example, this formatting technique might be used as part of the metadata for data elements. The scope of ISO/IEC 14957:2010 is limited to graphic characters, such as digits, letters and special characters. The scope is limited to the basic datatypes of characters, character strings, integers, reals, and pointers.

ISO/IEC 11404:2007 specifies the nomenclature and shared semantics for a collection of datatypes commonly occurring in programming languages and software interfaces, referred to as the General-Purpose Datatypes (GPD). It specifies both primitive datatypes, in the sense of being defined ab initio without reference to other datatypes, and non-primitive datatypes, in the sense of being wholly or partly defined in terms of other datatypes. The specification of datatypes in ISO/IEC 11404:2007 is "general-purpose" in the sense that the datatypes specified are classes of datatype of which the actual datatypes used in programming languages and other entities requiring the concept "datatype" are particular instances. These datatypes are general in nature; thus, they serve a wide variety of information processing applications. ISO/IEC 11404:2007 expressly distinguishes three notions of datatype: the conceptual, or abstract, notion of a datatype, which characterizes the datatype by its nominal values and properties; the structural notion of a datatype, which characterizes the datatype as a conceptual organization of specific component datatypes with specific functionalities; and the implementation notion of a datatype, which characterizes the datatype by defining the rules for representation of the datatype in a given environment. ISO/IEC 11404:2007 defines the abstract notions of many commonly used primitive and non-primitive datatypes which possess the structural notion of atomicity. ISO/IEC 11404:2007 does not define all atomic datatypes; it defines only those which are common in programming languages and software interfaces. ISO/IEC 11404:2007 defines structural notions for the specification of other non-primitive datatypes, and provides a means by which datatypes not defined herein can be defined structurally in terms of the GPDs defined herein. ISO/IEC 11404:2007 defines a partial terminology for implementation notions of datatypes and provides for the use of this terminology in the definition of datatypes. The primary purpose of this terminology is to identify common implementation notions associated with datatypes and to distinguish them from conceptual notions. ISO/IEC 11404:2007 specifies the required elements of mappings between the GPDs and the datatypes of some other language. ISO/IEC 11404:2007 does not specify the precise form of a mapping, but rather the required information content of a mapping.

ISO/IEC 11179-4:2004 specifies requirements and recommendations for constructing definitions for data and metadata. Only semantic aspects of definitions are addressed; specifications for formatting the definitions are deemed unnecessary for the purposes of this standard. While especially applicable to the content of metadata registries as specified in ISO/IEC 11179-3, ISO/IEC 11179-4:2004 is useful broadly for developing definitions for data and metadata. These definitional requirements and recommendations pertain to formulating definitions for data elements and other types of data constructs such as entity types, entities, relationships, attributes, object types (or classes), objects, composites, code entries, metadata items, and the data referred to by XML tags.

The purpose of this technical report is to describe a set of procedures for the consistent registration of value domains and their attributes in a registry. This technical report is not a data entry manual, but a user's guide for conceptualizing a value domain and its components for the purpose of consistently establishing good quality metadata. An organization may adapt and/or add to these procedures as necessary.

An ISO/IEC 11179-based metadata registry (MDR) (hereafter referred to as a "registry") is a tool for the management of shareable data; a comprehensive, authoritative source of reference information about data. It supports the standardization and harmonization processes by recording and disseminating data standards, which facilitates data sharing among organizations and users. It provides links to documents that refer to data elements and to information systems where data elements are used. When used in conjunction with an information database, the registry enables users to better understand the information obtained. A registry does not contain data itself. It contains the metadata that is necessary to clearly describe, inventory, analyze, and classify data. It provides an understanding of the meaning, representation, and identification of units of data. The standard identifies the information elements that need to be available for determining the meaning of a data element (DE) to be shared between systems. The purpose of ISO/IEC TR 20943-1:2003 is to describe a set of procedures for the consistent registration of data elements and their attributes in a registry. ISO/IEC TR 20943-1:2003 is not a data entry manual, but a user's guide for conceptualizing a data element and its associated metadata items for the purpose of consistently establishing good quality data elements. An organization may adapt and/or add to these procedures as necessary. The scope of ISO/IEC TR 20943-1:2003 is limited to the associated items of a data element: the data element identifier, names and definitions in particular contexts, and examples; data element concept; conceptual domain with its value meanings; and value domain with its permissible values. There is a choice when registering code sets and other value domains in an ISO/IEC 11179 metadata registry. Some Registration Authorities treat these sets as value domains, and others treat them as data elements. For the purposes of ISO/IEC TR 20943-1:2003, the choice will always be to treat the sets as data elements unless explicitly stated. This choice is made to help illustrate the way to register many different kinds of data elements, including examples for registering standard code sets as data elements.

This part of ISO/IEC 6523 specifies the procedure for registration of organization identification schemes, and the requirements for the administration of International Code Designator values, to designate these organization identification schemes.

Replaces the wording of some clauses and subclauses of ISO/IEC 10728:1993 and adds a new annex E.

Contains a great number of amendments and additions; Information Resource Dictionary System (IRDS) services interface; ADA language binding.

Contains some amendments and adds the annex C - C language binding.

Provides general guidance on the manner on which data can be expressed by codes. Describes the objectives of coding, the characteristics, advantages and disadvantages of different coding methods, the features of codes and gives guidelines for the design of codes. Examples of applications are ISO 9735:1988, ISO 8601:1988, ISO 3166:1993.

The services interface specified gives any program full access to all IRDS services. Defines the semantics of this interface, and also specifies the language bindings for ISO Pascal (ISO 7185). Language bindings for other ISO standard programming languages are provided as separate standards. Makes no assumptions about an implementation environment, and assumes no specific run-time or compile time interfaces. Details of the IRDS series of standards are to be found in ISO/IEC 10027.

This Technical Report type 3 contains the fundamental concepts and terminology for the conceptual schema, the information base, and the mechanisms involved in manipulating them. The approaches and associated languages described in the appendices A through H are intended to be explanatory only.

This document provides a specification for an extension to a Metadata Registry (MDR), as specified in ISO/IEC 11179-3:2013, Clauses 5 to 11 in which metadata which describes data sets, collections of data available for access or download in one or more formats, can be registered. Since a set can contain a single element, this document enables the recording of metadata about a single data value. The registered metadata provides information about the data set that includes the provenance and the quality of the dataset.

This document specifies basic attributes which are required to describe data elements and associated metadata, and which might be used in situations where a complete ISO/IEC 11179-3 metadata registry is not appropriate (e.g. in the specification of other International Standards).

ISO/IEC 11179-1:2015 provides the means for understanding and associating the individual parts of ISO/IEC 11179 and is the foundation for a conceptual understanding of metadata and metadata registries. ISO/IEC 11179-1:2015 is applicable to the formulation of data representations, concepts, meanings and relationships to be shared among people and machines, independent of the organization that produces the data. It is not applicable to the physical representation of data as bits and bytes at the machine level. In this part of ISO/IEC 11179-1:2015 (and all other parts), metadata refers to descriptions of data. It does not contain a general treatment of metadata.

ISO/IEC 11179-6:2015 defines the type of information to be specified, the conditions to be met, and the procedure(s) to be followed for each metadata item to be registered in a metadata registry. The requirements and procedures contained herein apply to all metadata items specified in ISO/IEC 11179‑3 and those specified in ISO/IEC 19763. Some Registration Authorities may want to use this part of ISO/IEC 11179 to register and manage locally defined metadata item types that are not defined in ISO/IEC 11179‑3 or ISO/IEC 19763. ISO/IEC 11179-6:2015 addresses the common metadata that is used to document the common facilities of a metadata registry: administration, identification, naming and definition, details that can apply to any and all types of metadata items.

ISO/IEC19763-1:2015 (Metamodel framework for interoperability) (MFI) family of standards. As the first part of MFI, this part provides an overview of the whole of MFI. In particular, the purpose, the underlying concepts, the overall architecture and the requirements for the development of other standards within the MFI family are described. MFI provides a set of normative metamodels to enable the registration of many different types of model. Each of these metamodels is expressed as a UML Class Diagram. MFI is evolving. Currently, in addition to this part, the MFI family comprises: · A core model and facilities for the basic mapping of models (Part 10) · A metamodel for ontology registration (Part 3) · A metamodel for process model registration (Part 5) · A metamodel for service model registration (Part 7) · A metamodel for role and goal model registration (Part 8) · A Technical Report describing on demand model selection based on RGPS (Role, Goal, Process and Service) (Part 9) · A metamodel for information model registration (Part 12) · A metamodel for form design registration (Part 13) · A metamodel for a registry summary (Part 6) These parts are described in more detail in Annex A.