ISO IEC 29161:2016 pdf free

ISO IEC 29161:2016 pdf free.Information technology一Data structure一Unique identification for the Internet of Things
Each form of unique identification stands on its own within the context of applications within that specific identification’s domain. When one travels outside of that closed system, an open system form of the identification is required. The nature of the Internet of Things (IoT) is for people and objects to communicate with one and the other. This means that the unique identification scheme will need to accommodate established forms of identification.
For the purposes of this International Standard, the “unambiguous wrapper” for identifiers used in IoT communications shall be a Uniform Resource ldentifier (URI) defined by IETE, in RFC 3986. URIs are traditionally classified as either a Uniform Resource Locator (URL, using a string starting with “http://”) denoting a web resource, or a Uniform Resource Name (URN, using a string starting with “urn:”) as defined in RFC 2141. In both cases, the URI is a text string from a limited subset of US ASCII (for maximum portability across systems). The URI syntax is organized hierarchically, with components listed in order of decreasing significance from left to right. Other structures were considered, but the URI structure is widely accepted and extensively used with today’s AIDC data carriers, while providing the flexibility of a broader implementation.
ISO IEC 29161 is primarily concerned with supporting the interoperable use of Identification schemes from different domains, using existing URNs as needed to provide this interoperability in an efficient manner. Although URLs will also be used extensively in IoT applications,no special treatment of them is required for interoperability, and so ISO IEC 29161 does
not also define headers for URLS.
In some existing applications, a specific data carrier only encodes one type of identifier, and the choice of a specific URI as an unambiguous wrapper is predetermined. In other cases, however, a data carrier may encode a wide variety of different unique identifiers, and the appropriate “wrapper” cannot be unambiguously distinguished from context. Therefore, it will often be the case that the appropriate URI wrapper must be determined (from some sort of encoded signal in the data carrier) in order to include
that encoded identifier in a mixed-format IoT message.ISO IEC 29161 pdf download.