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 provides specifications on business processes for exchanging an electronic product catalogues (“catalogues”) as part of the business processes in the post-award area and pre-award area (partially), so that catalogues can serve as a basis for placing orders as well as evaluating tenders. The key aspects covered by this choreography specification:
• Processes for submitting catalogues from the selling to the buying side;
• Processes for submitting catalogue-related data as part of tendering processes.
Transaction used in the specified choreographies are out of scope. These transactions are specified in the related transaction specification on “Catalogue Transactions”.
- Standard39 pagesEnglish languagesale 10% offe-Library read for1 day
This choreographies document describes ordering between Buyer and Seller where the Buyer wants to reach an agreement with the Seller about an order. It describes a series of activities that govern communication between the parties and refers to the specifications where information and rules that apply are described.
The various possible behaviours of the Seller and Buyer subsequent to the first order communication are conveyed by variants of this choreography that are described 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:2022.
How to claim conformance to this choreography is described in 5.2.3.
- Standard81 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
The standard defines the transfer of electronic documents between stakeholders in the insurance industry (for
example between insurer and intermediary).
The standard specifies:
the semantic process for the transfer of documents (for example insurance policy, claim notification,
correspondence) that may be transferred as an attached file and
a limited number of meta data describing the document (for example type of document, identification of
insurer, intermediary and client, policy number, claim number).
- 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
- 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
- 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
- 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
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
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 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 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 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 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 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
- 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
- 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
- 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
- Standard27 pagesEnglish languagesale 15% off
This document provides an overview of standards in the set Business Interoperability Interfaces (BII) for public procurement. It covers the first part of the e- procurement chain. BII focus on exchange of information between business partners. This brings in scope all electronic communication between a contracting authority and an economic operator. Back-office information processing is out of scope.
To ensure interoperability each electronic communication will be described as follows:
- A choreography describes the sequence of transactions;
- A transaction describes all information elements exchanged between business partners;
- A syntax implementation guideline (SIG) provides the syntax bindings needed to implement the transaction
- A procurement procedure guideline identifies the position of the transactions in a procedure.
- Technical report13 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides an overview of e-ordering standards in the set Business Interoperability Inter-
faces (BII) for public procurement. E-ordering covers the e-sourcing and e-ordering business areas of the
e-procurement chain, starting from the awarding of the contract or the receiving of a quotation to the receipt of a despatch advise or a receiving advice for the goods or services that have been ordered.
- Technical report15 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides an overview of standards in the set Business Interoperability Interfaces (BII) for public procurement. It covers the first part of the e- procurement chain. BII focus on exchange of information between business partners. This brings in scope all electronic communication between a contracting authority and an economic operator. Back-office information processing is out of scope.
To ensure interoperability each electronic communication will be described as follows:
- A choreography describes the sequence of transactions;
- A transaction describes all information elements exchanged between business partners;
- A syntax implementation guideline (SIG) provides the syntax bindings needed to implement the transaction
- A procurement procedure guideline identifies the position of the transactions in a procedure.
- Technical report13 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides an overview of e-ordering standards in the set Business Interoperability Inter-
faces (BII) for public procurement. E-ordering covers the e-sourcing and e-ordering business areas of the
e-procurement chain, starting from the awarding of the contract or the receiving of a quotation to the receipt of a despatch advise or a receiving advice for the goods or services that have been ordered.
- Technical report15 pagesEnglish languagesale 10% offe-Library read for1 day
ISO/IEC 24752-8:2018 defines a RESTful protocol for the provision and delivery of resources that are related to user interface adaptation based on context of use. ISO/IEC 24752-8:2018 addresses requirements and recommendations for the following services: - user-context service; - task-context service; - equipment-context service; - environment-context service; - resource service; - resource-description service; - matching service (for finding appropriate resources based on specific contexts and other match criteria).
- Standard86 pagesEnglish languagesale 15% off
- Standard86 pagesEnglish languagesale 15% off
This document provides an overview of eTendering standards in the set Business Interoperability Interfaces (BII) for public procurement. BII eTendering covers the tendering part of the e-procurement chain, starting from subscribing interest in a business opportunity till concluding the contract.
BII focus on exchange of information between business partners. This brings in scope all electronic communication between a contracting authority and an economic operator. Back-office information processing, like the evaluation of tenders, is out of scope.
To ensure interoperability each electronic communication will be described as follows:
- A procurement procedure guideline identifies the position of the transactions in a procedure;
- A choreography describes the sequence of transactions;
- A transaction describes all information elements exchanged between business partners;
- A syntax implementation guideline (SIG) provides the syntax bindings needed to implement the transaction.
- Technical report23 pagesEnglish languagesale 10% offe-Library read for1 day
The CEN/TC 440/WG5 has developed a set of deliverables to support interoperability in the pre- and post-award areas of public procurement. In particular, the deliverables cover the exchange of electronic product catalogues and related documents between contracting bodies and economic operators respectively buyers and sellers. An electronic product catalogue contains specifications of products (goods and services) with their pricing. A catalogue is used to serve as a basis for ordering and all other following post-award processes. To ensure interoperability each electronic communication will be described as follows:
• A choreography describes the sequence of transactions;
• A transaction describes all information elements exchanged between business partners;
• A syntax implementation guideline (SIG) provides the syntax bindings needed to implement the transaction.
- Technical report15 pagesEnglish languagesale 10% offe-Library read for1 day
The CEN/TC 440/WG5 has developed a set of deliverables to support interoperability in the pre- and post-award areas of public procurement. In particular, the deliverables cover the exchange of electronic product catalogues and related documents between contracting bodies and economic operators respectively buyers and sellers. An electronic product catalogue contains specifications of products (goods and services) with their pricing. A catalogue is used to serve as a basis for ordering and all other following post-award processes. To ensure interoperability each electronic communication will be described as follows:
• A choreography describes the sequence of transactions;
• A transaction describes all information elements exchanged between business partners;
• A syntax implementation guideline (SIG) provides the syntax bindings needed to implement the transaction.
- Technical report15 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides an overview of eTendering standards in the set Business Interoperability Interfaces (BII) for public procurement. BII eTendering covers the tendering part of the e-procurement chain, starting from subscribing interest in a business opportunity till concluding the contract.
BII focus on exchange of information between business partners. This brings in scope all electronic communication between a contracting authority and an economic operator. Back-office information processing, like the evaluation of tenders, is out of scope.
To ensure interoperability each electronic communication will be described as follows:
- A procurement procedure guideline identifies the position of the transactions in a procedure;
- A choreography describes the sequence of transactions;
- A transaction describes all information elements exchanged between business partners;
- A syntax implementation guideline (SIG) provides the syntax bindings needed to implement the transaction.
- Technical report23 pagesEnglish languagesale 10% offe-Library read for1 day
ISO/IEC TS 20071-15:2017 provides guidance on various aspects of the user interface of applications that scan visual information that are used directly by humans, including: - initiating the scanning application; - setting user's preferences and configuring the scanning application; - identifying the types of information currently of interest to the user; - locating visual objects of interest to the user; - creating a static image via scanning the visual object; - identifying the information content provided by the visual object; - processing scanned information and outputting the results to the user. ISO/IEC TS 20071-15:2017 provides increased accessibility by addressing the user accessibility needs of diverse users in diverse contexts. ISO/IEC TS 20071-15:2017 contains guidance that can be applied to a variety of devices, including: - specialized devices that are dedicated to scanning and processing visual information; - mobile devices (such as smartphones and tablets); - general purpose computers with camera capabilities; - office machines with scanning functions. ISO/IEC TS 20071-15:2017 contains guidance that can be applied to various types of software, including: - stand-alone scanning applications; - applications including scanning functionalities; - (scanning) applications that interoperate with other applications. ISO/IEC TS 20071-15:2017 contains guidance that can be used for outputting scanned information in various modalities, including: - audio outputs; - visual outputs; - tactile outputs; - storing information for future use within the application performing the scanning; - electronic outputs (to other applications, systems, or devices including those directly connected and those connected via the Internet). ISO/IEC TS 20071-15:2017 does not: - apply to fully automated scanning that is not under direct human control; - apply to applications that scan visual information for editing an image or just displaying it; - provide guidance on the design of specific hardware devices involved in scanning; - provide guidance on the specific objects that can be recognized or the specific software used to recognize these objects; - provide guidance on the internal functioning of software that recognizes specific types of objects. ISO/IEC TS 20071-15:2017 is intended for use by developers of applications that include user controlled scanning functionalities. It does not expect that an application includes all of these functionalities. It can be used for those functionalities that an application does provide.
- Technical specification24 pagesEnglish languagesale 15% off
- Technical specification24 pagesEnglish languagesale 15% off
0.1 Introduction
Directive 2014/55/EU states the following: "The standard shall be tested as to its practical application for an end user. The Commission shall retain overall responsibility for the testing and shall ensure that, during the performance of the test, special account be taken of the respect for the criteria of practicality, user-friendliness and possible implementation costs in accordance with the second subparagraph of paragraph 1.
0.2 In scope
This CEN Technical Report describes the methodology used for testing at a semantic level and at the syntax level, as well as describing the semantic testing, the syntax testing and testing of the validation artefacts that represent EN 16931-1 and the test results. The testing of the validation artefacts will ensure they can be used to automatically check conformance with EN 16931-1.
0.3 Out of scope
During meetings with the European Commission they agreed to supplement the testing activities as the need arises. This included the provision of a hosted GITB (Global eBusiness Interoperability Test Beds) environment for syntax testing and to run separate studies such as assessment of implementation costs. The results of these studies will be published separately by CEF.
It was agreed at earlier meetings that piloting was out of scope i.e. perform live transactions, because resources were unavailable to undertake this in the time allowed. Instead we could simulate scenarios by leveraging on the experience of our experts.
Working Group 3 (hereafter WG3) in CEN/TC 434 has produced the syntax bindings and validation artefacts, and the task of quality assurance of these deliverables has been the responsibility of WG3.
VAT issues are complex and require juridical or legal expertise. VAT is also sometimes very sectoral or even country specific. Certain sections, in the VAT Directive, apply to all trades, others deal with special cases. The model should facilitate, but cannot be seen as an enforcement model. Therefore, VAT compliance would have to be checked on a case by case basis, and is deemed out of scope. The Commission had taken this up and given the draft to their VAT experts. The result was that no issues were discovered.
Article 226(B) of the VAT Directive [2] describes the simplified invoice. There are significantly fewer requirements for this invoice. It can only be used when the value is below a specific total amount. The requirement is to provide a model for low value purchases such as train tickets, receipts etc. The key difference is that it doesn’t require the Buyer to be identified. Due to limited resources the simplified invoice requirements were not checked and so are being considered as an extension to be developed at a future stage.
The changing between form and format was discussed. It was generally agreed, based on the VAT Directive, that an eInvoice cannot change form i.e. transformed to paper, however it can change format i.e. syntax. This is common in EDI systems and for legal reasons the original needs to be clarified. This means if it is in paper form it shall be archived in paper form and if it is electronic it shall stay in electronic form. An electronic invoice may change format, provided this is documented in an audit trail. However, in Norway and France the legislation states that the format received from the Supplier is the original and no other. Also, general practice in Germany requires that the invoice received from the Supplier be archived and considered as the original. There may be other exceptions in some Member States. This was also considered to be out of scope for this document and would be dealt with by the Member State involved.
It was agreed at an initial Plenary session that we should test all four syntaxes as the decision to select syntaxes had not yet been made. However ultimately the group concluded, based on our research, that the ISO 20022 Financial Invoice was not in sufficient use to justify being included.
- Technical report85 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report85 pagesEnglish languagesale 10% offe-Library read for1 day
ISO/IEC 30113-11:2017 defines single-point gestures for common system actions used in information and communication technology (ICT) systems. It specifies movements for clear and classified gestures recognized by the systems and applications. The single-point gestures are performed using an input device (e.g. a mouse, a stylus, etc.) or a body part (e.g. a fingertip, a hand, etc.). These single-point gestures are intended to operate in a consistent manner regardless of the system, platform, application or device. 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.
- Standard30 pagesEnglish languagesale 15% off
This Technical Report describes how trading partners may extend the core invoice model and the related business rules and code lists, in order 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 Technical Report does not define a methodology for creation of core invoice usage specification, nor does it describe the detailed process of syntax binding.
- Technical report19 pagesEnglish languagesale 10% offe-Library read for1 day
This Technical Report recommends a set of Guidelines to ensure interoperability at the transmission level to be used in conjunction with the European Norm (EN) for the semantic data model of the core elements of an electronic invoice and its other associated deliverables. The Guidelines are by nature non-prescriptive and non-binding.
These Guidelines take into account the following aspects:
1) recommending best practices for use at the transmission level;
2) supporting interoperability between all the parties and systems that need to interact and within the various operating models in common use;
3) ensuring a level playing field for the various operating models and bi-lateral implementations and for the use of existing and future infrastructures, which support e-Invoicing;
4) promoting a common terminology and non-proprietary standards for transmission and related areas;
5) ensuring the authenticity of origin and integrity of electronic invoice content;
6) providing guidance on data protection, on the enablement of format conversion, and on e-invoice legibility, including the use of a readable visual presentations, as required;
7) providing guidance for identification, addressing and routing;
8) identifying requirements for robust legal frameworks and governance arrangements;
9) recognizing the roles of trading parties, solution and service providers and related infrastructure providers.
The Objectives of the Guidelines are:
10) to support the implementation of the EU Directive 2014/55/EU on e-Invoicing and the core invoice model;
11) to propose best practices and recommendations for standards to enable electronic exchange of e-Invoices and related data between participants by providing a basis for interoperability at the transmission level, based on common requirements and scenarios;
12) to facilitate Straight Through Processing (STP) by the key actors in the supply chain (Buyers, Sellers, Tax Authorities, Agents, Banks, Service and Solution Providers, etc.);
13) to provide a set of non-prescriptive and non-binding Guidelines and recommendations that are applicable to all common operating models for e-invoice exchange and transmission whilst also providing recommendations specific to each of the common operating models.
To accomplish these objectives, the Guidelines are based on the following Requirements and Guiding Principles:
14) the need to cover the transmission of e-invoices and related documents from the system of the sending trading party to the system of the receiving trading party, including transmission issues for any intermediary platforms;
15) the need to allow any seller in any European (EU, EEA and Switzerland) country to deliver invoices to any buyer in any location in another European country (EU, EEA and Switzerland);
16) the need to support all common invoicing processes and modes of operation;
17) the need to be compatible with the current legislative and regulatory environment for the exchange of e-Invoices and related data;
18) the need to support the European Norm and other commonly accepted content standards;
19) the need to ensure that other document exchanges beyond e-Invoicing can be supported;
20) the need to establish clear boundaries between the collaborative and competitive domains;
21) the need to enable competition between business models, solutions and service providers and foster innovation;
22) the need to ensure that European supply chains remain an integrated and competitive part of the global economy;
23) the need to promote network effects leading to the development of critical mass as e-Invoicing becomes the dominant mode of invoicing (network effects result in a service becoming more valuable as more trading parties use it, thus creating a virtuous circle and further momentum for adoption).
The following items are considered to be in the competitive domain and therefore out of scope of the Recommendations:
(....)
- Technical report24 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report24 pagesEnglish languagesale 10% offe-Library read for1 day
This Technical Specification (TS) specifies the methodology of the mapping between the semantic model of an electronic invoice, included in EN 16931-1 and a syntax. For each element in the semantic model (including sub-elements or supplementary components such as Identification scheme identifiers) it should be 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 specification17 pagesEnglish languagesale 10% offe-Library read for1 day
This Technical Specification provides in Clause 7 the list of syntaxes that complies with and allows to express syntactically the core invoice model as specified in EN 16931 1:2017, according to the selection criteria provided by the Standardization Request [1].
The selection of the syntaxes also derived from the Standardization Request [1]. It states that, to limit costs on public authorities, the list should ideally not exceed five syntaxes. Four syntaxes were taken into account and assessed according to criteria provided by the Standardization Request [1].
- Technical specification12 pagesEnglish languagesale 10% offe-Library read for1 day