|
1 | | -# SDK 0.3.0 Release Notes |
2 | | - |
3 | | -*Update: An older version of the schematron rules was included by mistake in version 0.3.0. Version 0.3.1 includes the latest version of the schematron rules.* |
| 1 | +# SDK 0.4.0 Release Notes |
4 | 2 |
|
5 | 3 | Below is a list of the major updates made to the SDK in this release. |
6 | 4 |
|
7 | | -The documentation is available as separate Asciidoc files, one per section. |
8 | | -The [eForms SDK Documentation](https://op-ted.github.io/eForms-SDK) website is generated from this source using [Antora](https://antora.org/). |
| 5 | +The documentation for the SDK is available at https://docs.ted.europa.eu. |
| 6 | + |
| 7 | +The source for this documentation is now maintained in a separate repository: [eforms-doc](https://github.com/OP-TED/eforms-docs). |
9 | 8 |
|
10 | | -Please note: in this release, the website is a single HTML page containing all the documentation. |
11 | | -In the next release, the website will have separate HTML pages for each major section of the documentation. |
12 | 9 |
|
13 | | -## Changes to the eForms schema |
| 10 | +## eForms schema |
14 | 11 |
|
15 | | -### Elements used to describe changes in a Change Notice and a Contract Modification Notice |
16 | | -The elements in a Change Notice and a Contract Modification Notice were remodelled to better reflect the usage of Change Notices. |
17 | | -* Element efac:Change was renamed to efac:Changes, and its cardinality restricted to "0 or 1". |
18 | | -* Element efac:ChangedElement was renamed to efac:Change. |
19 | | -* The cardinality of element efbc:ChangedSectionIdentifier was expanded to "0 to many". |
20 | | -* The elements efbc:ProcurementDocumentChangeIndicator and efbc:ProcurementDocumentChangeDate were moved to occur inside element efac:Change. |
21 | | -* The cardinality of element efac:ChangeReason was restricted to "0 or 1". |
| 12 | +* Add new elements for the identifiers of contracts and tenders used by the buyer (efac:ContractReference and efac:TenderReference). |
| 13 | +* Add missing efac:FieldsPrivacy under efac:ReceivedSubmissionsStatistics, to allow indicating that this information is not public. |
| 14 | +* Allow multiple occurrences of the contract title, so that it can be indicated in more than one language. |
22 | 15 |
|
23 | | -### Removed unused elements |
24 | | -The elements efbc:PaidAmount and efbc:ReasonCode were removed from the schema as they were not being used. |
25 | 16 |
|
26 | | -## Changes to the schematron rules |
| 17 | +## Schematron rules |
27 | 18 | The schematron rules have been updated to reflect the schema changes listed above, along with numerous improvements and corrections. |
28 | 19 |
|
29 | | -### Requiring use of time zones |
30 | | -All dates or times specified in Notices must now include time zones. This is to ensure consistency, understanding and fairness in the published Notices. |
| 20 | +### Addition of conditional rules |
| 21 | +New rules have been added for information that must be present under certain conditions. These rules corresponding to the indication "CM" in the extended annex to the eForms Regulation. |
| 22 | + |
| 23 | +In an upcoming version we will also add rules for information that must not be present under certain conditions. |
| 24 | + |
| 25 | +### Addition of warnings |
| 26 | +For information that must be present if it exists, we have added rules that will indicate a warning (with `role="WARN"`) if the information is not present. These rules corresponding to the indication "EM" in the extended annex to the eForms Regulation. |
| 27 | + |
| 28 | +### New rules enforcing consistency between values |
| 29 | +New rules have been added to check the consistency of the values indicated for: |
| 30 | +* dates for various steps in the procurement process |
| 31 | +* contract duration |
| 32 | +* number of lots allowed and awarded |
| 33 | +* highest and lowest tender value |
31 | 34 |
|
32 | | -## New rules enforcing use of code lists |
33 | | -Many elements are used to define indicators or codes. The content of these elements should be limited to one of a set of values in each case. Code lists, taken from or derived from those published in [EU Vocabularies](https://op.europa.eu/en/web/eu-vocabularies/e-procurement/tables), define the acceptable values. New schematron rules have been added to restrict the content of many elements to the values in the relevant code lists. Please note this work is incomplete; more such rules will be implemented in future releases of this SDK. |
| 35 | +### New rules on languages used |
| 36 | +For textual information that can be indicated in multiple languages, new rules check the consistency of the languages used with the notice official languages (BT-702). |
34 | 37 |
|
35 | | -### New pattern-matching rules |
36 | | -New schematron rules have been implemented which check that the content of some elements match specific patterns. These elements and patterns are listed in section "9. Identifiers and References" in the schema documentation. |
37 | | -* Elements within the Notice Information section at the beginning of a Notice, identifying the UBL and Customization versions, the Notice Identifier, and the publication identifiers. |
38 | | -* Elements identifying sections within a Notice, and elements which link to those sections. |
39 | | -* Elements referencing previous Notices must use either the Publication Identifier or a combination of the Notice Identifier plus the Notice Version of the Notice being referred to. |
| 38 | +### Length restrictions on numerical values |
| 39 | +Rules that limit the number of characters for numerical values have been removed. They will be re-added in the future in the form of minimum and maximum allowed values. |
| 40 | + |
| 41 | +### Corrections |
| 42 | +Several rules requiring the presence of specific parties (mediator, eSender, etc.) have been corrected. |
40 | 43 |
|
41 | | -### New length restrictions |
42 | | -New schematron rules have been added which restrict the maximum length of the content of most elements. The limits chosen have been generous, and should not hinder notice creators from including sufficient details. |
43 | 44 |
|
44 | 45 | ## Example Notices |
45 | 46 | The XML notices in the "examples" folder have been updated to incorporate the schema changes listed above, and the updated schematron rules. |
46 | 47 |
|
47 | | -### Codes used for Exclusion Grounds |
48 | | -The code list for Exclusion Grounds used in ESPD has been adopted into eForms. The notice examples have been updated to use these codes. |
| 48 | +A new notice example was added for a Contract Award Notice with multiple buyers. |
| 49 | + |
| 50 | +The validation reports have been regenerated, incorporating all the changes listed above. |
| 51 | + |
| 52 | + |
| 53 | +## Fields |
| 54 | +The SDK now includes information on the fields that compose an eForms notice, in a structured format (JSON). |
49 | 55 |
|
50 | | -New Notice examples were added for: |
51 | | -* PIN, Contract Notice and Contract Award Notice under Directive 2009/81/EC |
| 56 | +You can find more information about this in the [corresponding section of the documentation](https://docs.ted.europa.eu/eforms/0.4.0/fields/). |
52 | 57 |
|
53 | | -## Validation Reports |
54 | | -The existing validation reports have been regenerated, incorporating all the changes listed above. |
55 | 58 |
|
56 | | -New validation reports have been generated for the new example notices listed above. |
| 59 | +## Translations |
| 60 | +The SDK now includes the translations of various labels and short texts used in eForms notices. |
57 | 61 |
|
| 62 | +You can find more information about this in the [corresponding section of the documentation](https://docs.ted.europa.eu/eforms/0.4.0/translations/). |
0 commit comments