35.240.20 - IT applications in office work
ICS 35.240.20 Details
IT applications in office work
IT-Anwendungen im Buro
Applications des TI en bureautique
Uporabniške rešitve IT pri pisarniškem delu
General Information
Frequently Asked Questions
ICS 35.240.20 is a classification code in the International Classification for Standards (ICS) system. It covers "IT applications in office work". The ICS is a hierarchical classification system used to organize international, regional, and national standards, facilitating the search and identification of standards across different fields.
There are 302 standards classified under ICS 35.240.20 (IT applications in office work). These standards are published by international and regional standardization bodies including ISO, IEC, CEN, CENELEC, and ETSI.
The International Classification for Standards (ICS) is a hierarchical classification system maintained by ISO to organize standards and related documents. It uses a three-level structure with field (2 digits), group (3 digits), and sub-group (2 digits) codes. The ICS helps users find standards by subject area and enables statistical analysis of standards development activities.
e-Library Subscription
Create subscription and get permanent access to documents within 35.240.20 - IT applications in office work
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
This document specifies the mapping between the semantic model of an electronic invoice, included in EN 16931-1 and the ISO/IEC 9735 (UN/EDIFACT) syntax. For each element in the semantic model (including sub-elements or supplementary components such as Identification scheme identifiers) it is defined which element in the syntax is to be used to contain its information contents.
- Technical specification211 pagesEnglish languagee-Library read for1 day
This document specifies the mapping between the semantic model of an electronic invoice, included in EN 16931-1 and the UBL syntax. For each element in the semantic model (including sub-elements or supplementary components such as Identification scheme identifiers) it is defined which element in the syntax is to be used to contain its information contents. Any mismatches between semantics, format, cardinality or structure are indicated.
- Technical specification269 pagesEnglish languagee-Library read for1 day
This document provides requirements and guidance for kiosk manufacturers, service providers and purchasers to ensure that kiosks can be used by a diverse range of users. This document specifies requirements and recommendations for designing, manufacturing, installing, and operating kiosks to ensure accessibility across diverse users and varying physical and environmental conditions. The requirements and recommendations pertain to the presentation of information, operation and interaction with users on kiosks. They are applied to hardware, software and content of the kiosks, as well as their installation environment.
- Standard16 pagesEnglish languagesale 15% off
This CEN Technical Specification (TS) contains the mapping between the semantic data model of an electronic invoice (EN 16931-1) and the UN/EDIFACT INVOIC syntax. For each element in the semantic model (including sub-elements or supplementary components such as Code List identifiers) it is defined which element in the syntax is to be used to contain its information contents. Any mismatches between semantics, format, cardinality or structure are indicated. Any rules to be followed when using the specific syntax are stated informally in this TS. If later versions of the UN/EDIFACT INVOIC support the semantics more accurately, this is indicated.
- Technical specification211 pagesEnglish languagee-Library read for1 day
This CEN Technical Specification (TS) contains the mapping between the semantic data model of an electronic invoice (EN 16931-1) and the UBL syntax. For each element in the semantic model (including sub-elements or supplementary components such as Code List identifiers) it is defined which element in the syntax is to be used to contain its information contents. Any mismatches between semantics, format, cardinality or structure are indicated. Any rules to be followed when using the specific syntax are stated informally
in this TS. If later versions of UBL support the semantics more accurately, this is indicated. For earlier versions (from UBL 2.1 onwards) also a solution is presented.
- Technical specification269 pagesEnglish languagee-Library read for1 day
This document defines the purpose, governance and functional requirements of the eInvoicing Registry for CIUS and Extension Specifications. This document is not to be confused with other business / project focused Technical Specifications. It follows CEN rules and will be published as a CEN document with normative statements.
A key part of this document is to provide a functional specification, which will describe the various functions of eInvoice Registry Services.
The Registry is intended to serve as a structured, transparent and publicly accessible repository that facilitates the discovery, registration and management of eInvoicing Specifications that either restrict the conditional elements of the Core Invoice Model and/or extend it in conformance with Part 5 Extension Methodology.
The scope of this document includes:
- Definition of Registry Services - the structure and capabilities of the Registry including the types of artefacts it stores or references, e.g. CIUS, Extension Specifications, Validation Artefacts and Services, and Code Lists;
- Governance Model - the roles and responsibilities of entities involved in managing and maintaining the Registry;
- Submission and Verification Processes - how Specifications are submitted, reviewed and verified for inclusion in the Registry;
- Functional Specification - the required functionality, processes and procedures that enable the Registry to operate efficiently.
- Technical specification51 pagesEnglish languagee-Library read for1 day
This document describes the transaction information requirements of the transactions used in the basic
collaborations described in EN 17015-1 Electronic Public Procurement – Catalogue – Choreographies.
For each transaction there is an overview, the transaction business requirements and the transaction information requirements model containing definitions of terms, usage descriptions and cardinality of the information elements.
The document describes the following transactions:
1) Catalogue;
2) Catalogue Response
3) Pre-award Catalogue Request
4) Pre-award Catalogue
5) Shopping Cart
How to claim compliance to a transaction is described in paragraph 6.
How to claim conformance to a transaction is described in paragraph 6.
- Standard144 pagesEnglish languagee-Library read for1 day
This document describes the transaction information requirements of the transactions used in the collaborations described in EN 17016-1:2024. For each transaction are specified the transaction business requirements, the transaction information data model containing definitions of terms, usage descriptions and cardinality of the information elements and the transaction business rules.
This document describes the following transactions:
1) Order;
2) Order Change;
3) Order Cancellation;
4) Order Response Simple
5) Order Confirmation;
6) Order Rejection;
7) Order Response;
8) Order Change Confirmation;
9) Order Change Rejection;
10) Order Cancellation Confirmation;
11) Order Cancellation Rejection;
12) Order Agreement.
How to claim compliance to a transaction is specified in Clause 6.
How to claim conformance to a transaction is also specified in Clause 6.
- Standard392 pagesEnglish languagee-Library read for1 day
This document specifies a semantic data model of the core elements of an Electronic invoice. The semantic data model includes only the essential information elements that an Electronic invoice needs to ensure legal (including fiscal) compliance and to enable interoperability for cross-border, cross sector and domestic trade. The semantic data model can be applied by organizations in the private and the public sector for public procurement invoicing. It can also be used for invoicing between private sector enterprises. It has not been specifically designed for invoicing consumers.
This document complies at least with the following criteria:
— it is technologically neutral;
— it is compatible with relevant international standards on electronic invoicing;
— the application of this standard should comply with the requirements for the protection of personal data of Directive 95/46/EC, having due regard to the principles of privacy and data protection bydesign, data minimization, purpose limitation, necessity and proportionality;
— it is consistent with the relevant provisions of Directive 2006/112/EC [2];
— it allows for the establishment of practical, user-friendly, flexible and cost-efficient electronic invoicing systems;
— it takes into account the special needs of small and medium-sized enterprises as well as of subcentral contracting authorities and contracting entities;
— it is suitable for use in commercial transactions between enterprises.
- Standard163 pagesEnglish languagee-Library read for1 day
This document defines the purpose, governance and functional requirements of the eInvoicing Registry for CIUS and Extension Specifications. This document is not to be confused with other business / project focused Technical Specifications. It follows CEN rules and will be published as a CEN document with normative statements.
A key part of this document is to provide a functional specification, which will describe the various functions of eInvoice Registry Services.
The Registry is intended to serve as a structured, transparent and publicly accessible repository that facilitates the discovery, registration and management of eInvoicing Specifications that either restrict the conditional elements of the Core Invoice Model and/or extend it in conformance with Part 5 Extension Methodology.
The scope of this document includes:
- Definition of Registry Services - the structure and capabilities of the Registry including the types of artefacts it stores or references, e.g. CIUS, Extension Specifications, Validation Artefacts and Services, and Code Lists;
- Governance Model - the roles and responsibilities of entities involved in managing and maintaining the Registry;
- Submission and Verification Processes - how Specifications are submitted, reviewed and verified for inclusion in the Registry;
- Functional Specification - the required functionality, processes and procedures that enable the Registry to operate efficiently.
- Technical specification51 pagesEnglish languagee-Library read for1 day
This European Standard establishes a semantic data model of the core elements of an electronic invoice. The semantic model includes only the essential information elements that an electronic invoice needs to ensure legal (including fiscal) compliance and to enable interoperability for cross-border, cross sector and for domestic trade. The semantic model may be used by organizations in the private and the public sector for public procurement invoicing. It may also be used for invoicing between private sector enterprises. It has not been specifically designed for invoicing consumers.
This European Standard complies at least with the following criteria:
- it is technologically neutral;
- it is compatible with relevant international standards on electronic invoicing;
- the application of this standard should comply with the requirements for the protection of personal data of Directive 95/46/EC, having due regard to the principles of privacy and data protection by-design, data minimization, purpose limitation, necessity and proportionality;
- it is consistent with the relevant provisions of Directive 2006/112/EC [2];
- it allows for the establishment of practical, user-friendly, flexible and cost-efficient electronic invoicing systems;
- it takes into account the special needs of small and medium-sized enterprises as well as of sub-central contracting authorities and contracting entities;
- it is suitable for use in commercial transactions between enterprises.
- Standard163 pagesEnglish languagee-Library read for1 day
This document describes:
- business processes and the technical environments in which simplified invoices and e-receipts are exchanged; and
- the needed syntax bindings of electronic simplified invoices and e-receipts.
- Technical report21 pagesEnglish languagee-Library read for1 day
This document provides requirements and recommendations for the design and use of pictograms, photos, and icons in augmentative and alternative communication (AAC) in the information and communication technology (ICT) domain. This document recognizes that AAC can be delivered on various sized devices including computer displays, tablets, and smart phones. It applies to pictograms, photos, and icons that can be used on a range of devices. It is not specific to particular devices or the particular software used. This document focuses on the needs of those users who cannot use a natural language in written or spoken form to communicate with a peer group or the community as a whole. In facilitating communication with those other people, it also serves them.
- Technical specification18 pagesEnglish languagesale 15% off
This document provides an introduction to and basic guidance on augmentative and alternative communication (AAC) in the information and communication technology (ICT) domain. It also provides common definitions and a framework for the development of further, more detailed guidance relating to aspects of these AACs. This document recognizes that AAC can be delivered on various ICT devices and the importance of consistency for users across devices. It applies to AAC software and not the devices on which the software is used. This document recognizes that AAC provides many users with a unique form of communication that is not necessarily based on any specific natural language.
- Technical specification15 pagesEnglish languagesale 15% off
The European Commission will in its project "VAT in the digital age" (ViDA) mandate that VAT reporting on intra-EU transactions is performed in near real-time and based on EN 16931-1. This Technical Report defines the impact of this legislation on the various deliverables of CEN/TC 434, with a focus on the subset to be sent to tax authorities and how EN 16931-1 needs to be changed. The ViDA package applies to all EU member states and specific territories where the VAT legislation applies (e.g. Northern Ireland in respect to goods).
This document does not define the content of the common electronic message based on the electronic invoice to be sent to the authorities. The definition of that common electronic message (DRR message) is a task of the European Commission, possibly with help of CEN. As the DRR message is not an invoice, but a VAT report, it is not to be regarded as a Core Invoice Usage Specification (CIUS). The DRR message therefore needs not to obey the rules for developing a CIUS. For example, not all mandatory elements in the invoice need to be part of the DRR message.
- Technical report31 pagesEnglish languagee-Library read for1 day
This document describes:
- business processes and the technical environments in which simplified invoices and e-receipts are exchanged; and
- the needed syntax bindings of electronic simplified invoices and e-receipts.
- Technical report21 pagesEnglish languagee-Library read for1 day
This document defines multi-point gestures for screen readers. It specifies movements for clear and classified multi-point gestures recognized by the screen readers. It describes multi-point gestures performed by multiple point of interest (POI) for the screen readers. NOTE Multiple POI can be manipulated by using multiple objects such as fingertips, etc.
- Standard15 pagesEnglish 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.
- Technical specification37 pagesEnglish languagee-Library read for1 day
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 CEN/TC 440 Technical Committee.
- Technical specification52 pagesEnglish languagee-Library read for1 day
The European Commission will in its project "VAT in the digital age" (ViDA) mandate that VAT reporting on intra-EU transactions is performed in near real-time and based on EN 16931-1. This Technical Report defines the impact of this legislation on the various deliverables of CEN/TC 434, with a focus on the subset to be sent to tax authorities and how EN 16931-1 needs to be changed. The ViDA package applies to all EU member states and specific territories where the VAT legislation applies (e.g. Northern Ireland in respect to goods).
This document does not define the content of the common electronic message based on the electronic invoice to be sent to the authorities. The definition of that common electronic message (DRR message) is a task of the European Commission, possibly with help of CEN. As the DRR message is not an invoice, but a VAT report, it is not to be regarded as a Core Invoice Usage Specification (CIUS). The DRR message therefore needs not to obey the rules for developing a CIUS. For example, not all mandatory elements in the invoice need to be part of the DRR message.
- Technical report31 pagesEnglish languagee-Library read for1 day
This document describes how trading partners may extend the Core Invoice Model and the related business rules and code lists, to support business cases that are specific to their trading environment, while at the same time maintaining semantic interoperability with the Core Invoice Model.
This document does not define a methodology for creation of a Core Invoice Usage Specification, nor does it describe the detailed process of syntax binding.
- Technical specification38 pagesEnglish languagee-Library read for1 day
All parts of EN 16931 with a specific focus on CEN/TR 16931-5 (Electronic invoicing - Part 5: Guidelines on the use of sector or country extensions in conjunction with EN 16931-1, methodology to be applied in the real environment).
- Technical report49 pagesEnglish languagee-Library read for1 day
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 CEN/TC 440 Technical Committee.
- Technical specification52 pagesEnglish languagee-Library read for1 day
This document describes how trading partners may extend the Core Invoice Model and the related business rules and code lists, to support business cases that are specific to their trading environment, while at the same time maintaining semantic interoperability with the Core Invoice Model.
This document does not define a methodology for creation of a Core Invoice Usage Specification, nor does it describe the detailed process of syntax binding.
- Technical specification38 pagesEnglish languagee-Library read for1 day
This document provides a framework of voice user interfaces (VUI) for personal mobility services (PMS). The users of PMS ride personal mobility devices (PMD), which are empowered by electricity or a human, and interact with the PMS through the VUI (see Annex A) attached to the PMD. This document describes the functional requirements, the performance requirements and the procedure of the VUI. This document is applicable to a VUI attached to a PMD, which can be used for interaction between users and the PMD.
- Standard8 pagesEnglish languagesale 15% off
All parts of EN 16931 with a specific focus on CEN/TR 16931-5 (Electronic invoicing - Part 5: Guidelines on the use of sector or country extensions in conjunction with EN 16931-1, methodology to be applied in the real environment).
- Technical report49 pagesEnglish languagee-Library read for1 day
This document provides requirements and recommendations on the development of accessible audiovisual content. It provides requirements and recommendations for a variety of different accessibility components, dealt with in further detail in additional parts of the ISO 20071 series, that meet different user accessibility needs. It also provides guidance related to translations, localizations, timing, importance and other general aspects of the creation of these accessibility components. This document does not apply to the presentation devices or transmission mechanisms used to deliver audiovisual content. These devices could include, but are not limited to, televisions, computers, wireless devices, projection equipment, DVD and home cinema equipment, video game consoles, or any similar devices which use displays for visual presentation and other forms of user interface technology. This document does not apply to transcoding files and formats for the various audiovideo outputs. This document helps to improve accessibility. This document does not establish requirements for specific industries (e.g. television broadcasting, motion pictures) nor is it intended to supersede specific international standards within their domain.
- Standard11 pagesEnglish languagesale 15% off
This document specifies the test suite structure (TSS) and test purposes (TPs) for evaluating the conformity of on-board equipment (OBE) and roadside equipment (RSE) to ISO 12813.
It provides a basis for conformance tests for dedicated short-range communication (DSRC) OBE and RSE to support interoperability between different equipment supplied by different manufacturers.
ISO 12813 specifies requirements for the compliance check communication (CCC) interface level, but not for the OBE or RSE internal functional behaviour. Consequently, tests regarding OBE and RSE functional behaviour remain outside the scope of this document.
- Standard91 pagesEnglish languagee-Library read for1 day
This document describes:
- the rationale for building customisation supporting business cases that are specific to their business environment while maintaining organisational and semantic interoperability with the TC 440 specifications;
- the difference between Usage specification and Extension specification;
- a methodology on how to define customisations on:
- BII Transaction specification,
- Business rules,
- Code lists;
- how to claim compliance or conformance to a customisation of a TC 440 specification;
- the connection to the eProcurement Ontology project.
This specification does not describe the detailed process of building an extension.
- Technical specification22 pagesEnglish languagee-Library read for1 day
This document specifies the test suite structure (TSS) and test purposes (TPs) for evaluating the conformity of on-board equipment (OBE) and roadside equipment (RSE) to ISO 12813.
It provides a basis for conformance tests for dedicated short-range communication (DSRC) OBE and RSE to support interoperability between different equipment supplied by different manufacturers.
ISO 12813 specifies requirements for the compliance check communication (CCC) interface level, but not for the OBE or RSE internal functional behaviour. Consequently, tests regarding OBE and RSE functional behaviour remain outside the scope of this document.
- Standard91 pagesEnglish languagee-Library read for1 day
This document establishes a semantic data model of an e-receipt or a simplified electronic invoice.
NOTE In the remainder of this document, when “e-receipt” is mentioned, “simplified invoice” is also meant.
The semantic model includes essential information elements that an electronic receipt needs to ensure legal (including fiscal) compliance and to enable interoperability for cross-border, cross sector and domestic trade. The semantic model can be used by organizations in the private and the public sector for documenting by issuing a receipt for the purchase of services and /or goods. It can also be used for documenting a purchase between private sector enterprises. In addition, it has been designed for the use of consumers.
- Technical specification106 pagesEnglish languagee-Library read for1 day
This document describes:
- the rationale for building customisation supporting business cases that are specific to their business environment while maintaining organisational and semantic interoperability with the TC 440 specifications;
- the difference between Usage specification and Extension specification;
- a methodology on how to define customisations on:
- BII Transaction specification,
- Business rules,
- Code lists;
- how to claim compliance or conformance to a customisation of a TC 440 specification;
- the connection to the eProcurement Ontology project.
This specification does not describe the detailed process of building an extension.
- Technical specification22 pagesEnglish languagee-Library read for1 day
This document establishes a semantic data model of an e-receipt or a simplified electronic invoice.
NOTE In the remainder of this document, when “e-receipt” is mentioned, “simplified invoice” is also meant.
The semantic model includes essential information elements that an electronic receipt needs to ensure legal (including fiscal) compliance and to enable interoperability for cross-border, cross sector and domestic trade. The semantic model can be used by organizations in the private and the public sector for documenting by issuing a receipt for the purchase of services and /or goods. It can also be used for documenting a purchase between private sector enterprises. In addition, it has been designed for the use of consumers.
- Technical specification106 pagesEnglish languagee-Library read for1 day
This document provides requirements for the icons that are suitable for setting up interaction modes in all kinds of devices. It gives guidance about their purpose, their function, and how they are designed in order to be usable. This document specifies two sets of icons: a) icons that deal with global constraints that are taken into account by the product or service; b) icons that are oriented to more specific functions. Each icon is illustrated through a glyph, name, description and function.
- Standard19 pagesEnglish languagesale 15% off
This choreographies document specify ordering between Buyer and Seller where the Buyer wants to reach an agreement with the Seller about an order. It specifies a series of activities that govern communication between the parties and refers to the specifications where information and rules that apply are specified.
The various possible behaviours of the Seller and Buyer subsequent to the first order communication are conveyed by variants of this choreography that are specified in 5.2.
Previous activities (e.g. cataloguing) and subsequent activities (e.g. invoicing) are outside the scope of this document. If performed electronically, their implementation is covered by other choreographies.
The identifier of this choreographies document is EN 17016-1:2024.
How to claim compliance to this choreography is specified in 5.2.3.
- Standard81 pagesEnglish languagee-Library read for1 day
The purpose of this deliverable is to specify and describe choreographies for exchanging an electronic product catalogue (“catalogues”) as part of the business processes in the pre-award and post-award area, so that catalogues can serve as a basis for placing orders as well as evaluating tenders. The key aspects covered by this choreography specification are:
- processes for submitting catalogues from the selling to the buying side;
- processes for submitting catalogue-related data as part of a tendering process;
- processes integrating sell-side procurement systems.
This document does not apply to the transactions used in the specified choreographies. These transactions are specified in EN 17015 2. The relationship between the choreographies and the transaction is described in Clause 8.
The identifier of this choreographies document is EN 17015 1:2024.
How to claim compliance to this choreography is specified in 6.2.3.
- Standard39 pagesEnglish languagee-Library read for1 day
This choreographies document specify ordering between Buyer and Seller where the Buyer wants to reach an agreement with the Seller about an order. It specifies a series of activities that govern communication between the parties and refers to the specifications where information and rules that apply are specified.
The various possible behaviours of the Seller and Buyer subsequent to the first order communication are conveyed by variants of this choreography that are specified in 5.2.
Previous activities (e.g. cataloguing) and subsequent activities (e.g. invoicing) are outside the scope of this document. If performed electronically, their implementation is covered by other choreographies.
The identifier of this choreographies document is EN 17016-1:2024.
How to claim compliance to this choreography is specified in 5.2.3.
- Standard81 pagesEnglish languagee-Library read for1 day
This document identifies the affective characteristics for affective computing user interface (AUI), including universal, cultural, individual and situational issues relating to the affective needs of users. This document also describes the selection criteria of these affective characteristics, and the methods to identify or apply them. This document focuses on developers of affective computing user interfaces who want to meet the needs of users. This document does not specify the implementation of affective computing.
- Technical report13 pagesEnglish languagesale 15% off
This document defines the standardized mapping of the specific requirements of an insurance premium invoice to the generic electronic invoice described in EN 16931-1. This mapping meets the requirements of an electronic premium invoice to ensure legal (including fiscal) compliance as well as business and technical demands of the insurance industry.
Premium invoices can be issued by different organizations of the insurance industry to commercial clients or consumers. This document includes premium invoices issued by insurance companies as well as insurance intermediaries.
This document does not deal with data protection matters in premium invoices.
NOTE General Data Protection Regulation, EU Regulation 2016/679 can include requirements on personal data.
Premium invoices are regularly not subject to VAT but to special taxes. In particular, the requirements resulting from insurance tax regulations are considered. Requirements for other taxes are also incorporated.
The rules defined in EN 16931-1 do not support invoices with amounts not subject to VAT together with additional amounts which are subject to VAT. Therefore, this document also does not support premium invoices which invoice other goods and services which are subject to VAT invoiced together with premium amounts.
Out of the scope of this document are accounting transactions between insurance companies and insurance intermediaries which may contain premium invoice data, but regularly consist of other data (e.g. commissions) which are not part of a regular invoice.
- Technical specification34 pagesEnglish languagee-Library read for1 day
This document defines the standardized mapping of the specific requirements of an insurance premium invoice to the generic electronic invoice described in EN 16931-1. This mapping meets the requirements of an electronic premium invoice to ensure legal (including fiscal) compliance as well as business and technical demands of the insurance industry.
Premium invoices can be issued by different organizations of the insurance industry to commercial clients or consumers. This document includes premium invoices issued by insurance companies as well as insurance intermediaries.
This document does not deal with data protection matters in premium invoices.
NOTE General Data Protection Regulation, EU Regulation 2016/679 can include requirements on personal data.
Premium invoices are regularly not subject to VAT but to special taxes. In particular, the requirements resulting from insurance tax regulations are considered. Requirements for other taxes are also incorporated.
The rules defined in EN 16931-1 do not support invoices with amounts not subject to VAT together with additional amounts which are subject to VAT. Therefore, this document also does not support premium invoices which invoice other goods and services which are subject to VAT invoiced together with premium amounts.
Out of the scope of this document are accounting transactions between insurance companies and insurance intermediaries which may contain premium invoice data, but regularly consist of other data (e.g. commissions) which are not part of a regular invoice.
- Technical specification34 pagesEnglish languagee-Library read for1 day
This document provides requirements and recommendations on all written text so that it is easy to read and understand in any user interface, regardless of its format. This document addresses the process of creation, adaptation and evaluation of written text that is easy to read and understand. This document does not consider devices or transmission mechanisms used to deliver written text. It does not provide language-specific guidance.
- Standard21 pagesEnglish languagesale 15% off
- Standard22 pagesFrench languagesale 15% off
This document provides requirements and recommendations on the design of navigation methods for menu item selection with use on one-direction devices (using single or double-switch devices). It specifies requirements for menu navigation with one-direction devices in terms of time delay, loops and focus rendering. This document is applicable to any information technology equipment on which the display area is associated with the one-direction devices.
- Standard9 pagesEnglish languagesale 15% off
This document specifies user interfaces (UIs) designed for full duplex (FDX) speech interaction. It also specifies the FDX speech interaction model, features, functional components and requirements, thus providing a framework to support natural conversational interfaces between humans and machines. It also provides privacy considerations for applying FDX speech interaction. This document is applicable to UIs for speech interaction and communication protocols for setting up a session-oriented FDX interaction between humans and machines. This document does not define the speech interaction engines themselves or specify the details of specific engines, devices and approaches.
- Standard23 pagesEnglish languagesale 15% off
This document specifies a concrete REST webservice API description of the processes and data (see
EN 17419-1:2020 for more information) as an OpenAPI definition specified by the OpenAPI specification.
- Technical report102 pagesEnglish languagee-Library read for1 day
This document specifies a concrete REST webservice API description of the processes and data (see
EN 17419-1:2020 for more information) as an OpenAPI definition specified by the OpenAPI specification.
- Technical report102 pagesEnglish languagee-Library read for1 day
This document establishes a model for affective computing user interfaces (AUI). Annex B also suggests topics for AUI standardization. This document does not specify the implementation of affective computing.
- Standard16 pagesEnglish languagesale 15% off
This document provides a framework for the ISO/IEC 17549 series describing user interface guidelines on menu navigation. It specifies requirements and recommendations on how to design usable and consistent navigation through the interface component called a “menu”. This document specifies how to select and validate elements displayed on menus. This document covers design-consistent navigation inside menus. It does not include testing or organization of menus.
- Standard8 pagesEnglish languagesale 15% off
This document specifies requirements and recommendations for making accessibility settings accessible and usable. It provides guidance on specific accessibility settings, saving settings and modifying settings. It specifies how to access and operate the accessibility setting mode, and how to directly activate specific accessibility features. This document applies to all operating system user interfaces on all types of information and communications technologies (ICTs) from the point where the operating system is fully functional and waiting for the user to interact with it. This document does not apply to: — storing and retrieving information from a stored user profile, including personally identifiable information; — accessibility of the closed functionality that does not support access by assistive technology; — accessibility of boot mode.
- Standard29 pagesEnglish languagesale 15% off
IEC 62605:2021 specifies the interchange format for e-dictionaries among publishers, content creators and manufacturers.
This document does not address the following aspects:
• data formats for reading devices;
• elements necessary for final print reproduction only;
• rendering issues related to physical devices;
• security issues such as DRM for documents.
IEC 62605:2021 cancels and replaces the second edition published in 2016. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
The format described in Annex B was significantly enhanced in the following ways:
a) elements to enhance uses of data (e.g. web-related usage);
b) attribute for accessibility-related functions;
c) attributes for more detailed markup for data reusability.
- Standard240 pagesEnglish languagesale 15% off
This document defines the process and the structure of the transfer of electronic documents, and facilitates the transfer of electronic documents between stakeholders in the insurance industry.
- Standard65 pagesEnglish languagee-Library read for1 day