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
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 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 languagesale 10% offe-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 languagesale 10% offe-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.
- Draft52 pagesEnglish languagesale 10% offe-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 languagesale 10% offe-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 languagesale 10% offe-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 languagesale 10% offe-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 languagesale 10% offe-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 languagesale 10% offe-Library read for1 day
The European Commission will in its project “VAT in the digital age” mandate that VAT reporting on intra-EU transactions is performed in near real time and based on EN 16931. This document 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 will need to be changed.
NOTE 1 The ViDA proposal only applies to EU member states.
This document does not define the subset of the electronic invoice to be sent to the authorities.
NOTE 2 The definition of that subset is a task of the European Commission. As the subset message is not an invoice, but a VAT report, it is not regarded as a Core Invoice Usage Specification (CIUS). The subset 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 subset.
- Technical report32 pagesEnglish languagesale 10% offe-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 languagesale 10% offe-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 languagesale 10% offe-Library read for1 day
The European Commission will in its project “VAT in the digital age” mandate that VAT reporting on intra-EU transactions is performed in near real time and based on EN 16931. This document 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 will need to be changed.
NOTE 1 The ViDA proposal only applies to EU member states.
This document does not define the subset of the electronic invoice to be sent to the authorities.
NOTE 2 The definition of that subset is a task of the European Commission. As the subset message is not an invoice, but a VAT report, it is not regarded as a Core Invoice Usage Specification (CIUS). The subset 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 subset.
- Technical report32 pagesEnglish languagesale 10% offe-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 languagesale 10% offe-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 languagesale 10% offe-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 languagesale 10% offe-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 languagesale 10% offe-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 languagesale 10% offe-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 languagesale 10% offe-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 languagesale 10% offe-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 languagesale 10% offe-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 languagesale 10% offe-Library read for1 day
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 languagesale 10% offe-Library read for1 day
This document defines single-point gestures for screen readers. It specifies movements for clear and classified single-point gestures recognized by the screen readers. It describes single-point gestures performed by a POI (point of interest). The single-point gestures are intended to operate in a consistent manner regardless of systems, platforms, applications or devices. NOTE A POI can be manipulated by using an object such as a fingertip, a stylus, etc.
- Standard7 pagesEnglish languagesale 15% off
This document provides general guidance on gestures for screen readers running on various ICT devices. The document does not define or require specific technologies for recognizing the gestures. It focuses on descriptions of gestures and functions for screen readers running on ICT devices.
- Standard10 pagesEnglish languagesale 15% off
This document specifies description formats and functionality for the specification of cultural conventions, description formats for character sets, and description formats for binding character names to ISO/IEC 10646, as well as a set of default values for some of these items.
- Standard161 pagesEnglish languagesale 15% off
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.
- Corrigendum4 pagesEnglish languagesale 10% offe-Library read for1 day
- Corrigendum4 pagesEnglish languagesale 10% offe-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.
- Corrigendum4 pagesEnglish languagesale 10% offe-Library read for1 day
- Corrigendum4 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the mapping between the semantic model of an electronic invoice, included in EN 16931 1 and the Cross Industry Invoice in the UN/CEFACT XML 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 specification218 pagesEnglish languagesale 10% offe-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 2.1 syntax (ISO/IEC 19845). 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 specification265 pagesEnglish languagesale 10% offe-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.
- Standard158 pagesEnglish languagesale 10% offe-Library read for1 day
This documents specifies the mapping between the semantic model of an electronic invoice, included in EN 16931-1 and the ISO 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. Any mismatches between semantics, format, cardinality or structure are indicated.
- Technical specification225 pagesEnglish languagesale 10% offe-Library read for1 day
This document applies in case a CIUS is produced as a specification with the objective of registering it in the appropriate registry. This document also establishes requirements for the steps to be taken in the process of creating Core Invoice Usage Specifications (CIUS) as defined in EN 16931-1. Furthermore, this document provides guidance for the creation and implementation of a CIUS.
The following points are the focus:
- steps that need to be taken in consideration to avoid unnecessary proliferation and fragmentation in the use of CIUSs;
- guidance on the creation and implementation of CIUSs, with a quality control objective.
It should be noted that it is planned to apply the same principles and processes to extensions that are documented in a separate document.
- Technical specification32 pagesEnglish languagesale 10% offe-Library read for1 day
This document gives guidelines on the design of navigation methods for selection menus with the use of a 4-direction device. The guidelines are applicable to any information equipment on which the display area is associated with a 4-direction device. This document also provides recommendations for parameters for display screen settings, character sets and languages in use. This document is not applicable to safety-related uses on menu navigation.
- Standard12 pagesEnglish languagesale 15% off
This document gives guidance on how to create text alternatives and what information to put in text alternatives. This document applies to all static images that are used in any type of electronic document. It also applies to individual images within a slide show. This document does not apply to moving images (e.g. movies). NOTE 1 While text alternatives can be implemented via various mechanisms in various types of electronic documents, the contents of this document are not dependent on the choice of implementation mechanism or of electronic document type. NOTE 2 Guidance on making moving images accessible is contained in ISO/IEC TS 20071-21, ISO/IEC 20071-23 and ISO/IEC 20071-25.
- Standard42 pagesEnglish languagesale 15% off
This document defines multi-point gestures for common system actions used in information and communication technology (ICT) systems. It specifies movements and conditions for describing multi-point gestures recognized by the systems and applications. The multi-point gestures are performed using an input device (multi-touchpad, multi-touchscreen, etc.) or body parts (fingertips, hands, etc.). These multi-point gestures are intended to operate in a consistent manner regardless of systems, platforms or applications. The gestures for common system actions denote system-level functions and common functions across applications of ICT systems. The system-level functions are executed at a system or a platform level. They include initiation, resume, restart and termination, etc. The common functions across applications are commonly executed among applications of a system or a platform. The functions include navigation of menus, opening an object, closing an object, etc. NOTE ICT systems include, but are not limited to, digital televisions, set-top boxes, video game consoles, communication devices, internet devices, entertainment devices, and personal computers (PCs).
- Standard55 pagesEnglish languagesale 15% off
- Standard55 pagesEnglish languagesale 15% off
This document defines GIML (Gesture Interface Markup Language). The syntax and the structure of GIML are described in this document.
- Standard16 pagesEnglish languagesale 15% off
IEC 62665:2015(E) this International Standard specifies: - a text encoding scheme to generate a texture map, - a physical shape and dimension of the texture map for printing, - additional features for texture map printing and - a texture map decoding and an auditory presentation of decoded texts. These specifications enable the interchange of documents and publications between visually impaired and non-impaired people. This second edition cancels and replaces the first edition published in 2012 and constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition. Two different control codes are described by the different terms: "control codes for text" and "control codes for speech". Pack processing and LZSS processing are shown in their additional subclauses. An example of the header file "Speechio.h" is added. An example of error correction encoding is shown in additional Annex D.
- Standard44 pagesEnglish languagesale 10% offe-Library read for1 day
This document is an application profile for the International Standard ISO/IEC 30107. It provides requirements and recommendations for the implementation of Automated Border Control (ABC) systems in Europe with Presentation Attack Detection (PAD) capability.
This document covers the evaluation of countermeasures from the Biometrics perspective as well as privacy, data protection and usability aspects. Technical descriptions of countermeasures are out of scope. Enrolment, issuance and verification applications of electronic Machine Readable Travel Documents (eMRTD) other than border control are not in scope. In particular, presentation attacks at enrolment are out of scope.
The biometric reference data can be stored in an eMRTD and/or in a database of registered travellers.
This document covers:
- biometric impostor attacks and
- biometric concealer attacks in a watchlist scenario.
This document addresses PAD for facial and fingerprint biometrics only.
- Technical specification23 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides guidance for producers, exhibitors, and distributors on the visual presentation of alternatives to audio information in audiovisual content, such as captions/subtitles. This document provides requirements and recommendations that are intended to support users who are not able to use the audio information, prefer to use a visual representation of audio information, or prefer both audio and visual presentations. NOTE Many users do not have a choice, for instance, when in a noisy environment (e.g. bar, restaurant, etc.). In these situations, the user does not select a visual presentation of audio information but is offered the content with captions/subtitles. This document acknowledges the various needs and preferences of viewers (end users) as well as the different approaches to visual presentation of audio information. It applies to all presentations of visual alternatives to audio information intended to be presented as captions/subtitles. This document does not apply to the presentation devices or transmission mechanisms used to deliver the content or visual presentations of audio information. These devices could include, but are not limited to: televisions, computers, wireless devices, projection equipment, DVD and home cinema equipment, video game consoles, and other forms of user interfaces technology. This document does not apply to transcoding files and formats for the various video outputs. This document gives guidance on visual presentations which are delivered in the same language as in the audio (i.e., intra-lingual captions/subtitles) and visual presentations which are translated into a different language (i.e., inter-lingual captions/subtitles). This document does not apply to the specific process of language translation. This document helps to improve accessibility. This document does not establish requirements on specific industries (e.g. television broadcasting, motion pictures) nor is it intended to supersede specific international standards within their domain.
- Standard27 pagesEnglish languagesale 15% off