Biotechnology — Biobanking of microorganisms — Part 1: Bacteria and archaea

Biotechnologie — Biobanque des microorganismes — Partie 1: Bactéries et archées

This document specifies requirements for the biobanking of bacteria and archaea. It includes management of microbial material associated data as well as biosafety and biosecurity requirements.

This document is applicable to all organizations performing biobanking with bacteria and archaea used for research and development.

This document does not apply to processing methods for microbial materials intended for food/feed production, laboratories undertaking food/feed analysis or therapeutic use.

NOTE      International, national or regional regulations or requirements, or multiple of them, can also apply to specific topics covered in this document.


Biotechnology — Biobanking — Part 2: General guidelines for biobanking of human mesenchymal stromal cells derived from bone marrow


Dentistry — Hydrocolloid impression materials

Médecine bucco-dentaire — Produits pour empreintes à base d'hydrocolloïdes

This document specifies the requirements and test methods for hydrocolloid impression materials. This document helps to determine whether elastic aqueous agar and alginate hydrocolloid dental impression materials, as prepared for retail marketing, are of the quality needed for their intended purposes. It also specifies requirements for labelling and instructions for use. This document does not address possible biological hazards associated with the materials. Assessment of these hazards is addressed in ISO 7405 and the ISO 10993 series.


Air intake filter systems for rotary machinery — Test methods — Part 2: Filter element endurance test in fog and mist environments

Systèmes de filtration d'air d'admission pour machines tournantes — Méthodes d'essai — Partie 2: Essai d'endurance d'élément filtrant en brouillard et environnement brumeux

This document specifies general test requirements, the test rig and equipment, the test materials and the test procedure and report for determining water endurance performance of air filter elements used in air intake filter systems for rotary machinery such as stationary gas turbines, compressors and other stationary internal combustion engines.

The test evaluates water endurance performance of air filter elements under laboratory conditions. The performance results obtained in accordance with this document cannot be quantitatively applied (by themselves) to predict performance in service with regard to water endurance and lifetime.


Soil quality — Sampling of soil invertebrates — Part 4: Sampling, extraction and identification of soil-inhabiting nematodes

Qualité du sol — Prélèvement des invertébrés du sol — Partie 4: Prélèvement, extraction et identification des nématodes du sol

This document specifies a method for sampling and handling free-living nematodes from terrestrial field soils as a prerequisite for using them as bio-indicators (e.g. to assess the quality of a soil as a habitat for organisms).

This document applies to all terrestrial biotopes in which nematodes occur. The sampling design of field studies in general is specified in ISO 18400-101.

This document is not applicable to aquatic nematodes because of differences in the sample matrix (e.g. water column). Methods for some other soil organism groups such as earthworms, collembolans enchytraeids or macro-invertebrates are covered in ISO 23611-1, ISO 23611-2, ISO 23611-3 and ISO 23611-5.

This document does not cover the pedological characterization of the site which is highly recommendable when sampling soil invertebrates. ISO 10390, ISO 10694, ISO 11272, ISO 11274, ISO 11277, ISO 11461 and ISO 11465 include suitable procedures for measuring pH, particle size distribution, C/N ratio, organic carbon content and water-holding capacity.


Paints and varnishes — Corrosion protection of steel structures by protective paint systems — Part 5: Protective paint systems

Peintures et vernis — Anticorrosion des structures en acier par systèmes de peinture — Partie 5: Systèmes de peinture anticorrosion

This document describes the types of paint and paint system commonly used for corrosion protection of steel structures.

It also gives guidelines for the selection of paint systems available for different environments (see ISO 12944‑2) except for corrosivity category CX and category Im4 as defined in ISO 12944‑2 and different surface preparation grades (see ISO 12944‑4), and the durability grade to be expected (see ISO 12944‑1).


Road vehicles — Software update engineering

Véhicules routiers — Ingénierie de mise à jour du logiciel

This document specifies requirements and recommendations for software update engineering for road vehicles on both the organizational and the project level.

This document is applicable to road vehicles whose software can be updated.

The requirements and recommendations in this document apply to vehicles, vehicle systems, ECUs, infrastructure, and the assembly and deployment of software update packages after the initial development.

This document is applicable to organizations involved in software update engineering for road vehicles. Such organizations can include vehicle manufacturers, suppliers, and their subsidiaries or partners.

This document establishes a common understanding for communicating and managing activities and responsibilities among organizations and related parties.

The development of software for vehicle functions, except for software update engineering, is outside the scope of this document.

Finally, this document does not prescribe specific technologies or solutions for software update engineering.


Dried barberry — Specification and test methods

Épine-vinette séchée — Spécification et méthodes d'essai

This document specifies requirements and test methods for the dried barberry fruit of the Berberis vulgaris L. tree.

It is applicable to dried red barberries only.


Leather — Determination of chlorinated hydrocarbons in leather — Part 1: Chromatographic method for short-chain chlorinated paraffins (SCCPs)

Cuir — Dosage des hydrocarbures chlorés dans le cuir — Partie 1: Méthode chromatographique pour les paraffines chlorées à chaîne courte (PCCC)

This document specifies a chromatographic method to determine the amount of short-chain chlorinated paraffins (SCCPs) C10 to C13 in processed and unprocessed leathers.


Information technology — Automatic identification and data capture techniques — Code 39 bar code symbology specification

Technologies de l'information — Techniques automatiques d'identification et de capture des données — Spécifications des symbologies des codes à barres, code 39

This document specifies the requirements for the bar code symbology known as Code 39. This document specifies Code 39 symbology characteristics, data character encodation, dimensions, tolerances, decoding algorithms and parameters to be defined by applications. This document specifies the symbology identifier prefix strings for Code 39 symbols.


Information technology — Automatic identification and data capture techniques — EAN/UPC bar code symbology specification

Technologies de l'information — Techniques automatiques d'identification et de capture des données — Spécification de symbologie de code à barres EAN/UPC


Information technology — Power efficiency measurement specification for data center storage

This document describes a standardized method to assess the energy efficiency of commercial storage products in both active and idle states of operation. A taxonomy is defined that classifies storage products in terms of operational profiles and supported features. Test definition and execution rules for measuring the power efficiency of each taxonomy category are described; these include test sequence, test configuration, instrumentation, benchmark driver, IO profiles, measurement interval, and metric stability assessment. Qualitative heuristic tests are defined to verify the existence of several capacity optimization methods. Resulting power efficiency metrics are defined as ratios of idle capacity or active operations during a selected stable measurement interval to the average measured power.


Information security, cybersecurity and privacy protection — Guidelines for information security management systems auditing

Sécurité de l'information, cybersécurité et protection des données privées — Lignes directrices pour l'audit des systèmes de management de la sécurité de l'information

This document provides guidance on managing an information security management system (ISMS) audit programme, on conducting audits, and on the competence of ISMS auditors, in addition to the guidance contained in ISO 19011.

This document is applicable to those needing to understand or conduct internal or external audits of an ISMS or to manage an ISMS audit programme.


Lung ventilators — Part 4: Particular requirements for user-powered resuscitators

Ventilateurs pulmonaires — Partie 4: Exigences relatives aux ressuscitateurs actionnés par l’utilisateur

This document specifies requirements for user-powered resuscitators intended for use with all age groups and which are intended to provide lung ventilation to patients whose breathing is inadequate. User-powered resuscitators are designated according to ideal body mass range.

Example user-powered resuscitators include:

—    self-inflating bag resuscitators intended to be squeezed by the user’s hand and refilled by elastic recoil; and

NOTE 1    Self-inflating bag resuscitators are generally transit-operable and can be used in a wide range of environmental and emergency situations.

—    flow-inflating bag resuscitators intended to be squeezed by the user’s hand and refilled by a flow from a medical gas source.

This document is also applicable to those accessories that are intended for use with resuscitators where the characteristics of those accessories can affect the safety of the user-powered resuscitator.

Examples of such accessories include face masks, PEEP valves, capnometric indicators, manometers, metronomes, flow restrictors, filters, gas refill valves, oxygen gas mixers, connectors, electronic feedback devices, electronic sensors and transmission of data to other equipment.

This document is also applicable to point-of-use packaging.

This document does not specify the requirements for:

—    gas-powered emergency resuscitators, which are given in ISO 10651-5;

—    electrically-powered resuscitators;

—    gas powered resuscitators for professional healthcare facilities; and

—    anaesthetic reservoir bags, which are given in ISO 5362.

NOTE 2    This document has been prepared to address the relevant essential principles[24] and labelling[25] guidances of the International Medical Devices Regulators Forum (IMDRF) as indicated in Annex D.

NOTE 3    This document has been prepared to address the relevant essential principles of safety and performance of ISO 16142-1:2016 as indicated in Annex E.

NOTE 4    This document has been prepared to address the relevant general safety and performance requirements of European regulation (EU) 2017/745[23] as indicated in Annex F.


Aerospace elements of electrical and optical connection — Test methods — Part 326: Fire immersion test

Connections électriques et optiques d'éléments aérospatiaux — Méthodes d'essai — Partie 326: Immersion au feu


Raw Camel Hides — Guidelines for grading on the basis of mass, size and defects


Technical product documentation — Design for manufacturing, assembling, disassembling and end-of-life processing — Part 2: Vocabulary

Conception et documentation pour la fabrication, le montage, le démontage et le traitement en fin de vie (MADE) — Partie 2: Vocabulaire

This document deﬁnes terms for design for manufacturing, assembling, disassembling and end-of-life processing.


Animal feeding stuffs — Determination of crude ash

Aliments des animaux — Dosage des cendres brutes

This document specifies a method for the determination of crude ash of animal feeding stuffs.


Paints, varnishes and raw materials for paints and varnishes — Sampling

Peintures, vernis et matières premières pour peintures et vernis — Échantillonnage

This document specifies procedures for the sampling of paints and varnishes, including coating powders, and raw materials used in their manufacture. Such products include liquids and materials which, without undergoing chemical modification, are capable of being liquefied when heated up, and powdered, granulated and pasty materials. Samples can be taken from containers, for example cans, drums, tanks, tank wagons or ships' tanks, as well as from barrels, sacks, big-bags, silos or silo wagons or conveyor belts.

This document does not deal with the sample preparation for testing or reduction of the samples thus taken, which is dealt with in ISO 1513.


Technical product documentation (TPD) — Classification of requirements — Part 1: Framework

Documentation technique de produits (TPD) — Classification des exigences — Partie 1: Cadre

This document specifies a framework for building systems for the classification of requirements. Such systems can be used to indicate requirements of special importance, and communicate them for production set-up, verification, audit, etc.

This document:

—     gives background information why such systems are useful in many areas of manufacturing;

—     can be referred to for the concept of classification of requirements;

—     functions as a framework for applying such systems in technical product documentation (TPD);

—     indicates the needed elements for a classification system;

—     supports with aspects in the choice of symbols for a classification system.

As a framework, this document does not give the details of a specific classification system. Instead, it functions as a basis for an organization-specific system which contains details such as notations and symbols, classification levels, assessment procedures, etc., including usage and interpretation in the TPD.

This document does not specify the contractual consequences of a classification (e.g. needed actions such as choice of tools, reliability index or process capability for a classification level) nor other references to standards or documents for handling classifications and nonconformity to requirements.


Road vehicles — Standardized access to automotive repair and maintenance information (RMI) — Part 1: General information and use case definition

Véhicules routiers — Normalisation de l'accès aux informations relatives à la réparation et à la maintenance pour l'automobile (RMI) — Partie 1: Informations générales et définitions de cas d'utilisation

This document provides a general overview and structure of each part of the ISO 18541 series. This document also describes the use cases applicable to the standardized access to automotive RMI. The use cases address real world scenarios (e.g. servicing vehicles) regarding the information access necessary to perform vehicle roadside assistance, inspection, diagnosis, repair and maintenance, including the updating and replacement of electronic control units (ECU).

Furthermore, this document defines requirements for granting access to security-related RMI in Annex A following the SERMI scheme.

The RMI systems used by personnel to perform the services consist of:

—    a web-based system, which provides access to RMI needed to perform the service(s);

—    contact information for specific RMI;

—    a security framework to protect access to security-related RMI (vehicle theft protection measures).

This document is applicable to light passenger vehicles and light commercial vehicles.


Road vehicles — Standardized access to automotive repair and maintenance information (RMI) — Part 2: Technical requirements

Véhicules routiers — Normalisation de l'accès aux informations relatives à la réparation et à la maintenance pour l'automobile (RMI) — Partie 2: Exigences techniques

This document includes technical requirements which are related to automotive repair and maintenance information (RMI) systems in order to standardize access to RMI for independent operators.

This document specifies the minimum set of technical requirements related to a vehicle manufacturer's RMI system. These requirements will reflect the deriving needs from the use cases as specified in ISO 18541‑1.

Furthermore, this document defines requirements for granting access to security-related RMI in Annex A following the SERMI scheme.

This document is applicable to light passenger and commercial vehicles as defined in regulation (EC) 715/2007 Article 2 [15].


Road vehicles — Standardized access to automotive repair and maintenance information (RMI) — Part 3: Functional user interface requirements

Véhicules routiers — Normalisation de l'accès aux informations relatives à la réparation et à la maintenance pour l'automobile (RMI) — Partie 3: Exigences fonctionnelles relatives à l’interface utilisateur

This document includes functional user interface requirements related to automotive repair and maintenance information (RMI) systems in order to standardize access to RMI for independent operators.

This document specifies all functional user interface requirements related to a vehicle manufacturer's RMI system. These requirements will reflect the deriving needs from the use cases as specified in ISO 18541‑1.


Road vehicles — Standardized access to automotive repair and maintenance information (RMI) — Part 4: Conformance test

Véhicules routiers — Normalisation de l'accès aux informations relatives à la réparation et à la maintenance pour l'automobile (RMI) — Partie 4: Test de conformité

This document specifies a conformance test for a vehicle manufacturer assessment of self-conformance of the VM RMI system. The conformance test cases follow the use case definition of ISO 18541‑1 and the requirements stated in ISO 18541‑2 and ISO 18541‑3.

The primary, but not exclusive, purpose of this document is to provide information to the VM RMI system provider to build and test the VM RMI system against the conformance test cases. This final step in the development process of the VM RMI system is an enabler for all providers that their VM RMI system meets a high degree of functional requirements expected by the end user.

Furthermore, this document defines in Annex A conformance test cases for the use cases and requirements versions that apply for granting access to security-related RMI following the SERMI scheme.

This document is applicable to light passenger and commercial vehicles as defined in regulation (EC) 715/2007 Article 2 [9].


Road vehicles — Media Oriented Systems Transport (MOST) framework — Part 12: 50-Mbit/s balanced media physical layer

Véhicules routiers — Environnement du système axé sur les médias — Partie 12: Titre manque


Road vehicles — Media Oriented Systems Transport (MOST) framework — Part 13: 50-Mbit/s balanced media physical layer conformance test plan

Véhicules routiers — Environnement du système axé sur les médias — Partie 13: Titre manque


Road vehicles — Media Oriented Systems Transport (MOST) framework — Part 14: Lean application layer

Véhicules routiers — Environnement du système axé sur les médias — Partie 14: Titre manque


Road vehicles — Media Oriented Systems Transport (MOST) framework — Part 15: Lean application layer conformance test plan

Véhicules routiers — Environnement du système axé sur les médias — Partie 15: Titre manque


Document description and processing languages — Office Open XML file formats — Part 2: Open packaging conventions

Description des documents et langages de traitement — Formats de fichier "Office Open XML" — Partie 2: Conventions de paquetage ouvert

This document defines a set of conventions for packaging one or more interrelated byte streams (parts) as a single resource (package). These conventions are applicable not only to Office Open XML specifications as described in ISO/IEC 29500-1 and ISO/IEC 29500-4, but also to other markup specifications.


Straight cylindrical involute splines — Metric module, side fit — Part 1: Generalities

Cannelures cylindriques droites à flancs en développante — Module métrique, à centrage sur flancs — Partie 1: Généralités

This document provides the data and indications necessary for the design and manufacture of straight (non-helical) side-fitting cylindrical involute splines.

Limiting dimensions, tolerances, manufacturing deviations and their effects on the fit between connecting coaxial spline elements are defined in the formulae and given in the tables. Unless otherwise specified, linear dimensions are expressed in millimetres and angular dimensions in degrees.


Dentistry — Endodontic instruments — Part 5: Shaping and cleaning instruments

Médecine bucco-dentaire — Instruments d'endodontie — Partie 5: Instruments de mise en forme et de nettoyage

This document specifies requirements and test methods for hand-held and mechanically operated instruments used for shaping and cleaning root canals, and which are not specified in other parts of the ISO 3630 series.

This document specifies requirements for size, marking, product designation, safety considerations, labelling and packaging.


Straight cylindrical involute splines — Metric module, side fit — Part 2: Dimensions

Cannelures cylindriques droites à flancs en développante — Module métrique, à centrage sur flancs — Partie 2: Dimensions

This document specifies geometry and inspection dimensions for the design and manufacture of straight (non-helical) side-fitting cylindrical involute splines.

Limiting dimensions, tolerances, manufacturing errors and their effects on the fit between connecting coaxial spline elements are defined and tabulated. Linear dimensions are expressed in millimetres and angular dimensions in degrees.

The specified diameters for external splines in the geometry tables and the values in the inspection dimension tables are only valid for fundamental deviation "h".

For fundamental deviations other than "h", diameters and tooth thicknesses are calculated for external splines according to the formulae in ISO 4156-1 and inspection dimensions according to the formulae in ISO 4156-3.


Straight cylindrical involute splines — Metric module, side fit — Part 3: Inspection

Cannelures cylindriques droites à flancs en développante — Module métrique, à centrage sur flancs — Partie 3: Vérification

This document provides data, guidance and requirements for the inspection of straight (non-helical) side fitting cylindrical involute splines.

Limiting dimensions, tolerances, manufacturing deviations and their effects on the fit between connecting coaxial spline elements are defined and tabulated. Linear dimensions are expressed in millimetres and angular dimensions in degrees.


Essential oils — Name harmonization of components


Paper and board — Testing of cores — Part 4: Measurement of dimensions

Papier et carton — Essais des mandrins — Partie 4: Mesurage des dimensions

This document specifies test methods for the determination of the internal diameter, the external diameter, the wall thickness and the length of paper and board cores.


Gas cylinders — Compatibility of cylinder and valve materials with gas contents — Part 2: Non-metallic materials

Bouteilles à gaz — Compatibilité des matériaux des bouteilles et des robinets avec les contenus gazeux — Partie 2: Matériaux non métalliques

This document gives guidance on the selection and evaluation of compatibility between non-metallic materials for gas cylinders and valves and the gas contents. It is also applicable to tubes, pressure drums and bundles of cylinders.

This document covers composite and laminated materials used for gas cylinders. It does not include ceramics, glasses and adhesives.

This document considers the influence of the gas in changing the material and mechanical properties (e.g. chemical reaction or change in physical state). The basic properties of the materials, such as mechanical properties required for design purposes (normally available from the materials supplier), are not considered. Other aspects, such as quality of delivered gas, are not considered.

The compatibility data given are related to single component gases but can be applicable to gas mixtures.

This document does not apply to cryogenic fluids (this is covered in ISO 21010).


Robotics — Electrical interfaces — Connectivity and interoperability for end-effectors

This document specifies compatibility requirements for end-effectors with nominal power requirements of up to 200W.

The document covers the requirements for electrical connections at the robot, their related characteristics, designation and marking. This document also provides means for interfacing with safety related functions provided in external equipment.

The following is excluded from the scope of this document:

1.	mechanical requirements of the end-effector interface besides those related to the electrical connectors (the mechanical interface of end-effectors is covered by ISO 9409-1 and -2).
2.	communication protocols at the network, transport, session, presentation or application layer
3.	safety related performance requirements.
4.	the electrical connection requirements at the end-effector side; this document focuses on the robot side.
5.	aspects related to cyber security

Note: See ISO 10218-1:2025 and ISO 10218-2:2025 for cyber security requirements.


Information technology — JPEG 2000 image coding system: Conformance testing — Part 4: — Amendment 1: High-throughput JPEG 2000 conformance testing

Technologies de l'information — Système de codage d'images JPEG 2000: Tests de conformité — Partie 4: — Amendement 1: Titre manque


Information technology — JPEG 2000 image coding system: Reference software — Part 5: — Amendment 1: Additional reference software for HTJ2K

Technologies de l'information — Système de codage d'images JPEG 2000: Logiciel de référence — Partie 5: — Amendement 1: Titre manque


Tableware, giftware, jewellery and luminaries, made of glass — Glass clarity — Classification and test method

Vaisselle, objets de décoration, bijouterie et luminaires, faits de verre — Clarté du verre — Classification et méthode d'essai

This document establishes requirements for the use of the glass designations "clear glass" and "ultra-clear glass" for non-coloured glass items according to their clarity and iron content. It specifies a procedure for measuring the clarity of glass items by means of a spectrophotometer.

This document is applicable to

—     mineral glasses, and

—     glass items where a part is not covered by coating or decoration, and is therefore available for sampling.

This document is applicable to the use of glass as tableware, giftware, jewellery and luminaries.

It is not applicable to the use of glass in the context of building, watches, containers, medicine and laboratories, and to other technical uses of glass.


Information technology — Scalable compression and coding of continuous-tone still images — Part 1: Scalable compression and coding of continuous-tone still images — Amendment 1: Clarification of the upsampling process

Technologies de l'information — Compression échelonnable et codage d'images plates en ton continu — Partie 1: Codage des images à gamme dynamique élevée — Amendement 1: .


Information technology — Scalable compression and coding of continuous-tone still images — Part 8: Lossless and near-lossless coding — Amendment 1: Clarification of the upsampling process

Technologies de l'information — Compression échelonnable et codage d'images plates en ton continu — Partie 8: Titre manque — Amendement 1: .


Information technology — Coded representation of immersive media — Part 8: Network based media processing

Technologies de l'information — Représentation codée de média immersifs — Partie 8: Titre manque

The network-based media processing (NBMP) framework defines the interfaces including both data formats and application programming interfaces (APIs) among the entities connected through digital networks for media processing. Users can access and configure their operations remotely for efficient, intelligent processing. This document describes and manages workflows to be applied to the media data. This process includes uploading of media data to the network, instantiation of the media processing tasks, and configuration of the tasks. The framework enables dynamic creation of media processing pipelines, as well as access to processed media data and metadata in real-time or in a deferred way. The media and metadata formats used between the media source, workflow manager and media processing entities in a media processing pipeline are also specified.


Information technology — Internet of media things — Part 4: Reference software and conformance

Technologie de l'information — Internet des objets media — Partie 4: Logiciels de référence et conformité

This document specifies the conformance and reference software implementing ISO/IEC 23093-3. The information provided is applicable for determining the reference software modules available for ISO/IEC 23093-3, understanding the functionality of the available reference software modules, and utilizing the available reference software modules.

Furthermore, this document provides means for conformance testing, i.e. bitstreams ? XML descriptions ? that conform or do not conform to ISO/IEC 23093-3.


Hygrothermal performance of buildings — Calculation and presentation of climatic data — Part 4: Hourly data for assessing the annual energy use for heating and cooling

Performance hygrothermique des bâtiments — Calcul et présentation des données climatiques — Partie 4: Données horaires pour l'évaluation du besoin énergétique annuel  de chauffage et de refroidissement


Graphical symbols — Safety colours and safety signs — Registered safety signs — Amendment 101:  Safety sign P045 : No campfires

Symboles graphiques — Couleurs de sécurité et signaux de sécurité — Signaux de sécurité enregistrés — Amendement 101: Signal de sécurité P045 : Pas de feux de camp


Glass — Hydrolytic resistance of glass grains at 98 °C — Method of test and classification

Verre — Résistance hydrolytique du verre en grains à 98 °C — Méthode d'essai et classification

This document specifies

a)   a method for determining the hydrolytic resistance of glass grains at 98 °C. The resistance is measured and expressed by the volume of acid required for titration of the alkali extracted from the unit mass of glass, and can also be expressed by the amount of sodium oxide equivalent to this volume of acid, and

b)   a classification of glass according to the hydrolytic resistance determined by the method of this document.

This document is intended for use on the less resistant types of glass, such as soda-lime glass.

NOTE 1  For the more resistant glasses, e.g. borosilicate glass, the method specified in ISO 720 is more suited.

NOTE 2  It is emphasized that there is no exact correlation between the classification laid down in this document and that laid down in ISO 720, and it is, therefore, essential to identify which classification is being used.


Glass — Hydrolytic resistance of glass grains at 121 °C — Method of test and classification

Verre — Résistance hydrolytique du verre en grains à 121 °C — Méthode d'essai et classification

This document specifies

a)   a method for determining the hydrolytic resistance of glass grains at 121 °C. The resistance is measured and expressed by the volume of acid required for titration of the alkali extracted from the unit mass of glass, and can also be expressed by the amount of sodium oxide equivalent to this volume of acid, and

b)   a classification of glass according to the hydrolytic resistance determined by the method of this document.

This document is intended for use on the more resistant types of glass, e.g. borosilicate glass.

NOTE 1  For the less resistant glasses, e.g. soda-lime, the method specified in ISO 719 is more suited.

NOTE 2  It is emphasized that there is no exact correlation between the classification laid down in this document and that laid down in ISO 719, and it is, therefore, essential to identify which classification is being used.


Road vehicles — Vehicle to grid communication interface — Part 20: 2nd generation network layer and application layer requirements

Véhicules routiers — Interface de communication entre véhicule et réseau électrique — Partie 20: Exigences des couches réseau et application de 2ème génération

This document specifies the communication between the electric vehicle (EV), including battery electric vehicle (BEV) and plug-in hybrid electric vehicle (PHEV), and the electric vehicle supply equipment (EVSE). The application layer messages defined in this document are designed to support the electricity power transfer between an EV and an EVSE.

This document defines the communication messages and sequence requirements for bidirectional power transfer.

This document furthermore defines requirements of wireless communication for both conductive charging and wireless charging as well as communication requirements for automatic connection device and information services about charging and control status.

The purpose of this document is to detail the communication between an electric vehicle communication controller (EVCC) and a supply equipment communication controller (SECC). Aspects are specified to detect a vehicle in a communication network and enable an Internet Protocol (IP) based communication between the EVCC and the SECC.


Quantities and units — Part 6: Electromagnetism

Grandeurs et unités — Partie 6: Électromagnétisme

This part of IEC 80000 gives names, symbols, and definitions for quantities and units of electromagnetism. Where appropriate, conversion factors are also given.

This document is based on classical electromagnetism, i.e. mainly Maxwell’s equations. No reference is made to quantum field theories.


Paper and board — Stylus contact method — Part 1: Determination of surface roughness


Packed cork — Virgin cork, raw reproduction cork, burnt cork, boiled reproduction cork and raw cork waste — Determination of moisture content

Liège emballé — Liège mâle, liège de reproduction cru, liège flambé, liège de reproduction bouilli et rebut — Détermination de l'humidité

This document specifies a method for determination of the moisture content of packed cork, either virgin cork, raw reproduction cork, burnt cork, boiled reproduction cork and raw cork waste.


Information and documentation — International standard identifier for libraries and related organizations (ISIL)

Information et documentation — Identifiant international normalisé pour les bibliothèques et les organismes apparentés (ISIL)

This document specifies the International Standard identifier for libraries and related organizations (ISIL), which comprises a set of standard identifiers used for the unique identification of libraries and related organizations such as museums and archives with a minimum impact on already existing systems.

An ISIL identifies an organization, i.e. a library or a related organization, or one of its subordinate units, which is responsible for an action or service in an informational environment (e.g. creation of machine-readable information). It can be used to identify the originator or holder of a resource (e.g. library material or a collection in an archive). The ISIL is intended for use by libraries and related organizations such as museums and archives and agencies doing business or interacting with these organizations (e.g. suppliers, publishers, and government institutions). An ISIL identifies an organization or one of its subordinate units throughout its life. In some cases, such as when an organization has undergone a significant administrative change (e.g. a merger with another organization), particularly one that results in a name change, a new ISIL can be allocated.

Since this document allows the use of existing codes to be incorporated into the ISIL, it is possible that a given organization can have more than one ISIL. However, it is the intention of this document to minimize the number of codes.

Any library or related organization, administrative unit or subordinate unit, acting autonomously, can be allocated an ISIL.

An ISIL is not intended to be used to classify organizations or their services and holdings.


Paper and board — Stylus contact method — Part 2: Determination of surface friction


Agricultural irrigation equipment — Guideline on the implementation of pressurized irrigation systems — Part 1: General principles of irrigation

Matériel agricole d'irrigation — Lignes directrices relatives à la mise en œuvre des systèmes d'irrigation sous pression — Partie 1: Principes généraux d'irrigation

This document provides a guideline for the implementation of pressurized irrigation systems.

It is applicable to small-scale family agriculture and large-scale commercial agriculture, in open fields or within enclosed growing structures (e.g. greenhouse, net house).

This document is intended for the use of agriculture ministries, agronomists, irrigation planners, farmers and end-users.


Space data and information transfer systems — Spectral preprocessing transform for multispectral and hyperspectral image compression


Space data and information transfer systems — Spacecraft onboard interface services — RFID tag encoding specification


Space data and information transfer systems — Mission operations monitor & control services


Space data and information transfer systems — Voice and audio communications


Space data and information transfer systems — Mission operations — Message abstraction layer binding to TCP/IP transport and split binary encoding


Space data and information transfer systems — Delta-DOR quasar catalog update procedure


Space data and information transfer systems — Pointing request message


Space data and information transfer systems — Cross support service management — Simple schedule format specification


Space data and information transfer systems — Network layer security adaptation profile


Space data and information transfer systems — Mission operations — Message abstraction layer binding to HTTP transport and XML encoding


Internal protection by polymeric lining for ductile iron pipes

Protection interne des tuyaux en fonte ductile par revêtement polymérique


Information technology — Home electronic system (HES) interfaces — Part 4-1: Common user interface and cluster-to-cluster interface to support interworking among home cluster systems — Architecture

Technologies de l'information — Interfaces de systèmes électroniques domestiques (HES) — Partie 4-1: Titre manque

This document specifies an architecture for home cluster systems and for interworking among them. It specifies a cluster-to-cluster interface to enable interworking among home cluster systems and interoperability among the applications supported by these cluster systems as well as a common user interface to these cluster-system applications. This common user interface provides input and output methods for user information exchange to access, monitor and control applications running on home cluster systems.


Ships and marine technology — Design and testing of marine transfer arms for liquefied hydrogen

Navires et technologie maritime — Conception et essais des bras de transfert marins pour l'hydrogène liquéfié

This document specifies the design, minimum safety requirements, and inspection and testing procedures for liquefied hydrogen (LH2) marine transfer arms intended for use at onshore LH2 terminals handling LH2 carriers. It also covers the minimum requirements for safe LH2 transfer between ship and shore.

Although the requirements for power/control systems are covered, this document does not include all of the details for the design and fabrication of standard parts and fittings associated with transfer arms. This document is mainly focused on hard pipe type transfer systems; hose type transfer systems are not described in detail in the general description of this document. However, hose type transfer systems can also be considered as reasonable vacuum insulated technology for the design of transfer arms for liquefied hydrogen.


Linux Standard Base (LSB) — Part 1-1: Common definitions

Noyau de base normalisé Linux (LSB) — Partie 1-1: Définitions communes

This document defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.

The LSB specification set is divided into modules, each of which provides fundamental system interfaces, libraries, and runtime environment upon which all conforming applications and libraries using that module depend.

The modules of the Linux Standard Base are:

LSB Core - core components

LSB Desktop - desktop related components

LSB Languages - runtime languages

LSB Imaging - printing and scanning

LSB Trial Use - components that are not yet mandatory

Interfaces described in the LSB Core module specification are supplemented by other LSB module specifications. All other modules depend on the presence of LSB Core.

These specifications are composed of two basic parts: a common part describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part describing the parts of the interface that vary by processor architecture. Together, the common part and the relevant architecture-specific part for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture. Whenever a section of the common part is supplemented by architecture-specific information, the common part includes a reference to the architecture-specific part. Architecture-specific parts of of an LSB module specification may also contain additional information that is not referenced in the common part.

The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.

The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.


Linux Standard Base (LSB) — Part 1-2: Core specification generic part

Noyau de base normalisé Linux (LSB) — Partie 1-2: Partie générique de la spécification du module de base "Core"

This document defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.
These specifications are composed of two basic parts: a common part describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part describing the parts of the interface that vary by processor architecture. Together, the common part and the relevant architecture-specific part for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.
The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.
The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.
This is the common part of the Core module of the Linux Standard Base (LSB), LSB Core - Generic. This module provides the fundamental system interfaces, libraries, and runtime environment upon which all conforming applications and libraries depend.
LSB Core - Generic, the common part, should be used in conjunction with an architecture-specific part. Whenever a section of the common part is supplemented by architecture-specific information, the common part includes a reference to the architecture-specific part. Architecture-specific parts of the LSB Core Specification may also contain additional information that is not referenced in the common part.
Interfaces described in this part of the LSB Core Specification are mandatory except where explicitly listed otherwise. Interfaces described in the LSB Core module are supplemented by other LSB modules. All other modules depend on the presence of LSB Core.


Linux Standard Base (LSB) — Part 1-3: Desktop specification generic part

Noyau de base normalisé Linux (LSB) — Partie 1-3: Partie générique de la spécification du module de bureau "Desktop"

This document defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.

These specifications are composed of two basic parts: a common part describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part describing the parts of the interface that vary by processor architecture. Together, the common part and the relevant architecture-specific part for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.

The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.

The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.

This is the common part of the Desktop module of the Linux Standard Base (LSB). This module provides the fundamental system interfaces, libraries, and runtime environment upon which all conforming applications and libraries depend requiring the LSB Desktop module depend.

The common part of LSB Desktop should be used in conjunction with an architecture-specific part. Whenever a section of the common part is supplemented by architecture-specific information, the common part includes a reference to the architecture-specific part. Architecture-specific parts of LSB Desktop may also contain additional information that is not referenced in the common part.

Interfaces described in this part of LSB Desktop are mandatory except where explicitly listed otherwise. Interfaces described in the LSB Desktop module supplement those described in the LSB Core module. They do not depend on other LSB modules.


Linux Standard Base (LSB) — Part 1-4: Languages specification

Noyau de base normalisé Linux (LSB) — Partie 1-4: Spécification du module de langues "Languages"

The LSB Languages specification defines components for runtime languages which are found on an LSB conforming system.


Linux Standard Base (LSB) — Part 1-5: Imaging specification

Noyau de base normalisé Linux (LSB) — Partie 1-5: Spécification du module d'images "Imaging"

This document defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.
These specifications are composed of two basic parts: a common part describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part describing the parts of the interface that vary by processor architecture. Together, the common part and the relevant architecture-specific part for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.
The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.
The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.
This is the Imaging module of the Linux Standard Base (LSB). This module provides the fundamental system interfaces, libraries, and runtime environment upon which conforming applications and libraries requiring the LSB Imaging module depend.
Interfaces described in LSB Imaging are mandatory except where explicitly listed otherwise. Interfaces described in the LSB Imaging module supplement those described in the LSB Core module. They do not depend on other LSB modules.


Linux Standard Base (LSB) — Part 1-6: Graphics and Gtk3 specification

Noyau de base normalisé Linux (LSB) — Partie 1-6: Spécification graphique et Gtk3

The Trial Use Specification defines components which are not required parts of the LSB Specification.


Linux Standard Base (LSB) — Part 2-2: Core specification for X86-32 architecture

Noyau de base normalisé Linux (LSB) — Partie 2-2: Spécification du module de base "Core" pour l'architecture X86-32

This document defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.
These specifications are composed of two basic parts: a common part describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part describing the parts of the interface that vary by processor architecture. Together, the common part and the relevant architecture-specific part for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.
The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.
The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.
This is the X86 architecture specific part of the Core module of the Linux Standard Base (LSB). This part supplements the common part of the LSB Core module with those interfaces that differ between architectures.
This part should be used in conjunction with LSB Core - Generic, the common part. Whenever a section of the common part is supplemented by architecture-specific information, the common part includes a reference to the architecture-specific part. This part may also contain additional information that is not referenced in the common part.
Interfaces described in this part of the LSB Core Specification are mandatory except where explicitly listed otherwise. Interfaces described in the LSB Core module are supplemented by other LSB modules. All other modules depend on the presence of LSB Core.


Linux Standard Base (LSB) — Part 2-3: Desktop specification for X86-32 architecture

Noyau de base normalisé Linux (LSB) — Partie 2-3: Spécification du module de bureau "Desktop" pour l'architecture X86-32

This document defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.
These specifications are composed of two basic parts: a common part describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part describing the parts of the interface that vary by processor architecture. Together, the common part and the relevant architecture-specific part for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.
The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.
The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.
This is the X86 architecture specific part of the Desktop module of the Linux Standard Base (LSB). This part supplements the common part of the LSB Desktop module with those interfaces that differ between architectures.
This part should be used in conjunction with the common part of LSB Desktop. Whenever a section of the common part is supplemented by architecture-specific information, the common part includes a reference to the architecture-specific part. This part may also contain additional information that is not referenced in the common part.
Interfaces described in this part of LSB Desktop are mandatory except where explicitly listed otherwise. Interfaces described in the LSB Desktop module supplement those described in the LSB Core module. They do not depend on other LSB modules.


Linux Standard Base (LSB) — Part 3-2: Core specification for IA64 (Itanium™) architecture

Noyau de base normalisé Linux (LSB) — Partie 3-2: Spécification du module de base "Core" pour l'architecture IA64 (Itanium™)

This document defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.
These specifications are composed of two basic parts: a common part describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part describing the parts of the interface that vary by processor architecture. Together, the common part and the relevant architecture-specific part for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.
The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.
The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.
This is the Itanium™ architecture specific part of the Core module of the Linux Standard Base (LSB). This part supplements the common part of the LSB Core module with those interfaces that differ between architectures.
This part should be used in conjunction with LSB Core - Generic, the common part. Whenever a section of the common part is supplemented by architecture-specific information, the common part includes a reference to the architecture-specific part. This part may also contain additional information that is not referenced in the common part.
Interfaces described in this part of the LSB Core Specification are mandatory except where explicitly listed otherwise. Interfaces described in the LSB Core module are supplemented by other LSB modules. All other modules depend on the presence of LSB Core.


Linux Standard Base (LSB) — Part 3-3: Desktop specification for IA64 (Itanium TM) architecture

Noyau de base normalisé Linux (LSB) — Partie 3-3: Spécification du module de bureau "Desktop" pour l'architecture IA64 (Itanium™)

This document defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.
These specifications are composed of two basic parts: a common part describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part describing the parts of the interface that vary by processor architecture. Together, the common part and the relevant architecture-specific part for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.
The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.
The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.
This is the Itanium™ architecture specific part of the Desktop module of the Linux Standard Base (LSB). This part supplements the common part of the LSB Desktop module with those interfaces that differ between architectures.
This part should be used in conjunction with the common part of LSB Desktop. Whenever a section of the common part is supplemented by architecture-specific information, the common part includes a reference to the architecture-specific part. This part may also contain additional information that is not referenced in the common part.
Interfaces described in this part of LSB Desktop are mandatory except where explicitly listed otherwise. Interfaces described in the LSB Desktop module supplement those described in the LSB Core module. They do not depend on other LSB modules.


Linux Standard Base (LSB) — Part 4-2: Core specification for AMD64 (X86-64) architecture

Noyau de base normalisé Linux (LSB) — Partie 4-2: Spécification du module de base "Core" pour l'architecture AMD64 (X86-64)

This document defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.
These specifications are composed of two basic parts: a common part describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part describing the parts of the interface that vary by processor architecture. Together, the common part and the relevant architecture-specific part for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.
The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.
The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.
This is the X86-64 architecture specific part of the Core module of the Linux Standard Base (LSB). This part supplements the common part of the LSB Core module with those interfaces that differ between architectures.
This part should be used in conjunction with LSB Core - Generic, the common part. Whenever a section of the common part is supplemented by architecture-specific information, the common part includes a reference to the architecture-specific part. This part may also contain additional information that is not referenced in the common part.
Interfaces described in this part of the LSB Core Specification are mandatory except where explicitly listed otherwise. Interfaces described in the LSB Core module are supplemented by other LSB modules. All other modules depend on the presence of LSB Core.


Linux Standard Base (LSB) — Part 4-3: Desktop specification for AMD64 (X86-64) architecture

Noyau de base normalisé Linux (LSB) — Partie 4-3: Spécification du module de bureau "Desktop" pour l'architecture AMD64 (X86-64)

The Linux Standard Base (LSB) defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.
These specifications are composed of two basic parts: a common part describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part describing the parts of the interface that vary by processor architecture. Together, the common part and the relevant architecture-specific part for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.
The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.
The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.
This is the X86-64 architecture specific part of the Desktop module of the Linux Standard Base (LSB). This part supplements the common part of the LSB Desktop module with those interfaces that differ between architectures.
This part should be used in conjunction with the common part of LSB Desktop. Whenever a section of the common part is supplemented by architecture-specific information, the common part includes a reference to the architecture-specific part. This part may also contain additional information that is not referenced in the common part.
Interfaces described in this part of LSB Desktop are mandatory except where explicitly listed otherwise. Interfaces described in the LSB Desktop module supplement those described in the LSB Core module. They do not depend on other LSB modules.


Linux Standard Base (LSB) — Part 5-2: Core specification for PowerPC 32 architecture

Noyau de base normalisé Linux (LSB) — Partie 5-2: Spécification du module de base "Core" pour l'architecture PowerPC 32

This document defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.

These specifications are composed of two basic parts: a common part describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part describing the parts of the interface that vary by processor architecture. Together, the common part and the relevant architecture-specific part for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.

The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.

The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.

This is the PPC32 architecture specific part of the Core module of the Linux Standard Base (LSB). This part supplements the common part of the LSB Core module with those interfaces that differ between architectures.

This part should be used in conjunction with LSB Core - Generic, the common part. Whenever a section of the common part is supplemented by architecture-specific information, the common part includes a reference to the architecture-specific part. This part may also contain additional information that is not referenced in the common part.

Interfaces described in this part of the LSB Core Specification are mandatory except where explicitly listed otherwise. Interfaces described in the LSB Core module are supplemented by other LSB modules. All other modules depend on the presence of LSB Core.


Linux Standard Base (LSB) — Part 5-3: Desktop specification for PowerPC 32 architecture

Noyau de base normalisé Linux (LSB) — Partie 5-3: Spécification du module de bureau "Desktop" pour l'architecture PowerPC 32

This document defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.

These specifications are composed of two basic parts: a common part describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part describing the parts of the interface that vary by processor architecture. Together, the common part and the relevant architecture-specific part for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.

The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.

The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.

This is the PPC32 architecture specific part of the Desktop module of the Linux Standard Base (LSB). This part supplements the common part of the LSB Desktop module with those interfaces that differ between architectures.

This part should be used in conjunction with the common part of LSB Desktop. Whenever a section of the common part is supplemented by architecture-specific information, the common part includes a reference to the architecture-specific part. This part may also contain additional information that is not referenced in the common part.

Interfaces described in this part of LSB Desktop are mandatory except where explicitly listed otherwise. Interfaces described in the LSB Desktop module supplement those described in the LSB Core module. They do not depend on other LSB modules.


Linux Standard Base (LSB) — Part 6-2: Core specification for PowerPC 64 architecture

Noyau de base normalisé Linux (LSB) — Partie 6-2: Spécification du module de base "Core" pour l'architecture PowerPC 64

This document defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.

These specifications are composed of two basic parts: a common part describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part describing the parts of the interface that vary by processor architecture. Together, the common part and the relevant architecture-specific part for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.

The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.

The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.

This is the PPC64 architecture specific part of the Core module of the Linux Standard Base (LSB). This part supplements the common part of the LSB Core module with those interfaces that differ between architectures.

This part should be used in conjunction with LSB Core - Generic, the common part. Whenever a section of the common part is supplemented by architecture-specific information, the common part includes a reference to the architecture-specific part. This part may also contain additional information that is not referenced in the common part.

Interfaces described in this part of the LSB Core Specification are mandatory except where explicitly listed otherwise. Interfaces described in the LSB Core module are supplemented by other LSB modules. All other modules depend on the presence of LSB Core.


Linux Standard Base (LSB) — Part 6-3: Desktop specification for PowerPC 64 architecture

Noyau de base normalisé Linux (LSB) — Partie 6-3: Spécification du module de bureau "Desktop" pour l'architecture PowerPC 64

This document defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.

These specifications are composed of two basic parts: a common part describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part describing the parts of the interface that vary by processor architecture. Together, the common part and the relevant architecture-specific part for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.

The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.

The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.

This is the PPC64 architecture specific part of the Desktop module of the Linux Standard Base (LSB). This part supplements the common part of the LSB Desktop module with those interfaces that differ between architectures.

This part should be used in conjunction with the common part of LSB Desktop. Whenever a section of the common part is supplemented by architecture-specific information, the common part includes a reference to the architecture-specific part. This part may also contain additional information that is not referenced in the common part.

Interfaces described in this part of LSB Desktop are mandatory except where explicitly listed otherwise. Interfaces described in the LSB Desktop module supplement those described in the LSB Core module. They do not depend on other LSB modules.


Linux Standard Base (LSB) — Part 7-2: Core specification for S390 architecture

Noyau de base normalisé Linux (LSB) — Partie 7-2: Spécification du module de base "Core" pour l'architecture S390

This document defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.

These specifications are composed of two basic parts: a common part describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part describing the parts of the interface that vary by processor architecture. Together, the common part and the relevant architecture-specific part for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.

The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.

The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.

This is the S390 architecture specific part of the Core module of the Linux Standard Base (LSB). This part supplements the common part of the LSB Core module with those interfaces that differ between architectures.

This part should be used in conjunction with LSB Core - Generic, the common part. Whenever a section of the common part is supplemented by architecture-specific information, the common part includes a reference to the architecture-specific part. This part may also contain additional information that is not referenced in the common part.

Interfaces described in this part of the LSB Core Specification are mandatory except where explicitly listed otherwise. Interfaces described in the LSB Core module are supplemented by other LSB modules. All other modules depend on the presence of LSB Core.


Linux Standard Base (LSB) — Part 7-3: Desktop specification for S390 architecture

Noyau de base normalisé Linux (LSB) — Partie 7-3: Spécification du module de bureau "Desktop" pour l'architecture S390

This document defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.

These specifications are composed of two basic parts: a common part describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part describing the parts of the interface that vary by processor architecture. Together, the common part and the relevant architecture-specific part for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.

The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.

The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.

This is the S390 architecture specific part of the Desktop module of the Linux Standard Base (LSB). This part supplements the common part of the LSB Desktop module with those interfaces that differ between architectures.

This part should be used in conjunction with the common part of LSB Desktop. Whenever a section of the common part is supplemented by architecture-specific information, the common part includes a reference to the architecture-specific part. This part may also contain additional information that is not referenced in the common part.

Interfaces described in this part of LSB Desktop are mandatory except where explicitly listed otherwise. Interfaces described in the LSB Desktop module supplement those described in the LSB Core module. They do not depend on other LSB modules.


Linux Standard Base (LSB) — Part 8-2: Core specification for S390X architecture

Noyau de base normalisé Linux (LSB) — Partie 8-2: Spécification du module de base "Core" pour l'architecture S390X

This document defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.

These specifications are composed of two basic parts: a common part describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part describing the parts of the interface that vary by processor architecture. Together, the common part and the relevant architecture-specific part for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.

The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.

The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.

This is the S390X architecture specific part of the Core module of the Linux Standard Base (LSB). This part supplements the common part of the LSB Core module with those interfaces that differ between architectures.

This part should be used in conjunction with LSB Core - Generic, the common part. Whenever a section of the common part is supplemented by architecture-specific information, the common part includes a reference to the architecture-specific part. This part may also contain additional information that is not referenced in the common part.

Interfaces described in this part of the LSB Core Specification are mandatory except where explicitly listed otherwise. Interfaces described in the LSB Core module are supplemented by other LSB modules. All other modules depend on the presence of LSB Core.


Linux Standard Base (LSB) — Part 8-3: Desktop specification for S390X architecture

Noyau de base normalisé Linux (LSB) — Partie 8-3: Spécification du module de bureau "Desktop" pour l'architecture S390X

This document defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.

These specifications are composed of two basic parts: a common part describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part describing the parts of the interface that vary by processor architecture. Together, the common part and the relevant architecture-specific part for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.

The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.

The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.

This is the S390X architecture specific part of the Desktop module of the Linux Standard Base (LSB). This part supplements the common part of the LSB Desktop module with those interfaces that differ between architectures.

This part should be used in conjunction with the common part of LSB Desktop. Whenever a section of the common part is supplemented by architecture-specific information, the common part includes a reference to the architecture-specific part. This part may also contain additional information that is not referenced in the common part.

Interfaces described in this part of LSB Desktop are mandatory except where explicitly listed otherwise. Interfaces described in the LSB Desktop module supplement those described in the LSB Core module. They do not depend on other LSB modules.


Thermal insulation of building elements — In-situ measurement of thermal resistance and thermal transmittance — Part 3: Probe insertion method

Isolation thermique — Éléments de construction — Mesurage in situ de la résistance thermique et du coefficient de transmission thermique — Partie 3: Titre manque


Thermal insulating products for building applications — Determination of length and width

Produits isolants thermiques destinés aux applications du bâtiment — Détermination de la longueur et de la largeur

This document specifies the equipment and procedures for determining the length and width of full‑size products. It is applicable to thermal insulating products.


Ships and marine technology — Pilot ladder winch reels

Navires et technologie maritime — Enrouleurs de winch pour échelles de pilote

This document specifies requirements and characteristics of ships’ pilot ladder winch reels provided with hydraulic, pneumatic, electric, or manual drive. It is applicable to the design and test of pilot ladder winch reels. It does not include requirements for the prime mover used to operate the pilot ladder winch reels.

Pilot ladder winch reels specified in this document are intended to be only used with pilot ladders conforming to ISO 799-1. They are not intended to be used for ‘man lifting’ activities.


Cranes and hoists — Selection of wire ropes, drums and sheaves

Appareils de levage à charge suspendue et treuils — Choix des câbles, tambours et poulies

This document provides a proof of competence and criteria for the selection of steel wire ropes used in cranes as defined in ISO 4306-1.

The influence of the geometry of the rope drive, as well as drum and sheave geometry, are incorporated in the proof of competence.

This document does not apply to fibre ropes.


Thermal insulating products for building applications — Determination of thickness

Produits isolants thermiques destinés aux applications du bâtiment — Détermination de l'épaisseur

This document specifies the equipment and procedures for determining the thickness of full‑size products. It is applicable to thermal insulating products.

This document provides the reference method. Other methods can be used (e.g. for quality control), provided a correlation has been established with this reference method; Annex B gives some examples of such methods.


Thermal insulating products for building applications — Determination of flatness

Produits isolants thermiques destinés aux applications du bâtiment — Détermination de la planéité

This document specifies the equipment and procedures for determining the deviation from flatness for full-size products. It is applicable to thermal insulating products.


Information technology — Common Biometric Exchange Formats Framework — Part 1: Data element specification

Technologies de l'information — Cadre de formats d'échange biométriques communs — Partie 1: Spécification des éléments de données

This document defines:

—     structures and data elements for biometric information records (BIRs);

—     the concept of a domain of use to establish the applicability of a standard or specification that conforms with CBEFF requirements;

—     the concept of a CBEFF patron format, which is a published BIR format specification that complies with CBEFF requirements, specified by a CBEFF patron;

—     the abstract values and associated semantics of a set of CBEFF data elements to be used in the definition of CBEFF patron formats;

This document describes methods to define CBEFF patron formats using CBEFF data elements to specify the structure of BIRs, including the standard biometric headers (SBHs).

This document also provides the means for identification of BDB formats in a BIR, but the standardization and interoperability of BDB formats is not within the scope of this document. This document provides a security block (SB) as a means for BIRs to carry information about the encryption of a BDB in the BIR and about integrity mechanisms applied to the BIR itself. The structure and content of SBs is not within the scope of this document. Further, the specification of encryption mechanisms for BDBs and of integrity mechanisms for BIRs is not within the scope of this document.

This document specifies transformations from one CBEFF patron format to a different CBEFF patron format.

The following are not within the scope of this document:

—     the encoding of the abstract values of CBEFF data elements to be used in the specification of CBEFF patron formats; and

—     protection of the privacy of individuals from inappropriate dissemination and use of biometric data.


Information technology — Object oriented BioAPI — Part 2: Java implementation

Technologies de l'information — Objet orienté BioAPI — Partie 2: Mise en oeuvre Java

This document specifies an interface of a BioAPI Java framework and BioAPI Java BSP, which will mirror the corresponding components, specified in ISO/IEC 30106-1. The semantic equivalent of ISO/IEC 30106-1 is maintained in this document.


Information technology — Object oriented BioAPI — Part 3: C# implementation

Technlogies de l'information — Objet orienté BioAPI — Partie 3: Mise en oeuvre de C#

This document specifies an interface of a BioAPI C# framework and BioAPI C# BSP which mirror the corresponding components specified in ISO/IEC 30106-1. The semantic equivalence of this document will be maintained with ISO/IEC 30106-2 (Java implementation). In spite of the differences in actual parameters passed between functions, the names and interface structure are the same.


Thermal insulating products for building applications — Determination of tensile strength parallel to faces

Produits isolants thermiques destinés aux applications du bâtiment — Détermination de la résistance à la traction parallèlement aux faces

This document specifies the equipment and procedures for determining the tensile strength of a product parallel to its faces. It is applicable to thermal insulating products.

This document can be used to determine whether the product has sufficient strength to withstand stresses during transportation and application.


Thermal insulating products for building applications — Determination of linear dimensions of test specimens

Produits isolants thermiques destinés aux applications du bâtiment — Détermination des dimensions linéaires des éprouvettes

This document specifies the characteristics and choice of measuring equipment and the procedure for determining the linear dimensions of test specimens that are taken from thermal insulating products. The procedures for measuring the dimensions of full-size products are specified in ISO 29465 and ISO 29466.


Thermal insulating products for building applications — Determination of thickness for floating-floor insulating products

Produits isolants thermiques destinés aux applications du bâtiment — Détermination de l'épaisseur des produits d'isolation pour sol flottant

This document specifies the equipment and procedures for determining the thickness of thermal insulating products for impact sound insulation in floating-floor applications.


Plain bearings — Surface modification by press fitting solid lubricants combined with micro dimple processing

Paliers lisses — Modification de la surface par fixation par pression de lubrifiants solides combinée à un traitement par micro-cavités

This document specifies the method of surface modification that improves the friction characteristics of plain bearings, by press fitting a solid lubricant onto the bearing metal surface mechanically in combination with processing a lot of micro dimples on the surface.


Information and documentation — International Standard Content Code (ISCC)

Information et documentation — Code international normalisé de contenu (ISCC)

This document specifies the syntax and structure of the International Standard Content Code (ISCC), as an identification system for digital assets (including encodings of text, images, audio, video or other content across all media sectors). It also describes ISCC metadata and the use of ISCC in conjunction with other schemes, such as DOI, ISAN, ISBN, ISRC, ISSN and ISWC.

An ISCC applies to a specific digital asset and is a data-descriptor deterministically constructed from multiple hash digests using the algorithms and rules in this document. This document does not provide information on registration of ISCCs.


Rolling bearings — Symbols for physical quantities — Amendment 1

Roulements — Symboles relatifs aux grandeurs physiques — Amendement 1


Safety and control devices for gas burners and gas-burning appliances — Particular requirements — Part 6: Thermoelectric flame supervision controls

Dispositifs de commande et de sécurité pour brûleurs à gaz et  appareils à gaz — Exigences particulières — Partie 6: Équipements thermoélectriques de surveillance de flamme

This document specifies safety, constructional, and performance and testing requirements for thermoelectric flame supervision controls, energized by a thermocouple, intended for use with gas burners and gas-burning appliances, hereafter referred to as “controls”.

This document applies to thermoelectric flame supervision controls for gas burners and gas-burning appliances of nominal connection size up to, and including DN 50, that can be used and tested independently of these appliances.

These thermoelectric flame supervision controls are suitable for fuel gases, such as natural gas, manufactured gas or liquefied petroleum gas (LPG) at inlet pressures up to and including 50 kPa. It is not applicable to corrosive and waste gases.

This document covers type testing only.

This document is not applicable to:

a) the thermocouple; and

b) controls which use auxiliary energy (e.g. electrical energy supplied externally).


Information technology — Office equipment — Method for the determination of ink cartridge yield for colour inkjet printers and multi-function devices that contain printer components

Technologies de l'information — Équipements de bureau — Méthode pour la détermination du rendement de cartouches d'encre pour les imprimantes couleur à jet d'encre et pour les dispositifs multifonctionnels qui contiennent des composants d'imprimantes

The scope of this document is limited to the evaluation of ink cartridge page yield for ink-containing cartridges (i.e. integrated ink cartridges and ink cartridges without integrated printheads) for colour inkjet print systems. This document can also be applied to the printer component of any multifunctional device that has a digital input printing path, including multi-function devices that contain inkjet printer components. Both liquid and solid ink products can be tested using this document.

This document is only intended for the measurement of ink cartridge page yield when printing on plain paper. No other claims can be made from this testing regarding quality, reliability, etc.

This document can be used to measure the yield of any cartridge that is used in a significant amount during the printing of the test page suite defined in ISO/IEC 24712.

This document is not for use with printers whose minimum printable size is equal to or greater than A3 or for printers designed or configured to print photos (for example, maximum printable size less than A4 or a printer configuration intended for photo-only printing). In addition, it only applies to drop-on-demand printing systems.

NOTE       Integrated ink cartridges is a cartridge that includes at least: an ink containment part, an ink deposition mechanism and an ink transport part (see ISO/IEC 29142-1).


Ergonomics — Accessible design — Doors and handles of consumer products

Ergonomie — Conception accessible — Portes et poignées des produits de consommation courante


Petroleum and natural gas industries — Corrosion resistant alloy clad bends and fittings for pipeline transportation system — Part 1: Clad bends

Industries du pétrole et du gaz naturel — Coudes et raccords recouverts d'alliage résistant à la corrosion pour système de transport par conduites — Partie 1: Coudes recouverts

This document specifies the technical delivery conditions regarding design, geometric dimensions, materials, manufacturing procedures, inspection methods, non-destructive testing (NDT), marking, package and storage for corrosion resistant alloy (CRA) clad bends for use in pipeline transportation systems for the petroleum and natural gas industries.

This document is applicable to CRA clad bends for use in transportation or process pipelines transporting corrosive media-containing single-phase or multi-phase fluid such as oil, gas and water for the petroleum and natural gas industries. It can also be used as reference in other fields.

Two technical delivery conditions classes for clad bends are designated. Class B provides a standard quality level for clad bends and Class S provides technical requirements for sour-service conditions. It is the responsibility of the purchaser to specify the appropriated class, based upon the intended use and design requirements.


Petroleum and natural gas industries — Corrosion resistant alloy clad bends and fittings for pipeline transportation system — Part 2: Clad fittings

Industries du pétrole et du gaz naturel — Coudes et raccords recouverts d'alliage résistant à la corrosion pour système de transport par conduites — Partie 2: Raccords recouverts

This document specifies the technical delivery conditions regarding design, geometric dimensions, materials, manufacturing procedures, inspection methods, non-destructive testing, marking, package and storage for factory-made, seamless and welded, corrosion resistant alloy (CRA) clad fittings for use in pipeline transportation systems for the petroleum and natural gas industries as defined in ISO 13623.

This document is applicable to CRA clad fittings for use in transportation or process pipelines transporting corrosive media-containing single-phase or multi-phase fluid such as oil, gas and water for the petroleum and natural gas industries. It can also be used as reference in other fields.

The clad fittings specified in this document include clad elbows, clad reducers, clad tees and clad caps.

Two technical delivery conditions classes for clad fittings are designated. Class B provides a standard quality level for clad fittings and Class S provides technical requirements for sour-service conditions.

Fabricated laterals, fabricated lap joint stub ends and other fittings employing circumferential or intersection welds are considered as pipe fabrication and are outside the scope of this document.


Petroleum products — Determination of bromine number of distillates and aliphatic olefins — Electrometric method — Amendment 1

Produits pétroliers — Détermination de l'indice de brome des distillats et des oléfines aliphatiques — Méthode électrométrique — Amendement 1