Digital Product Passport

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.

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.

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.

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 describes the basic concept of metadata, and its relationship to both data and metamodels.

ISO/IEC TR 10032:2003 defines the ISO Reference Model of Data Management. It establishes a framework for coordinating the development of existing and future standards for the management of persistent data in information systems.
ISO/IEC TR 10032:2003 defines common terminology and concepts pertinent to all data held within information systems. Such concepts are used to define more specifically the services provided by particular data management components, such as database management systems or data dictionary systems. The definition of such related services identifies interfaces which may be the subject of future standardization.
ISO/IEC TR 10032:2003 does not specify services and protocols for data management. ISO/IEC TR 10032:2003 is neither an implementation specification for systems, nor a basis for appraising the conformance of implementations.
The scope of ISO/IEC TR 10032:2003 includes processes which are concerned with handling persistent data and their interaction with processes particular to the requirements of a specific information system. This includes common data management services such as those required to define, store, retrieve, update, maintain, backup, restore and communicate applications and dictionary data.
The scope of ISO/IEC TR 10032:2003 includes consideration of standards for the management of data located on one or more computer systems, including services for distributed database management.
ISO/IEC TR 10032:2003 does not include within its scope common services normally provided by an operating system including those processes which are concerned with specific types of physical storage devices, specific techniques for storing data, and specific details of communications and human computer interfaces.

This document defines interfaces for device management of RFID systems. Interfaces are defined that provide for discovery, configuration, initialization and monitoring of RFID systems within the software system infrastructure (SSI).

This document only deals with devices that provide RFID related services. It does not distinguish the form factor of such RFID devices.

This document provides two distinct interface sets, one based on the GS1 EPCglobal DCI standard and the IETF SNMP RFCs and the other based on the Organization for the Advancement of Structured Information Standards (OASIS) DPWS standard. The definition of the Device Profile for RFID is referred to in this document as the RFID Device Management Profile, or RDMP.
Each interface option set provides interface definitions that provide ISO/IEC 24791-3 Client Endpoints and Services Endpoints with the mechanisms for:
— the discovery of the RFID devices and services on a local or remote subnet;
— a firmware upgrade service;
— a management service that implements configuration related functions;
— a monitoring service for reporting alerts, diagnostics, and performance information.
The two interface set definitions provided by this document allow for clients and services endpoints to implement and provide the services based on the specific characteristics of the RFID system to be implemented. Subclause 1.2 defines the Conformance requirements for systems that implement components of one or both of the interface sets.

ISO/IEC 24791-2:2011 defines the interface(s) that provide operations on radio frequency identification (RFID) tag data including, but not limited to, reading, writing, collection, filtering, grouping, and event subscription and notification within the Software System Infrastructure (SSI).Specifically, the interface(s) defined by ISO/IEC 24791-2:2011 provide the following features:
full support for the commands and responses for air protocols supported by ISO/IEC 24791-2:2011 at an abstraction level appropriate for Data Management's position in the SSI architecture defined in ISO/IEC 24791-1;
an abstract definition of commands and operations that can be applied to different network bindings and encoding mechanisms;
support for the encoding mechanisms defined in ISO/IEC 15962;
volume reduction, format or structure modification, data analysis, and data access appropriate for Data Management's position in the SSI architecture defined in ISO/IEC 24791-1;
reporting of data to support application or data managing in formats controlled by the client, either inside or outside of SSI.
ISO/IEC 24791-2:2011 is composed of the EPCglobal Application Level Events Standard, in its entirety, with extensions to further support operation with ISO/IEC 15962 and the air protocols defined by ISO/IEC 18000.

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

This document defines the structure and the data elements of Authentication Context for Biometrics (ACBio), which is used for checking the validity of the result of a biometric enrolment and verification process executed at a remote site. This document allows any ACBio instance to accompany any biometric processes related to enrolment and verification. The specification of ACBio is applicable not only to single modal biometric enrolment and verification but also to multimodal fusion. The real-time information of presentation attack detection is not provided in this document. Only the assurance information of presentation attack detection (PAD) mechanism can be contained in the BPU report.
Biometric identification is out of the scope of this document.
This document specifies the cryptographic syntax of an ACBio instance. The cryptographic syntax of an ACBio instance is defined in this document applying a data structure specified in Cryptographic Message Syntax (CMS) schema whose concrete values can be represented using a compact binary encoding. This document does not define protocols to be used between entities such as BPUs, claimant, and validator. Its concern is entirely with the content and encoding of the ACBio instances for the various processing activities.