Informationsteknik, kontorsutrustning

This document specifies a reference architecture for distributed ledger technology (DLT) systems including blockchain systems. The reference architecture addresses concepts, cross-cutting aspects, architectural considerations, and architecture views, including functional components, roles, activities, and their relationships for blockchain and DLT.

This document provides the minimum functions and requirements of software based planned maintenance system (SPMS) covering specific requirements for planning and implementing the maintenance schedule, recording, reporting, analysis and optimization to maintain onboard equipment and systems in support of ISM 2018 Part A /10.

This document is applicable to all construction products and services related to buildings and construction works. It specifies and describes the communication format for the information defined in EN 15804 for business-to-business communication to ensure a common understanding through consistent communication of information.

NOTE This document does not deal with business to consumer communication and is not intended for that purpose. Business to consumer communication format is planned to be the subject of a future document.

This Document specifies:

— the Localized Message (LM) format: an NPDU of a networking & transport layer protocol that does not support routing of a packet through a network;

— the Service Advertisement Message (SAM): an APDU to be transported in e.g. an LM;

— the Service Response Message (SRM): an APDU acknowledging a SAM that offered a service based on an ITS application class,[2] to be transported in e.g. an LM;

— related basic requirements for procedures.

Specifications are partly done by normative references to IEEE 1609.3™-2016.

NOTE These message format specifications and basic procedures need to be complemented by complete procedures and SAP specifications according to the context of usage, i.e. an ITS station specified in ISO 21217,[4] or a WAVE device specified in IEEE 1609.0,[13] or any other context.

This part of ISO 28005 contains technical specifications that facilitate efficient exchange of electronic information between ships and shore for coastal transit or port calls. It covers safety, security and efficiency enhancement information requirements related mainly to the relationships between the ship and the port and coastal state authorities.

This part of ISO 28005 contains the definition of core data elements for use in electronic port clearance (EPC) messages. It does not define any structuring of messages or provide any guidance on what information is required for a particular purpose; it is a general data dictionary for safety, security or operation-related maritime information. Details about message formats and applications are defined in part 1 of this standard.

The data elements in this part of ISO 28005 covers the data elements and the data model defined in the IMO Reference Data Model as specified in the IMO Compendium on Facilitation and Electronic Business. This version of the standard also contains data elements required to implement mandatory ship reporting as defined in IMO Resolution A.851(20) as amended by resolution MEPC.138(53) and bulk loading and unloading information as defined in IMO Resolution A.862(20).

This document specifies the data structure and data exchange procedure related to the micro-mobility service applications utilizing P-ITS-S (i.e. nomadic devices) including car sharing, parcel delivery, last & first mile connections. In addition, this document also delivers related standards required to develop and operate the service platform between nomadic device and micro mobility with intelligent transport systems (ITS) technologies, which would undertake joint work with ISO Technical Committee 204 (ISO/TC204) – Intelligent Transport Systems (ITS).

This document defines the data structure and data exchange procedures based on dataset and messages which are defined in DIS 22085-2.

This document specifies the storage format for streams of video that is structured as NAL units, such as AVC (ISO/IEC 14496-10) and HEVC (ISO/IEC 23008-2) video streams.
 

This document specifies carriage of coded media representations which comply with visual volumetric video-based coding and video-based point cloud compression specification, ISO/IEC 23090-5 [V3C].

This document specifies the conformance and reference software for ISO/IEC 23090-2. The information provided describes the reference software modules and the features that is supports. It also provides a description of how the reference software can be utilized.

In addition, the document also lists and describes test vectors comprising ISO base media file format files, media presentation descriptions, segments, and combinations thereof that conform to the normative clauses of ISO/IEC 23090-2.

This document defines the conformance test plan, based on ISO/IEC 10373 6, for the contactless interface of eMRTDs and eMRTD associated readers compliant with ICAO Doc 9303.

Application requirements for eMRTD and eMRTD reader are outside of the scope of this document and are defined in ICAO Doc 9303 Part 10.

This document specifies the format of the Session-Based Description document and the MPD's extension to be used in session-based operations with MPEG DASH (ISO/IEC 23009-1).

This document specifies examples of application-specific requirements, recommendations, and best practices in data acquisition applicable to gait image sequence data. Its typical applications include:

a) support for human examination of high-resolution video and still images;

b) support for human biometric verification based on video and still images;

c) automated gait image sequence verification and identification.

This specification ensures that image sequences are suitable for identification and verification generated by video surveillance and other similar systems.

The following topics are not in scope of this document:

— Definitions for facial and/or full body image related biometric profiles which are fully covered in ISO/IEC 39794-5 and ISO/IEC 39794-16 respectively.

— Security aspects like digital image sequence electronic signature, Presentation Attack Detection (PAD), and morphing prevention.

This document specifies interindustry commands which can be used for security operations. This document also provides informative directives on how to construct security mechanisms with commands defined in ISO/IEC 7816-4.

The choice and conditions of use of cryptographic mechanism in security operations can affect card exportability. The evaluation of the suitability of algorithms and protocols is outside the scope of this document. It does not cover the internal implementation within the card and/or the outside world.

This part of ISO/IEC 39794 specifies

— generic extensible data interchange formats for the representation of vascular image data: a tagged binary data format based on an extensible specification in ASN.1 and a textual data format based on an XML schema definition that are both capable of holding the same information,

— examples of data record contents,

— application specific requirements, recommendations, and best practices in data acquisition, and

— conformance test assertions and conformance test procedures applicable to this part of ISO/IEC 39794.

This document is part of a series of standards denoted JPEG XL. This document describes JPEG XL Part 2 (ISO/IEC 18181-2), the Transport and Container formats for JPEG XL codestreams as specified in ISO/IEC 18181-1. This provides a way to add metadata and extensions to JPEG XL codestreams. A file as described by this document is called a JPEG XL file.

This document specifies
— the interfaces between electronic fee collection (EFC) systems for vehicle related transport services, e.g. road user charging, parking and access control; it does not cover interfaces for EFC systems for public transport; an EFC system can include any EFC system, e.g. including systems that automatically read licence plate numbers of vehicles passing a toll point,
— an exchange of information between the central equipment of the two roles of service provision and toll charging, e.g.
     — charging related data (toll declarations, billing details),
     — administrative data, and
     — confirmation data,
— transfer mechanisms and supporting functions,
— information objects, data syntax and semantics,
— examples of data interchanges (see Annex B and Annex C), and
— an example of toll rounding (see Annex D).
This document is applicable for any toll service and any technology used for charging.
It is defined as a toolbox standard of transactions and Application Protocol Data Units (APDUs), which can be used for the assigned purpose. The detailed definitions of mandatory and optional elements in a real implementation are defined elsewhere. It does not define all communication sequences, communication stacks and timings.
The data types and associated coding related to the data elements described in clause 6 are defined in Annex A, using the abstract syntax notation one (ASN.1) according to ISO/IEC 8824-1.
This document is not applicable, among others, to
— any communication between toll charger (TC) or toll service provider (TSP) with any other involved party,
— any communication between elements of the TC and the TSP that is not part of the back office communication,
— processes regarding payments and exchanges of fiscal, commercial or legal accounting documents, and
— definitions of service communication channels, protocols and service primitives to transfer the APDUs.

This document specifies
— the interfaces between electronic fee collection (EFC) systems for vehicle related transport services, e.g. road user charging, parking and access control; it does not cover interfaces for EFC systems for public transport; an EFC system can include any EFC system, e.g. including systems that automatically read licence plate numbers of vehicles passing a toll point,
— an exchange of information between the central equipment of the two roles of service provision and toll charging, e.g.
     — charging related data (toll declarations, billing details),
     — administrative data, and
     — confirmation data,
— transfer mechanisms and supporting functions,
— information objects, data syntax and semantics,
— examples of data interchanges (see Annex B and Annex C), and
— an example of toll rounding (see Annex D).
This document is applicable for any toll service and any technology used for charging.
It is defined as a toolbox standard of transactions and Application Protocol Data Units (APDUs), which can be used for the assigned purpose. The detailed definitions of mandatory and optional elements in a real implementation are defined elsewhere. It does not define all communication sequences, ommunication stacks and timings.
The data types and associated coding related to the data elements described in clause 6 are defined in Annex A, using the abstract syntax notation one (ASN.1) according to ISO/IEC 8824-1.
This document is not applicable, among others, to
— any communication between toll charger (TC) or toll service provider (TSP) with any other involved party,
— any communication between elements of the TC and the TSP that is not part of the back office communication,
— processes regarding payments and exchanges of fiscal, commercial or legal accounting documents, and
— definitions of service communication channels, protocols and service primitives to transfer the APDUs.