35.240.63 - IT applications in trade
ICS 35.240.63 Details
IT applications in trade
Applications des TI dans le commerce
Uporabniške rešitve IT v trgovini
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 35.240.63 - IT applications in trade
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
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 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 document: a) focuses on PbD aspects of privacy protection requirements as external constraints on any type of Person, (e.g. organization or public administration) involved in any kind of business transaction among such Persons which involves the electronic data interchange (EDI) of any personal information; b) establishes a fundamental set of privacy principles known as Privacy by Design and assumptions based on primary sources; c) integrates existing normative elements in support of PbD as are already identified in ISO/IEC 14662 and ISO/IEC 15944-1, ISO/IEC 15944-5, ISO/IEC 15944-8, ISO 15944-12; d) provides overarching operational ‘best practice’ statements for associated (and not necessarily automated) processes, procedures, practices and governance requirements that need to act in support of implementing and enforcing technical mechanisms that support PbD in Open-edi transaction and collaboration space environments; e) focuses on PbD related aspects of the life cycle management of and accountability for the personal information, i.e. the contents of SPIs (and their SRIs) related to the business transaction interchanged via EDI as information bundles and their associated semantic components among the parties to a business transaction. This document focuses on the BOV aspects of a business transaction and does not concern itself with the technical mechanisms needed to implement the FSV aspects of the business requirements of the FSV including the specification of requirements of an FSV nature which include security techniques and services, communication protocols, etc.). The FSV includes any existing standard (or standards development of an FSV nature), which has been ratified by existing ISO, IEC, UN/ECE and/or ITU standards. This document does not specify the technical mechanisms, i.e. FSV which are required to support BOV-identified requirements. Detailed exclusions to the scope of this document are provided in Annex D.
- Standard63 pagesEnglish languagesale 15% off
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 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 specifies the principles and framework for e-commerce transaction assurance, including participants, activities and assurance elements. It does not describe specific e-commerce transaction assurance requirements or methodologies in detail. It is intended to be used by organizations and individuals engaged in e-commerce transactions.
- Standard22 pagesEnglish languagesale 15% off
This document provides terms and definitions in the field of transaction assurance in e-commerce.
- Standard11 pagesEnglish languagesale 15% off
This document provides: — a review and summary of the adoption of digital methods and technology in the national nuclear sectors; — a summary of the state of the art of some of the standards supporting the digital representation and interoperability of industrial data; — orientation on the use of these standards for model-based systems engineering (MBSE) in order to achieve a nuclear digital ecosystem (NDE); — a high-level roadmap of the stages by which this ecosystem can be achieved, taking into account the maturity of the actors of the ecosystem, their relationships and the added value of using advanced standards. NOTE The complete reports from the participating entities are presented in Annexes A to G. This document includes the following: — the systems composing the nuclear facilities and their input, output, and other products resulting from interactions in the nuclear system or with its environment; — the material accounting and the corresponding requirements; — waste management: all types of nuclear waste produced during processes and activities, and their properties are considered for a seamless management of information in the whole value chain of the nuclear ecosystem.
- Technical report87 pagesEnglish languagesale 15% off
This document provides a consolidated set of rules and associated guidelines as found and defined in the existing parts of the ISO/IEC 15944 series. NOTE Not all parts of the ISO/IEC 15944 series have rules, that is ISO/IEC 15944-6, ISO/IEC 15944-14 and ISO/IEC 15944-20.
- Standard213 pagesEnglish languagesale 15% off
This document: — specifies a group of structured and inter-related concepts pertaining to traceability as a legal or regulatory requirement in the Open-edi context, in addition to concepts that appear in other parts of ISO/IEC 15944 series these concepts having the characteristics of cultural adaptability through the use of multilingual terms and definitions; — provides additional specifications for Open-edi scenarios and scenario components from the perspective of traceability as required by internal or external constraints in business transactions; — provides a more detailed specification for business transactions regarding aspects of traceability, including refined models of Person, Data and Process in support of the ability for Open-edi to incorporate elements or characteristics of traceability in its information bundles (including their semantic components) and business processes; — realizes specifications and descriptions from the traceability requirements as rules and guidelines, to provide recommendations or guidance on Open-edi practices; and, — provides revised primitive Open-edi scenario templates for traceability, integrating the modifications to the template from other existing parts of ISO/IEC 15944 series. This document can be used by Open-edi implementers (including business modellers and system designers) and Open-edi standard developers in specifying Open-edi scenarios, developing Open-edi related standards, and implementing Open-edi rules and guidelines for Open-edi activities. This document does not specify the FSV aspects of traceability, internal behaviour requirements of an organization, or traceability as a metrological concept. Detailed exclusions to the scope of this document are provided in Annex H.
- Standard60 pagesEnglish languagesale 15% off
This document specifies the fundamental principles governing coded domains, identification and description of the coded domains from the BOV view, the rules governing the rule-base of coded domains, the rules for management of ID codes, rules for specifying Human Interface Equivalents (HIEs) to an ID Code, the relations between the coded domain and controlled vocabularies, the rules governing the registration of coded domains as re-usable business objects, and the IT-enablement of coded domains. The document is applicable to the use of standards, specifications, authority files, etc., of a “codes representing X” nature being used in electronic business transactions among parties engaged in Open-edi, which pertains to flows of information using information bundles which cause pre-defined (or pre-definable) changes in the states of the IT systems of the parties to such electronic data interchanges. Detailed exclusions to the scope of this document are provided in Annex I.
- Standard105 pagesEnglish languagesale 15% off
This document specifies the business operational view of an implementation of an Open-edi Distributed Business Transaction Repository (OeDBTR), building on the principles and concepts defined in ISO/IEC 15944-4 of a business transaction. The repository stores the history of the transitions in states of the economic claim and/or other business entities that happen over the course of a business transaction, and does so for a collection of business events. These business events, comprised of transactions and their states, can be identified unambiguously so as to provide the ability to inspect or query the information at some point after the record has been made. The distributed nature of the repository offers users ubiquitous and robust access to the recorded history. A history of business transactions of market exchanges can be useful in auditing or other memoing-based activities, looking back at the immutable record of the interactions between parties. This document does not specify the Functional Services View of a particular implementation of an Open-edi Distributed Business Transaction Repository. For best performance, candidate technologies would likely exhibit properties of long-term permanence, robust immutability, decentralized access, distributed resilience, and fine-grained addressability.
- Standard21 pagesEnglish languagesale 15% off
This document specifies the architecture of an enterprise canonical model. It defines the abstract model, conceptual model and physical model. This document is applicable to organizations implementing an enterprise-wide interoperability capability. Some implementers can find it useful in more targeted applications (e.g. departmental interoperability, projects).
- Standard18 pagesEnglish languagesale 15% off
This document specifies general trustworthiness and safety requirements applicable to operators of digital platforms within the sharing economy. While this document does not cover system requirements for digital platforms, the document is still beneficial for system development.
- Technical specification15 pagesEnglish languagesale 15% off
This document provides guidelines for sharing economy platform operators when verifying providers, including on-boarding, maintenance, and deactivation. This document applies to both digital platform operators and providers within the sharing economy.
- Technical specification8 pagesEnglish languagesale 15% off
This document specifies the syntax service directories of all parts in the ISO 9735 series.
- Standard73 pagesEnglish languagesale 15% off
This document specifies the elements, among those defined in CMS digital signatures and CAdES digital signatures that enable verification of a digital signature over a long period of time. It does not give new technical specifications about the digital signature itself, nor new restrictions of usage of the technical specifications about the digital signatures which have already existed. NOTE CAdES digital signature is the extended specification of Cryptographic message syntax (CMS), used widely.
- Standard19 pagesEnglish languagesale 15% off
This document specifies the profiling rules of ISO 9735-1 to ISO 9735-9 that allow users of version 3 (ISO 9735:1988 and ISO 9735:1988/Amd.1:1992: Syntax version number: 3) to migrate to version 4 (ISO 9735:1998: Syntax version number: 4) with a minimum effort and cost.
- Standard12 pagesEnglish languagesale 15% off
This document provides general sharing economy principles. It is intended to be used by all types and sizes of organization (e.g. commercial enterprises, government agencies, not-for-profit organizations).
- Standard5 pagesEnglish languagesale 15% off
- Standard5 pagesEnglish languagesale 15% off
This document specifies the elements, among those defined in XAdES digital signatures, that enable verification of a digital signature over a long period of time. It does not give new technical specifications about the digital signature itself, nor new restrictions of usage of the technical specifications about the digital signatures which already exist. NOTE XAdES digital signatures is the widely-used extended specification of “XML-Signature Syntax and Processing”.
- Standard19 pagesEnglish languagesale 15% off
- Standard19 pagesEnglish languagesale 15% off
As a connected standard of ISO 19626-1, this document defines the communication interactions between TCP system components and specifies their detailed interfaces — the processes and the APIs of the TCP system components. It provides the common communication interface for deployment and implementation of the system components, and their functions in a specific technology-neutral way to those who consider applying and establishing a TCP system.
- Standard66 pagesEnglish languagesale 15% off
This document: — examines the basic concepts that have been developed for both cloud computing and Open-edi; — identifies key Open-edi concepts relevant to cloud computing; — identifies key cloud computing concepts relevant to Open-edi; — compares Open-edi model and cloud computing architecture and identifies mappings (similarities in whole or in part) between them using formal semantic modelling techniques.
- Technical report45 pagesEnglish languagesale 15% off
- Technical report45 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 following syntax: UN/CEFACT XML Industry Invoice D16B. 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. Together with this TS a set of validation
artefacts is published, including formalisation of the rules.
In addition, the deliverable shall unambiguously define the code lists and, where applicable, the subset of codes to be used for each
coded element in the model of EN 16931-1 when using the UN/CEFACT XML Industry Invoice D16B syntax as defined in CEN/TS
16931-3-3. The deliverable must guide the user how and where to apply for additions to these code lists. It will be issued as an annex
to the existing text of CEN/TS 16931-3-3:2017
- 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.
- Corrigendum4 pagesEnglish languagesale 10% offe-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 following syntax: UBL 2.1. 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. Together with this TS a set of validation
artefacts is published, including formalisation of the rules.
In addition, the deliverable shall unambiguously define the code lists and, where applicable, the subset of codes to be used for each
coded element in the model of EN 16931-1 when using the UBL 2.1 syntax as defined in CEN/TS 16931-3-2. The deliverable must
guide the user how and where to apply for additions to these code lists. It will be issued as an annex to the existing text of CEN/TS
16931-3-2:2017
- 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.
- 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 CEN Technical Specification (TS) contains the mapping between the semantic data model of an electronic invoice (EN 16931-1) and the following syntax: UN/EDIFACT INVOIC D16B. For each element in the semantic model (including sub-elements or supplementary componentts sucha 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. Together with this TS a set of validation artefacts is published, including formalisation of the rules.
- 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 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: — provides method(s) for identifying, in Open-edi modelling technologies and development of scenarios, the additional requirements in business operational view (BOV) specifications for identifying the additional external constraints to be applied to recorded information in business transactions relating to personal information of an individual, as required by legal and regulatory requirements of applicable jurisdictional domains; — integrates existing normative elements in support of privacy and data protection requirements as are already identified in ISO/IEC 14662 and ISO/IEC 15944-1, ISO/IEC 15944-2, ISO/IEC 15944-4, ISO/IEC 15944-5, ISO/IEC 15944-8, ISO/IEC 15944-9, and ISO/IEC 15944-10; — provides overarching, operational ?best practice' statements for associated (and not necessarily automated) processes, procedures, practices and governance requirements that act in support of implementing and enforcing technical mechanisms which support the privacy/data protection requirements necessary for implementation in Open-edi transaction environments; — focuses on the life cycle management of personal information i.e., the contents of SPIs (and their SRIs) related to the business transaction interchanged via EDI as information bundles and their associated semantic components among the parties to a business transaction. NOTE Privacy protection requirements (PPR) on information life cycle management (ILCM) and EDI of personal information as stated in this document serve as a minimum set of ILCM policy and operational requirements for all recorded information pertaining to a business transaction in particular, as well as ILCM implementation in any organization in general. This document does not specify the technical mechanisms, i.e., functional support services (FSV) which are required to support BOV-identified requirements. Detailed exclusions to the scope of this document are provided in Annex H.
- Standard136 pagesEnglish languagesale 15% off
- Standard136 pagesEnglish languagesale 15% off
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 specifies three business requirements for the visibility of logistics traffic flow based on the use cases and gap analysis in Annex A. It includes 1) LISS network architecture requirements, 2) visibility data interchange requirements between LISSs, and 3) visibility data interface and process requirements for an LISS network. These three business requirements are described further in Clause 6, Clause 7 and Clause 8 respectively. Furthermore, Clause 8 describes the requirement for a guideline for business participants and stakeholders in an LISS network such as logistics information service providers, single window/SSP operators, data providers and logistics data users. This document does not include standardization 1) at the level of logistics devices (areas of standardisation covered by ISO/TC 104, ISO/TC 204), 2) for ships, navigation and marine technologies (areas of standardisation covered by ISO/TC 8), or 3) related to international data exchange such as standards developed, published and maintained by UN/CEFACT, GS1, WCO which are referenced as appropriate in this document.
- Standard24 pagesEnglish languagesale 15% off
- Standard24 pagesEnglish languagesale 15% off
This document defines the requirements about trusted communication in legal, administrative and technical considerations. This document shows a TCP system architecture to guarantee trusted communication and promote trusted services by providing trusted communication evidence as the proof. This document focuses on TCP at the view of 7th application layer of OSI (Open Systems Interconnection) Reference Model. The audiences are the policy makers for IT innovation such as dematerialization, legal experts regarding electronic activities, IT planners for single windows and secure transactions, IT service providers related to distributed networking and ledger, trusted system auditors, trusted communication concerned parties and so on.
- Standard36 pagesEnglish languagesale 15% off
***Access to this CEN and SIST technical publication has been sponsored by the European Commission.***
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 provides a set of requirements, functionality and criteria for ensuring reliability and safety of mobile e-business. The specification of this document covers overall use cases for mobile e-business including simple inquiry of electronic documents, exchange of electronic documents for general transaction and even exchange of contract and payment documents. This can be applied to the most wireless protocols such as 3G, 4G and Wi-Fi, etc. This could be also used in the general mobile e-business area such as logistics, electronic trades, financing, manufacturing and service, and can be referenced by system developers of electronic transaction using mobile devices, mobile network service providers and users.
- Standard29 pagesEnglish languagesale 15% off
This document specifies the elements defined in the international standards of ISO/ITU-T, ETSI and IETF RFC that enable at least a proof of existence of data objects and digital signatures and the preservation of the validity status of digital signatures over a long period of time used in validation. It provides the definitions of the proof of existence (PoE) attributes and clarification of the usage of (external) PoE objects, with digital signatures and trusted time values, which have already existed and can be used by the PoE attributes pointing to (external) PoE objects used in long term signature validation or preservation.
- Standard37 pagesEnglish languagesale 15% off
- Standard37 pagesEnglish languagesale 15% off
This document considers requirements of the eIDAS regulation and use cases for qualified electronic seal creation devices and how these requirements may be met by standards.
These use cases will take into account differences in articles 26 and 36 of eIDAS on (sole) control of the signatory and seal creator on its signature / seal creation data, whilst also recognizing the commonalities.
This may possibly lead to identifying requirements for updates to existing standards.
The proposed table of content is the following:
1 Scope
2 References
3 Terms and definitions
3.1 Terminology
3.2 Abbreviations
4 A Consideration of Relevant Regulatory Requirements
5 Use cases
6 Analysis of features of Standard and Use cases
6.1 EN 419 211-x
6.1.1 Main Features relating to use cases
6.1.2 Applicability to use cases
6.2 EN 419 221-5
6.2.1 Main Features relating to use cases
6.2.2 Applicability to use cases
6.3 EN 419 241-1 / -2
6.3.1 Main Features relating to use cases
7 Summary of Conclusions
- Technical report22 pagesEnglish languagesale 10% offe-Library read for1 day
This document considers requirements of the eIDAS regulation and use cases for qualified electronic seal creation devices and how these requirements may be met by standards.
These use cases will take into account differences in articles 26 and 36 of eIDAS on (sole) control of the signatory and seal creator on its signature / seal creation data, whilst also recognizing the commonalities.
This may possibly lead to identifying requirements for updates to existing standards.
The proposed table of content is the following:
1 Scope
2 References
3 Terms and definitions
3.1 Terminology
3.2 Abbreviations
4 A Consideration of Relevant Regulatory Requirements
5 Use cases
6 Analysis of features of Standard and Use cases
6.1 EN 419 211-x
6.1.1 Main Features relating to use cases
6.1.2 Applicability to use cases
6.2 EN 419 221-5
6.2.1 Main Features relating to use cases
6.2.2 Applicability to use cases
6.3 EN 419 241-1 / -2
6.3.1 Main Features relating to use cases
7 Summary of Conclusions
- Technical report22 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 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
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
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