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

This document provides a mapping between the ISO/IEC 11179-34 metamodel for computable data registration and the IEEE 2791 standard for bioinformatics analyses generated by high-throughput sequencing (HTS), to facilitate the production of IEEE 2791 objects from instances of ISO/IEC 11179-34 metamodel and the registration of IEEE 2791 objects as computable data within an MDR conforming to ISO/IEC 11179-34. This document is applicable to those who are submitting data to organizations that require metadata submissions in IEEE 2791 compliant format, as well as those aiming to register IEEE 2791 objects into an MDR that conforms to ISO/IEC 11179-34.

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

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 (IBs) and their associated Semantic Components (SCs) 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 primarily via enumerated rules which 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 possible instantiation of the registry metamodel specified in ISO/IEC 11179-3, ISO/IEC 11179-31, ISO/IEC 11179-32 using the SQL database language as specified in ISO/IEC 9075-2.

This document specifies the structure of ISO/IEC 11179-3:2013. It defines a mapping of the ISO/IEC 11179-3:2013 conceptual model to a formal schema representation based on the W3C Resource Description Framework (RDF). The schema is available as a separate artefact. This document specifies the principles and conventions that were followed to map classes, attributes, and associations of the conceptual model to a formal RDF schema. This document does not provide detailed explanatory details about the ISO/IEC 11179 series or RDF. For more information, refer to References [7] to [9].

This document addresses the fundamental requirements of the commercial and legal frameworks and their environments on business transactions. It also integrates the requirements of the information technology and telecommunications environments. In addition to the existing strategic directions of "portability" and "interoperability", the added strategic direction of ISO/IEC JTC 1 of "cultural adaptability" is supported in this document. It also supports requirements arising from the public policy/consumer environment, cross-sectoral requirements and the need to address horizontal issues. It integrates these different sets of requirements. (See Figure 3) This document allows constraints which include legal requirements, commercial and/or international trade and contract terms, public policy (e.g. privacy/data protection, product or service labelling, consumer protection), laws and regulations to be defined and clearly integrated into Open-edi through the BOV. This means that terms and definitions in this document serve as a common bridge between these different sets of business operational requirements, allowing the integration of code sets and rules defining these requirements to be integrated into business processes electronically. This document contains a methodology and tool for specifying common business practices as part of common business transactions in the form of scenarios, scenario attributes, roles, Information Bundles and Semantic Components. It achieves this by: 1) developing standard computer processable specifications of common business rules and practices as scenarios and scenario components; and thus, 2) maximizing the re-use of these components in business transactions.

This document describes the model of database language SQL as defined in ISO/IEC 9075-1, ISO/IEC 9075-2, and ISO/IEC 9075-11. The meanings of and the relationships between various concepts of that model are described in text and illustrated graphically. Background in the form of some historical review and a brief overview of key SQL features is included. NOTE 2 — In spite of the fact that the names of the ISO/IEC 9075 series of standards contain the phrase “database language”, the standards do not use the word “database” to describe the thing that SQL creates and on which it operates. The word “database” is used in many different contexts and has meanings wholly unrelated to the intent of the ISO/IEC 9075 series. Consequently, a variety of other terms are defined and used by the ISO/IEC 9075 series. The word “database” is frequently used in this document informally to mean “a collection of data managed by an SQL-implementation at any given time.”

This document provides a specification for an extension to a metadata registry (MDR), as specified in ISO/IEC 11179-3, in which metadata that describe computable data 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 computable data.

This document defines data structures and basic operations on property graphs. It provides capabilities for creating, accessing, querying, maintaining, and controlling property graphs and the data they comprise. This document specifies the syntax and semantics of a data management language for specifying and modifying the structure of property graphs and collections thereof. This document provides a vehicle for portability of data definitions and manipulation among GQL-implementations. Implementations of this document can exist in environments that also support application programming languages, end-user query facilities, and various tools for database design, data administration, and performance optimization.

This document: a) focuses on PbD aspects of privacy protection requirements as external constraints on any type of Person, (e.g. organization or public administration) involved in any kind of business transaction among such Persons which involves the electronic data interchange (EDI) of any personal information; b) establishes a fundamental set of privacy principles known as Privacy by Design and assumptions based on primary sources; c) integrates existing normative elements in support of PbD as are already identified in ISO/IEC 14662 and ISO/IEC 15944-1, ISO/IEC 15944-5, ISO/IEC 15944-8, ISO 15944-12; d) provides overarching operational ‘best practice’ statements for associated (and not necessarily automated) processes, procedures, practices and governance requirements that need to act in support of implementing and enforcing technical mechanisms that support PbD in Open-edi transaction and collaboration space environments; e) focuses on PbD related aspects of the life cycle management of and accountability for the 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. This document focuses on the BOV aspects of a business transaction and does not concern itself with the technical mechanisms needed to implement the FSV aspects of the business requirements of the FSV including the specification of requirements of an FSV nature which include security techniques and services, communication protocols, etc.). The FSV includes any existing standard (or standards development of an FSV nature), which has been ratified by existing ISO, IEC, UN/ECE and/or ITU standards. This document does not specify the technical mechanisms, i.e. FSV which are required to support BOV-identified requirements. Detailed exclusions to the scope of this document are provided in Annex D.

This document provides the criteria for effective concept systems. It provides the requirements for components, formation, representations, structural levels and management of concept systems. Concept systems are used in the description of semantics of data in ISO/IEC 11179 standards.

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 a structure for globally and unambiguously identifying organizations, and parts thereof, for the purpose of information interchange. This document also gives recommendations regarding cases where prior agreements can be concluded between interchange partners. This document does not specify file organization techniques, storage media, languages, etc. to be used in its implementation. NOTE The procedure for registration of organization identification schemes is specified in ISO/IEC 6523-2.

This document provides an overview of the whole ISO/IEC 19763 series. This overview includes the purpose, the underlying concepts, the overall architecture and the requirements for the development of other standards within the 19763 series. Collectively, the other parts of the ISO/IEC 19763 series provide a set of normative metamodels to enable the registration of many different types of model. Each of these metamodels is expressed both as a UML class diagram and, more formally, in text. The metamodels, along with the specification in ISO/IEC 11179-3, define the information about the models that is to be registered. The models themselves can be stored in a model repository or can just exist as paper documents. The ISO/IEC 19763 series does not specify any physical structure of a registry where model information is to be recorded.

This document specifies the metamodel that provides a facility to register administrative information and common semantics of models. This document does not specify the metamodel of models in a specific language, but provides a common core metamodel for the other parts of the ISO/IEC 19763 series, 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.

This document provides a consolidated set of rules and associated guidelines as found and defined in the existing parts of the ISO/IEC 15944 series. NOTE Not all parts of the ISO/IEC 15944 series have rules, that is ISO/IEC 15944-6, ISO/IEC 15944-14 and ISO/IEC 15944-20.

This document: — specifies 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 series these concepts having the characteristics of cultural adaptability through the use of multilingual terms and definitions; — provides additional specifications for Open-edi scenarios and scenario components from the perspective of traceability as required by internal or external constraints in business transactions; — provides 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; — realizes specifications and descriptions from the traceability requirements as rules and guidelines, to provide recommendations or guidance on Open-edi practices; and, — provides revised primitive Open-edi scenario templates for traceability, integrating the modifications to the template from other existing parts of ISO/IEC 15944 series. This document 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. This document does not specify the FSV aspects of traceability, internal behaviour requirements of an organization, or traceability as a metrological concept. Detailed exclusions to the scope of this document are provided in Annex H.

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

ISO/IEC 9075-2 specifies embedded SQL for the programming languages: Ada, C, COBOL, Fortran, MUMPS, Pascal, and PL/I. ISO/IEC 9075-10:2016 defines similar features of Database language SQL that support embedding of SQL-statements into programs written in the Java? programming language (Java is a registered trademark of Sun Microsystems, Inc.). The embedding of SQL into Java is commonly known as "SQLJ". This part of ISO/IEC 9075 specifies the syntax and semantics of SQLJ, as well as mechanisms to ensure binary portability of resulting SQLJ applications. In addition, it specifies a number of Java packages and their contained classes (including methods). Throughout ISO/IEC 9075-10:2016, the terms "SQLJ" and "SQL/OLB" are used synonymously. NOTE Additional explanatory material (non-normative) about certain facilities defined in ISO/IEC 9075-2 can be found in ISO/IEC TR 19075-3.

This document specifies the fundamental principles governing coded domains, identification and description of the coded domains from the BOV view, the rules governing the rule-base of coded domains, the rules for management of ID codes, rules for specifying Human Interface Equivalents (HIEs) to an ID Code, the relations between the coded domain and controlled vocabularies, the rules governing the registration of coded domains as re-usable business objects, and the IT-enablement of coded domains. The document is applicable to the use of standards, specifications, authority files, etc., of a “codes representing X” nature being used in electronic business transactions among parties engaged in Open-edi, which pertains to flows of information using information bundles which cause pre-defined (or pre-definable) changes in the states of the IT systems of the parties to such electronic data interchanges. Detailed exclusions to the scope of this document are provided in Annex I.

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.

ISO/IEC 9075-9:2016 defines extensions to Database Language SQL to support management of external data through the use of foreign-data wrappers and datalink types.

ISO/IEC 9075-13:2016 specifies the ability to invoke static methods written in the Java? programming language as SQL-invoked routines and to use classes defined in the Java programming language as SQL structured user-defined types. (Java is a registered trademark of Oracle Corporation and/or its affiliates.)

This document specifies the business operational view of an implementation of an Open-edi Distributed Business Transaction Repository (OeDBTR), building on the principles and concepts defined in ISO/IEC 15944-4 of a business transaction. The repository stores the history of the transitions in states of the economic claim and/or other business entities that happen over the course of a business transaction, and does so for a collection of business events. These business events, comprised of transactions and their states, can be identified unambiguously so as to provide the ability to inspect or query the information at some point after the record has been made. The distributed nature of the repository offers users ubiquitous and robust access to the recorded history. A history of business transactions of market exchanges can be useful in auditing or other memoing-based activities, looking back at the immutable record of the interactions between parties. This document does not specify the Functional Services View of a particular implementation of an Open-edi Distributed Business Transaction Repository. For best performance, candidate technologies would likely exhibit properties of long-term permanence, robust immutability, decentralized access, distributed resilience, and fine-grained addressability.

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 models, and their associated metamodels, 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) models used in software engineering or information processing, for example, information or data models, process models, models of web services or any other type of models used to develop software systems or the processing of information; b) the concepts associated with the various elements within the models; c) the metamodels associated with the models; d) the mappings identified between the models, between the metamodels, and between the models and their associated metamodels – this is achieved by using the mapping facilities specified in ISO/IEC 11179-3. This document is applicable to the formulation of models and metamodels to be shared among people and machines, independent of the organization that produces the model or metamodel. It is not applicable to the physical instantiation of any model.

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 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 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 can include the provenance of the data set and quality, fitness for role, and risk assessments of the data set.

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 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 specifies “basic attributes” which are required to describe metadata 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 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 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 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.