ISO/IEC JTC 1/SC 32 - Data management and interchange

This document specifies a uniform representation of human sexes for the interchange of information. It is intended to: — reduce the time required to record and/or format the representation of sexes and transmit the corresponding data; — improve clarity and accuracy of interchange; — minimize the amount of human intervention required for communicating the representation of sexes; and — reduce costs. This document does not prescribe file sequences, storage media, programming languages, or other features of information processing to be used in its implementation. This document meets the requirements of most applications that need to code human sexes. It does not provide codes for sexes that can be required in specific medical and scientific applications or in applications that need to code sex information other than for human beings. It also does not provide codes for human gender identities that can be required in other applications. This document does not supplant national standards for coding sexes that are designed based upon codes derived from names of sexes in the various languages (for example “M” for “male” and “F” for “female” in the English language). It provides a numeric code that is independent of language-derived codes and as such is intended to provide a common basis for the international exchange of information containing human sex data elements.

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 describes the support in SQL for JavaScript Object Notation. This document discusses the following features of the SQL language: — Storing JSON data. — Publishing JSON data. — Querying JSON data. — SQL/JSON data model and path language.

This document provides a tutorial of SQL routines and types using the Java™ programming language. This document discusses the following features of the SQL Language: — The use of routines written in the Java programming language within SQL expressions and statements. — The use of user-defined types written in the Java programming language within SQL expressions and statements.

This document describes the definition and use of multidimensional arrays in SQL. Multidimensional arrays represent a core underlying structure of manifold science and engineering data. It is generally recognized today, therefore, that arrays have an essential role in Big Data and should become an integral part of the overall data type orchestration in information systems. This document discusses the syntax and semantics of operations on the MD-array data type defined in ISO/IEC 9075-15.

This document describes the support for the use of SQL within programs written in Java. This document discusses the following features of the SQL language: — The embedding of SQL expressions and statements in programs written in the Java programming language.

This document discusses the syntax and semantics for recognizing patterns in rows of a table, as defined in ISO/IEC 9075-2, commonly called “SQL/RPR”. SQL/RPR defines two features regarding row pattern recognition: — Feature R010, “Row pattern recognition: FROM clause” — Feature R020, “Row pattern recognition: WINDOW clause” These two features have considerable syntax and semantics in common, the principle difference being whether the syntax is placed in the FROM clause or in the WINDOW clause.

This document describes the definition and use of polymorphic table functions in SQL. The Report discusses the following features of the SQL Language: — The processing model of polymorphic table functions in the context of SQL. — The creation and maintenance of polymorphic table functions. — Issues related to methods of implementing polymorphic table functions. — How polymorphic table functions are invoked by application programs. — Issues concerning compilation, optimization, and execution of polymorphic table functions.

This document describes the support in SQL for time-related information. This document discusses the following features of the SQL language: — Time-related data types — Operations on time-related data — Time-related Predicates — Application-time period tables — System-versioned tables — Bi-temporal tables

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: — examines the basic concepts that have been developed for both cloud computing and Open-edi; — identifies key Open-edi concepts relevant to cloud computing; — identifies key cloud computing concepts relevant to Open-edi; — compares Open-edi model and cloud computing architecture and identifies mappings (similarities in whole or in part) between them using formal semantic modelling techniques.

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 discusses the syntax and semantics for including online analytic processing (OLAP) capabilities in SQL, as defined in ISO/IEC 9075-2. It discusses the following features regarding OLAP capabilities of the SQL language: — Feature T611, "Elementary OLAP operations", — Feature T612, "Advanced OLAP operations", — Feature T614, "NTILE function", — Feature T615, "LEAD and LAG functions", — Feature T616, "Null treatment option for LEAD and LAG functions", — Feature T617, "FIRST_VALUE and LAST_VALUE functions", — Feature T618, "NTH_VALUE function", — Feature T619, "Nested window functions", — Feature T620, "WINDOW clause: GROUPS option", — Feature T621, "Enhanced numeric functions".

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: — provides method(s) for identifying, in Open-edi modelling technologies and development of scenarios, the additional requirements in business operational view (BOV) specifications for identifying the additional external constraints to be applied to recorded information in business transactions relating to personal information of an individual, as required by legal and regulatory requirements of applicable jurisdictional domains; — integrates existing normative elements in support of privacy and data protection requirements as are already identified in ISO/IEC 14662 and ISO/IEC 15944-1, ISO/IEC 15944-2, ISO/IEC 15944-4, ISO/IEC 15944-5, ISO/IEC 15944-8, ISO/IEC 15944-9, and ISO/IEC 15944-10; — provides overarching, operational ?best practice' statements for associated (and not necessarily automated) processes, procedures, practices and governance requirements that act in support of implementing and enforcing technical mechanisms which support the privacy/data protection requirements necessary for implementation in Open-edi transaction environments; — focuses on the life cycle management of personal information i.e., the contents of SPIs (and their SRIs) related to the business transaction interchanged via EDI as information bundles and their associated semantic components among the parties to a business transaction. NOTE Privacy protection requirements (PPR) on information life cycle management (ILCM) and EDI of personal information as stated in this document serve as a minimum set of ILCM policy and operational requirements for all recorded information pertaining to a business transaction in particular, as well as ILCM implementation in any organization in general. This document does not specify the technical mechanisms, i.e., functional support services (FSV) which are required to support BOV-identified requirements. Detailed exclusions to the scope of this document are provided in Annex H.

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).

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

This document defines ways in which Database Language SQL can be used in conjunction with multidimensional arrays.

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.

This document specifies a family of logic languages designed for use in the representation and interchange of information and data among disparate computer systems. The following features are essential to the design of this document. — Languages in the family have declarative semantics. It is possible to understand the meaning of expressions in these languages without appeal to an interpreter for manipulating those expressions. — Languages in the family are logically comprehensive ? at its most general, they provide for the expression of arbitrary first-order logical sentences. — Languages in the family are translatable by a semantics-preserving transformation to a common XML-based syntax, facilitating interchange of information among heterogeneous computer systems. The following are within the scope of this document: — representation of information in ontologies and knowledge bases; — specification of expressions that are the input or output of inference engines; — formal interpretations of the symbols in the language. The following are outside the scope of this document: — specification of proof theory or inference rules; — specification of translators between the notations of heterogeneous computer systems; — computer-based operational methods of providing relationships between symbols in the logical "universe of discourse" and individuals in the "real world". This document describes Common Logic's syntax and semantics. This document defines an abstract syntax and an associated model-theoretic semantics for a specific extension of first-order logic. The intent is that the content of any system using first-order logic can be represented in this document. The purpose is to facilitate interchange of first-order logic-based information between systems. Issues relating to computability using this document (including efficiency, optimization, etc.) are not addressed.

ISO/IEC 9075-3:2016 defines the structures and procedures that can be used to execute statements of the database language SQL from within an application written in a programming language in such a way that procedures used are independent of the SQL statements to be executed.

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 13249-1:2016 defines a number of packages of generic data types and table structures common to various kinds of data used in multimedia and application areas, to enable that data to be stored and manipulated in an SQL database. The package in each subject area is defined as a part of ISO/IEC 13249. ISO/IEC 13249-1:2016 defines those concepts, notations and conventions that are common to two or more other parts of ISO/IEC 13249. In particular, it describes the way parts of ISO/IEC 9075 are used to define the user-defined types and their behaviour and views as a representation of table structures appropriate to each subject area.

ISO/IEC 13249:2016 a) defines concepts specific to this part of ISO/IEC 13249, b) defines spatial user-defined types and their associated routines.

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 15944-20:2015 specifies the properties of Base Functional Specification View (FSV) Standards in order to best meet the requirements of the Business Operational View (BOV) with interoperable implementations. Base FSV standards exhibiting these properties support business transactions beyond those that are in compliance with Open-edi scenarios (OeS). Additional beneficial business transactions may also be supported between a given IT system and IT system(s) outside of the Open-edi scenarios for which they were designed. These base FSV standards address those aspects of interoperability between IT systems used among Parties of the Open-edi Community participating in the scenario. Examples of such standards include the choreography of interchanges among systems, and the foundational structure and syntax used to express Information Bundles (IB) in the interchanges.

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.

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.

ISO/IEC 15944-2:2015 specifies procedures to be followed in establishing, maintaining, and publishing registers of unique, unambiguous and permanent identifiers and meanings that are assigned to Open-edi scenarios and scenario components. In order to accomplish this purpose, ISO/IEC 15944-2:2015 specifies elements of information that are necessary to provide identification and meaning to the registered items and to manage the registration of these items. ISO/IEC 15944-2:2015 defines the procedures to be applied by qualified JTC1 Registration Authority(ies) appointed by the ISO and IEC council to maintain a register(s) of Open-edi scenarios and/or scenario components for the purpose of their reusability.

ISO/IEC 15944-9:2015 presents a framework consisting of several models, including a reference model, a model of concepts, a content model, an information model, as well as rules, templates and other technical specifications for traceability requirements based on internal or external constraints as applicable to a business transaction. The internal constraints are imposed in Open-edi due to mutual agreements among parties to a business transaction and the external constraints are invoked by the nature of a business transaction due to applicable laws, regulations, policies, etc. of jurisdictional domains which need to be considered in Open-edi business transactions. All requirements in ISO/IEC 15944-9:2015 originate from external constraints. However, parties to a business transaction may well by mutual agreement apply external constraints of this nature as internal constraints. The focus therefore of this traceability framework standard is on commitment exchange among autonomous parties to a business transaction. As such, this statement of scope includes the ability of the traceability framework to specify a group of structured and inter-related concepts pertaining to traceability as a legal or regulatory requirement in the Open-edi context, in addition to concepts that appear in other Parts of ISO/IEC 15944 these concepts having the characteristics of cultural adaptability through the use of multilingual terms and definitions; provide additional specifications for Open-edi scenarios and scenario components from the perspective of traceability as required by internal or external constraints in business transactions; provide a more detailed specification for business transactions regarding aspects of traceability, including refined models of Person, Data and Process in support of the ability for Open-edi to incorporate elements or characteristics of traceability in its information bundles (including their semantic components) and business processes; realize specifications and descriptions from the traceability requirements as rules and guidelines, to provide recommendations or guidance on Open-edi practices; and, provide revised primitive Open-edi scenario templates for traceability, integrating the modifications to the template from other existing Parts of ISO/IEC 15944. ISO/IEC 15944-9:2015 can be used by Open-edi implementers (including business modellers and system designers) and Open-edi standard developers in specifying Open-edi scenarios, developing Open-edi related standards, and implementing Open-edi rules and guidelines for Open-edi activities.

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-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.

This part of ISO/IEC 15944 discusses and describes the following three topics of eBusiness modelling: — fundamentals of business transaction modelling that describe the conceptual aspects of eBusiness; — principles of eBusiness modelling that specify the semantic aspect of business transactions and their components and relationships involved in the business transaction; — classification scheme of Open-edi scenarios based on eBusiness modelling.

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.

ISO/IEC 15944-4:2015 provides a set of UML class diagrams and conceptual explanations that circumscribe the Open-edi Business Transaction Ontology (OeBTO). It explains the mechanics of a business transaction state machine, the procedural component of an OeBTO, and the (internal) constraint component of OeBTO, its repository for business rules. ISO/IEC 15944-4:2015 addresses collaborations among independent trading partners as defined in ISO/IEC 15944‑1. ISO/IEC 15944-4:2015 applies to both binary collaborations (buyer and seller) and mediated collaborations (buyer, seller, third-party). The ontological features described herein propose standards only for the Business Operational View (BOV), that is, the business aspects of business transactions as they are defined in ISO/IEC 15944‑1.

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).

ISO/IEC 19763-10: 2014 specifies a metamodel framework for interoperability. This part of ISO/IEC 19763 specifies the metamodel that provides a facility to register administrative information and common semantics of models and mapping between two models. ISO/IEC 19763-10: 2014 does not specify the metamodel of models in a specific language, but provides a common core metamodel for the other parts of ISO/IEC 19763, each of which specifies a metamodel for a registry that can register models of a specific type, such as ontologies, process models or information models, in a number of different languages. ISO/IEC 19763-10: 2014 also provides a metamodel for registering the mappings between two models registered in those other parts of ISO/IEC 19763. ISO/IEC 19763-10: 2014 utilises the common facilities specified in ISO/IEC 11179‑3. ISO/IEC 11179 (all parts) specifies a metadata registry (MDR). These common facilities provide the ability to identify and register models and their associated model elements and modelling languages within a metadata registry used to register models.

The purpose of ISO/IEC TR 20943-5:2013 is to describe a procedure for establishing metadata crosswalks based on the ISO/IEC 11179 series, subsequently improving mapping quality between metadata. Therefore, ISO/IEC TR 20943-5:2013 describes a metadata mapping procedure (MMP), which can maximize the interoperability among ISO/IEC 11179-based registries through achieving metadata registry content consistency.

ISO/IEC TR 20943-6:2013 covers the framework for generating ontologies based on ISO/IEC 11179-3, and provides the procedure and mapping model for generating ontologies. ISO/IEC TR 20943-6:2013 describes a method to generate ontologies for a context using concepts in ISO/IEC 11179-3. Most ontologies are basically composed of classes (concepts), properties, relations between classes, and instances (objects or individuals). ISO/IEC TR 20943-6:2013 considers the generation of ontology consisting of a subset of ontology components required for defining ontologies at the conceptual level which is called "FGO_Ontology". ISO/IEC TR 20943-6:2013 uses the prefix "FGO_" to avoid confusion from homonym and to clearly identify each term. For example, "Property" is specified in ISO/IEC 11179-3 as well as in ISO/IEC TR 20943-6:2013, but the meaning is slightly different. ISO/IEC TR 20943-6:2013 defines FGO_Class, FGO_Property, and FGO_Relation to distinguish between components of FGO_Ontology and components of ISO/IEC 11179-3. ISO/IEC TR 20943-6:2013 specifies the method to generate ontologies using registered concepts in ISO/IEC 11179-3 Concepts metamodel region and Data description metamodel region. ISO/IEC TR 20943-6:2013 specifies a procedure and method for generating ontologies due to an application domain reusing concepts registered in a metadata registry. ISO/IEC TR 20943-6:2013 does not include a way to describe in a specific ontology description language, such as Resource Description Framework (RDF), RDF Schema (RDFS), Web Ontology Language (OWL), Topic Map, and Knowledge Interchange Format (KIF).

The primary purpose of ISO/IEC 15944-10:2013 is to provide, in a single consolidated document, an integrated approach for the key concepts and their definitions as well as rules pertaining to "coded domains" as they already exist in the multipart ISO/IEC 15944 eBusiness standard, especially Parts 1, 2, 5 and 8. It does so in a systematic and rules-based manner. As such, ISO/IEC 15944-10:2013 serves as a methodology and tool for an IT-enabled approach to existing widely used standards, specifications, authority files, pick-lists, etc., of a "codes representing X" nature, i.e. as ISO/IEC 15944-10:2013 compliant coded domains, involving the making of (legally-binding) commitments, based on common business practices. ISO/IEC 15944-10:2013 specifies the five key characteristics of coded domains and identifies twelve benefits of the use of coded domains. A key purpose of ISO/IEC 15944-10:2013 is to maximize and state very explicitly the level of "intelligence" at the highest and most precise required level with respect to the semantics of the actual data being interchanged among autonomous parties in a business transaction. Here the use of coded domains presents a simple and very pragmatic approach at the data element, i.e. semantic component level. It focuses on the development of intelligently coded data elements as part of coded domains. This involves rule-based, structured and pre-defined values whose purpose and use has been clearly stated and unambiguously defined (thereby facilitating an IT-enabled approach). In an Open-edi and eBusiness context ISO/IEC 15944-10:2013 supports the use of coded domains as re-useable business objects among participating parties in any type of business transaction. Coded domains can be used is support of any type of scenario component, i.e. "roles", and "Information Bundles (IBs)", and "semantic components (SCs)", as well as scenario attributes. Re-use of coded domains is supported through coded domains being registered through procedures specified in ISO/IEC 15944-2. The semantics of the data values in a coded domain are identified and referenced via unique and unambiguous "ID codes", i.e. as unique identifiers. With such unambiguous and unique ID codes, in ISO/IEC 15944-10:2013 compliant coded domains can be associated multiple human interface equivalents (HIEs) in many forms and languages. The approach taken here is that of the separation of the (single) IT interface requirements of semantic interoperability from their (multiple) human interface (linguistic) equivalents (required by the jurisdictional domains of the participating parties as well as those of an individual accessibility nature). Use of ISO/IEC 15944-10:2013 therefore facilitates semantic interoperability requirements of both jurisdictional domains and all kinds of parties to a business transaction [including where the buyer is an individual, and public policy requirements apply (e.g. consumer protection, privacy protection, individual accessibility, etc.)]. In addition to its twelve normative clauses and two normative annexes, ISO/IEC 15944-10:2013 provides extensive informative text in its Clause 0 "Introduction" and six informative annexes.

ISO/IEC 11179-3:2013 specifies the structure of a metadata registry in the form of a conceptual data model. While the model diagrams are presented in UML notation, ISO/IEC 11179-3:2013 does not assume nor endorse any specific system environment, database management system, database design paradigm, system development methodology, data definition language, command language, system interface, user interface, computing platform, or any technology required for implementation. ISO/IEC 11179-3:2013 does not directly apply to the actual use of data in communications and information processing systems. ISO/IEC 11179-3:2013 specifies basic attributes which are required to describe metadata items, and which might be used in situations where a complete metadata registry is not appropriate (e.g. in the specification of other 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-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.