Standard

This standard defines definitions, types, test specifications, test methods and test processes for blockchain systems. Test contents are included for each type of test. This standard also defines the test architecture of blockchain systems, including but not limited to functional testing, performance testing, security testing, stability testing, and compliance testing.

This standard defines a framework of service capability which includes the technology, human resource and qualifications of the entity and provides a set of indicators for the evaluation of service capability. It also proposes evaluation methods for the blockchain industry.

This standard is IEEE Standard for Application Interface Specification for Blockchain Systems. It defines an application programming interface (API) collection and data transmission format between the chain layer and the application layer in a blockchain system and standardizes the string, encoding, and request-response format of the API.

Technical framework, application processes and technical requirements for carbon trading applications based on blockchain, including functions, access, interface, security, and carbon consumption voucher coding are described in this standard.

The surging needs for the Internet of Things (IoT) are dramatically shifting the network structure and challenging the traditional perimeter security paradigm. To establish secure and trustworthy interoperability among billions of heterogeneous interconnected devices, there is a need for standards defining a common framework. This standard defines a blockchain-based Zero-Trust access control framework and gives a typical implementation model and deployment variations, addressing general security and trust in IoT applications with the inspiration of the emerging Zero-Trust paradigm and blockchain technology. The leverage of blockchain and Zero-Trust could provide reliable interactions among people, things, and applications in the presence of failures and attacks, and improve an IoT system's overall information technology security posture.

This document provides privacy engineering guidelines that are intended to help organizations integrate recent advances in privacy engineering into system life cycle processes. It describes:(1) the relationship between privacy engineering and other engineering viewpoints (system engineering, security engineering, risk management); and(2) privacy engineering activities in key engineering processes such as knowledge management, risk management, requirement analysis, and architecture design.The intended audience includes engineers and practitioners who are involved in the development, implementation or operation of systems that need privacy consideration, as well as managers in organizations responsible for privacy, development, product management, marketing, and operations.

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

This document specifies how to extend the ISO 32000-2 specification by adding the ISO 10303-242 (STEP AP 242) format as a valid format for 3D assets contained in a RichMedia annotation. It is intended for:- developers of software that creates PDF files (PDF writers);- software that reads existing PDF files and usually interprets their contents for display (PDF readers);- software that reads and displays PDF content and interacts with the computer users to possibly modify and save the PDF file (PDF processors);- PDF products that read and/or write PDF files for a variety of other purposes (PDF processors).

The present document provides reference test material and test results for improved usability of technologies in 3GPP TS 26.118: Virtual Reality (VR) profiles for streaming applications. The specification 3GPP TS 26.118 includes several VR media profiles for video and a single media profile for audio with different configuration options. The specification focuses primarily on interoperability requirements for VR360 applications, but does not address performance characterization of the solutions. In order for content providers and the rest of the ecosystem to be able to select and configure the technologies defined in 3GPP TS 26.118 and to generate content for streaming applications, collecting such information would be most valuable.

This document specifies the key requirements of a quality open source license compliance program in order to provide a benchmark that builds trust between organizations exchanging software solutions comprised of open source software.

This document establishes high-level requirements for privacy by design to protect privacy throughout the lifecycle of a consumer product, including data processed by the consumer. This document does not contain specific requirements for the privacy assurances and commitments that organizations can offer consumers nor does it specify particular methodologies that an organization can adopt to design and-implement privacy controls, nor the technology that can be used to operate such controls.

This document provides a description of privacy-enhancing data de-identification techniques, to be used to describe and design de-identification measures in accordance with the privacy principles in ISO/IEC 29100.In particular, this document specifies terminology, a classification of de-identification techniques according to their characteristics, and their applicability for reducing the risk of re-identification.This document is applicable to all types and sizes of organizations, including public and private companies, government entities, and not-for-profit organizations, that are PII controllers or PII processors acting on a controller's behalf, implementing data de-identification processes for privacy enhancing purposes.