eForms SDK 1.9.3

SDK 1.9.3 Release Notes

This release brings the following corrections in the validation rules, making them more permissive:

• Removed rules that required the participation request deadline (BT-1311(d)-Lot) to match the end of the DPS.
• Allow change notices with "cancel-intent" to be submitted after the tender deadline has passed.
• Allow change notices to have a dispatch date (BT-05(a)-notice) that is after the "Future Notice" date (BT-127-notice).
• Allow change notices to have a dispatch date (BT-05(a)-notice) that is after the "Deadline Receipt Expressions" (BT-630(d)-Lot).
• Corrected various rules to allow information on framework agreements in contract modification notices (subtypes 38 and 39).
• Removed rule requiring "Notice Framework Maximum Value" (BT-118-NoticeResult) to be the sum of the corresponding values in each lot.

This release also includes updated translations and updated notice visualisation templates.

Warning

Some of the changes in view templates trigger a bug in efx-toolkit-java version 2.0.0-alpha.1 and before, causing an error when translating some templates.
So if your application uses the view templates and the EFX Toolkit, ensure that you're using efx-toolkit-java version 2.0.0-alpha.2 or later.

A comprehensive list of changes between SDK 1.9.2 and SDK 1.9.3 can be seen at 1.9.2...1.9.3

You can explore the changes between those versions at https://docs.ted.europa.eu/eforms-sdk-explorer?version=1.9.3&base=1.9.2

eForms SDK 1.8.3

SDK 1.8.3 Release Notes

This release brings the following corrections in the validation rules, making them more permissive:

• Removed rules that required the participation request deadline (BT-1311(d)-Lot) to match the end of the DPS.
• Allow change notices with "cancel-intent" to be submitted after the tender deadline has passed.
• Allow change notices to have a dispatch date (BT-05(a)-notice) that is after the "Future Notice" date (BT-127-notice).
• Allow change notices to have a dispatch date (BT-05(a)-notice) that is after the "Deadline Receipt Expressions" (BT-630(d)-Lot).
• Corrected various rules to allow information on framework agreements in contract modification notices (subtypes 38 and 39).
• Removed rule requiring "Notice Framework Maximum Value" (BT-118-NoticeResult) to be the sum of the corresponding values in each lot.

This release also includes updated translations and updated notice visualisation templates.

Warning

Some of the changes in view templates trigger a bug in efx-toolkit-java version 2.0.0-alpha.1 and before, causing an error when translating some templates.
So if your application uses the view templates and the EFX Toolkit, ensure that you're using efx-toolkit-java version 2.0.0-alpha.2 or later.

A comprehensive list of changes between SDK 1.8.2 and SDK 1.8.3 can be seen at 1.8.2...1.8.3

You can explore the changes between those versions at https://docs.ted.europa.eu/eforms-sdk-explorer?version=1.8.3&base=1.8.2

eForms SDK 1.7.4

SDK 1.7.4 Release Notes

This release brings the following corrections in the validation rules, making them more permissive:

• Removed rules that required the participation request deadline (BT-1311(d)-Lot) to match the end of the DPS.
• Allow change notices to have a dispatch date (BT-05(a)-notice) that is after the "Future Notice" date (BT-127-notice).
• Allow change notices to have a dispatch date (BT-05(a)-notice) that is after the "Deadline Receipt Expressions" (BT-630(d)-Lot).
• Removed rule requiring "Notice Framework Maximum Value" (BT-118-NoticeResult) to be the sum of the corresponding values in each lot.

This release also includes updated translations and updated notice visualisation templates.

Warning

Some of the changes in view templates trigger a bug in efx-toolkit-java version 2.0.0-alpha.1 and before, causing an error when translating some templates.
So if your application uses the view templates and the EFX Toolkit, ensure that you're using efx-toolkit-java version 2.0.0-alpha.2 or later.

A comprehensive list of changes between SDK 1.7.3 and SDK 1.7.4 can be seen at 1.7.3...1.7.4

You can explore the changes between those versions at https://docs.ted.europa.eu/eforms-sdk-explorer?version=1.7.4&base=1.7.3

eForms SDK 1.11.0

SDK 1.11.0 Release Notes

This release of the SDK does not contain any backwards incompatible changes: software that was able to use version 1.9.0 should also be able to use this version.

Additional information

Two new index files were added :

• schemas.json in the schemas folder, with information on each XSD file available under this folder.
• schematrons.jsonin the schematrons folder, with information on each Schematron file available under this folder.

In the index file codelists\codelists.json, we have added a "version" property for each codelist.

Updated metadata content

Schema, nodes, fields and notice type definitions

• For contract modification notices, the field BT-1501(s)-Contract was replaced by 2 fields:
  • BT-1501(c)-Contract for the identifier of the contract being modified, with a new element named efbc:ModifiedContractIdentifier added in the schema.
  • BT-1501(p)-Contract for the identifiers of other sections of the notice impacted by the modification.
• A new field OPT-093-Review was added for the review technical identifier, with the corresponding element added in the schema under efac:AppealStatus. This field is currently not used, and is intended for the new "Contract completion" notices that will be added in a future version.
• The field BT-150-Contract-Scheme was removed, as the corresponding attribute is not needed in the XML.
• The node ND-Modification was corrected to not be repeatable.
• The notice type definitions for subtypes 14 and 15 were updated for the fields related to the second stage invitation.
• The notice type definition for subtype 1 was corrected to add fields BT-01(e)-Procedure and BT-01(f)Procedure.
• The notice type definition for subtype 5 was corrected to change GR-Part-DPS from SECTION to GROUP.
• The notice type definition for subtype 13 was corrected to change GR-ChangedSectionIdentifiers from SECTION to GROUP.

Rules

In the schematron files, the identifiers for the phases added in SDK 1.10.0 now all start with an "eforms-" prefix. This was necessary because the Schematron standard requires that identifiers do not start with a digit. This might require an adaptation if you are executing the Schematron rules and use the phases introduced in SDK 1.10.0.

• Added rules to check that required XML attributes "listName", "currencyID" are present.
• Allow Renewal Description (BT-57-Lot) when Renewal Maximum (BT-58) is not null.
• Have an interdependency between BT-26 and BT-262 for the main classification.
• Correct rule BR-BT-01118-0032 and remove rules BR-BT-00556-0034, BR-BT-00556-0033 & BR-BT-00556-0032 improperly based on BT-142.
• Make email and phone number optional for organisations except buyers.
• Update rules about deadlines for Other Single & Multi Stages Procedures.
• Update condition on rule BR-BT-00630-0150 to allow for change publication after Deadline Receipt Expression (BT-630) has passed.
• Allow Winner Decision (BT-1451) to be on the same day the notice is submitted (BT-05) and the contract is signed (BT-145).
• Fix rule BR-OPT-00301-1411 description to refer to the correct field.
• Allow for 2nd stage Business Terms for Notice Subtype 14 instead of 15 and activate 2nd stage conditional rules.
• Update the rules that involve comparison of summed decimal values (e.g. Award Criteria Weight, Monetary Values) by including a tolerance.
• Removing Rules for uniqueness of Order of Importance.
• Align the BT-106-Procedure conditional Rules with the agreed upon table for procedure accelerated.
• Activate rules for No Negotiation Necessary (BT-120-Lot).
• Update the Sections/Parts reference options in Contract Modification and Changed Sections.
• Define a Pattern rule for OPP-131-Business.
• Update message for Schematron rule on dispatch date.
• Align the rules expressions for identifiers uniqueness (does not affect actual validation).
• Remove manual Schematron that make request to old TED website API.
• Make BT-131 optional for Notice Subtype 8.
• Have the rules on Tender Subcontracting Information activated (BT-553, BT-554, BT-555, BT-730, BT-731).
• Allow for Touchpoint Part Name (BT-16-Organization-TouchPoint) only when Touchpoint Name (BT-500-Organization-TouchPoint) exists.
• Activate rules on Lot Subcontracting Information (BT-64, BT-651, BT-729).
• Align rule BR-BT-00615-0119 on Document restricted URL (BT-615) for Notice Subtype 7 on other equivalent Notice Subtypes.
• Only allow for Group of Lots (BT-137-LotsGroup) when there are at least two lots.
• Prevent the use of Duration Other (BT-538) for Notice Subtypes T01 & T02.
• Remove CF rule that prevents Direct Award Justification for T01.
• Make BT-22 optional.
• Allow "cancel-intent" to be used also once submission deadline has passed.
• Remove the constraint on DPS that enforced the Participation Request Deadline to match the end of the DPS.
• Reject values with leading or trailing whitespace for some fields.
• Allow for GPA coverage (BT-115) when not explicitly mandatory or forbidden, and remove the GPA dependency on the Buyer Legal Type (BT-11).
• Allow Guarantee Required Description (BT-75-Lot) when Guarantee (BT-751) is true.
• Forbid DPS termination (BT-119-LotResult) when there is no DPS.
• Make Tendering Party ID (OPT-210) & Tenderer ID Ref. (OPT-300) mandatory when a Tender exists, Tendering Party Leader (OPT-170) allowed when multiple tenderers tender together, Subcontractor ID Ref. (OPT-301) allowed when a main contractor exists.
• Allow Tender Validity Deadline (BT-98-Lot) for Open procedures only.
• Forbid Tender Variant (BT-193-Tender) when the Lot has not been awarded.
• Allow NDA Description (BT-802-Lot) only when Non Disclosure Agreement (BT-801) is true.
• Allow Organization Size (BT-165-Organization-Company) specification for tenderers only (winners included).
• Allow Security Clearance Deadline (BT-78-Lot) and require Security Clearance Description (BT-732-Lot) when Security Clearance (BT-578) is true.
• Extend the possibility to use ojs-notice-id to identify a TEDXML notice for which the previous Procedure has been unsuccessful (BT-1252).
• Allow for Procedure Description (BT-24) for T01 and T02.
• Update rule BR-BT-00127-0100 on Future Notice (BT-127) to allow for change publication even when the Future Notice date has passed.
• Make Review Deadline Description (BT-99) mandatory in absence of any organisation providing review information.
• Forbid the use of Maximum Candidates Indicator (BT-661), Minimum Candidates (BT-50), Successive Reduction Indicator (BT-52) for single stage procedures and have Maximum Candidates Number (BT-51) when BT-661 is true.
• Allow for Electronic Auction URL & Description (BT-122, BT-123) only when Electronic Auction indicator (BT-767) is 'true'.
• Allow for Tenderer Legal Form Description (BT-76-Lot) only when a specific legal form is expected (BT-761 is true).
• Allow Lots All Required (BT-763), Lots Max Awarded (BT-33) and Lots Max Allowed (BT-31) only when multiple lots exist and make BT-31 mandatory when BT-763 is not set to true.
• Have the review info provider (OPT-301-Part-ReviewInfo, OPT-301-Lot-ReviewInfo) optional for PIN Only forms and, for other forms, mandatory when a review deadline is set.
• Make Reserved Execution Justification (OPT-070) allowed and needed when the execution is reserved.
• Make Provided Service Type (OPT-030) allowed and mandatory only once the service provider is identified.
• Make Recurrence Description (BT-95) allowed only when Recurrence (BT-94) is set to "true".
• Allow and require Strategic Procurement Description (BT-777) when it is about a Strategic Procurement.
• Make Late Tenderer Information (BT-772) allowed when late information provision is possible and mandatory when only some information may be provided later.
• Require for Received submissions code (BT-760) when competition is over, and Received Submission Count (BT-759) when BT-760 is specified.
• Make Accessibility justification (BT-755) required when "accessibility criteria not considered and intended to be used by natural person".
• Provision of Buyer Review Complainants (BT-712) only possible once competition is over - Number (BT-712(b)-LotResult) mandatory once technical code (BT-712(a)-LotResult) specified.
• Allow for Buyer Review Requests Irregularity Type (BT-636) when competition is over, and require Buyer Review Requests Count (BT-635) once BT-636 specified.
• Remove constraints on Framework Agreement values for Contract Modification notices.
• Make Tender Value, Highest & Lowest (BT-720, BT-711, BT-710) forbidden when competition ongoing; Tender Value (BT-720) mandatory if no FA or contracts within a FA; FA Re-calculated Max Value or Re-estimated Value (BT-709, BT-660) mandatory for a FA.

Codelists

• Updated codelists related to forms T01 and T02:
  • procedure-type: added exp-int-rail.
  • direct-award-justification: added exc-circ-rail, sm-contr, sm-contr-sme, char-imp and sim-infra and removed rail.
  • procedure-type-t01 and procedure-type-t02: added neg-wo-call and exp-int-rail.
  • Made some labels clearer.
• measurement-unit: added unit for "piece" and removed 39 redundant units.
• Added missing Croatian labels in CPV.
• Removed redundant eforms-country codelist (same as country codelist).
• Updated codelists corporate-body (added CJU, removed KDTJU), and eu-programme (added years in labels for programmes with the same name).

View templates

• The Winner section is now displayed for VEAT (direct award) notices that do not include a LotResult
• The Results section will now be displayed for notices with no Tenders included
• CEI notices ("C...

eForms SDK 1.9.2

SDK 1.9.2 Release Notes

This release brings the following corrections in the validation rules, making them more permissive:

• The field "The winner is listed on a regulated market" (BT-746-Organization) is now optional.
• Correct rules to avoid errors when "Unpublished Access Date" (BT-198) is not present.

This release also includes updated translations and updated notice visualisation templates.

A comprehensive list of changes between SDK 1.9.1 and SDK 1.9.2 can be seen at 1.9.1...1.9.2

You can explore the changes between those versions at https://docs.ted.europa.eu/eforms-sdk-explorer?version=1.9.2&base=1.9.1

eForms SDK 1.8.2

SDK 1.8.2 Release Notes

This release brings the following corrections in the validation rules, making them more permissive:

• The field "The winner is listed on a regulated market" (BT-746-Organization) is now optional.
• Remove rule BR-BT-00743-0100 that required "Electronic invoicing" (BT-743-Lot) to be set to "required".
• Remove ineffective rules for change notices to improve performance when validating notices with a large number of lots.

This release also includes updated translations and updated notice visualisation templates.

A comprehensive list of changes between SDK 1.8.1 and SDK 1.8.2 can be seen at 1.8.1...1.8.2

You can explore the changes between those versions at https://docs.ted.europa.eu/eforms-sdk-explorer?base=1.8.1&version=1.8.2

eForms SDK 1.7.3

SDK 1.7.3 Release Notes

This release brings the following corrections in the validation rules, making them more permissive:

• Remove rule BR-BT-00743-0100 that required "Electronic invoicing" (BT-743-Lot) to be set to "required".
• Remove ineffective rules for change notices to improve performance when validating notices with a large number of lots.

This release also includes updated translations and updated notice visualisation templates.

A comprehensive list of changes between SDK 1.7.2 and SDK 1.7.3 can be seen at 1.7.2...1.7.3

You can explore the changes between those versions at https://docs.ted.europa.eu/eforms-sdk-explorer?base=1.7.2&version=1.7.3

eForms SDK 1.6.4

SDK 1.6.4 Release Notes

This release brings the following corrections in the validation rules, making them more permissive:

• Remove rule BR-BT-00743-0100 that required "Electronic invoicing" (BT-743-Lot) to be set to "required".
• Remove ineffective rules for change notices to improve performance when validating notices with a large number of lots.

This release also includes updated translations and updated notice visualisation templates.

A comprehensive list of changes between SDK 1.6.3 and SDK 1.6.4 can be seen at 1.6.3...1.6.4

You can explore the changes between those versions at https://docs.ted.europa.eu/eforms-sdk-explorer?base=1.6.3&version=1.6.4

eForms SDK 1.10.1

SDK 1.10.1 Release Notes

This release adds missing translations for rule messages, and adds a new label for "Change notice" with the identifier auxiliary|text|change-notice.

A comprehensive list of changes between SDK 1.10.0 and SDK 1.10.1 can be seen at 1.10.0...1.10.1

eForms SDK 1.10.0

SDK 1.10.0 Release Notes

This release of the SDK does not contain any backwards incompatible changes: software that was able to use version 1.9.0 should also be able to use this version.

Additional information

Two new files were added in the translations folder:

• An index file named translations.json, with information on each translation file available in the folder.
• A list of the EU official languages, named language-codes.xml, with the 2 and 3 letter codes for each language. This file is in XML to make it easier to use in XPath or XSLT.

Updated metadata content

This version brings various changes in the metadata content that were needed for corrections, enhancements and consistency. The following sections contain an overview of the main changes.

Schema, nodes, fields and notice type definitions

• Removed the definition of the element efbc:TermIndicator from the schema, as this element was not used any more.
• The node structure was improved, and the notice type definitions were adjusted accordingly.
• Added references to the identifier scheme for fields OPT-301-ReviewBody and OPT-301-ReviewReq.
• Updated fields and nodes properties to allow for multiple direct award justifications.
• Added fields OPP-035-Tender and OPP-035-Tender-List for T02 notices.
• Corrected codelist used for OPP-030-Tender.
• The Clean Vehicles Directive (CVD) fields and groups have been added to the notice type definition for subtypes 32 to 35, both in the lot (GR-Lot-TenderingTerms-CVD) and the lot result (GR-LotResult-CVD) sections. The positioning reflects what was already in place in other subtypes.
• Many other changes to notice type definitions to provide consistency and completeness.

Rules

The Schematron rules are now split in phases, with one phase for each notice subtype. This allows us to significantly reduce the execution time of the validation, in particular for large notices. The Schematron rules can be executed as before, but some adaptations are needed to take advantage of the improved performance. More information is available in the documentation. The Central Validation Service will be updated soon to take advantage of this improvement.

Other changes in the rules include:

• Reactivated various conditional rules related to: Framework agreements, GPA coverage, change-related fields, business registration, title and description of groups of lots, classification type, additional nature, address components, group framework values, EU Funds, and vehicles.
• Added rules to check that the procedure type (BT-105-Procedure) is consistent with the notice subtype.
• Added rules on various fields to check that their value is unique in the notice, in particular for identifiers.
• Updated rules on accelerated procedure (BT-106-Procedure and BT-105-Procedure).
• Corrected the rule on CPV codes for subsidized contracts.
• Reduced the minimum period between Notice Dispatch Date (BT-05-notice) and Preferred Publication Date (BT-738-notice) from 2 to 0 days.
• Modified the rule on dispatch date to use "Notice Dispatch Date eSender" (BT-803) when it exists, and Dispatch Date (BT-05) otherwise.
• Modified rules on Duration fields (BT-36-Lot, BT-536-Lot, BT-537-Lot, BT-538-Lot) to be less restrictive and allow for various combinations without absolutely requiring the Duration Start Date (BT-536-Lot).
• Made OPT-320-LotResult forbidden for Notice Subtype 28.
• Corrected rules on "unpublished" fields related to BT-105-Procedure for subtypes 32 and 35.
• Corrected rules on BT-198* fields to only apply when a value is present.
• Improved rules on buyers to check that each and every buyer corresponds to an organisation.
• Improved rules for "Cross Border Law" (BT-09).
• Added a pattern rule for BT-1501(s)-Contract.
• Corrected the regular expression used to check e-mail addresses to not reject valid addresses.
• Corrected rules on opening event information to properly check when it is mandatory.
• Updated rules to allow OJ publication fields in X01 and X02 notices: "Notice Publication Number" (OPP-010-notice), "OJEU Identifier" (OPP-011-notice), "OJEU Publication Date" (OPP-012-notice).
• Added rules to forbid any "Group of Lots" field for notice subtype 15.
• Removed rules on Lot and Part Technical ID when a single Lot or Part exists (BR-BT-00137-0207 and BR-BT-00137-0208).
• Removed unnecessary rule comparing Opening Tender Event Date with the Deadline Receipt Request to Participate.
• Removed the rule on Notice Framework Maximum Value as the sum of individual framework values (BR-BT-00118-0100).
• Removed the mandatory rule on "Listed on a Regulated Market" (BT-746-Organization).
• Added specific lawfulness warning for notice subtypes 1 to 6, only on the buyer country. The current lawfulness warning now applies on the other notice subtypes.
• Added systematic lawfulness warning for CEI notices (reserved to EU institutions).
• Added missing assert identifiers in file validation-stage-6b.sch.

Codelists

• Added new tailored codelist "contract-term" based on "contract-detail".
• Updated the list of lawful countries with the 7 French territories.

View templates

• Extended new Result CVD fields introduced in the Regulation amendment to eForms subtypes 32 to 35.
• Removed EFX templates for Views where their Fields are forbidden.
• Improved EFX templates for X01, X02, T01 and T02.
• Where a Tendering Party is comprised of more than one organisation, we now display the name of the group leader, followed by the names of the other organisations.
• Removed the section for group of lots from notice subtype 15, as they are not allowed.
• Improved the display of lists of codes.
• Added "Notice Dispatch Date eSender" to the display for all notice subtypes.

Labels and translations

• The messages for rules are now easier to understand. When they mention a field, the field name is indicated in addition to the identifier.
• Corrected the message for rules on BT-634.
• Corrected the message for rule "BR-BT-13713-0102".

Examples

• Added XML notice examples for notices subtypes that were not covered yet.
• Corrected the example for X02 to reference the correct codelist.

As new rules were added, a notice that was valid with SDK 1.9.x might not be valid with this version.

The documentation for the SDK is available at https://docs.ted.europa.eu. The source for this documentation is maintained in the eforms-docs repository.

This release note does not cover the details of all changes.

A comprehensive list of changes between SDK 1.9.0 and SDK 1.10.0 can be seen at 1.9.0...1.10.0