IT in general

This standard defines requirements for multiple aspects of user identification and Anti-Money Laundering on cryptocurrency exchanges, such as KYC (Know Your Customer) and AML (Anti-Money Laundering) regulations, outsourcing proper compliance measures to third-party solutions, and building up a self-regulatory layer of security and accountability among exchanges. It is to keep customers from malignant influence of unethical and illegal money that can be traced back inside/outside the cryptocurrency space. It is different from the IEEE P2140.2 standard, which is based on the protection of customer cryptographic assets.

This standard defines a technical reference framework and terminology for the platform of blockchain in electronic contracts. Functional requirements and technical indicators are also defined.

Blockchain interoperability is the ability of two or more blockchain systems or applications to exchange information and to mutually use the information that has been exchanged. The interfaces and protocols play a very important role in realizing interoperability. Therefore, the standard of cross-chain interoperability interfaces and protocols, especially those for data authentication and communication among homogeneous and heterogeneous blockchains systems, is needed. Such protocols coordinate blockchains while supporting multiple cross-chain models and levels to meet business demands without the need to customize gateways or exchanges for specific use cases. Provided in this standard are an infrastructure of cross-chain interoperability, as well as interfaces and protocols of data authentication and communication for homogeneous and heterogeneous blockchain interoperability. The protocols include the distributed identity protocol, metadata protocol, on-chain proof transformation protocol, and cross-chain communication protocol.

This standard defines a baseline architectural framework and defines functional roles for blockchain-driven supply chain finance (SCF) implementations, e.g., core enterprise, supplier, bank, blockchain platform provider, and so on. The procedures of registration, asset issuance, asset transfer, financing based on asset on chain, asset clearing and settlement, and asset tracing, are explained. Finally, the technique requirement of the business system, and blockchain platform are discussed.

Data format requirements for blockchain systems are established in this standard. This standard addresses data structures, data types, and data elements.

A baseline architectural framework will be defined in this standard. In addition, the general process for digital asset management on blockchain will be outlined.

The standard defines the Entity Risk Mutual Assistance Model (RMAM) based on blockchain technology, including the involved entities of interest, the relationship between entities, organizational framework, and design method. A framework of blockchain-based Internet of Things (IoT ) data management is defined in this standard. It identifies the common building blocks of the framework that blockchain enabled during IoT data lifecycle including data acquisition, processing, storage, analyzing, usage/exchange and obsoletion, and the interactions among these building blocks.

This document specifies an XML format for representing forms data and annotations in the Portable Document Format, ISO 32000-2 (PDF 2.0).

This part of ISO 29481 specifies:

- a methodology that links the business processes undertaken during the construction of built facilities with the specification of information that is required by these processes, and

- a way to map and describe the information processes across the life cycle of construction works.

This part of ISO 29481 is intended to facilitate interoperability between software applications used during all stages of the life cycle of construction works, including briefing, design, documentation, construction, operation and maintenance, and demolition. It promotes digital collaboration between actors in the construction process and provides a basis for accurate, reliable, repeatable and high-quality information exchange.

This document describes the glTF file format. glTF is an API-neutral runtime asset delivery format. glTF bridges the gap between 3D content creation tools and modern graphics applications by providing an efficient, extensible, interoperable format for the transmission and loading of 3D content.

This document defines the framework and information reference model for representing sensor-based 3D mixed-reality worlds. It defines concepts, an information model, architecture, system functions, and how to integrate 3D virtual worlds and physical sensors in order to provide mixed-reality applications with physical sensor interfaces. It defines an exchange format necessary for transferring and storing data between physical sensor-based mixed-reality applications. This document specifies the following functionalities:

a) representation of physical sensors in a 3D scene;

b) definition of physical sensors in a 3D scene;

c) representation of functionalities of each physical sensor in a 3D scene;

d) representation of physical properties of each physical sensor in a 3D scene;

e) management of physical sensors in a 3D scene; and

f) interface with physical sensor information in a 3D scene.

This document defines a reference model for physical sensor-based mixed-reality applications to represent and to exchange functions of physical sensors in 3D scenes. It does not define specific physical interfaces necessary for manipulating physical devices, but rather defines common functional interfaces that can be used interchangeably between applications. This document does not define how specific applications are implemented with specific physical sensor devices. It does not include computer generated sensor information using computer input/output devices such as a mouse or a keyboard. The sensors in this document represent physical sensor devices in the real world.

ISO/IEC 23000-13:2017 specifies the following:

- scene description elements for representing AR content; and

- mechanisms to connect to local and remote sensors and actuators; mechanisms to integrated compressed media (image, audio, video, graphics); mechanisms to connect to remote resources such as maps and compressed media.