Information technology — Automatic identification and data capture techniques — Encoding and resolving identifiers over HTTP
Introduction: There are many identifier systems in use today, some of which enjoy widespread usage and long histories. Examples include the International Air Travel Association (IATA) airport codes and identifiers such as digital object identifiers (DOIs) (see ISO 26324[5]), and country and currency codes. The ISO/IEC 15459 series[7] provides the basis for all identifier issuing agencies in the field of Automatic Identification and Data Capture (AIDC). The ISO/IEC 15459 series[7] defines methods for ensuring that identifiers are globally unique in the world of AIDC without any reliance on, for example, the internet’s domain name system or any given data service. This is critical for use cases where internet connectivity and the availability of online services cannot be allowed to affect whether a process can be completed, such as the purchase of an item. However, existing identifiers can be usefully encoded in Hypertext Transfer Protocol Uniform Resource Identifiers (HTTP URIs) following Linked Data principles so that when connectivity is available, they can be used in multiple methods of online lookup, data query and data integration. It is important to note that identity on the internet is defined by the domain name system. The Internet Engineering Task Force (IETF)’s Best Current Practice[2] makes it clear that each domain is sovereign over the URIs under that domain. This document brings the internet, Linked Data[8] and AIDC together to allow the discovery of online data related to phy
Scope: This document specifies the different approaches for using HTTP URIs to encode globally unique identifiers. It specifies a dual use data structure. It is both an HTTP URI and a composition of structured item identification properties and optionally descriptive attributes. These can be decomposed and interpreted on their own and/or be used as a pointer to additional information. Methods are described to enable identification uniqueness in the context of AIDC. These rely on either: a) identifiers, such as described in the ISO/IEC 15459 series[7], in the path or query string independent of the internet domain name; or, b) the internet domain name. The document further defines a basic common API for querying online services for information about identified items.