The ESPD Exchange Data Model is the technical representation of the legal European Single Procurement Document. It is used to support interoperability between ESPD services provided all over Europe.
To have a comprehensive view of what ESPD-EDM is and how to use it, we strongly recommend visiting the ESPD-EDM Wiki, that aims to be the Unique Access Point for all of its resources: documentation, tools, assets, etc.
Dear ESPD implementation community,
We are happy to inform you about the future release of ESPD EDM version 3.0.0 on March 2021
This new version of the ESPD-EDM aims to align the logic to eForms for future alignment and their joint usage in procurement. With the same purpose, the ESPD-EDM has updated the UBL version to 2.3. For more information regarding the release, please refer to the release notes.
This version is currently under development and its precise release date is yet to be announced. v2.1.1 focuses mainly on correcting minor errors and implementing the backwards-compatible-changes suggested by Member States and other Stakeholders in the ESPD-EDM in the GitHub issues workspace.
ESPD nomenclature for, now former, ESPD Regulated and ESPD Self-Contained will be changed to ESPD Basic and Extended, respectively.
The ESPD EDM version 2.1.0 is now released and focuses, mainly, on the improvement of the ESPD-SELF-CONTAINED features. All the changes introduced in this new version were based on the inputs from Member States and other Stakeholders collected through the GitHub issues workspace. For further details please read the release notes.
The ESPD EDM version 2.0.2 addresses bugs fixed on the basis of the received comments on GitHub. For further details please read the release notes. The release contains a definition of all relevant business rules and corresponding schematron files to validate Regulate and Self-Contained ESPD Request and Response XML instances (including the validation of the criteria taxonomy). The corresponding TestBed for version 2.0.2 has been set up. The specifications for version 2.0.2 contain an updated distribution of the ESPD Exchange Data Model and include a corresponding implementation guideline which clarifies the ESPD validation architecture in Annex I. Also, the BIS 41 – ESPD version 2.0.2 was updated accordingly.
A release of criteria taxonomy file errata [ESPD EDM version 1.0.2] was necessary as the documentation on the criteria taxonomy was not updated to reflect the changes that were made to the Commission ESPD service up until July 2017. All corrections relate to the Criteria Data Flows and result in a revision of the criteria taxonomy for version 1.0.2 (revisions are marked within the sheet). No other change was done to the ESPD EDM version 1.0.2. The revisions should therefore have no impact on all current ESPD services based on v1.0.2 but we recommend using the revised criteria taxonomy to approve the correct Criteria Data Flows.
Bug fixes detected in the previous versions; change requests related to these bugs were collected in this Github Issues space (see Issues for the details. See also the Release Notes above and the 'dist/rn' folder for details on those issues related to v2.1.0 that have been closed).
The goal of version 2.0.0 is that the ESPD-EDM is self contained. Meaning that public buyers can specify directly in their ESPD services criteria instead of defining them in the procurement document or the notice. Examples are that the public buyer can specify the number of years needed for the turnovers, the financial ratios needed for the procedure or that they can specify certificates needed. Something else that will be implemented in version 2.0.0 is the possibility to weight criteria which is important to reduce the number of participants in a procedure. Issues for this release are in https://github.com/ESPD/ESPD-EDM/issues.
Version 1.0.2 has no impact on current implementation. It fixes the issue https://github.com/ESPD/ESPD-EDM/issues.
Very first version of the ESPD-EDM. Partially based on UBL 2.1.
The recommended way to get started using the exchange-model in a Java project is with a dependency management system.
<dependency>
<groupId>eu.europa.ec.grow.espd</groupId>
<artifactId>exchange-model</artifactId>
<version>1.0.2</version>
</dependency>dependencies {
compile("eu.europa.ec.grow.espd:exchange-model:1.0.2")
}Please note that this version requires Java 8
<dependency>
<groupId>eu.europa.ec.grow.espd</groupId>
<artifactId>exchange-model3</artifactId>
<version>3.0.0</version>
</dependency>Version 3 of the Exchange Model has a different artifactId, i.e. exchange-model2, in order to support
the usage of both versions at the same time inside a Java Maven project.
In order to use the snapshot version, you might have to enable the Maven snapshot repository in your pom.xml.
<repositories>
<repository>
<id>oss-sonatype</id>
<name>oss-sonatype</name>
<url>https://oss.sonatype.org/content/repositories/snapshots/</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
</repositories>The ESPD-EDM is made publicly available through Github.
- If you just want to browse or access the model, you don't need to be registered in Github.
- If you want to create issues concerning the ESPD-EDM you have to be a registered user in Github. Please assign all issues in this repository to paulakeen
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent