35 - INFORMATION TECHNOLOGY
ICS 35 Details
INFORMATION TECHNOLOGY
INFORMATIONSTECHNIK. BUROTECHNIK
TECHNOLOGIES DE L'INFORMATION. MACHINES DE BUREAU
INFORMACIJSKA TEHNOLOGIJA
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 35 - INFORMATION TECHNOLOGY
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
IEC 62541-100:2025 defines the information model associated with Devices. This document describes three models which build upon each other as follows:
• The (base) Device Model is intended to provide a unified view of devices and their hardware and software parts irrespective of the underlying device protocols.
• The Device Communication Model adds Network and Connection information elements so that communication topologies can be created.
• The Device Integration Host Model finally adds additional elements and rules required for host systems to manage integration for a complete system. It enables reflecting the topology of the automation system with the devices as well as the connecting communication networks.
This document also defines AddIns that can be used for the models in this document but also for models in other information models. They are:
• Locking model – a generic AddIn to control concurrent access,
• Software update model – an AddIn to manage software in a Device.
This second edition cancels and replaces the first edition published in 2015. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a a ComponentType that can be used to model any HW or SW element of a device has been defined and a SoftwareType has been added as subtype of ComponentType;
b the new OPC UA interface concept and defined interfaces for Nameplate, DeviceHealth, and SupportInfo has been added.
c) a new model for Software Update (Firmware Update) has been added;
d) a new entry point for documents where each document is represented by a FileType instance has been specified;
e) a model that provides information about the lifetime, related limits and semantic of the lifetime of things like tools, material or machines has been added.
- Standard152 pagesEnglish languagesale 15% off
- Standard158 pagesFrench languagesale 15% off
- Standard310 pagesEnglish and French languagesale 15% off
IEC 62541-10:2025 is available as IEC 62541-10:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-10:2025 defines the Information Model associated with Programs in OPC Unified Architecture (OPC UA). This includes the description of the NodeClasses, standard Properties, Methods and Events and associated behaviour and information for Programs. The complete AddressSpace model including all NodeClasses and Attributes is specified in IEC 62541-3. The Services such as those used to invoke the Methods used to manage Programs are specified in IEC 62541-4. An example for a DomainDownload Program is defined in Annex A. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
- StateMachine table format has been aligned.
- Standard42 pagesEnglish languagesale 15% off
- Standard45 pagesFrench languagesale 15% off
- Standard87 pagesEnglish and French languagesale 15% off
IEC 62541-7: 2025 specifies value and structure of Profiles in the OPC Unified Architecture.
OPC UA Profiles are used to segregate features with regard to testing of OPC UA products and the nature of the testing. The scope of this document includes defining functionality that can only be tested. The definition of actual TestCases is not within the scope of this document, but the general categories of TestCases are covered by this document.
Most OPC UA applications will conform to several, but not all of the Profiles.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Profiles and ConformanceUnits are not part of this document, but are solely managed in a public database as described in Clause 1.
- Standard160 pagesEnglish languagesale 15% off
- Standard173 pagesFrench languagesale 15% off
- Standard333 pagesEnglish and French languagesale 15% off
IEC 62541-13:2025 is available as IEC 62541-13:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-13:2025 defines the information model associated with Aggregates. Programmatically produced aggregate examples are listed in Annex A. This third edition cancels and replaces the second edition published in 2020. This edition constitutes a technical revision.
This edition includes the following technical changes with respect to the previous edition:
a) Multiple fixes for the computation of aggregates
• The Raw status bit is always set for non-bad StatusCodes for the Start and End aggregates.
• Entries in the Interpolative examples Tables A2.2 Historian1, Historian2, and Historian3 have been changed from Good to Good, Raw status codes when the timestamp matches with the timestamp of the data source.
• Missing tables have been added for DurationInStateZero and DurationInStateNonZero.
• The value of zero has been removed for results with a StatusCode of bad.
• Data Type was listed as "Status Code" when it is "Double" for both Standard Deviation and both Variance Aggregates.
• Rounding Error in TimeAverage and TimeAverage2 have been corrected.
• The status codes have been corrected for the last two intervals and the value has been corrected in the last interval.
• The wording has been changed to be more consistent with the certification testing tool.
• UsedSlopedExtrapolation set to true for Historian2 and all examples locations needed new values or status' are modified.
• Values affected by percent good and percent bad have been updated.
• PercentGood/PercentBad are now accounted for in the calculation.
• TimeAverage uses SlopedInterpolation but the Time aggregate is incorrectly allowed to used Stepped Interpolation.
• Partial bit is now correctly calculated.
• Unclear sentence was removed.
• Examples have been moved to a CSV.
• The value and status code for Historian 3 have been updated.
• TimeAverage2 Historian1 now takes uncertain regions into account when calculating StatusCodes.
• TimeAverage2 Historian2 now takes uncertain regions into account when calculating StatusCodes.
• Total2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• Total2 Historian2 now takes uncertain regions into account when calculating StatusCodes
• Maximum2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• MaximumActualTime2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• Minimum2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• MinimumActualTime2 Historian1 now has the StatusCodes calculated while using the TreatUncertainAsBad flag.
• Range2 Historian1 now looks at TreatUncertainAsBad in the calculation of the StatusCodes.
• Clarifications have been made to the text defining how PercentGood/PercentBad are used. The table values and StatusCodes of the TimeAverage2 and Total2 aggregates have been corrected.
- Standard64 pagesEnglish languagesale 15% off
- Standard64 pagesFrench languagesale 15% off
- Standard128 pagesEnglish and French languagesale 15% off
IEC 62541-4:2025 is available as IEC 62541-4:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-4:2025 defines the OPC Unified Architecture (OPC UA) Services. The Services defined are the collection of abstract Remote Procedure Calls (RPC) that are implemented by OPC UA Servers and called by OPC UA Clients. All interactions between OPC UA Clients and Servers occur via these Services. The defined Services are considered abstract because no particular RPC mechanism for implementation is defined in this document. IEC 62541‑6 specifies one or more concrete mappings supported for implementation. For example, one mapping in IEC 62541‑6 is to UA-TCP UA-SC UA-Binary. In that case the Services described in this document appear as OPC UA Binary encoded payload, secured with OPC UA Secure Conversation and transported via OPC UA TCP. Not all OPC UA Servers implement all of the defined Services. IEC 62541‑7 defines the Profiles that dictate which Services must be implemented in order to be compliant with a particular Profile. A BNF (Backus-Naur form) for browse path names is described in Annex A. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of new definitions to Method Call Service to allow optional Method arguments;
b)addition of reference to SystemStatusChangeEventType for event monitored item error scenarios;
c) enhancement of the general description of how determining if a Certificate is trusted;
d) addition of support for ECC;
e) addition of revisedAggregateConfiguration to AggregateFilterResult structure;
f) addition of INVALID to the BrowseDirection enumeration data type;
g) addition of INVALID to the TimestampsToReturn enumeration data type;
h) addition of definitions that make sure the subscription functionality works if retransmission queues are optional;
i) addition of client checks has been added to be symmetric to the Server Certificate check has been added;
j) clarification that ‘local’ top level domain is not appended by server into certificate and not checked by client when returned from LDS-ME;
k) addition of a definition for expiration behaviour of IssuedIdentityTokens;
l) addition of status code Good_PasswordChangeRequired to ActivateSession;
m) restriction of AdditionalInfo to servers in debug mode;
n) addition of new status code Bad_ServerTooBusy;
o) addition of definition for cases where server certificate must be contained in GetEndpoints response.
- Standard245 pagesEnglish languagesale 15% off
- Standard257 pagesFrench languagesale 15% off
- Standard502 pagesEnglish and French languagesale 15% off
This document describes how product catalogue data for building services products is exchanged by means of ISO 16739-1 (Industry Foundation Classes, IFC) and EN 17549-2 from manufacturers to designers of building services systems.
This document specifies how the product catalogue structures and content are set up using the definitions stored in a data dictionary.
In scope of this document are:
— processes for the provision and exchange of product catalogues;
— rules for the geometrical representation of products;
— representation of products, product classes, ports, in/outlets, components and accessories by using IFC;
— representation of properties in IFC and the use of IFC constraints for the representation of product variants;
— representation of parametric geometry and the generation of IFC geometries for selected variants;
— calculation of article number.
The resulting product catalogue can be used by designers to select the desired products and integrate them into their model of the building services system.
The expected audience of this document are software providers for the built environment sector and professionals working in the sector who create product catalogues or use product catalogues by means of software tools.
Not in scope of this document is the representation of properties in data dictionaries. The use of data dictionaries is described in ISO 16757-4.
- Standard98 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies requirements for data dictionaries that are used by product catalogues for building services to provide the semantics of their definitions and data modelling. For this purpose, it defines an overall model that contains:
— subject kinds that allow to distinguish:
— product subjects representing products in product catalogues;
— catalogue subjects comprising meta data of product catalogues;
— various kinds of blocks that collect properties of complex product features, including ports and in/outlets;
— relationship types that allow to distinguish between different kinds of relationships like isSubtypeOf, hasPart, or hasBlock;
— property kinds to distinguish between:
— static properties describing products by providing property values in product catalogues;
— dynamic properties that describe the behaviour of products;
— external properties that represent external conditions that influence the behaviour of the product by influencing the values of dynamic properties.
This document also describes a mapping of the overall model to the data dictionary model of ISO 12006-3 by introducing a dictionary meta level.
Finally, to overcome deficiencies of the standards underlying ISO 16757-5 in capturing all aspects of product catalogues, this document provides some rules and recommendations for required data dictionary elements.
This document does not describe how product catalogues have to be organized, and it does not describe any formats for the exchange of product catalogues. Product catalogues are described in ISO 16757-5.
- Standard34 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies systems and methods for the inspection and testing of installed optical fibre cabling designed in accordance with premises cabling standards including the EN 50173 series. The test methods refer to existing standards-based procedures where they exist.
- Draft86 pagesEnglish languagesale 10% offe-Library read for1 day
This document establishes a framework for age assurance systems and describes their core characteristics, including privacy and security, for enabling age-related eligibility decisions.
- Standard29 pagesEnglish languagesale 15% off
This document showcases existing practices to monitor supply chains as implemented in the healthcare supply chains, by making use of medicines verification or authentication systems, or both, traceability tools, safe communication technology solutions, and more. This document also discusses the potential benefits of expanding the identification of medicinal products (IDMP) to provide global identifiers for medicinal products, ingredients and batches. It also addresses potential pathways to a global registration system.
- Technical report13 pagesEnglish languagesale 15% off
This document provides a mapping between the ISO/IEC 11179-34 metamodel for computable data registration and the IEEE 2791 standard for bioinformatics analyses generated by high-throughput sequencing (HTS), to facilitate the production of IEEE 2791 objects from instances of ISO/IEC 11179-34 metamodel and the registration of IEEE 2791 objects as computable data within an MDR conforming to ISO/IEC 11179-34. This document is applicable to those who are submitting data to organizations that require metadata submissions in IEEE 2791 compliant format, as well as those aiming to register IEEE 2791 objects into an MDR that conforms to ISO/IEC 11179-34.
- Standard50 pagesEnglish languagesale 15% off
This document gives guidance relating to successful, secure and usable implementation of biometric enrolment processes, while indicating risk factors that organizations which use biometric technologies can address during procurement, design, deployment and operation. Much of this document is generic to many types of applications, e.g. from national scale commercial and government applications, to closed systems for in-house operations, and to consumer applications. However, the intended application and its purpose often have influence on the necessary enrolment data quality and are taken into account when specifying an enrolment system and process. This document specifies the differences in operation relating to specific types of application, e.g. where self-enrolment is more appropriate than attended enrolment. This document focuses on mandatory, attended enrolment at fixed locations. It ultimately consolidates information relating to better practices for the implementation of biometric enrolment capability in various business contexts including considerations of process, function (system), and technology, as well as legal/privacy and policy aspects. This document provides guidance on collection and storage of biometric enrolment data and the impact on dependent processes of verification and identification. This document does not include material specific to forensic and law enforcement applications.
- Technical specification48 pagesEnglish languagesale 15% off
- Standard2 pagesEnglish languagesale 15% off
This document specifies a methodology for describing and managing interactions and a format for digital communication between actors in any use case associated with the management of an asset during all life cycle stages. It provides: — a methodology that describes an interaction framework for a use case; — an appropriate way to map responsibilities and interactions that provides a process context for information flow; — a format in which the interaction framework is specified and executed. This document is intended to promote secure, verifiable, traceable and high-quality digital IDM communication between actors during all phases of the life cycle of assets, facilitate interoperability between software applications used, and to provide a basis for data- and process-driven information exchange and traceability of communication.
- Standard82 pagesEnglish languagesale 15% off
- Standard85 pagesFrench languagesale 15% off
The purpose of this deliverable is to specify and describe the reference architecture applied as the basis for the development of Business Interoperability Interface specifications in the eProcurement domain by the TC 440 technical committee.
- Draft37 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the requirements of parameters for the physical and the link layer for systems using radio to remotely read meters. The primary focus is to use the Short Range Device (SRD) unlicensed bands. This document encompasses systems for walk-by, drive-by and fixed installations. As a broad definition, this document can be applied to various Application Layers.
- Draft104 pagesEnglish languagesale 10% offe-Library read for1 day
This document describes the core principles for supporting the development, implementation and ongoing maintenance of IDMP identifiers and terminologies. This document provides considerations for the evaluation and/or design when considering current or future operations and service level agreements for systems and terminology support services in conformity with IDMP.
- Technical report15 pagesEnglish languagesale 15% off
This document provides information security controls for the energy utility industry, based on ISO/IEC 27002:2022, for controlling and monitoring the production or generation, transmission, storage and distribution of electric power, gas, oil and heat, and for the control of associated supporting processes.
- Draft47 pagesEnglish languagesale 10% offe-Library read for1 day
The present document specifies interception of Internet Protocol (IP) Multimedia (MM) Services based on the Session Initiation Protocol (SIP) and Realtime Transport Protocol (RTP) and Message Session Relay Protocol (MSRP) and IP MM services as described by the Recommendations ITU-T H.323 [6] and H.248-1 [i.3]. The present document is consistent with the definition of the Handover Interface, as described in ETSI TS 102 232-1 [2]. The present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 [9] and ETSI TS 101 671 [1].
- Standard30 pagesEnglish languagesale 15% off
- Technical specification30 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies requirements and provides recommendations for the selection, usage and dependencies of visual user-interface elements and their application. This document is concerned with visual software components of interactive systems to make human-system interaction usable. This document is applicable regardless of a fixed, portable or mobile interactive system, or cross-device use. It does not provide detailed coverage of the methods and techniques required for design of visual user-interface elements. This document does not address implementation (e.g. graphical design of elements) and interaction details for specific input methods or technologies. It does not cover decorative user-interface elements that are intended to address solely aesthetic (hedonic) qualities in the user interface e.g. background images.
- Standard67 pagesEnglish languagesale 15% off
- Standard71 pagesFrench languagesale 15% off
This document specifies a framework for representing data recorded in terminological data collections (TDCs). This framework includes a metamodel and methods for describing specific terminological markup languages (TMLs), exemplified in this document in eXtensible Markup Language (XML). The mechanisms for implementing constraints in a TML are defined, but not the specific constraints for individual TMLs. This document is designed to support the development and use of computer applications for terminological data and the exchange of such data between different applications. This document also defines the conditions that allow the data expressed in one TML to be mapped onto another TML.
- Standard18 pagesEnglish languagesale 15% off
- Draft21 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies a common, interoperable set of extensible properties for the description of resource content, functionality, user needs and preferences, to enable network-supported individualization of resources, services and environments to match the unique needs and preferences of the individual. This document includes all relevant mechanisms for the publication of terminology for such descriptions, including publicly available registries of properties and related metadata resources such as application profiles. This document takes an inclusive approach to individualization, since any user can experience a mismatch of their individual needs and preferences and the content or services delivered; it is not restricted to descriptions related to stereotypical notions of disability. It provides properties for describing access attributes of resources. It does not ascribe medical conditions to such properties (e.g. ‘non-visual’ as a property value does not infer visual disability, as when the user’s eyes are busy watching the road). This document defines a set of core Access for All (AfA) properties that can be used in a digital resource description (DRD), an AfA record, and equally in a stored personal needs and preferences profile, also an AfA record. It also includes how to extend or add a property or its value using an application profile as defined by ISO/IEC 19788-1.
- Standard31 pagesEnglish languagesale 15% off
This document defines markers of harm in online gambling. It is a minimum set of markers to analyse. The individual indicators can be analysed over additional time spans as well as in excess of those re-quired, and other markers can be added to the analysis as well.
In the event that the collection or analysis of data for a limited set of markers is prohibited within a spe-cific jurisdiction (for example, where legislation prevents it), operators can still be compliant with the standard provided that only these markers are omitted, and only for players who fall under that specific jurisdiction.
This document does not provide guidelines regarding the interventions to be employed when addressing individuals with gambling issues, nor does it establish predefined thresholds for intervention.
- Standard19 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies a taxonomy of information elements to assist AI stakeholders with identifying and addressing the needs for transparency of AI systems. The document describes the semantics of the information elements and their relevance to the various objectives of different stakeholders.
This document is applicable to any kind of organization and application involving an AI system.
- Standard54 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies requirements and gives guidelines for designing accessible software for people with the widest range of physical, sensory and cognitive abilities, including those who are temporarily or situationally disabled, and the elderly. It addresses software considerations for accessibility that complement general design for usability as addressed by parts of the ISO 9241 series, especially ISO 9241-11 and ISO 9241-210. This document is applicable to the accessibility of interactive systems. It addresses a wide range of software (e.g. home, mobile, office, web, learning support and library systems). It promotes the increased usability of systems for a wider range of users in the widest range of contexts of use. This document does not apply to the behaviour of, or requirements for, assistive technologies (including assistive software), but it does address the use of assistive technologies as an integrated component of interactive systems. It is intended for use by those responsible for the specification, design, development, evaluation and procurement of software platforms and software applications.
- Standard103 pagesEnglish languagesale 15% off
- Standard114 pagesFrench languagesale 15% off
This document provides a specification for QR codes for mobile (instant) credit transfers (MCTs) whereby the payer uses a mobile device to initiate the payment transaction. The QR code is used to exchange data between the payer and the payee to enable the initiation of the (instant) credit transfer by the payer.
This document is applicable to both cases where the QR code is presented by the payee or by the payer.
This document excludes the following from its scope:
— The details of technical requirements and the supporting infrastructure to achieve interoperability amongst mobile (instant) credit transfer (MCT) service providers;
— The detailed implementation specification of the payload included in the QR code.
- Draft36 pagesEnglish languagesale 10% offe-Library read for1 day
This document establishes an organized set of concepts and relationships to understand the competency requirements for information security conformance-testing and evaluation specialists, thereby establishing a basis for shared understanding of the concepts and principles central to the ISO/IEC 19896 series across its user communities.
- Draft16 pagesEnglish languagesale 10% offe-Library read for1 day
This document prescribes:
— how to document a use case with an associated business context and exchange requirements;
— a methodology to identify and specify the information exchanges required at identified times during the life cycle of assets.
This document presents the information delivery manual (IDM) in natural language terms to facilitate interoperability between software applications used during all phases of the life cycle of assets (both buildings and infrastructure). It promotes digital collaboration between actors within the identified business context and provides a basis for accurate, reliable, repeatable and high-quality information exchange.
The information delivery manual (IDM) methodology specified in this document can be applied to any information management trigger event to identify the details of the information required to be exchanged.
- Draft41 pagesEnglish languagesale 10% offe-Library read for1 day
This document contains recommendations on how to integrate the principle of ‘data protection and privacy by design’
during the entire lifecycle of biometric access-control products and services, in order to achieve ‘data protection and
privacy by default’.
Biometric facial recognition for access control is covered by this document. Biometric facial recognition for surveillance is
covered by CEN/CLC/JTC 13 TR ‘Video surveillance’.
This document specifies recommendations for the management of data protection and privacy by design in biometricaccess-
control products and services. This document extends ISO/IEC 27552. This document applies to aspects of data
protection and privacy by design. This document is not applicable to non-biometric aspects of access control, or to aspects
not relating to data protection or privacy.
- Draft12 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines universal and specialized characteristics of health terminological resources that make them fit for the purposes required of various applications. It covers only terminological resources that are primarily designed to be used for clinical concept representation or to those parts of other terminological resources designed to be used for clinical concept representation.
This document helps users to assess whether a terminology has the characteristics or provides the functions that will support their specified requirements. In order to do that, this document focuses on defining characteristics and functions of terminological resources in healthcare that can be used to identify different types of terminological resources for categorization purposes.
NOTE 1 Categorization of healthcare terminological systems according to the name of the system might not be helpful and has caused confusion in the past.
The following aspects are not covered in this document:
— evaluations of terminological resources;
— health service requirements for terminological resources and evaluation criteria based on the characteristics and functions;
— the nature and quality of mappings between different terminologies;
NOTE 2 It is unlikely that a single terminology will meet all the terminology requirements of a healthcare organization: some terminology providers produce mappings to administrative or classification systems such as the International Classification of Diseases (ICD). The presence of such maps would be a consideration in the evaluation of the terminology.
— the nature and quality of mappings between different versions of the same terminology;
NOTE 3 To support data migration and historical retrieval, terminology providers can provide maps between versions of their terminology. The presence of such maps would be a consideration in the evaluation of the terminology.
— terminology server requirements and techniques and tools for terminology developers;
— characteristics for computational biology terminology.
- Draft29 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard70 pagesEnglish languagesale 15% off
This document provides a framework that applies to all resources and specifies how to describe resources. It includes rules governing the way in which descriptions are made.
This document provides principles, rules and structures for specifying the description of any type of resource; it identifies and establishes attributes for specifying properties, resources classes, vocabularies and application profiles and the rules governing their use. The key principles set out in this document are framed in a user-centric context and aim to meet the requirements of multilingual and cultural adaptability from a global perspective.
This document can be used for the specification of metadata describing any type of resource (not only learning resources). This document is information-technology-neutral and defines a set of common approaches.
This document specifies generic properties, generic resource classes and predefined rule sets for content value rules. These generic elements are proposed in such a way that they can be widely reused, thereby promoting interoperability.
This document is applicable to the development of:
— application profiles based on the ISO/IEC 19788 series but not part of it or any other document based on it,
— standards consisting of the description of resources (in a broad sense), whether they belong to the domain of education or to any other domain.
- Standard90 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard72 pagesEnglish languagesale 15% off
ISO/IEC 11801-1:2017(E) This document specifies a multi-vendor cabling system which may be implemented with material from single or multiple sources. This part of ISO/IEC 11801 defines requirements that are common to the other parts of the ISO/IEC 11801 series. Cabling specified by this document supports a wide range of services including voice, data, and vido that may also incorporate the supply of power.
The contents of the corrigendum of April 2018 have been included in this copy.
- Standard149 pagesEnglish languagesale 15% off
- Standard425 pagesEnglish languagesale 15% off
This document specifies test methods for testing conformity of a mobile driving licence (mDL) or an mDL reader to ISO/IEC 18013-5. This document specifies test methods for: — mDL on its interface to an mDL reader; — mDL reader on its interface to an mDL; — mDL reader on its (optional) interface to an issuing authority infrastructure. Test cases for an issuing authority infrastructure on its interface to an mDL reader are not included in this document. Test cases for the use of OpenID Connect (OIDC) by an mDL reader on its interface to an issuing authority infrastructure are not included in this document. This document only provides test cases for the use of WebAPI on this interface. This document only addresses the functional behaviour of an implementation under test (IUT) on its interface(s) in scope. It does not address: — the internal implementation of an IUT, such as a secure area in an mDL; — any functional requirements to an IUT not specified in ISO/IEC 18013-5, for example, requirements of a particular issuing authority; — non-functional aspects of the IUT, nor IUT interfaces not listed above, such as the interface from an issuing authority infrastructure to an mDL, used to provision mDL data.
- Technical specification58 pagesEnglish languagesale 15% off
This document defines the conceptual framework and mechanisms for mapping information elements from building information modelling (BIM) to geographic information systems (GIS) to access the required information based on specific user requirements. The conceptual framework for mapping BIM information to GIS is defined with the following three mapping mechanisms: — BIM to GIS perspective definition (B2G PD); — BIM to GIS element mapping (B2G EM); — BIM to GIS level of detail (LOD) mapping (B2G LM). This document does not describe physical schema integration or mapping between BIM and GIS models because the physical schema integration or mapping between two heterogeneous models is very complex and can cause a variety of ambiguity problems (see REF Annex_D \r \h Annex D 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000000800000041006E006E00650078005F0044000000 ). Developing a unified information model between BIM and GIS is a desirable goal, but it is out of the scope of this document. This document is applicable to the following concepts: — definition for BIM to GIS conceptual mapping requirement description; — definition of BIM to GIS conceptual mapping framework and component; — definition of mapping for export from one schema into another. This document does not apply to the following concepts: — definition of any particular mapping application requirement and mechanism; — bi-directional mapping method between BIM and GIS; — definition of physical schema mapping between BIM and GIS; — definition of coordinate system mapping between BIM and GIS; — definition of relationship mapping between BIM and GIS; — implementation of the application schema. NOTE For cases involving requirements related to geo-referencing for providing the position and orientation of the BIM model based on GIS, other standards exist such as REF ISO_19111 \r \h ISO 19111 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000000A000000490053004F005F00310039003100310031000000 and the Information Delivery Manual (IDM) from buildingSMART on Geo-referencing BIM.
- Technical specification24 pagesEnglish languagesale 15% off
This document defines universal and specialized characteristics of health terminological resources that make them fit for the purposes required of various applications. It covers only terminological resources that are primarily designed to be used for clinical concept representation or to those parts of other terminological resources designed to be used for clinical concept representation. This document helps users to assess whether a terminology has the characteristics or provides the functions that will support their specified requirements. In order to do that, this document focuses on defining characteristics and functions of terminological resources in healthcare that can be used to identify different types of terminological resources for categorization purposes. NOTE 1 Categorization of healthcare terminological systems according to the name of the system might not be helpful and has caused confusion in the past. The following aspects are not covered in this document: — evaluations of terminological resources; — health service requirements for terminological resources and evaluation criteria based on the characteristics and functions; — the nature and quality of mappings between different terminologies; NOTE 2 It is unlikely that a single terminology will meet all the terminology requirements of a healthcare organization: some terminology providers produce mappings to administrative or classification systems such as the International Classification of Diseases (ICD). The presence of such maps would be a consideration in the evaluation of the terminology. — the nature and quality of mappings between different versions of the same terminology; NOTE 3 To support data migration and historical retrieval, terminology providers can provide maps between versions of their terminology. The presence of such maps would be a consideration in the evaluation of the terminology. — terminology server requirements and techniques and tools for terminology developers; — characteristics for computational biology terminology.
- Standard23 pagesEnglish languagesale 15% off
- Standard25 pagesFrench languagesale 15% off
This document defines markers of harm in online gambling. It is a minimum set of markers to analyse. The individual indicators can be analysed over additional time spans as well as in excess of those re-quired, and other markers can be added to the analysis as well.
In the event that the collection or analysis of data for a limited set of markers is prohibited within a spe-cific jurisdiction (for example, where legislation prevents it), operators can still be compliant with the standard provided that only these markers are omitted, and only for players who fall under that specific jurisdiction.
This document does not provide guidelines regarding the interventions to be employed when addressing individuals with gambling issues, nor does it establish predefined thresholds for intervention.
- Standard19 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides the specialized requirements for individuals to demonstrate competence in performing IT product security evaluations and reviews according to the ISO/IEC 15408 series and ISO/IEC 18045.
NOTE It is possible that evaluators and testers belong to bodies operating under ISO/IEC 17025 and reviewers belong to bodies operating under ISO/IEC 17065.
- Draft49 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the categorial structure within the subject field of acupuncture by defining a set of domain constraints of sanctioned characteristics, each composed of a semantic link and an applicable characterizing category, in order to represent the concept of acupuncture point.
- Standard10 pagesEnglish languagesale 15% off
This document prescribes: — how to document a use case with an associated business context and exchange requirements; — a methodology to identify and specify the information exchanges required at identified times during the life cycle of assets. This document presents the information delivery manual (IDM) in natural language terms to facilitate interoperability between software applications used during all phases of the life cycle of assets (both buildings and infrastructure). It promotes digital collaboration between actors within the identified business context and provides a basis for accurate, reliable, repeatable and high-quality information exchange. The information delivery manual (IDM) methodology specified in this document can be applied to any information management trigger event to identify the details of the information required to be exchanged.
- Standard32 pagesEnglish languagesale 15% off
- Standard34 pagesFrench languagesale 15% off
The present document is based on requirements from ETSI TS 102 656 [i.2].
The present document contains handover requirements and a handover specification for the data that is identified in national legislations on Retained Data. The present document considers both the requesting of retained data and the delivery of the results. The present document defines an electronic interface. An informative annex describes how this interface may be adapted for manual techniques. Apart from in annex I, the present document does not consider manual techniques.
- Standard104 pagesEnglish languagesale 15% off
- Technical specification104 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides a list of recommended ISO cryptographic algorithms for use within applicable ISO TC 68, Financial services, standards. It also provides strategic guidance on key lengths and associated parameters and usage dates. This document focuses on core algorithms, key lengths and frequently used mechanisms. The included algorithms are considered to be fit for purpose for financial service use. For additional algorithms, see the body of standards produced by ISO/IEC JTC 1 SC 27, Information security, cybersecurity and privacy protection. For standards on key management, see ISO 11568. The categories of algorithms covered are: a) block ciphers and modes of operation; b) stream ciphers; c) message authentication codes (MACs); d) authenticated encryption algorithms; e) format preserving encryption; f) hash functions; g) asymmetric algorithms: 1) digital signature schemes giving message recovery; 2) digital signatures with appendix; 3) asymmetric ciphers. h) authentication mechanisms; i) key derivation, establishment and agreement mechanisms; j) key transport mechanisms: 1) key wrapping. This document does not define any cryptographic algorithms. However, the standards to which this document refers contain necessary implementation information as well as more detailed guidance regarding choice of security parameters, security analysis and other implementation considerations.
- Technical specification36 pagesEnglish languagesale 15% off
Within the general scope described in ISO/IEC 9995-1, this document specifies symbols and methods to distinguish graphic characters which share the same glyph or are represented by similar glyphs on keyboards (including virtual keyboards) and in documentation. Each of these symbols is intended to be considered as universal and non-language related equivalent of names for the function they represent.
- Standard11 pagesEnglish languagesale 15% off
This standard provides a comprehensive set of procedures for verifying the correct implementation of each capability claimed on a BACnet PICS including:
(a) support of each claimed BACnet service, either as an initiator, executor, or both,
(b) support of each claimed BACnet object-type, including both required properties and each claimed optional property,
(c) support of the BACnet network layer protocol,
(d) support of each claimed data link option, and
(e) support of all claimed special functionality.
- Standard990 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62386-351:2025 is applicable to control devices to be used in, on, or attached to, a luminaire. This document builds on the digital addressable lighting interface as specified in the IEC 62386 series of standards, by adding specific requirements for power consumption, integrated bus and AUX power supplies, a mechanism to arbitrate between multiple application controllers, and a memory bank definition for multi-master devices.
This document is only applicable to control devices complying with IEC 62386‑103.
- Standard19 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides reference software for Rec. ITU-T H.266 | ISO/IEC 23090-3. The reference software includes both encoder and decoder functionality. Reference software is useful in aiding users of a video coding standard to establish and test conformance and interoperability, and to educate users and demonstrate the capabilities of the standard. For these purposes, the accompanying software is provided as an aid for the study and implementation of Rec. ITU-T H.266 | ISO/IEC 23090-3.
- Standard3 pagesEnglish languagesale 15% off
The management of electronic transport regulations (METR) provides trustworthy, authoritative, machine-interpretable, transport-related rules for using the road network.
This document describes the operational concept (ConOps) for METR in a format that is consistent with ISO/IEC/IEEE 29148.
- Technical report94 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the requirements for the bar code symbology known as EAN/UPC. This document specifies EAN/UPC symbology characteristics, data character encodation, dimensions, tolerances, decoding algorithms and parameters to be defined by applications. It specifies the symbology identifier prefix strings for EAN/UPC symbols. Data content and the rules governing the use of this symbology are outside the scope of this document; they are defined in GS1 General Specifications.
- Standard37 pagesEnglish languagesale 15% off