Ämnesområden

This document specifies the in-vehicle information (IVI) data structures that are required by different intelligent transport system (ITS) services for exchanging information between ITS stations (ITS-S). A general, extensible data structure is specified, which is split into structures called containers to accommodate current-day information. Transmitted information includes IVI such as contextual speed, road works warnings, vehicle restrictions, lane restrictions, road hazard warnings, location-based services and re-routing. The information in the containers is organized in sub-structures called data frames and data elements, which are described in terms of their content and syntax. The data structures are specified as communications-agnostic. This document does not provide the communication protocols. This document provides scenarios for usage of the data structure, e.g. in case of real time, short-range communications.

This document specifies an inspection procedure to be used by the purchaser where no prior agreement exists. It also specifies a reference acceptance procedure for acceptance or rejection of an inspection lot, when no agreement can be reached between the purchaser and the supplier, or where conformance to specification is disputed. It applies to inspection lots of bolts, screws, studs, nuts, pins, washers, rivets and other related fasteners. This document applies to fasteners not intended for high volume machine assembly, special-purpose applications or specially engineered applications requiring more advanced in-process control and lot traceability. For in-process control or final inspection by the manufacture and sorting, see ISO 16426.

This document specifies:

—   the interfaces between electronic fee collection (EFC) back-office systems for vehicle-related transport services, e.g. road user charging, parking and access control;

—   an exchange of information between the back-office system of the two roles of service provision and toll charging, e.g.:

—  charging-related data (toll declarations, billing details, payment claims, payment announcements),

—  administrative data (trust objects, EFC context data, etc.), and

—  confirmation data;

—   transfer mechanisms and supporting functions;

—   information objects, data syntax and semantics.

This document is applicable for any vehicle-related toll service and any technology used for charging.

The data types and associated coding related to the data elements described in Clause 6 are specified in Annex A, using the abstract syntax notation one (ASN.1) according to ISO/IEC 8824-1.

This document specifies basic protocol mechanisms over which implementations can specify and perform complex transfers (transactions).

This document does not specify, amongst others:

—   any communication between TC or 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;

—   interfaces for EFC systems for public transport;

—   any complex transfers (transactions), i.e. sequences of inter-related ADUs that can possibly involve several APDU exchanges;

—   processes regarding payments and exchanges of fiscal, commercial or legal accounting documents;

—   definitions of service communication channels, protocols and service primitives to transfer the APDU.

Amendment

1  Scope

Replace the last paragraph with the following text (in which “any complex transfers (transactions), i.e. 

sequences of inter-related ADUs that can possibly involve several APDU exchanges has been removed”):

This document does not specify, amongst others:

— any communication between TC or 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;

— interfaces for EFC systems for public transport;

— processes regarding payments and exchanges of fiscal, commercial or legal accounting documents;

— definitions of service communication channels, protocols and service primitives to transfer the APDU.

Warning — Persons using this document should be familiar with normal laboratory practice. This document does not purport to address all of the safety problems, if any, associated with its use. It is the responsibility of the user to establish appropriate safety and health practices and to determine the applicability of any other restrictions.

Warning — It is absolutely essential that tests conducted according to this document be carried out by suitably trained staff.

This document specifies methods to determine 90Sr and 89Sr by liquid scintillation counting (LSC) or proportional counting (PC) in supply water, drinking water, rainwater, surface and ground water, marine water, as well as cooling water, industrial water, domestic, and industrial wastewater after proper sampling, handling and test sample preparation. The detection limit depends on the sample volume, the instrument used, the sample counting time, the background count rate, the detection efficiency and the chemical yield. The method described in this document, using currently available LSC and PC instruments, has a detection limit of approximately 2 mBq·l-1 and 10 mBq·l-1 for 90Sr and 89Sr, respectively, for a volume of 2 l and a measuring time of 60 000 s, which is lower than the WHO criteria for safe consumption of drinking water (100 Bq·l-1 for 89Sr and 10 Bq·l-1 for 90Sr)[4]. The methods described in this document are applicable in the event of an emergency situation. When contamination contains fresh fission products, the contribution of 89Sr to the total amount of radioactive Sr is not negligible. This document provides test methods to determine the activity concentration of 90Sr in presence of 89Sr, and to determine the activity concentration of 90Sr in large volume of water sample (>50 L). The analysis of 90Sr and 89Sr adsorbed to suspended matter is not covered by this method. Filtration of the test sample and a chemical separation are required to separate and purify Sr from a test portion of the sample as the analysis of 90Sr and 89Sr adsorbed to suspended matter is not covered by this method. It is the user’s responsibility to ensure the validity of this test method selected for the water samples tested.

Post-fire data collection for large outdoor fires will be reviewed based on available studies conducted for wildland-urban interface fires, urban fires, including post-earthquake urban fires, and informal settlement fires. These studies will be used to develop a standardized data collection methodology for large outdoor fires that may be used in the event of future large outdoor fire disasters. A standardized approach, at the international level, will is required to be able to assess and compare fire spread and damage across all these large outdoor fire types.

This document specifies methodologies for measuring the performance of AI models for classification, regression, clustering and recommendation tasks.

This document provides terminology, concepts, requirements, and guidance for humanoversight of AI systems. It is primarily intended for organizations placing on the market or putting into service AI systems and is not specific to any particular sector;