DIRECTORATE-GENERAL
INFORMATICS
Information systems Directorate
European Commission
e-PRIOR ICD Release Notes
e-Invoicing and e-Ordering project for Public Procurement
Version: / 2.100
Authors:
Revised by:
Approved by:
Public:
Reference Number:
TABLE OF CONTENTS
1.1. Purpose......
1.2. Definitions, Acronyms, and Abbreviations......
1.3. References......
2. About This Release......
2.1. Release information......
2.2. Change Log......
Introduction
1.1.Purpose
The purpose of this document is to provide the summary of changes (improvements, new features, fixes and tasks) in a given release of the Customer Interface Control Document (ICD) of e-PRIOR.
1.2.Definitions, Acronyms, and Abbreviations
See [REF1], Appendix I.
Additional definitions:
e-PRIOR / e-PRocurement, Invoicing and Ordering is the name of the e-Procurement system being developed by DIGIT.ICD / Interface Control Document of e-PRIOR.
Each change will classified as specified in the table below.
Improvements / An enhancement made on the ICD to disambiguate and improve the clarity of the specification.New Features / A new capability of the system.
Fixes / A correction made on the system or in its specification.
Tasks / Generic maintenance work on the specification.
The impact of each changeon the consumers of e-PRIOR’s services will be qualitatively measured as specified in the table below. The key words "MUST", "SHOULD" and "MAY are inspired in the description in RFC 2119.
High / Action must be taken by the consumer of e-PRIOR’s services.MUST To be compliant with the new version of the ICD, the consumer is required to take action.
Medium / Action should be taken by the consumer of e-PRIOR’s services.
SHOULD To be compliant with the new version of the ICD, the consumer is required to understand the implications of the change but does not necessarily need to take action.
Low / Action may be taken by the consumer of e-PRIOR’s services.
MAY To be compliant with the new version of the ICD, the consumer is required to understand the implications of the change but no further action is required.
In any case the service consumer must always evaluate if the change applies to its own implementation of the interface with e-PRIOR.
1.3.References
# / Document / Contents outline[REF1] / Interface Control Documentby DIGIT/B4 / Interface Control Document of e-PRIOR.
2.About This Release
2.1.Release information
Version / 2.100(minor release)Release date (dd/mm/yyyy) / 17/09/2012
2.2.Change Log
2.2.1 Improvements
Artifact Name / Impact / Description of changese-PRIOR_Customer_Interface_Control_Document.doc / Medium / Corrected document states in chapter 4 (End-to-end communication workflows) and added implementation notes.
Updated links to FAQs.
Annexes\002_Data_Dictionary\000_CodeTables\ EC_CodeList.xls / Medium / Updated ResponseCode code list with two missing entries for Credit Note
Annexes\004_XML_Instances\017_ApplicationResponse / Low / Updated ApplicationResponse sample to be more similar to the actual messages currently sent on production.
Annexes\008_FAQ / Low / Made specific references to DIGIT more generic.
Moved FAQs to Supplier and Customer folder.
Annexes\008_FAQ\Customer_FAQs\FAQ04_WSDL_Location.doc / Low / Added FAQ for Customer WSDL and service endpoints.
Annexes/008_FAQ/Supplier_FAQs/FAQ07_ValidAttachmentTypes.doc / Low / Corrected MIME type for JPG files from image/jpg to image/jpeg.
2.2.2 New Features
No new features were added.
2.2.3 Fixes
No fixes were made.
2.2.4 Tasks
No tasks were implemented.
e-PRIOR ICD Release Notes - e-Invoicing and e-Ordering project for Public ProcurementPage 1
Document Version 2.000 dated 1/08/2012