Infoteenus
35 INFOTEHNOLOOGIA
Uued standardid
EVS-EN 12896-8:2026
Public transport - Reference data model - Part 8: Management information & statistics
Käsitlusala: The present document is composed of the following data packages:
— Indicators;
— Reusable components;
— Explicit frames for statistics
— Query.
This document itself is composed of the following parts:
— main document representing the conceptual foundations and corresponding data model (normative);
— Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative);
— Annex B presenting the model evolution (informative);
— Annex C, providing details of the significant technical changes between this document and EN 12896-8:2019 (informative)
— Indicators;
— Reusable components;
— Explicit frames for statistics
— Query.
This document itself is composed of the following parts:
— main document representing the conceptual foundations and corresponding data model (normative);
— Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative);
— Annex B presenting the model evolution (informative);
— Annex C, providing details of the significant technical changes between this document and EN 12896-8:2019 (informative)
Alusdokumendid: EN 12896-8:2026
Asendab: EVS-EN 12896-8:2019
ISO/IEC 23008-2:2026
Information technology — High efficiency coding and media delivery in heterogeneous environments — Part 2: High efficiency video coding
Käsitlusala: This document specifies high efficiency video coding.
Alusdokumendid:
Asendab: ISO/IEC 23008-2:2025
CEN/TS 17370:2026
Public transport - Operating raw data and statistics exchange
Käsitlusala: This project proposal addresses:
• the development of a data exchange format, based on Transmodel (EN 12896) and NeTEx (CEN/TS 16614), focused on a minimum set of Public Transport raw data needed for quantitative analysis in public transport services. For instance, the elaboration of standardized operational data (e.g., observed run times, passenger load) collected during service operations is an input for strategic planning (e.g., how and when to amend the schedules), tactical planning (e.g., when to undertake a certain control action), quality follow-up, etc.
• the development of a glossary for public transport aiming at assigning to each concept used in Public Transport, a unique “standard” term.
This project proposal develops a data exchange format and API, that will be documented in a Technical Specification (TS) focusing on the exchange of a minimum set of Public Transport raw data needed for quantitative analysis in public transport services.
The exchange protocol format will be based on NeTEx standard, in particular:
• CEN/TS 16614-1:2020 Network topology;
• CEN/TS 16614-2:2020 Scheduled Timetables;
Raw data identification and description will be compliant with Transmodel (EN 12896), with particular emphasis on Data Dictionary description and Part 8 Management Information Statistics.
OpRa will also develop a Public Transport unified glossary to harmonised terms and definitions from existing data dictionaries.
• the development of a data exchange format, based on Transmodel (EN 12896) and NeTEx (CEN/TS 16614), focused on a minimum set of Public Transport raw data needed for quantitative analysis in public transport services. For instance, the elaboration of standardized operational data (e.g., observed run times, passenger load) collected during service operations is an input for strategic planning (e.g., how and when to amend the schedules), tactical planning (e.g., when to undertake a certain control action), quality follow-up, etc.
• the development of a glossary for public transport aiming at assigning to each concept used in Public Transport, a unique “standard” term.
This project proposal develops a data exchange format and API, that will be documented in a Technical Specification (TS) focusing on the exchange of a minimum set of Public Transport raw data needed for quantitative analysis in public transport services.
The exchange protocol format will be based on NeTEx standard, in particular:
• CEN/TS 16614-1:2020 Network topology;
• CEN/TS 16614-2:2020 Scheduled Timetables;
Raw data identification and description will be compliant with Transmodel (EN 12896), with particular emphasis on Data Dictionary description and Part 8 Management Information Statistics.
OpRa will also develop a Public Transport unified glossary to harmonised terms and definitions from existing data dictionaries.
Alusdokumendid: CEN/TS 17370:2026
Asendab: CEN/TR 17370:2019
ISO/IEC 23002-7:2026
Information technology — MPEG video technologies — Part 7: Versatile supplemental enhancement information messages for coded video bitstreams
Käsitlusala: This Specification specifies the syntax and semantics of video usability information (VUI) parameters and supplemental enhancement information (SEI) messages. The VUI parameters and SEI messages defined in this Specification are designed to be conveyed within coded video bitstreams in a manner specified in a video coding specification or to be conveyed by other means determined by the specifications for systems that make use of such coded video bitstreams. This Specification is particularly intended for use with coded video bitstreams as specified by Rec. ITU-T H.266 | ISO/IEC 23090-3, although it is drafted in a manner intended to be sufficiently generic that it can also be used with other types of coded video bitstreams.
VUI parameters and SEI messages can assist in processes related to decoding, display or other purposes. However, unless otherwise specified in a referencing specification, the interpretation and use of the VUI parameters and SEI messages specified in this Specification is not a required functionality of a video decoder or receiving video system. Although semantics are specified for the VUI parameters and SEI messages, decoders and receiving video systems can simply ignore the content of the VUI parameters and SEI messages or can use them in a manner that somewhat differs from what is specified in this Specification.
VUI parameters and SEI messages can assist in processes related to decoding, display or other purposes. However, unless otherwise specified in a referencing specification, the interpretation and use of the VUI parameters and SEI messages specified in this Specification is not a required functionality of a video decoder or receiving video system. Although semantics are specified for the VUI parameters and SEI messages, decoders and receiving video systems can simply ignore the content of the VUI parameters and SEI messages or can use them in a manner that somewhat differs from what is specified in this Specification.
Alusdokumendid:
Asendab: ISO/IEC 23002-7:2024
ISO/IEC TR 30189-2:2026
Internet of Things (IoT) — IoT-based management of tangible cultural heritage assets — Part 2: Use cases
Käsitlusala: This document describes the use cases for IoT-based management of tangible cultural heritage assets, which builds upon the framework provided in ISO/IEC TR 30189-1:2025.
Alusdokumendid:
CEN/TS 16157-15:2026
Intelligent transport systems — DATEX II data exchange specifications for traffic management and information — Part 15: JSON Schema mapping
Käsitlusala: The CEN 16157 multipart standard specifies and defines component aspects supporting the shared use of data and information in the field of traffic and travel. The component aspects include the modelling approach, the data content, the data structure and relationships and the communications specification.
This document defines a mapping from UML models, compliant with EN 16157-1, into JavaScript Object Notation (JSON) using JSON Schema as specified in draft 2020-12 and subsequent versions.
The schema mapping conforms to the JSON format defined by the Internet Engineering Task Force (IETF) in RFC 8259.
In the context of describing generation of schema, this refers to the webtool made available as part of the CEN 16157 multipart standard, which can generate the JSON schema mapping specified in this document.
This document defines a mapping from UML models, compliant with EN 16157-1, into JavaScript Object Notation (JSON) using JSON Schema as specified in draft 2020-12 and subsequent versions.
The schema mapping conforms to the JSON format defined by the Internet Engineering Task Force (IETF) in RFC 8259.
In the context of describing generation of schema, this refers to the webtool made available as part of the CEN 16157 multipart standard, which can generate the JSON schema mapping specified in this document.
Alusdokumendid: CEN/TS 16157-15:2026
ISO/IEC 11801-6:2017/Amd 1:2026
Information technology — Generic cabling for customer premises — Part 6: Distributed building services — Amendment 1
Käsitlusala: Amendment to ISO/IEC 11801-6:2017
Alusdokumendid:
ISO/IEC 23090-3:2026
Information technology — Coded representation of immersive media — Part 3: Versatile video coding
Käsitlusala: This document specifies a video coding technology known as versatile video coding (VVC), comprising a video coding technology with a compression capability that is substantially beyond that of the prior generations of such standards and with sufficient versatility for effective use in a broad range of applications.
Only the syntax format, semantics, and associated decoding process requirements are specified, while other matters such as pre-processing, the encoding process, system signalling and multiplexing, data loss recovery, post-processing, and video display are considered to be outside the scope of this document. Additionally, the internal processing steps performed within a decoder are also considered to be outside the scope of this document; only the externally observable output behaviour is required to conform to the specifications of this document.
This document is designed to be generic in the sense that it serves a wide range of applications, bit rates, resolutions, qualities and services. Applications include, but are not limited to, video coding for digital storage media, television broadcasting and real-time communication. In the course of creating This document, various requirements from typical applications have been considered, necessary algorithmic elements have been developed, and these have been integrated into a single syntax. Hence, this document is designed to facilitate video data interchange among different applications.
Only the syntax format, semantics, and associated decoding process requirements are specified, while other matters such as pre-processing, the encoding process, system signalling and multiplexing, data loss recovery, post-processing, and video display are considered to be outside the scope of this document. Additionally, the internal processing steps performed within a decoder are also considered to be outside the scope of this document; only the externally observable output behaviour is required to conform to the specifications of this document.
This document is designed to be generic in the sense that it serves a wide range of applications, bit rates, resolutions, qualities and services. Applications include, but are not limited to, video coding for digital storage media, television broadcasting and real-time communication. In the course of creating This document, various requirements from typical applications have been considered, necessary algorithmic elements have been developed, and these have been integrated into a single syntax. Hence, this document is designed to facilitate video data interchange among different applications.
Alusdokumendid:
Asendab: ISO/IEC 23090-3:2024
ISO/IEC TS 20000-18:2026
Information technology — Service management — Part 18: Guidance on the use of experience management in a service management system
Käsitlusala: This document provides guidance on the use of experience management (XM) in a service management system (SMS) based on ISO/IEC 20000-1. The target group for this document includes professionals and organizations interested in using XM.
XM can focus on various aspects of experience with the services by customers, users, personnel, suppliers and other interested parties.
XM practices are intended to optimize the value to interested parties and to improve the quality of the services provided. XM is not a stand-alone methodology but should be integrated into the existing or new SMS which is used to operate the services.
NOTE This document does not distinguish between organizations providing services to internal or external customers (known as internal or external service providers). XM applies to internal and external service providers and their respective suppliers.
XM can focus on various aspects of experience with the services by customers, users, personnel, suppliers and other interested parties.
XM practices are intended to optimize the value to interested parties and to improve the quality of the services provided. XM is not a stand-alone methodology but should be integrated into the existing or new SMS which is used to operate the services.
NOTE This document does not distinguish between organizations providing services to internal or external customers (known as internal or external service providers). XM applies to internal and external service providers and their respective suppliers.
Alusdokumendid:
ISO 19593-1:2026
Graphic technology — Use of PDF to associate processing steps and content data — Part 1: Processing steps for packaging and labels
Käsitlusala: This document describes a method for storing data in a PDF file that correspond to the processing steps of printed products. This method has three parts:
metadata identifying processing steps;
limitations on the interaction between PDF graphics objects that are part of a processing step and other PDF graphics objects;
limitations on PDF graphics objects in processing steps.
This method is intended to be generic, i.e. not specific to packaging and labels.
In addition, this document defines the following packaging- and label-specific groups of processing steps data:
data corresponding to finishing steps, such as cutting, folding or glueing;
braille;
information panels;
indications of physical dimensions;
indications of intended positions of graphical elements;
printed white, for example on transparent or metallic surfaces;
printed varnish;
primer;
printing plate making.
metadata identifying processing steps;
limitations on the interaction between PDF graphics objects that are part of a processing step and other PDF graphics objects;
limitations on PDF graphics objects in processing steps.
This method is intended to be generic, i.e. not specific to packaging and labels.
In addition, this document defines the following packaging- and label-specific groups of processing steps data:
data corresponding to finishing steps, such as cutting, folding or glueing;
braille;
information panels;
indications of physical dimensions;
indications of intended positions of graphical elements;
printed white, for example on transparent or metallic surfaces;
printed varnish;
primer;
printing plate making.
Alusdokumendid:
Asendab: ISO 19593-1:2018
ISO/TS 16569:2026
Health informatics — Standardized data set for exchanging exercise therapy recommendations for degenerative arthritis and backpain
Käsitlusala: This document specifies a standardized data set for exercise recommendations to facilitate data exchange between healthcare providers and patients.
This document specifically focuses on degenerative arthritis and backpain because these conditions commonly require long-term structured rehabilitation exercise exchange.
This document defines the structure of exercise recommendation data for electronic exchange between healthcare providers and patients with degenerative arthritis and back pain.
This document focuses on data exchange of exercise recommendations for backache and degenerative arthritis; other musculoskeletal disorders are outside the scope of this document.
This document is not intended to provide a data set for symptoms of other musculoskeletal disorders, or for the patient’s pain intensity.
This document does not cover medication orders, observation data measured by personal health devices, or other information that can be relevant in the context of recommendations for musculoskeletal disorders.
This document specifically focuses on degenerative arthritis and backpain because these conditions commonly require long-term structured rehabilitation exercise exchange.
This document defines the structure of exercise recommendation data for electronic exchange between healthcare providers and patients with degenerative arthritis and back pain.
This document focuses on data exchange of exercise recommendations for backache and degenerative arthritis; other musculoskeletal disorders are outside the scope of this document.
This document is not intended to provide a data set for symptoms of other musculoskeletal disorders, or for the patient’s pain intensity.
This document does not cover medication orders, observation data measured by personal health devices, or other information that can be relevant in the context of recommendations for musculoskeletal disorders.
Alusdokumendid:
ISO 13133:2026
Financial services — Security reference model for digital currency hardware wallet (SRM-DCHW)
Käsitlusala: This document provides a taxonomy, reference model, considerations for a security framework and a security problem definition for digital currency hardware wallets (DCHWs). It also specifies security objectives to address security issues related to the security problem definition.
This document is applicable to organizations that develop and operate DCHWs, e.g. mobile device manufacturers, chip manufacturers and companies that provide DCHW solutions. This document is also relevant to third parties that provide services to these stakeholders. It addresses sovereign or fiat digital currencies issued by a specific entity, e.g. a central bank.
This document is applicable to organizations that develop and operate DCHWs, e.g. mobile device manufacturers, chip manufacturers and companies that provide DCHW solutions. This document is also relevant to third parties that provide services to these stakeholders. It addresses sovereign or fiat digital currencies issued by a specific entity, e.g. a central bank.
Alusdokumendid:
ISO/TR 6203:2026
Health informatics — Personalized digital health — Common factors for frailty assessment
Käsitlusala: This document reviews existing frailty indices and identifies common factors of frailty, laying a foundation for developing standardized frailty prediction models that can be used across clinical and demographic contexts to improve early identification and intervention efforts.
Alusdokumendid:
ISO/IEC TR 5812:2026
Information technology — Semantic metadata support in office documents
Käsitlusala: This document outlines:
descriptions of use cases for identified application domains that benefit from additional semantic metadata support in office documents;
descriptions of semantic metadata requirements from experts of identified application domains;
specifications of possible technical strategies for associating domain-specific semantic metadata with office documents entities.
This document applies to users of office documents, for example, publishers, librarians, archivists, data scientists and other document users, as well as office software developers and service system integrators.
This document focuses on the methods of supporting various kinds of metadata, rather than on metadata itself.
descriptions of use cases for identified application domains that benefit from additional semantic metadata support in office documents;
descriptions of semantic metadata requirements from experts of identified application domains;
specifications of possible technical strategies for associating domain-specific semantic metadata with office documents entities.
This document applies to users of office documents, for example, publishers, librarians, archivists, data scientists and other document users, as well as office software developers and service system integrators.
This document focuses on the methods of supporting various kinds of metadata, rather than on metadata itself.
Alusdokumendid:
ISO 20525:2026
Tourism and related services — Semantics applied to tourism destinations
Käsitlusala: This document provides a semantic base that allows the representation of relevant information related to tourism destinations, including resources and services within the destination, travel experiences, and the destination itself. It establishes the terminology, hierarchy, and the minimum properties and relationships required for the definition of a reference semantic structure, ensuring the interoperability of local, territorial and country tourism information technology (IT) platforms with third-party digital systems.
This document provides tourism destinations with semantic data structures that primarily benefit final users (i.e. tourists and other interested parties), as these structures allow destinations to provide access to relevant information in an intuitive and agile way, and improve the interaction between tourists and the systems that manage, publish, carry transactions and accompany tourists during their journey. Furthermore, destination managers, data managers and data publishers, applying this document can also benefit from such implementation.
This document provides tourism destinations with semantic data structures that primarily benefit final users (i.e. tourists and other interested parties), as these structures allow destinations to provide access to relevant information in an intuitive and agile way, and improve the interaction between tourists and the systems that manage, publish, carry transactions and accompany tourists during their journey. Furthermore, destination managers, data managers and data publishers, applying this document can also benefit from such implementation.
Alusdokumendid:
Asendatud standardid
ISO 19593-1:2018
Graphic technology -- Use of PDF to associate processing steps and content data -- Part 1: Processing steps for packaging and labels
Käsitlusala: This document describes a method for storing data in a PDF file that correspond to the processing steps of printed products. This method has three parts:
1) metadata identifying processing steps;
2) limitations on the interaction between PDF graphics objects that are part of a processing step and other PDF graphics objects;
3) limitations on PDF graphics objects in processing steps.
This method is intended to be generic, i.e. not specific to packaging and labels.
In addition, this document defines the following packaging- and label-specific groups of processing-steps data:
- data corresponding to finishing steps, such as cutting, folding or glueing;
- Braille;
- information panels;
- indications of physical dimensions;
- indications of intended positions of graphical elements;
- printed white, for example on transparent or metallic surfaces;
- printed varnish.
1) metadata identifying processing steps;
2) limitations on the interaction between PDF graphics objects that are part of a processing step and other PDF graphics objects;
3) limitations on PDF graphics objects in processing steps.
This method is intended to be generic, i.e. not specific to packaging and labels.
In addition, this document defines the following packaging- and label-specific groups of processing-steps data:
- data corresponding to finishing steps, such as cutting, folding or glueing;
- Braille;
- information panels;
- indications of physical dimensions;
- indications of intended positions of graphical elements;
- printed white, for example on transparent or metallic surfaces;
- printed varnish.
Alusdokumendid:
Asendatud: ISO 19593-1:2026
EVS-EN 12896-8:2019
Public transport - Reference data model - Part 8 : Management information & statistics
Käsitlusala: 1.1 General Scope of the Standard
The main objective of the present standard is to present the Reference Data Model for Public Transport, based on:
- the Reference Data Model, EN 12896, known as Transmodel V5.1;
- EN 28701:2012, Intelligent transport systems - Public transport - Identification of Fixed Objects in Public Transport (IFOPT), although note that this particular standard has been withdrawn as it is now included within Parts 1 and 2 of this standard (EN 12896 1:2016 and EN 12896 2:2016) following their successful publication;
incorporating the requirements of:
- EN 15531-1 to −3 and CEN/TS 15531-4 and −5: Public transport - Service interface for real-time information relating to public transport operations (SIRI);
- CEN/TS 16614-1 and -2: Network and Timetable Exchange (NeTEx), in particular the specific needs for long distance train operation.
Particular attention is drawn to the data model structure and methodology:
- the data model is described in a modular form in order to facilitate the understanding and the use of the model;
- the data model is entirely described in UML.
The following functional domains are considered:
- Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places;
- Timing Information and Vehicle Scheduling (runtimes, vehicle journeys, day type-related vehicle schedules);
- Passenger Information (planned and real-time);
- Fare Management (fare structure, sales, validation, control);
- Operations Monitoring and Control: operating day-related data, vehicle follow-up, control actions;
- Driver Management:
- Driver Scheduling (day-type related driver schedules),
- Rostering (ordering of driver duties into sequences according to some chosen methods),
- Driving Personnel Disposition (assignment of logical drivers to physical drivers and recording of driver performance);
- Management Information and Statistics (including data dedicated to service performance indicators).
The data modules dedicated to cover most functions of the above domains will be specified.
Several concepts are shared by the different functional domains. This data domain is called "Common Concepts".
1.2 Functional Domain Description
The different functional domains (enumerated above) taken into account in the present document, and of which the data have been represented as the reference model, are described in EN 12896-1:2016, Public transport - Reference data model - Part 1: Common Concepts.
1.3 Particular Scope of this Document
The present document entitled Public transport - Reference data model - Part 8: Management information & statistics describes how to structure data which refers to the planning stages (e.g. timetables, run times, driver rosters, etc.) and/or to the daily actual production, and which is registered for different purposes, in particular to build service performance indicators. The data model is based on a generic design pattern, Generic Loggable Objects Model (provided in the Additional Common Concepts part - Annex B), and incorporates the following data packages:
- Logging Time and Place, providing additions to the Generic Loggable Objects Model,
- Recorded Objects,
- Recorded Use of Services,
- Service Journey Performance.
The last three packages show how the recorded data contributes to the implementation of indicators.
This document itself is composed of the following parts:
- Main document (normative),
- Annex A (normative), containing the data dictionary, i.e. the list of all the concepts and attribute tables present in the main document together with the definitions,
- Annex B (normative), providing a complement to EN 12896-1:2016, particularly useful for Parts 4 to 8 of the Public Transport Reference Data Model;
- Annex C (informative), indicating the data model evolution from the previous version.
The main objective of the present standard is to present the Reference Data Model for Public Transport, based on:
- the Reference Data Model, EN 12896, known as Transmodel V5.1;
- EN 28701:2012, Intelligent transport systems - Public transport - Identification of Fixed Objects in Public Transport (IFOPT), although note that this particular standard has been withdrawn as it is now included within Parts 1 and 2 of this standard (EN 12896 1:2016 and EN 12896 2:2016) following their successful publication;
incorporating the requirements of:
- EN 15531-1 to −3 and CEN/TS 15531-4 and −5: Public transport - Service interface for real-time information relating to public transport operations (SIRI);
- CEN/TS 16614-1 and -2: Network and Timetable Exchange (NeTEx), in particular the specific needs for long distance train operation.
Particular attention is drawn to the data model structure and methodology:
- the data model is described in a modular form in order to facilitate the understanding and the use of the model;
- the data model is entirely described in UML.
The following functional domains are considered:
- Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places;
- Timing Information and Vehicle Scheduling (runtimes, vehicle journeys, day type-related vehicle schedules);
- Passenger Information (planned and real-time);
- Fare Management (fare structure, sales, validation, control);
- Operations Monitoring and Control: operating day-related data, vehicle follow-up, control actions;
- Driver Management:
- Driver Scheduling (day-type related driver schedules),
- Rostering (ordering of driver duties into sequences according to some chosen methods),
- Driving Personnel Disposition (assignment of logical drivers to physical drivers and recording of driver performance);
- Management Information and Statistics (including data dedicated to service performance indicators).
The data modules dedicated to cover most functions of the above domains will be specified.
Several concepts are shared by the different functional domains. This data domain is called "Common Concepts".
1.2 Functional Domain Description
The different functional domains (enumerated above) taken into account in the present document, and of which the data have been represented as the reference model, are described in EN 12896-1:2016, Public transport - Reference data model - Part 1: Common Concepts.
1.3 Particular Scope of this Document
The present document entitled Public transport - Reference data model - Part 8: Management information & statistics describes how to structure data which refers to the planning stages (e.g. timetables, run times, driver rosters, etc.) and/or to the daily actual production, and which is registered for different purposes, in particular to build service performance indicators. The data model is based on a generic design pattern, Generic Loggable Objects Model (provided in the Additional Common Concepts part - Annex B), and incorporates the following data packages:
- Logging Time and Place, providing additions to the Generic Loggable Objects Model,
- Recorded Objects,
- Recorded Use of Services,
- Service Journey Performance.
The last three packages show how the recorded data contributes to the implementation of indicators.
This document itself is composed of the following parts:
- Main document (normative),
- Annex A (normative), containing the data dictionary, i.e. the list of all the concepts and attribute tables present in the main document together with the definitions,
- Annex B (normative), providing a complement to EN 12896-1:2016, particularly useful for Parts 4 to 8 of the Public Transport Reference Data Model;
- Annex C (informative), indicating the data model evolution from the previous version.
Alusdokumendid: EN 12896-8:2019
Asendatud: EVS-EN 12896-8:2026
EVS-EN 726-3:2000
Identifitseerimiskaardisüsteemid. Sides kasutatavad kiipkaardid ja terminalid. Osa 3: Rakendusest sõltumatud nõuded kaardile
Käsitlusala: Käesolev standard määratleb sides kasutatavatele kiipkaartidele ja kaarditerminalidele esitatavaid nõudeid Euroopas. Osa 3 sisaldab terminalide rakendusest sõltumatuid karakteristikuid.
Alusdokumendid: EN 726-3:1994
EVS-EN 726-4:2000
Identifitseerimiskaardisüsteemid. Sides kasutatavad kiipkaardid ja terminalid. Osa 4: Kaardiga seotud ja rakendusest sõltumatud nõuded terminalile
Käsitlusala: Standardi EN 726 osa 4 spetsifitseerib rakendusest sõltumatud ja kaardiga seotud karakteristikud kaarditerminalidele, mis on võimelised käitlema standardi EN 726 osale 3 vastavaid kaarte. Määratletud on kõik vajalikud üldised karakteristikud standardiseeritud kaardi kasutamiseks terminalides.
Alusdokumendid: EN 726-4:1994
EVS-EN 726-5:2001
Identification card system - Telecommunications integrated circut(s) cards and terminals - Part 5: Payment methods
Käsitlusala: This part of EN 726 specifies payment methods for telecommunication applications, using IC cards. These payment methods are not necessarily linked to the applications which use them, and they can be used by more than one application.
Alusdokumendid: EN 726-5:1999
EVS-EN 726-6:2000
Identifitseerimiskaardisüsteemid. Sides kasutatavad kiipkaardid ja terminalid. Osa 6: Side eriomadused
Käsitlusala: Käesoleva standardi käsitlusalaks on kiipkaardi kasutamisega seotud side eriomadused. Neid eriomadusi saab kasutada enam kui ühel rakendusotstarbel. Käesolev standard kirjeldab kaarditerminali liidest, kusjuures vajadusel arvestatakse kogu süsteemiga. Käesolev standard kirjeldab järgnevaid side eriomadusi: lühivalimine; viimase numbri valimine (salvestatud kaardile); eelsalvestatud numbri valimine.
Alusdokumendid: EN 726-6:1995
CEN/TR 17370:2019
Public transport - Operating raw data and statistics exchange
Käsitlusala: 2.1 Introduction
The OpRa work scope is the definition of a minimum set of Public Transport raw data needed as PT quantitative analysis enabling factor. To obtain this considering all the several aspects involved in this complex domain, the work has been conducted through the following phases:
1) assessment;
2) use cases definition and classification;
3) indicators definition;
4) raw data identification.
OpRa work does not go into the field of service quality measurement and reporting: service quality analysis will of course use data provided by OpRa, but quality definition remains a contractual level issue between a Public Transport Authority and a Public Transport Operator or an operator’s internal choice for a purely private service. OpRa mainly only reports unbiased actual data (i.e. measured or observed), described and aggregated in a shared and understandable way.
The OpRa work documented in detail in this document is coherent with EU Directive 2010/40. In particular, it relates to the Article 4 of the Delegated Regulation EU 2017/1926, as regards the historic data. OpRa proposes to complement NeTEx (dedicated to the static scheduled information), for the historic data based on the underlying conceptual data reference model Transmodel EN 12896, similarly to the requirement of the Delegated Regulation EU 2017/1926 referring to the static scheduled information. (...)
The OpRa work scope is the definition of a minimum set of Public Transport raw data needed as PT quantitative analysis enabling factor. To obtain this considering all the several aspects involved in this complex domain, the work has been conducted through the following phases:
1) assessment;
2) use cases definition and classification;
3) indicators definition;
4) raw data identification.
OpRa work does not go into the field of service quality measurement and reporting: service quality analysis will of course use data provided by OpRa, but quality definition remains a contractual level issue between a Public Transport Authority and a Public Transport Operator or an operator’s internal choice for a purely private service. OpRa mainly only reports unbiased actual data (i.e. measured or observed), described and aggregated in a shared and understandable way.
The OpRa work documented in detail in this document is coherent with EU Directive 2010/40. In particular, it relates to the Article 4 of the Delegated Regulation EU 2017/1926, as regards the historic data. OpRa proposes to complement NeTEx (dedicated to the static scheduled information), for the historic data based on the underlying conceptual data reference model Transmodel EN 12896, similarly to the requirement of the Delegated Regulation EU 2017/1926 referring to the static scheduled information. (...)
Alusdokumendid: CEN/TR 17370:2019
Asendatud: CEN/TS 17370:2026
ISO/IEC 23090-3:2024
Information technology — Coded representation of immersive media — Part 3: Versatile video coding
Käsitlusala: This document specifies a video coding technology known as versatile video coding (VVC), comprising a video coding technology with a compression capability that is substantially beyond that of the prior generations of such standards and with sufficient versatility for effective use in a broad range of applications.
Only the syntax format, semantics, and associated decoding process requirements are specified, while other matters such as pre-processing, the encoding process, system signalling and multiplexing, data loss recovery, post-processing, and video display are considered to be outside the scope of this document. Additionally, the internal processing steps performed within a decoder are also considered to be outside the scope of this document; only the externally observable output behaviour is required to conform to the specifications of this document.
This document is designed to be generic in the sense that it serves a wide range of applications, bit rates, resolutions, qualities and services. Applications include, but are not limited to, video coding for digital storage media, television broadcasting and real-time communication. In the course of creating This document, various requirements from typical applications have been considered, necessary algorithmic elements have been developed, and these have been integrated into a single syntax. Hence, this document is designed to facilitate video data interchange among different applications.
Only the syntax format, semantics, and associated decoding process requirements are specified, while other matters such as pre-processing, the encoding process, system signalling and multiplexing, data loss recovery, post-processing, and video display are considered to be outside the scope of this document. Additionally, the internal processing steps performed within a decoder are also considered to be outside the scope of this document; only the externally observable output behaviour is required to conform to the specifications of this document.
This document is designed to be generic in the sense that it serves a wide range of applications, bit rates, resolutions, qualities and services. Applications include, but are not limited to, video coding for digital storage media, television broadcasting and real-time communication. In the course of creating This document, various requirements from typical applications have been considered, necessary algorithmic elements have been developed, and these have been integrated into a single syntax. Hence, this document is designed to facilitate video data interchange among different applications.
Alusdokumendid:
Asendatud: ISO/IEC 23090-3:2026
ISO/IEC 23002-7:2024
Information technology — MPEG video technologies — Part 7: Versatile supplemental enhancement information messages for coded video bitstreams
Käsitlusala: This document specifies the syntax and semantics of video usability information (VUI) parameters and supplemental enhancement information (SEI) messages. The VUI parameters and SEI messages defined in this document are designed to be conveyed within coded video bitstreams in a manner specified in a video coding specification or to be conveyed by other means determined by the specifications for systems that make use of such coded video bitstreams. This document is particularly intended for use with coded video bitstreams as specified by Rec. ITU-T H.266 | ISO/IEC 23090-3, although it is drafted in a manner intended to be sufficiently generic that it can also be used with other types of coded video bitstreams.
VUI parameters and SEI messages can assist in processes related to decoding, display or other purposes. However, unless otherwise specified in a referencing specification, the interpretation and use of the VUI parameters and SEI messages specified in this document is not a required functionality of a video decoder or receiving video system. Although semantics are specified for the VUI parameters and SEI messages, decoders and receiving video systems can simply ignore the content of the VUI parameters and SEI messages or can use them in a manner that somewhat differs from what is specified in this document.
VUI parameters and SEI messages can assist in processes related to decoding, display or other purposes. However, unless otherwise specified in a referencing specification, the interpretation and use of the VUI parameters and SEI messages specified in this document is not a required functionality of a video decoder or receiving video system. Although semantics are specified for the VUI parameters and SEI messages, decoders and receiving video systems can simply ignore the content of the VUI parameters and SEI messages or can use them in a manner that somewhat differs from what is specified in this document.
Alusdokumendid:
Asendatud: ISO/IEC 23002-7:2026
ISO/IEC 23008-2:2025
Information technology — High efficiency coding and media delivery in heterogeneous environments — Part 2: High efficiency video coding
Käsitlusala: This document specifies high efficiency video coding.
Alusdokumendid:
Asendatud: ISO/IEC 23008-2:2026
Kavandid
prEN ISO 19186-1
Geographic information - GeoSPARQL - Part 1: A geographic query language for RDF data (ISO/DIS 19186-1:2026)
Käsitlusala: This document comprises multiple human and machine-readable resources with different roles that together define a vocabulary for representing some spatial information according to a data model and extensions to a query language for accessing that information. See the Introduction section 0.4 for details of the parts.
It does not define a comprehensive vocabulary for representing all spatial information: it only defines a core set of classes, properties and datatypes that can be used to construct query patterns. Many useful extensions to this vocabulary are possible, and we intend for the Semantic Web and Geospatial communities to develop additional vocabularies for describing spatial information.
It does not define a comprehensive vocabulary for representing all spatial information: it only defines a core set of classes, properties and datatypes that can be used to construct query patterns. Many useful extensions to this vocabulary are possible, and we intend for the Semantic Web and Geospatial communities to develop additional vocabularies for describing spatial information.
Alusdokumendid: ISO/DIS 19186-1; prEN ISO 19186-1
prEN 18283
Artificial Intelligence - Concepts, measures and requirements for managing bias in AI systems
Käsitlusala: This document defines concepts, measures and requirements for assessment and treatment of bias in AI systems. This includes bias unwanted by the AI Provider and AI Deployer according to their specification of the AI system, in the context of the AI Act.
This encompasses consideration of data bias including any data used to build or assess the AI system, but also system or model bias that can result from algorithmic factors, such as algorithm design choices.
This encompasses consideration of data bias including any data used to build or assess the AI system, but also system or model bias that can result from algorithmic factors, such as algorithm design choices.
Alusdokumendid: prEN 18283
EN 18052:2025/prA1
Intelligent transport systems - ESafety - ECall end to end conformance testing for eCall HLAP in hybrid circuit switched/packet switched network environments
Käsitlusala: This document describes the key actors in the eCall chain of service provision in hybrid circuit switched/packet switched network environments as:
1) In-Vehicle System (IVS)/vehicle,
2) Mobile Network Operator (MNO),
3) Public Safety Answering Point (PSAP),
and to provide conformance tests for actor groups 1) – 3).
NOTE 1 Conformance tests are not appropriate nor required for vehicle occupants, although they are the recipient of the service.
NOTE 2 Third party eCall systems (TPS-eCall) are not within the scope of this deliverable. This is because the core TPS-eCall standard (EN 16102) does not specify the communications link between the vehicle and the TPS service provider.
NOTE 3 These conformance tests are partly based on the appropriate conformance tests from EN 16454 and CEN/prEN 17240.
This deliverable therefore adapts and revises Conformance Test Protocols (CTP) from EN 16454 and CEN/prEN 17240 for hybrid circuit switched/packet switched network environments.
This document complements EN 16454 and CEN/prEN 17240 and provides a suite of conformance tests for IVS equipment, MNOs and PSAPs, required to ensure and demonstrate compliance with CEN/prEN 7905.
The scope covers conformance testing of new engineering developments, products and systems, and does not imply testing associated with individual installations in vehicles or locations.
1) In-Vehicle System (IVS)/vehicle,
2) Mobile Network Operator (MNO),
3) Public Safety Answering Point (PSAP),
and to provide conformance tests for actor groups 1) – 3).
NOTE 1 Conformance tests are not appropriate nor required for vehicle occupants, although they are the recipient of the service.
NOTE 2 Third party eCall systems (TPS-eCall) are not within the scope of this deliverable. This is because the core TPS-eCall standard (EN 16102) does not specify the communications link between the vehicle and the TPS service provider.
NOTE 3 These conformance tests are partly based on the appropriate conformance tests from EN 16454 and CEN/prEN 17240.
This deliverable therefore adapts and revises Conformance Test Protocols (CTP) from EN 16454 and CEN/prEN 17240 for hybrid circuit switched/packet switched network environments.
This document complements EN 16454 and CEN/prEN 17240 and provides a suite of conformance tests for IVS equipment, MNOs and PSAPs, required to ensure and demonstrate compliance with CEN/prEN 7905.
The scope covers conformance testing of new engineering developments, products and systems, and does not imply testing associated with individual installations in vehicles or locations.
Alusdokumendid: EN 18052:2025/prA1
prEN 40004-3:2026
Cybersecurity requirements for Field Programmable Gate Arrays and Application Specific Integrated Circuits with security-related functionalities
Käsitlusala: This document specifies the technical requirements for general-purpose Application Specific Integrated Circuits (ASICs) and Field Programmable Gate Arrays (FPGAs) with security features, related to cybersecurity. The products with digital elements in scope, thereafter "platforms":
— are specified within the "technical description" of the "category of product" number "NN" by the Commission Implementing Regulation (EU) 2025/2392 [16] as:
• “Application specific integrated circuits (ASIC) with security-related functionalities are products with digital elements that are integrated circuits, fully or partially custom-designed to perform a specific function or implement a specific application, and which additionally provide security-related functionalities that aim to secure other products, networks or services beyond the ASIC itself, such as trusted execution environments or secure communication interfaces.”
• “Field-programmable gate arrays (FPGA) with security-related functionalities are products with digital elements that are integrated circuits characterized by a matrix of configurable logic blocks designed to be reprogrammable after manufacturing to perform a specific function or implement a specific application, and which additionally provide security-related functionalities that aim to secure other products, networks or services beyond the FPGA itself, such as trusted execution environments or secure communication interfaces.”
— are only covered within the product context described in Clause 4.
The present document covers those products to demonstrate compliance with essential cybersecurity requirements in the Regulation (EU) 2024/2847 [16] Annex I Part I under the conditions identified in Annex ZZ.
ASICs and FPGAs additionally provide security-related functionalities, such as encryption, authentication, secure key storage, random number generation, trusted execution environment, or other hardware- based protection mechanisms, that aim to secure other products, networks or services beyond the ASIC or FPGA itself, such as secure boot chain, virtualization or secure communication interfaces
Such ASICs and FPGAs are intended to be integrated in a larger system, complemented by application software, and optionally by additional hardware components by integrators to build a device corresponding to a given intent of use. The intent of use of the platform integrated into a device is likely be known to the manufacturer of the ASIC with security-related functionalities, while the intent of use of the platform integrated into a device may not be known to the manufacturer of the FPGA with security-related functionalities.
The ASICs and FPGAs in scope are designed for deployment in environments where the security features of the product integrating the platform are of importance, and where the threat landscape includes attackers with low/medium attack potential.
— are specified within the "technical description" of the "category of product" number "NN" by the Commission Implementing Regulation (EU) 2025/2392 [16] as:
• “Application specific integrated circuits (ASIC) with security-related functionalities are products with digital elements that are integrated circuits, fully or partially custom-designed to perform a specific function or implement a specific application, and which additionally provide security-related functionalities that aim to secure other products, networks or services beyond the ASIC itself, such as trusted execution environments or secure communication interfaces.”
• “Field-programmable gate arrays (FPGA) with security-related functionalities are products with digital elements that are integrated circuits characterized by a matrix of configurable logic blocks designed to be reprogrammable after manufacturing to perform a specific function or implement a specific application, and which additionally provide security-related functionalities that aim to secure other products, networks or services beyond the FPGA itself, such as trusted execution environments or secure communication interfaces.”
— are only covered within the product context described in Clause 4.
The present document covers those products to demonstrate compliance with essential cybersecurity requirements in the Regulation (EU) 2024/2847 [16] Annex I Part I under the conditions identified in Annex ZZ.
ASICs and FPGAs additionally provide security-related functionalities, such as encryption, authentication, secure key storage, random number generation, trusted execution environment, or other hardware- based protection mechanisms, that aim to secure other products, networks or services beyond the ASIC or FPGA itself, such as secure boot chain, virtualization or secure communication interfaces
Such ASICs and FPGAs are intended to be integrated in a larger system, complemented by application software, and optionally by additional hardware components by integrators to build a device corresponding to a given intent of use. The intent of use of the platform integrated into a device is likely be known to the manufacturer of the ASIC with security-related functionalities, while the intent of use of the platform integrated into a device may not be known to the manufacturer of the FPGA with security-related functionalities.
The ASICs and FPGAs in scope are designed for deployment in environments where the security features of the product integrating the platform are of importance, and where the threat landscape includes attackers with low/medium attack potential.
Alusdokumendid: prEN 40004-3:2026
prEN IEC 62439-1:2026
Industrial communication networks - High availability automation networks - Part 1: General concepts and calculation methods
Käsitlusala: The IEC 62439 series is applicable to high-availability automation networks based on the ISO/IEC/IEEE 8802-3:2021/Amd 3 (IEEE 802.3) (Ethernet) technology.
This part of the IEC 62439 series specifies
– the common elements and definitions for other parts of the IEC 62439 series;
– the conformance test specification (normative);
– a classification scheme for network characteristics (informative);
– a methodology for estimating network availability (informative);
– the configuration rules, calculation and measurement method for a deterministic recovery time in RSTP.
This part of the IEC 62439 series specifies
– the common elements and definitions for other parts of the IEC 62439 series;
– the conformance test specification (normative);
– a classification scheme for network characteristics (informative);
– a methodology for estimating network availability (informative);
– the configuration rules, calculation and measurement method for a deterministic recovery time in RSTP.
Alusdokumendid: 65C/1472/CDV; prEN IEC 62439-1:2026