ESPD-EDM version 3.3.0

The ESPD-EDM version 3.2.0 was focused mainly on correcting minor errors in the data structure and the codelists, as suggested by the Member States and stakeholders via the GitHub repositories issues workspace.
The ESPD-EDM version 3.3.0 focuses also on correcting other minor errors in the data structure and the codelists.

ESPD-EDM Criterion file - Data Structure

Several issues have been resolved related to the data structure of the ESPD-EDM Criterion (taxonomy) file.

• Fix Jira issue - "Update criterion files with codes of EU Vocabularies for v3.3.0

  • In criterion C27, the element code "autorisation" has been replaced with the code "authorisation".
  • In criterion C23, the element code "misinterpr" has been replaced with the code "misrepresent".
  • In criterion C23, the Name contents have been updated as well. "Guilty of misinterpretation" has been replaced by "Guilty of misrepresentation".
  • The worksheet "EG-Misinterpretation" has been renamed "EG-Misrepresentation".

• Fix GitHub issue #368 - Typo's in taxonomy

  • Typo errors such as double spaces and duplicated words, as well as spelling issues, have been fixed.

ESPD-EDM XSLT files

The following changes have been performed related to the ESPD-EDM XSLT files:

• Updating attributes values in the xslt files for the xml samples
  * SchemeVersionID value is “3.3.0” and not “3.2.0”.
  * ListVersionID value is “3.3.0” and not “3.2.0”.
  * The right ESPD version in comments is ESPD-V3.x.x

• Updating the xslt file "ESPDRequest-Annotated.xslt" (missing element/attribute or incorrect value)
  * Fix GitHub issue #387 - Improper listVersionID attribute value in cbc:DocumentTypeCode: cac:Language/cbc:LocaleCode/@listVersionID for the codelist "language"
  * Fix GitHub issue #387 - Improper listVersionID attribute value in cbc:DocumentTypeCode: cbc:ExpectedCode/@listVersionID for the codelist "eo-role-type"
  * cac:Language/cbc:LocaleCode/@listAgencyID for the codelist "language"
  * cbc:ExpectedCode/@listAgencyID for the codelist "occupation"

• Updating the xslt file "From-REQUEST-to-RESPONSE.xslt" (missing element/attribute or incorrect value)
  * Fix GitHub issue #387 - Improper listVersionID attribute value in cbc:DocumentTypeCode: cbc:ResponseCode/@listVersionID for the codelist "eo-role-type"
  * Fix GitHub issue #387 - Improper listVersionID attribute value in cbc:DocumentTypeCode: cbc:ResponseCode/@listVersionID for the codelist "country"
  * Fix GitHub issue #390 - PERCENTAGE Questions: Artifact Examples and Shematrons Inconsistency: cbc:ResponseQuantity/@unitCode replaced by cbc:ResponseNumeric/@format
  * cbc:ResponseCode/@listAgencyID for the codelist "occupation"

• Updating the xslt file "EconomicOperatorData.xslt" (missing element/attribute or incorrect value)
  * Fix GitHub issue #387 - Improper listVersionID attribute value in cbc:DocumentTypeCode: cac:Party/cbc:IndustryClassificationCode/@listVersionID for the codelist "economic-operator-size"

• Updating the xslt file "Legislation.xslt" (missing element/attribute or incorrect value)
  * Fix GitHub issue #387 - Improper listVersionID attribute value in cbc:DocumentTypeCode: cac:Language/cbc:LocaleCode/@listVersionID for the codelist "language"
  * cac:Language/cbc:LocaleCode/@listAgencyID for the codelist "language"

• Converting samples from Excel to XML format with the Updated XSLT

The resulting updated XSLT files have been used to generate the XML samples available in the GitHub folder xml-examples.

Code Lists

ESPD version has been updated in the technical codelist files to match the current version (specific files can be found in the folder codelists/gc), for tags: Version, CanonicalURI, CanonicalVersionURI, LocationURI.

The label "ESPD-EDMv3.3.0" has been added in the related sheet "ProfileExecutionID" (in the last row of the table) of the excel file ESPD-CodeLists.xlsx .

• Fix GitHub issue #387 - Improper listVersionID attribute value in cbc:DocumentTypeCode
  This github issue has led to a broader review of the codelists related to the value of the attribute "listVersionID". This attribute value was indeed incorrect for several codelists (DocRefContentType, Language, EoRoleType, Country, EconomicOperatorSize) in various artefacts (CodeLists, XSLT, XML, Schematron). The updates have been made at different levels: XSLT files and Schematron files.
  • XSLT files: RootElements-Annotated.xslt, From-REQUEST-to-RESPONSE.xslt, ESPDRequest-Annotated.xslt, Legislation.xslt, EconomicOperatorData.xslt, ContractingAuthorityData-RequestResponse.xslt
  • Schematron files: "./common/sch/01-ESPD-common-cl-attributes.sch", "./common/sch/01-ESPD-codelist-values.sch", "./common/sch/04-ESPD-common-other-br"

The corresponding generic code files and the corresponding XML files have been generated.

Validation - Interoperability Testbed

Update of Interoperability Testbed ESPD validator

• Fix GitHub issue #387 - Improper listVersionID attribute value in cbc:DocumentTypeCode

  • Schematron files: "./common/sch/01-ESPD-common-cl-attributes.sch", "./common/sch/01-ESPD-codelist-values.sch", "./common/sch/04-ESPD-common-other-br"

• Fix GitHub issue #390 - PERCENTAGE Questions: Artifact Examples and Shematrons Inconsistency

  • Schematron file: "./common/sch/03-ESPD-resp-criterion-br.sch"

• Generating the ESPD validator, for the Request and the Response, for v3.3.0 with the latest entry files (generic code files for codelists, xml files for the ESPD Request and the ESPD Response).

Online documentation - espd-docs GitHub Repository

Update of the online documentation available at Ted Developer Docs.

Attribute value updates

Attribute value for ESPD version has been updated all over the online documentation.

• version value for attributes schemeVersionID, listVersionID.

Attribute value for "listVersionID" has been updated all over the online documentation for the various codelists.

• following the fix of GitHub issue #387 .

Datatype "Percentage" related to UBL element "ResponseQuantity" has been updated to be related to UBL element "ResponseNumeric" all over the online documentation.

• following the fix of GitHub issue #390 .

Code value or text related to "autorisation" has been updated to "authorisation" all over the online documentation.

Code value or text related to "misinterpr" or "misinterpretation" has been updated to "misrepresent" or "misrepresentation" all over the online documentation.

Release Notes

Release Notes have been updated for the online documentation.

Readme file

The Readme file for v3.3.0 has been updated as well.

ESPD-EDM version 3.2.0

The ESPD-EDM v3.1.0 was focused on the ESPD-EDM changes and fixes mostly related to the data structure. The ESPD-EDM version 3.2.0 focuses mainly on correcting minor errors in the data structure and the codelists, as suggested by the Member States and stakeholders via the GitHub repositories issues workspace.
The list below details exhaustively every change introduced since the publication of the previous release (3.1.0) of the ESPD-EDM.

ESPD-EDM Criterion file - Data Structure

Several issues have been resolved related to the data structure of the ESPD-EDM Criterion (taxonomy) file.

• Indentation Issues and elements closure in the Criterion Excel file

  • Indentation has been corrected in criteria C40, C41, C42, C43, C44, C45, C46, C47 for element “./RG1/RSG1/QSG1”.
  • Closure element issue has been corrected in criterion C50 for element "./RG1/RSG1".

• Fix GitHub issue #371 - "Special requierements check" criteria has closing tags for subgroups on the same levels in taxonomy

  • Indentation issue is fixed in criterion 48.

• Fix GitHub issue #340 - General yearly turnover - differences in taxonomy and mock-ups from ESPD-EDM

  • Cardinality is fixed to 1 in line 11 of criterion 29
  • Cardinality is fixed to 1..n in line 14 of criterion 29

• Fix GitHub issue #368 - Typo's in taxonomy

  • Typo errors such as double spaces and duplicated words, as well as spelling issues, are fixed.

• Fix GitHub issue #369 - The same "ElementUUID" is associated to different Question Subgroup.

  • A new UUID is generated and assigned to criterion 34 (line 22): 78b2e0e6-1bfe-43f5-a061-d9cf4e6e6ecc.

• Fix GitHub issue #374 - Missing cardinalities values in ESPD-Criterion.xlsx v3.1.0

  • Question subgroups with no values have been populated to 1 for all the occurrences of the following UUID: 0e50931d-4d39-4f1d-9fdc-b2cf16c0807a, 9b3a04ff-e36d-4d4f-b47c-82ad402b9b02 and 5fe93344-ed91-4f97-bcab-b6720a131798.

• Fix GitHub issue #375 - Technical Handbook v3.1.0 inconsistencies - cbc:CustomizationID is missing from root element table in section 2.4

  • Element "cbc:CustomizationID" was removed from the xml samples, the documentation (except an image in section 2.3), and the conceptual model, in version v3.1.0 of the ESPD-EDM. In this current version v3.2.0, this element has been removed from the documentation image where it appeared in section "2.3 ESPD Request Cardinalities". Its re-introduction in all the ESPD artefacts will be discussed for a future ESPD-EDM release.
  • Element "cbc:ProfileID" was removed from the xml samples and from the documentation (except an image in section 2.3), but not from the conceptual model, in version v3.1.0 of the ESPD-EDM. In this current version v3.2.0, the element "cbc:ProfileID" has been removed from the conceptual model for consistency purpose. This element has been also removed from the documentation image where it appeared in section "2.3 ESPD Request Cardinalities". Its re-introduction in all the ESPD artefacts will be discussed for a future ESPD-EDM release.
  • Element "cbc:ProcedureCode" was removed from the conceptual model but not from the xml samples and the documentation, in version v3.1.0 of the ESPD-EDM. In this current version v3.2.0, the element "cbc:ProcedureCode" has been put back in the conceptual model for consistency purpose with a "Dummy" value for the codelist attribute "listID" and also for future alignment with eForms.

ESPD-EDM XSLT files

The following changes have been performed related to the ESPD-EDM XSLT files:

• Fix GitHub issue #378 - Clarification on date and time format : a wrong time format with miliseconds in the “issue date” column of the XML example has been fixed to remove these miliseconds.

• Updating attributes values in the xslt files for the xml samples
  * SchemeVersionID value is “3.2.0” and not “3.1.0”.
  * ListVersionID value is “3.2.0” and not “3.1.0”.
  * The right ESPD version in comments is ESPD-V3.x.x

• Updating the xslt file "ContractingAuthorityData-RequestResponse.xslt" (missing element/attribute or incorrect value)
  * Country listVersionID = 20220928-0
  * cbc:EndpointID/@schemeID

• Updating the xslt file "EconomicOperatorData.xslt" (missing element)
  * EconomicOperatorRole, RoleCode, ID, Name, IndustryClassificationCode, IdentificationCode

• Updating the xslt file "From-REQUEST-to-RESPONSE.xslt" (missing element/attribute)
  * "cbc:ResponseID"
  * "cac:Evidence/cbc:ConfidentialityLevelCode"
  * "cac:Evidence/cbc:ConfidentialityLevelCode/@listVersionID"

• Converting samples from Excel to XML format with the Updated XSLT

The resulting updated XSLT files have been used to generate the XML samples available in the GitHub folder xml-examples.

Code Lists

ESPD version has been updated in the technical codelist files to match the current version (specific files can be found in the folder codelists/gc), for tags : Version, CanonicalURI, CanonicalVersionURI.

The label "ESPD-EDMv3.2.0" has been added in the related sheet "ProfileExecutionID" (in the last row of the table) of the excel file ESPD-CodeLists.xlsx .

• Fix GitHub issue #380 - Question regarding the correct listID values
  This github issue has led to a broader review of the codelists related to the value of the attribute "listID". This attribute value was indeed missing or incorrect for several codelists in various artefacts (XSL, Generic code, XSLT, XML, Schematron). The updates have been made at three different levels : XSL file, XSLT files and Schematron file.

  • XSL file : excel-to-gc-multilang-v1.0.xsl
  • XSLT files : RootElements-Annotated.xslt, From-REQUEST-to-RESPONSE.xslt, ESPDRequest-Annotated.xslt, Legislation.xslt, EconomicOperatorData.xslt, Request-Root-Elements.xslt, BASIC-RootElements-annotated.xslt
  • Schematron file : "./common/sch/01-ESPD-common-cl-attributes.sch"

• Fix GitHub issue #348 - Two different occupations have same ID in occupations codelist

  • The latest version of the codelist "Occupation" has been downloaded from EU Vocabularies.
  • All the related artefacts ( ESPD-Codelists, XSLT files) have been updated with the corresponding new version.

• Fix GitHub issue #325 - Incorrect element code in ESPD-criterion.xlsx v3.0.1 for Criterion #27

  • The latest version of the codelist "Criterion" has been downloaded from EU Vocabularies.
  • All the related artefacts ( ESPD-Codelists, XSLT files) have been updated with the corresponding new version.

The corresponding generic code files and the corresponding XML files have been generated.

Validation - Interoperability Testbed

Update of Interoperability Testbed ESPD validator

• Generating the ESPD validator, for the Request and the Response, for v3.2.0 with the latest entry files (generic code files for codelists, xml files for the ESPD Request and the ESPD Response).

Online documentation - espd-docs GitHub

Update of the online documentation available at Ted Developer Docs.

Attribute value updates

Attribute value for ESPD version has been updated all over the online documentation.

• version value for attributes schemeVersionID, listVersionID.

Attribute value for "listID" has been updated all over the online documentation.

• following the fix of GitHub issue #380 .

Release Notes

Release Notes have been updated for the online documentation as well.

v3.1.0

The ESPD-EDM v3.0.1 was focused on the ESPD-EDM online documentation updates. This current version v3.1.0 provides changes and fixes suggested by the Member States and stakeholders via the GitHub repositories issues workspace, mostly related to the data structure.

The list below details the updates included in this release.

ESPD-EDM conceptual model

• .eap and .xmi files with two views and diagrams, allowing a holistic representation of the model (business and technical perspective):

  • Business oriented view (BOV) aimed at facilitating the understanding of the model and the business context, with references to the technical model, and;
  • Technically oriented view (TOV) providing an UBL-based schema with references to business-oriented view and aligned with the eProcurement ontology.

• HTML version of the UML conceptual model. If you do not want to download the folder to view the model you can view it on the documentation page under ESPD-EDM CONCEPTUAL MODEL HTML.

The changes applied to the ESPD-EDM Conceptual model are:

• Update of descriptions in both views to align them to UBL 2.3 and the procurement Ontology respectively.
• Fix errors: typos

ESPD-EDM Criterion file - Data Structure

Several issues have been resolved related to the data structure of the ESPD-EDM Criterion file.

• Zooming, Bolding first 2 lines, Missing the first line, and Indentation Issue in the Criterion Excel file

  • The following Criterion Excel sheets have been zoomed in at 100%: “SC-Abilities_1 (Persons)” that contains C41, “SC_Abilities_3 (Education)” that contains C47.
  • Title rows 1 and 2 have been put in bold for the following sheets: “SC-Professional_risk_insurance” which contains C35, “SC-Other_economic_or_financial” which contains C36.
  • Indentation issue has been corrected:  in criteria related to turnover C29, C30, C31, C32 for element: “./RG1/QSG4”.  
  • Numbered first line has been added in the Criterion Excel file for Criterion C65 SC SME.

• UUID and Cardinality to be removed from closing Requirement Group element

  • The UUID and the Cardinality have been removed from the closing Requirement Group of criterion C30.

• Confusing Evidence Group or Subgroup relation with Question Subgroup (QSG) in criteria

  • In criterion C36, the evidence subgroup has been moved as a child of the parent Requirement Subgroup for the 2 related Question Subgroups. So, it is common to the 2 related QSG.
  • In criteria C37, C38, C39 (SC-References), the Evidence Subgroup has been kept as linked to "Reference".

• Updating description of Requirement in criteria C49, C50

  • In the description of requirement 1, there was a misspelling of the word "minimum" which was written "minum" in criteria C49 and C50. The misspelling has been corrected.

• Why cardinality of the Requirement "Business Domain" of criterion C31 spec-aver-to is multiple?

  • Cardinality of Requirement "Business Domain" of criterion C31 spec-aver-to should be aligned with the cardinality of Requirement "Business Domain" of criterion C32 spec-year-to.
  • Cardinality of Requirement "Business Domain" of criterion C31 spec-aver-to has been updated to 1.

• Legislation UUID)

  • Legislation UUID should be different all over the Criterion Excel file since it is a structural terminal element that holds value.
  • The Legislation UUID is now different for each criterion in the criterion excel file.

• Fix GitHub issue #287 - Part IV: Selection criteria, C: Technical and professional ability (CA`s)

  • At the user´s request, a new optional requirement section has been added to criterion 51 with cardinality 0..n.
  • A new UUID has been generated for this new requirement section: 75b14cf3-c30f-4b8f-b9ab-549ff5ba595a

• Fix GitHub issue #320 - Duplicate "Question Group UUID" in the same Criterion and the Question Groups have different structures

  • UUID used in Criterions 40 and 41 for question subgroup structures: "Technician" and "Technical body" were the same but the structures were different.
  • A new UUID has been generated in Criterion 40 and 41 for structure "Technical body" to avoid this issue: 70e28455-d0e1-47e7-9caa-ead3b7df7644.

• Fix GitHub issue #326 - EVIDENCE_IDENTIFIER with different cardinality

  • EVIDENCE_IDENTIFIER: 0a166f0a-0c5f-42b0-81e9-0fc9fa598a48 cardinality fixed to 1..n in criteria 40 and 41 in ESPD-criterion.xlsx file

• Fix GitHub issue #327 - Groups with same UUID and different cardinality

  • 10822ddd-9ba6-42d5-9339-de0845aeafc9: different cardinality are 1 and 1..n: different structures, a new UUID has been generated and assigned to criterion 50: add786b6-7e75-4303-8b9a-3d477331abd9.
  • 289f39b3-2a15-421a-8050-a29858031f35: different cardinality are 1 and 1..n: the issue no longer exists since version 3.0.1 and older versions are not under support, so no changes are necessary.
  • 5f9f09f7-f701-432c-9fdc-c22c124a74c9: different cardinality are 1 and 0..1: cardinality is wrong in criterion 22, it has been updated to 1.
  • 74e6c7b4-757b-4b40-ada6-fad6a997c310: different cardinality are 0..1 and [empty]: empty cardinality is wrong in criteria 18 and 19, it has been updated to 0..1.
  • 9026e403-3eb6-4705-a9e9-e21a1efc867d: different cardinality are 1 and 0..1: cardinalities 0..1 in criteria 40 and 41 are wrong, have been updated to 1
  • a53561d5-6614-4dbe-987e-b96f35387f46: different cardinality are 0..n and 1..n: cardinality is wrong in criterion 26, it has been updated to 0..n
  • c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16: different cardinality are 1 and 1..n: cardinality is correct as this criterion is for Yearly Turnovers (more than one value, usually 3 years) while Average Turnover is just one single value, so no changes are necessary.
  • cc1da737-6c4e-4f4e-821d-c260029058f6: different cardinality are 0..1 and 1..n: UUID has been removed as it´s a structure close line.

• Fix GitHub issue #333 - Same requirement group UUID with different content

  • The same UUID: 53c9aad8-dc80-48f8-85d9-755c2aab8e95 is re-used for exclusion grounds (criterions 7 and 8) and selection criteria (criterions 37, 38 and 39) and they have different structures in the file, therefore, one of the two requires a different UUID.
  • A new UUID has been generated: c7d60cb5-b6fc-4e1a-a6b0-e0d91a09c80a and assigned to the criterions 7 and 8 that were previously using the UUID: 53c9aad8-dc80-48f8-85d9-755c2aab8e95.

• Fix GitHub issue #338 - Invalid text in Taxonomy in SC-Professional_risk_insurance tab

  • There was an error in Criterion 25 (tab SC-Professional_risk_insurance tab): the values in the Codelist column needed to be moved to the Comment column, one to the right.

• Fix GitHub issue #340 - General yearly turnover - differences in taxonomy and mock-ups from ESPD-EDM

  • it was missing an intermediate requirement that represents the selection of "threshold per year".
  • It has been added in the data structures a new requirement that allows selecting when it should apply per year or all years together.
  • If it is per year, the question_subgroup that has 1..n and it is marked in yellow, would be replicated as many times as years asked.
  • Since no other data structure is equal, a new UUID has been generated to cover this data structure.

• Fix GitHub issue #347 - Missing "0000.0" code in Occupation codelist

  • Updating the data structure by removing the requirement "other register" in criterion C25 SC prof-regist.
  • The Note where the code "0000.0" was mentioned has been deleted. The note was in the online documentation "Technical handbook", section "Selection criteria", subsection "Suitability" and finally sub-subsection "XML example".

• Fix GitHub issue #350 - SC Suitability: EO side. Question_subgroup: Your answer?

  • There was a mistake in the cardinality of the question subgroup, which should be 1.
  • Although it is possible to have several requirement groups within criteria within Suitability, prof-regist allowing here to define different occupations, we can have only one set of answers per requirement group meaning per occupation.

ESPD-EDM XSLT files

• Refactoring the XSLT files

  • Generation of UUID only in the main XSLT files available in the GitHub folder ODS-Data-Structures-to-ESPD-XML
  • Different use cases for exclusion ground and selection criteria
  • Refactoring of templates (or functions) position in the XSLT files

• Updating attributes values in the xslt files for the xml samples

  • The value of some attributes is not correct (schemeAgencyID, schemeVersionID, listAgencyID, listVersionID) and hence has been updated:

    • SchemeAgencyID value is “OP” and not “EU-COM-GROW/EU-COM-OP” for groups or subgroups ID.

    • SchemeAgencyID value is “XXXESPD-SERVICEXXX” (a given espd-service) and not “EU-COM-GROW/EU-COM-OP for questions and requir...

v3.0.1

The ESPD-EDM v3.0.0 focuses on the ESPD-EDM alignment with eForms. This version provides changes and fixes suggested by the Member States and stakeholders via the GitHub repositories issues workspace.

The list below details the updates included in this release.

ESPD-EDM GitHub

• __ESPDTeam__: contains files for ESPD Team internal use in maintenance tasks of the ESPD-EDM;
• codelists: contains the different code lists used in ESPD in Genericode format and the criterion structure definition.
• conceptual-model: contains the UML conceptual model of the ESPD in .eap, .xmi and HTML format.
• java-library: contains the XML schemas used to generate the JAXB annotated Java classes.
• ubl-2.3: contains a redistribution package from UBL 2.3.
• validation: contains business rules validation files for Schematron and Testbed.
• xml-examples: contains default ESPDRequest and ESPDResponse xml samples and the criterion xml schema.

ESPD-EDM conceptual model

• .eap and .xmi files with two views and diagrams:

  • Business oriented view (BOV) aimed at facilitating the understanding of the model and the business context, with references to the technical model, and;
  • Technically oriented view (TOV) providing an UBL based schema with references to business oriented view and aligned with the eProcurement ontology.

• HTML version of the UML conceptual model.If you do not want to download the folder to view the model you can view it on the documentation page under ESPD-EDM CONCEPTUAL MODEL HTML.

Code Lists

EU Vocabularies code lists version updated (specific files can be found in folder codelists/gc)

• access-right version updated to 20211208-0.
• country version updated to 20211208-0.
• criterion version updated to 20210616-0.
• currency version updated to 20211208-0.
• economic-operator-size version updated to 20210317-0.
• eo-role-type version updated to 20211208-0.
• language version updated to 20211208-0.

Interoperability Testbed

Update of Interoperability Testbed ESPD validator

• Updated v3.0.1 on the validator.
• Removed v3.0.0 from the validator.

Online documentation

Documented handbook migration to Ted Developer Docs.

Corrected errors on cardinalities and element naming on the Technical Handbook as follows:

1. Section 2.3 ESPD Request cardinalities

   • Removed sentence 'Notice that ESPD-EDM does not change anything else from the UBL-2.3 Schema.' because it did not help understanding what is kept from UBL-2.3 and what is changed.

   • Figure 12. ESPD-EDM 'QualificationApplicationRequest', UML diagram

     • cac:EconomicOperatorParty
       • Component: removed because it is not used in the ESPD Request.
       • cac:ProcurementProject
       • Component: replaced by cac:ProcurementProject/cbc:Description in alignment with eForms.
     • cac:ProcurementProjectLot
       • Component: replaced by cac:TenderingCriterion/cac:ProcurementProjectLotReference/cbc:ID.
       • Cardinality: updated from 1..n to 0..n.

   • cbc:QualificationApplicationTypeCode

     • Component: removed because it is not used in ESPD-EDM v3.0.x.

   • cbc:WeightScoringMethodologyDescription

     • Component: removed because it is not used in ESPD-EDM v3.0.x.

   • cbc:WeightingType

     • Component: removed because it is not used in ESPD-EDM v3.0.x.

2. Section 2.4 Root elements

   • Table 5. Class QualificationApplicationRequest, components required by the ESPD-EDM
     • cac:ProcurementProject
       • Component: replaced by cac:ProcurementProject/cbc:Description in alignment with eForms.
       • Type: updated from Associated class to Text in alignment with eForms.
       • Cardinality: updated from 0..1 to 1 according to Figure 12. ESPD-EDM 'QualificationApplicationRequest', UML diagram.
       • Requirement: updated from 'This information is not required for the ESPD 3.0.0 since the information related to the procedure will come from eForms.' to 'This element is required in the ESPD, however it should be identical to that provided in eForms. In general the corresponding eForm should feed the corresponding ESPD with the corresponding data.'.
     • cac:ProcurementProjectLot
       • Component: replaced by cac:TenderingCriterion/cac:ProcurementProjectLotReference/cbc:ID.
       • Type: updated from Associated class to Identifier.
       • Cardinality: updated from 1..n to 0..n.
     • cbc:ProcedureCode
       • Cardinality: updated from 0..1 to 1 according to Figure 12. ESPD-EDM 'QualificationApplicationRequest', UML diagram.

3. Section 2.5 Lot Management

   • cac:ProcurementLotReference
     • Element replaced by cac:ProcurementProjectLotReference.

4. Section 2.6 EU and notice publications

   • XSD Schema
     • cac:AdditionalReferenceDocument
       • Component: replaced by cac:AdditionalDocumentReference.
   • Table 6. Reference to additional documents, expected elements
     • cac:AdditionalDocumentReference
       • Path: replaced /QualificationApplicationRequest/cac:AdditionalReferenceDocument by /QualificationApplicationRequest/cac:AdditionalDocumentReference.
   • Table 7. External Reference
     • cac:AdditionalDocumentReference
       • Path: replaced /QualificationApplicationRequest/cac:AdditionalReferenceDocument/cac:Attachment/cac:ExternalReference by /QualificationApplicationRequest/cac:AdditionalDocumentReference/cac:Attachment/cac:ExternalReference.

5. Section 2.7 Contracting Body

   • Table 8. Contracting body, expected elements

     • cac:ContractParty
       • Component: replaced by cac:ContractingParty according to Figure 11: QualificationApplicationRequest-2.3 main elements..

   • Table 9. Contracting body party, expected elements

     • cac:PartyIdentification/cbc:Identifier
       • Component: Replaced by cac:PartyIdentification/cbc:ID because cac:PartyIdentification/cbc:Identifier does not exist in UBL-2.3.
       • Cardinality: Updated from 0..1 to 1.
       • Requirement: updated from 'More than one identifier can be specified. When possible use the VAT identification of the contracting body (see the VIES platform for a EU cross-border national VAT number verification system). ' to 'When possible use the VAT identification of the contracting body (see the link:https://ec.europa.eu/taxation_customs/vies/[VIES] platform for a EU cross-border national VAT number verification system). When not possible a different identifier may be used.' because previous text was ambiguous.

6. Section 2.8. Service Provider

   • Table 38. Service provider, expected elements
     • cac:PostalAddress/cac:Country/cbc:IdentificationCode
       • Type: updated from Identifier to Code.

7. Section 3. Common aspects for criteria

   • Figure 33. Criterion - UML diagram
     • Updated wrong cardinalities 1.... to 1..* to fix the typo. Cardinalities corrected are: cac:TenderingCriterionPropertyGroup, cac:TenderingCriterionProperty and cac:ProcurementProjectLotReference.
     • cac:EconomicOperatorParty
       • Component: removed because it is not used in the ESPD Request.
     • cac:ProcurementProject
       • Component: replaced by cac:ProcurementProject/cbc:Description in alignment with eForms.
     • cac:ProcurementProjectLot
       • Component: removed because it is replaced by cac:TenderingCriterion/cac:ProcurementProjectLotReference in the same figure.
     • cac:TenderingCriterion/cac:ProcurementProjectLotReference
       • Cardinality: update from 1..n to 0..n.
     • cbc:QualificationApplicationTypeCode
       • Component: removed because it is not used in ESPD-EDM v3.0.x.
     • cbc:WeightScoringMethodologyDescription
       • Component: removed because it is not used in ESPD-EDM v3.0.x.
     • cbc:WeightingType
       • Component: removed because it is not used in ESPD-EDM v3.0.x.

8. Section 3.1 General behavior

   • Table 20. Criterion, expected elements
     • cac:ProcurementProjectLotReference
       • Type: updated from Text to Class.
       • Cardinality: updated from 1..n to 0..n.

9. Section 3.2 Legislation

   • Table 21. Legislation, expected elements
     • cbc:ID
       • Component: added.
     • cbc:Description
       • Type: updated from Code to Text.
     • cbc:LegislationTitle
       • Component: replaced by cbc:Title.

10. Section 3.4 Properties

    • Table 23. Properties, expected elements
      • cbc:ExpectedAmount
        • Component: added.
      • cbc:ExpectedDescription
        • Component: added.

11. Section 5.1 Lot Management approach for Selection Criteria

    • Text updated from 'The buyer may specify the criteria that each selection criteria apply by using the element cac:ProcurementProjectLotReference that includes cbc:TenderingCriterion.' to 'The buyer may specify the criteria that each selection criteria apply by using the element cac:TenderingCriterion that includes cac:ProcurementProjectLotReference.'.
      *...

v3.0.0

The ESPD-EDM v3.0.0 focuses on the ESPD-EDM alignment with eForms. This version provides changes and fixes suggested by the Member States and stakeholders via the GitHub repositories issues workspace.
The list below details the updates included in this release.

Online documentation

• Online documentation has been split in business and technical documentation to give a clearer view of each ESPD-EDM domain.

• ‘Business Handbook’ provides business domain information for the ESPD-EDM to help non-technical audiences to better understand ESPD-EDM and its context.

• ‘Technical Handbook’ provides information related to the implementation of the ESPD-EDM and its technical aspects.

TOOP Requirements in ESPD-EDM (UBL2.2) Schema

A mapping between TOOP and UBL2.3 Schema has been made and tested. For more information, please refer to specific section on the online documentation. You can also access issue #277 for a detailed discussion of this topic.

Code Lists

Code lists have been updated for a closer alignment between ESD-EDM and eForms. Some code lists have been removed because the related information is available in eForms and the information can be gathered from eForms’ notices and placed into the proper placeholder.

Code lists removed:

• BidType
• ProcedureType
• ProjectType
• ServicesProjectSubType
• LegislationType
• EvaluationMethodType (version 3.0.0 of the ESPD does not include weights, in order to keep the model as simple as possible)
• CPVCodes

Code lists from EU Vocabularies used in ESPD-EDM:

• country
• currency
• economic-operator-size
• language

A new code list has been added for the requirement of being enrolled in a professional register (criterion #25 Suitability I ‘Abilities’ – “prof-regist”) based on ESCO:

• Occupation

ESPD Criteria Data Structures (former ESPD Criteria Taxonomy)

Criteria Taxonomy has been renamed to criterion. The BASIC model present in ESPD-EDM v2.1.1 has been removed and only one model based on ESPD-EDM v2.1.1 EXTENDED model is provided.

Criteria code list codes have been updated to make them business agnostic and allow reuse across sectors (see criterion tab within ESPD-CodeLists-V3.0.0.xlsx). This is reflected in criteria codes in column ‘ElementType’ of file ESPD-criterion-V3.0.0.xlsx.

The following criteria have been removed from the file ESPD-criterion-V3.0.0.xlsx:

• CRITERION.OTHER.CA_DATA.LOTS_SUBMISSION
• Criteria DEFENCE-SELECTION-OTHER and UTILITIES-SELECTION-OTHER
• CRITERION.OTHER.EO_DATA.LOTS_TENDERED

A QUESTION_SUBGROUP element has been added to selection criteria to provide information about whether the tenderer meets the criteria on its own or relies upon other entities.

UUIDs

New UUID identifiers have been assigned for new criteria, groups and sub-groups. For a comprehensive list of the new UUID and their creation reason, please refer to new_UUIDs_for_eCertis.xlsx.

Business Rules

Business rules used to validate the ESPD requests and responses have been updated as follows:

• ‘Context’ element has been removed because it contained references to EXTENDED or BASIC type and this specification has been removed in ESPD-EDM v3.0.0;
• Weightings’ validations have been removed because the ESPD-EDM v3.0.0 does not include weights;
• Business rules related to criteria not present in this version have been removed;
• Business rules related to code list not present in this version have been removed;
• A rule has been added for the new lot management approach (one Lot/Group of Lots per ESPD Response). ESPD Request includes exclusion and selection criteria for all lots while economic operators need to produce one ESPD Response per each lot tendered to.

v2.1.1

The ESPD EDM version 2.1.1 focuses 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. The list below details exhaustively every change introduced since the publication of the previous release (2.1.0) of the ESPD-EDM:

Online documentation

As a part of the improvements introduced by this v2.1.1, the ESPD-EDM Wiki has been refactored in order to offer users a Single Information Point, where it is possible to easly acess to all its resources: documentation, tools, assets, etc.

One of the major novelties in the new v2.1.1 is the nomenclature change to refer the two different models: Regulated and Self-Contained, that from now on will be refered as Basic and Extended, respectively.

TOOP Requirements in ESPD-EDM (UBL2.2) Schema

A mapping for TOOP requirements to UBL2.2 Schema (which is the one used by ESPD-EDM) has been made, and it has been proved that they are fully mappable. For more information, please refer to the dedicated section of the online documentation.

You can also access to issue #254, where the topic was discussed.

Code Lists

• New Criteria OTHER-EO-SME, DEFENCE-SELECTION-OTHER and UTILITIES-SELECTION-OTHER codes have been added to Criteria Taxonomy Code List. ESPD-CodeLists-V2.1.1.xlsx.

• New code QUAL_IDENTIFIER has been added to ResponseDataType Code List, to properly identify the educational qualifications requested in Criterion 47, SC.ABILITIES.3 (Education).

• Two new codes to identify the "new" Basic and Extended models have been added to QualificationApplicationType Code List.

• Missing Canonical Version URI and Location URI have been added to WeightingType Code List.

The code lists can be downloaded as an MS-Excel or as an ODS file. The list of criteria has been produced based on the CriteriaTaxonomy spread-sheets (both Basic and Extended).

The complete set of code lists has been generated as Genericode 1.0 XML files, which can be accessed and downloaded from the GitHub repository GC folder.

Business Rules

• National grounds are no longer mandatory.

ESPD Criteria Taxonomy

• The first question subgroup of Criterion #61: NOT_RELIED_ON_ENTITITES of Basic model has been rolled-up to the its state on previous v1.0.2 to ensure maximum compatibility between versions. I.e. "Name of entity", "ID of the entity" and "Activity of the entity" questions have been removed.

The question subgroup of Extended model maintains the structure introduced in v2.0.2.

• New Criterion OTHER-EO-SME has been added to *Extended model, as the UBL code "industry classification" used until now does not allow to give the yes/no answer included in the Directives.

• The type of "Number of fiscal years" requirement of Criterion #30: SC-General_Average_Turnover of **Extended model ** has been changed from start date/end date to QUANTITY_INTEGER.

• New Criteria DEFENCE-SELECTION-OTHER and UTILITIES-SELECTION-OTHER have been created for the specific needs of procedures regulated by Directives 2009/81/EC and 2004/17/EC, respectively.

• In the selection Criterion #37: SC-REFERENCES The cardinality of the first QUESTION, "Recipient name" of QUESTION_SUBGROUP 6afa7569-e4c4-4538-be89-84a82b2a301b has been changed to 0..1.

UUIDs

• New UUIDs have been added for the newly created Criteria, groups and sub-groups where needed. For a comprehensive list of the new UUIDs and their creation reason, please refer to the following document.

v2.1.0

The ESPD EDM version 2.1.0 focuses on the stabilisation of the previous specification, notably of the SELF-CONTAINED features. No changes have been introduced in the UBL-2.2 XSD schemas beyond the fact that the namespace of the XSD Schema is now the final one (as published by the OASIS UBL-2.2 TC in July 2018). The list below details exhaustively every change introduced since the publication of the previous release (2.1.0) of the ESPD-EDM:

Online documentation

The following sections are new, in the XML Implementation Guide v2.1.0.

• IV.8 GUI control elements: About the sets of data elements (codes acting as ''processing instructions'') that help software applications control how to show the Graphic User Interfaces (GUI). The section covers three subjects:

  • The use of the ONTRUE/ONFALSE codes for GROUP and SUBGROUP control;
  • The use of CAPTION;
  • Ideas for decoupling the data from the GUI in future versions of the ESPD-EDM. See also the link:examples provided to illustrate this idea.

• VI.1 Alpha criterion: This section describes how the economic operator (EO) has the possibility, in the REGULATED ESPD-Response document, of specifying that it meets all the selection criteria (thus avoiding the specification of each one of the selection criteria specified in the ESPD-Request. This is a special feature only possible in the REGULATED ESPD;

• Some selection criteria have been split in multiples sub-sections, e.g. "Abilities"; this is also explained with more detail below;

• VII. Other aspects of participation and selection: In restricted procedures, competitive procedures with negotiation, competitive dialogue procedures and innovation partnerships, contracting authorities may limit the number of candidates meeting the selection criteria that they will invite to tender or to conduct a dialogue. To cover this possibility, the ESPD Regulation introduces a section named "Reduction of the number of qualified candidates" that is not a true selection criterion. Hence this denomination of "participation criterion".

• IX Putting pieces together: The ESPD-EDM specification, notably regarding the SELF-CONTAINED ESPD, defines different complex sets of data that are scattered in distant locations of the corresponding XML instance. Consequently, implementors of software dealing with the ESPD XML instances may have a hard time to identify what needs to go in the XML instance and where. This is the case of, specifically, the data related to topics dealing with special situations like lots, weights and uuids. To help implementors understand these topics and how to tackle them, the sub-section provides abundant explanations and examples.

• Interoperability testbed: A new section has been added to provide the latest URL to access the interoperability testbed and validate the ESPD document instances at testing and integration time.

• Other new resources:

  • Examples related to the proposal on how to decouple the GUI from the data structures in future versions of the ESPD-EDM;
  • Examples on how to assign constant UUIDs to the Properties of a Criterion, instead of using dynamically generated UUIDs (a method that is currently under discussion: see the Issue #226);
  • Examples provided by the ESPDint solution and other manually adapted for the illustration of Lots, Weights and References.

UBL-2.2 Schemas

• The default namespaces for the two UBL-2.2 maindoc used in ESPD are now:
  • urn:oasis:names:specification:ubl:schema:xsd:QualificationApplicationRequest-2
  • urn:oasis:names:specification:ubl:schema:xsd:QualificationApplicationResponse-2
  • The rest of all the XSD Schemas namespaces used in UBL-2.2 start now with urn:oasis:names:specification:ubl:schema:xsd:, too
  • See also how the section II.3 UBL-2.2 Documents and libraries in the online documentation has been adapted

Code Lists

• The criteria taxonomy has been added as a code list to the spread-sheet ESPD-CodeLists-V2.1.0.xlsx. This has facilitated the automated generation of the ESPD-CriteriaTaxonomy Genericode instance with the UUIDs and Codes of each criterion. The code lists can be downloaded as an MS-Excel or as an ODS file. The list of criteria has been produced based on the CriteriaTaxonomy spread-sheets (both REGULATED and SELF-CONTAINED).

• New codes have been added to the Code List ResponseDataType to increase the semantics of the basic elements thus facilitating the software application to process the responses of the economic operator in the SELFCONTAINED ESPD-Response document (the ''semantisation'' also facilitates the validation purposes, e.g. to ease the validation of whether the attribute schemeID carries a code defined in the EOIDType code list).

  • ECONOMIC_OPERATOR_IDENTIFIER, to detect whether an identifier in the response corresponds to to detect an Economic Operator
  • LOT_IDENTIFIER, to identify procurement procedure lots in the responses
  • WEIGHT_INDICATOR, to easily detect that an indicator corresponds to the fact that a criterion is weighted or not
  • CODE_BOOLEAN, to identify a specific type of GUI control element (e.g. a radio button)

• Two new codes have been added to distinguish the Sole Contractor from the Consortium's Lead Entity. The old SCL one has been marked as deprecated. See the code list EORoleType.

• The complete set of code lists has been re-generated as Genericode 1.0 XML files, which can be accessed and downloaded from the GitHub repository GC folder.

Business Rules

The Interoperability Testbed has been set up to cope with the validation of ESPD-Request and ESPD-Response v2.1.0 documents (click on the arrow of the combo-box 'Validate as').

ESPD-REGULATED Criteria Taxonomy

• In previous versions it was decided not to have a criterion named 'Global indication for all selection criteria' (a.k.a. the "Alpha Criterion") which would avoid the need of specifying long lists of selection criteria. The description of this criterion, as shown in the transitional EC's ESPD-Service, is "Concerning the selection criteria the economic operator declares that It satisfies all the required selection criteria indicated in the relevant notice or in the procurement documents referred to in the notice.". After discussion the ESPD Working Group decided to retrieve back. Thus a new data structure for the Alpha Criterion has been added to the REGULATED Criteria Taxonomy spread-sheet.
  A new Section has also been added to the online documentation (see section VI.1 Alpha Criterion).

• Exclusion Criteria #7 and #8 (section V.2 Contributions)

  • The data structures have been redone for better alignment to the ESPD Regulation

• Selection criteria about ''Suitability'' are now split into two types of data structure, ''Enrolments'' and ''Service Contracts''. See tabs ''Suitability-I'' and ''Suitability-II'' of the [E...

v2.0.2

The ESPD EDM version 2.0.2 is now released and contains only bugs fixed on the basis of the received comments on GitHub.
For further details please read the release notes. 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.

This release encompasses these other minor updates:

• Code lists

  • A new code list has been added: "WeightingType". Reason: some selection criteria need to be weighted. In version 2.0.0 the element "cbc:WeightingTypeCode" was added to the root of the "UBL-QualificationApplicationResponse-2.2-Pre-award.xd" document.
  • Two code lists have been removed as they are not used anymore in versions 2.0.x: PeriodMeasureTypeCodes and TechnicalCapabilityTypeCode.

• Criteria data structures

  • All criteria have now one block "Is this information available electronically" with cardinality 0..n. See data structures spread-sheets for both the REGULATED and the SELF-CONTAINED flavours.
  • In the SELF-CONTAINED ESPD CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.RISK_INDEMNITY_INSURANCE Subgroup "83e3dcc4-c9b3-47e5-9fb8-ffd8386679f1" changed its cardinality from 1 to 1..n.
  • In "Financial Ratios" for the SELF-CONTAINED ESPD, the REQUIREMENT "Ratio Type" needs to be a CODE (not a DESCRIPTION, as in previous versions). This code is needed by the Contracting Authority
    to specify the BACH's code (See section "VI.4.2 Self-contained financial ratios" of the online documentation for details on this).

• UUIDS

  • In the previous versions the UUIDs for the block "Is this information available electronically" where not 100% consistent. For some criteria they used the same UUIDs as in version 1.0.2 and for other a completely different set of UUIDS.
    This has been corrected and now all criteria have one block "Is this information available electronically", and all of them use the same UUIDs (the ones used also in version 1.0.2).

v2.0.1

The changes specified herein have been applied in both (1) the ESPD-EDM specification, version 2.0.1 published in this Github repository; and (2) the ESPDInt BIS document.

See also details in: Release Notes Details and in this Github "Issues" section.

• Code Lists:

  • The "ActivityType", "AmountTypeCode" and "ContractType" Code Lists have been removed, as they're not used. The Code List "ContractType" is covered (i.e. replaced) by the CodeList "ProcedureType". The ESPDInt BIS document has been modified accordingly: Section about Code Lists has been updated.

• Use of the UBL-2.2 Schemas elements:

  • The UBL-2.2 element ProfileExecutionID is used now to compulsorily specify the version and flavour of the ESPD-EDM. See the possible values in the Code List "ProfileExecutionID" (e.g. "ESPD-EDMv2.0.0-REGULATED", "ESPD-EDMv2.0.0-SELFCONTAINED", "ESPD-EDMv2.0.1-REGULATED", "ESPD-EDMv2.0.1-SELFCONTAINED"...see also the Guideline and XML examples. Remember also that cardinalities are to be controlled via business rule). The ESPDInt BIS document has been modified accordingly: Inclusion of the ESPD version identifier (tir070-299;tir092-299). The following Business Rules have been added: TRDM092-55, TRDM072-36 for tir92-299 and tir070-299 to control the Evidence version.

  • The v2.0.0 documentation specified in section "VII.5 Reference to publications and to the ESPD Request" that the elements cac:QualificationApplicationRequest/cac:AdditionalDocumentReference/cbc:ID and cac:QualificationApplicationRequest/cac:AdditionalDocumentReference/cbc:UUID had to be used to refer to other documents. This was an editorial error and has been corrected: the elements to be referred are: cac:QualificationApplicationRequest/cbc:ID and cac:QualificationApplicationRequest/cbc:UUID.

  • Element cac:ProcurementProject (cardinality 0..1): Use this component to identify and describe the procurement administrative procedure. The REGULATED version should not contain a cac:ProcurementProject in order to ensure the back-wards compatibility with the version 1.0.2. Use this component in case the ESPD is SELF-CONTAINED and the procedure is divided into lots. In this case use the ProcurementProjectLot component to provide details specific to the lot and reserve the ProcurementProject component to describe the global characteristics of the procedure.

• ESPD-EDM Cardinalities:

  • The ESPD-EDM cardinality for the element cac:TenderingCriterionResponse/cac:ResponseValue has been modified to 0..n (see the online ESPD-EDM documentation).

  • The cardinality of the element cac:Evidence/cbc:ID is now mandatory (to be controlled via business rule, as the UBL-XSD is 0..1). The ESPDInt BIS document has been modified accordingly.

  • About elements of cac:ProcurementProject:

    • The cardinality of cbc:ProcurementTypeCode is now '0..1' in both the REGULATED and the SELFCONTAINED ESPD Requests (Thus ensuring compatibility between version 2.0.1 REGULATED and v1.0.2). The ESPDInt BIS document has been modified accordingly: Cardinality for the class Procurement Project and the subordinated elements tir070-503, tir070-504, tir92-505, tir92-506 from 1..1 to 0..1 has been changed.
    • The cardinality of cbc:Name is now 0.1 in both the REGULATED and the SELFCONTAINED ESPD Requests. If used the text must match the one used in the Contract Notice.
    • The cardinality of cbc:Description is now 0.n in both the REGULATED and the SELFCONTAINED ESPD Requests (thus ensuring compatibility with UBL-2.2 multi-line descriptions). If used the text must match the one used in the Contract Notice.
    • ESPDInt BIS document: Adding cardinalitites for "Evidence issuer party" and "Criterion fulfillment URI".

• UUIDS reviewed: UUIDs, names and descriptions in files ESPD-REGULATED-CriteriaTaxonomy-V02.00.01 and ESPD-SELFCONTAINED-CriteriaTaxonomy-V02.00.01.xlsx do match now the ones in ESPD-Data_Structures-REGULATED-V02.00.01 and ESPD-Data_Structures-SELFCONTAINED-V02.00.01 spreadsheet books. Some UUIDS for subgroups of requirements have also been corrected (e.g. SC-General_Turnover --> 5ca58d66-3ef1-4145-957c-45d5b18a837f, SC-Specific_Turnover --> 19a68e37-d307-4a28-9061-c22cd767be58, SC-General_Average_Turnover --> 53882893-f4a8-40ae-99dc-cad7b0748790, SC-Specific_Average_Turnover --> 6cff132b-8d15-4f79-ae37-2f9295432381).

• Data Structures:

  • Information available electronically: The group "Is this information available electronically" is now present i all the criteria data structures (see "Data Structures" in the "dist/cl" files).
  • Some codes "ON*" were erroneous and have been transformed into "ONTRUE", e.g.Criterion 22 in the REGULATED Data Structures spreadsheets book AND Criterion 22 in the SELF-CONTAINED Data Structures spreadsheets book.
  • Missing data types: Some data types were missing and have been added; e.g. compare criteria 9 to 11, and criteria 62 and 63 between versions 2.0.0 and version 2.0.1.

The ESPDInt BIS document has been aligned accordingly.

• Editorial corrections:

  • ESPD-EDM specification:

    • The definitions in the Data Structure spread-sheets containing syntax and grammar errors have been corrected (based on the texts on the Regulation Annex II and ESPD Service GUI). Additional comments have also been added in the online documentation about the use of the UBL-2.2 0..n multi-line descriptions, as requested by some users.
    • Requirement about LotsThe documentation (in version 2.0.1) has been modified and reads now "One Lot must be always instantiated in the REGULATED ESPD XML document, and its identifier value should be '0'. The REGULATED version of the ESPD cannot be used for procurement procedures divided into Lots. For procedures divided into Lots use the SELF-CONTAINED version.
    • Additional explanatory texts have been added at the beginning of sections "VI.2.6 Self-contained specific yearly turnover" and "VI.2.8 Self-contained specific average turnover" to clarify the use of CPVs.
    • Group "Is this information available electronically": Beware that in version 2.0.0 this sentence was phrased differently as "Is this information available at no cost to the authorities from an EU Member State database?".
    • Enhanced description of the codes ON*, ONTRUE,ONFALSE, and other Data Structure elements: A sub-section "IV.4 Mock-ups, data structures, XML examples and tools" has been added to the online documentation explaining the meaning and use of each column of the Data Structures.
    • The figures representing the criteria taxonomies (both exclusion grounds and selection criteria) are now aligned with the criteria defined in the CriteriaTaxonomy and Data Structure spread-sheets (compare images in sections "V. Exclusion criteria", "VI. Selection criteria" and these files located in the "dist/cl" folder).

  • ESPDInt BIS document:

    • "Customization Identifier" for the Request and the Response to the section "Identifiers" added.
    • Name of the ListIDs named in the Business Rules TRDM092-33 and TRDM070-BR-22 has been modified.
    • Implementation Guideline for tir070-061 and tir92-071 modified.
    • tir70-502 added to reflect the country name.
    • Illustration of the differences between the regulated and the self-contained ESPD in data models and implementation guidelines.

• ESPD-EDM specification artefacts:

  • The content of the "dist/xlst" folder has been enriched and reorganised as follows:

    • The stylesheets used to transform the Data Structure *.ods files into ESPD-EDM XML instances are now under the folder 'dist\xslt\ODS Data Structures to ESPD XML'. New files have been added to this folder to help with the automation of the generation of the bunch of all the data structures in a go: e.g. ESPD-Transformation.jar, ESPD-Transformer.bat. The use of these files is explained in section "IV.4 Mock-ups, data structures, XML examples and tools", subsection "Data structures spread-sheets as a tool to generate XML instances" of the documentation.
    • A new folder named "XLSX CodeLists to Genericode" contains a style-sheet that can be used to generate OASIS Genericode 1.0 *.gc files (see "dist/cl/gc" folder) out of the spread-sheets book containing the Code Lists (file "dist/cl/xlsx/ESPD-CodeLists-V02.00.01.xlsx"). Please read the README.txt file inside this folder with the usage instructions.

• Business Rules:

  • Modifications applied to the ESPDInt BIS document (aligned to the modifications on the ESPD-EDM specification):
    • Changing path mentioned in the following Business Rules: TRDM092-13, TRDM092-14 and in the following implementation guidelines tir92-543, tir92-309.
    • Adding the following Business Rules: TRDM092-56, TRDM072-37 for tir070-601, tir092-601 to control the criterion requirement structure.
    • Adding the following Business Rules: TRDM092-57 for tir92-525 to control the confidentiality of responses.
    • Removed the element "Postbox" from all address classes.
    • Extended requirement description of tbr070-002 and tbr92-019
    • Adding the following elements tir070-601, tir092-601
    • Adding the Business Rule TRDM092-58 for tir092-526 to control the Criterion Property Groups

v2.0.0

• Adoption of UBL-2.2 XSD Schemata;
• Introduction of REGULATED and SELFCONTAINED ESPD