├── test-notices
├── eforms-xml
│ └── .keep
└── README.md
├── development-notices
├── eforms-xml
│ └── 23-119901-001-EXP.xml
├── README.md
└── ted-xml
│ ├── 20-318547-001-EXP.xml
│ ├── 23-119901-001-EXP.xml
│ ├── 21-364240-001-EXP.xml
│ ├── 20-155018-001-EXP.xml
│ ├── 21-364236-001-EXP.xml
│ ├── 21-364516-001-EXP.xml
│ ├── 19-090974-001-EXP.xml
│ ├── 20-164186-001-EXP.xml
│ ├── 21-362774-001-EXP.xml
│ ├── 20-377805-001-EXP.xml
│ └── 21-119282-001-EXP.xml
├── CHANGELOG.md
├── eforms-structure-files
└── README.md
├── xslt
├── create-ted-map.xslt
├── translations.xml
├── README.md
├── common.xslt
├── simple.xslt
└── languages-map.xml
├── installation.md
├── usage-information.md
├── README.md
├── ted-elements-not-convertible.md
├── development-methodology.md
└── LICENSE
/test-notices/eforms-xml/.keep:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/development-notices/eforms-xml/23-119901-001-EXP.xml:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/CHANGELOG.md:
--------------------------------------------------------------------------------
1 |
2 | # TED XML Data Converter 1.0.4 Release Notes
3 |
4 | This is a minor release of the TED XML Data Converter. Some cosmetic changes are not listed below.
5 |
6 | ## Changes
7 |
8 | * Changed fatal error message output for F14 notices
9 | * Changed mapping for NOTICE_NUMBER_OJ to always map to OPP-090
10 |
11 | ## Notes
12 | This release of the TED XML Data Converter can convert notices published in the R2.0.9 TED schema, versions S01 to S05. It is not able to convert notices published in the R2.0.8 schema, or notices published under the 1370/2007 ("Transport") Regulation.
13 |
14 | It is not possible to convert F14 (Corrigendum) notices, due to their text-based format. F20 (Contract Modification) notices can be converted, but only the original contract information will be included, the modifications will be excluded.
15 |
--------------------------------------------------------------------------------
/eforms-structure-files/README.md:
--------------------------------------------------------------------------------
1 |
2 | # Structure files
3 |
4 | These files are in draft status. Only notice-structure-CN.xml is complete.
5 |
6 | These "structure" files are intended to include all possible elements used in eForms. This excludes elements that are valid according to the relevant eForms schema, but which are not actually used in eForms. Use of the correct attributes and values is not guaranteed. These files will not pass the eForms business rules Schematron validation. Element values used are fictitious, and may be redundant or inconsistent or contradictory.
7 |
8 | Repeatability. Where elements are repeatable, it is not the purpose of these XML files to show that. Only one instance of these elements will usually be present. However, where the schema defines an exclusive choice of child elements for a parent element (meaning that the XML would be schema-invalid if the same parent element contained both child elements), then the parent element will be repeated to allow all possible child elements to be present, and maintain schema validity.
9 |
10 |
11 |
12 | | File | Purpose |
13 | | --- | --- |
14 | | notice-structure-CN.xml | XML file containing all possible used elements for any Contract Notice |
15 | | notice-structure-CAN.xml | XML file containing all possible used elements for any Contract Award Notice |
16 | | notice-structure-PIN-CFC.xml | XML file containing all possible used elements for any PIN used as a Call for Competition Notice |
17 |
--------------------------------------------------------------------------------
/test-notices/README.md:
--------------------------------------------------------------------------------
1 | # TED XML files selected for testing the converter
2 |
3 | In order to provide a way of testing the converter, a set of Notices in both TED XML and eForms XML formats is required. The TED XML notices should be representative; each set of notices should:
4 |
5 | - collectively include all the TED XML elements used in each TED form type covered
6 | - include variations in structure and language
7 |
8 | The eForms XML notice files should be created using information from the TED XML notice files, by a different process from the converter. This work is in progress; no example eForms XML files are included in this release.
9 |
10 | This table lists the TED XML files chosen to test the Converter, and the reasons for their choosing.
11 |
12 | | File | Form Type | Document Type | Reasons for selection |
13 | | --- | --- | --- | --- |
14 | | 20-320448-001-EXP.xml | F02_2014 | CN | Covers 81 elements, 2 Lots |
15 | | 20-242009-001-EXP.xml | F02_2014 | CN | Covers 25 other elements, 1 Lot, includes translations |
16 | | 21-013188-001-EXP.xml | F02_2014 | CN | Covers 11 other elements, 1 Lot |
17 | | 20-382921-001-EXP.xml | F02_2014 | CN | Covers 7 other elements, 1 Lot |
18 | | 20-259392-001-EXP.xml | F02_2014 | CN | LOT_MAX_NUMBER = 2 and 4 Lots |
19 | | 20-156925-001-EXP.xml | F02_2014 | CN | LOT_ONE_ONLY and 4 Lots |
20 |
21 | There are 14 elements in TED not covered by the first four files:
22 | ACCELERATED_PROC
23 | AC_COST
24 | CPV_SUPPLEMENTARY_CODE
25 | DOCUMENT_RESTRICTED
26 | LEGAL_BASIS_OTHER
27 | LOT_COMBINING_CONTRACT_RIGHT
28 | LOT_MAX_NUMBER
29 | LOT_ONE_ONLY
30 | PLACE
31 | PROCUREMENT_LAW
32 | PT_COMPETITIVE_DIALOGUE
33 | PT_INNOVATION_PARTNERSHIP
34 | RESTRICTED_SHELTERED_PROGRAM
35 | RESTRICTED_SHELTERED_WORKSHOP
36 |
--------------------------------------------------------------------------------
/xslt/create-ted-map.xslt:
--------------------------------------------------------------------------------
1 |
2 |
4 |
5 |
6 |
7 |
8 |
9 |
10 | country
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 |
33 |
34 |
--------------------------------------------------------------------------------
/xslt/translations.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 | Информация относно национални процедури, налични на:
4 | Informace o národních řízeních jsou k dispozici na:
5 | Oplysninger om nationale udbud er tilgængelig på:
6 | Angaben zu nationalen Verfahren sind erhältlich unter:
7 | Πληροφορίες για τις εθνικές διαδικασίες διατίθενται από:
8 | Information about national procedures is available at:
9 | La información sobre los procedimientos a nivel nacional se encuentra disponible en:
10 | Teave riiklike menetluste kohta on avaldatud aadressil:
11 | Tietoa kansallisista menettelyistä on saatavilla:
12 | Des informations sur les procédures nationales sont disponibles sur:
13 | Tá faisnéis maidir le nósanna imeachta náisiúnta ar fáil ag:
14 | Podaci o nacionalnim postupcima dostupni su na:
15 | A nemzeti eljárásokról a következő helyen található információ:
16 | Le informazioni relative alle procedure nazionali sono disponibili all'indirizzo:
17 | Informacija apie nacionalines procedūras pateikiama:
18 | Informācija par valsts procedūrām ir pieejama šeit:
19 | Informazzjoni dwar proċeduri nazzjonali hija disponibbli fuq:
20 | Inlichtingen over nationale procedures zijn beschikbaar op:
21 | Informacje o krajowych procedurach można znaleźć pod adresem:
22 | A informação relativa aos concursos nacionais está disponível em:
23 | Informaţii privind procedurile naţionale sunt disponibile la:
24 | Informácie o vnútroštátnych postupoch sú k dispozícii na:
25 | Informacije o nacionalnih postopkih so na voljo na:
26 | Information om nationella förfaranden finns på:
27 |
28 |
29 |
--------------------------------------------------------------------------------
/xslt/README.md:
--------------------------------------------------------------------------------
1 |
2 | ## XSLT files
3 | This folder contains the converteer code: XSLT and data files.
4 |
5 | | File | Purpose |
6 | | --- | --- |
7 | | XSLT |
8 | | [ted-to-eforms.xslt](ted-to-eforms.xslt) | The main (starting) XSLT file |
9 | | [functx-1.0.1-doc.xsl](lib/functx-1.0.1-doc.xsl) | The FunctX XSLT Function Library, available [here](http://www.xsltfunctions.com/) |
10 | | [functions-and-data.xslt](functions-and-data.xslt) | Retrieving data from the mapping files, and common functions |
11 | | [common.xslt](common.xslt) | Templates used in more than one location |
12 | | [simple.xslt](simple.xslt) | Simple templates (one-to-one mappings) |
13 | | [lot.xslt](lot.xslt) | Templates for converting information at Lot level |
14 | | [notice-result.xslt](notice-result.xslt) | Templates for converting information at Notice Result level |
15 | | [addresses.xslt](addresses.xslt) | Templates for addresses |
16 | | [award-criteria.xslt](award-criteria.xslt) | Templates for converting Award Criteria (BG-38) |
17 | | [procedure.xslt](procedure.xslt) | Templates for converting information at Procedure level |
18 | | [create-ted-map.xslt](create-ted-map.xslt) | XSLT to create languages-map.xml and countries-map.xml from the EU Vocabularies files |
19 | | Mapping files |
20 | | [notice-type-mapping.xml](notice-type-mapping.xml) | Mapping file to determine eForms Notice Subtype from TED XML content for R2.0.9 schema |
21 | | [eforms-notice-subtypes.xml](eforms-notice-subtypes.xml) | Mapping file to determine BT-02 Notice Type and BT-03 Form Type from Notice Subtype |
22 | | [languages.xml](languages.xml) | The "Language" codelist XML file, downloaded from https://op.europa.eu/en/web/eu-vocabularies/e-procurement/tables |
23 | | [languages-map.xml](languages-map.xml) | Mapping of Language codes in TED to eForms, derived from the "Language" codelist XML file |
24 | | [countries.xml](countries.xml) | The "Country" codelist XML file, downloaded from https://op.europa.eu/en/web/eu-vocabularies/e-procurement/tables |
25 | | [countries-map.xml](countries-map.xml) | Mapping of Country codes in TED to eForms, derived from the "Country" codelist XML file |
26 | | [other-mappings.xml](other-mappings.xml) | Other data mappings |
27 | | [translations.xml](translations.xml) | Translations for TED form section IV.1.10 "Information about national procedures is available at:" for BT-300 Additional Information |
28 |
29 |
--------------------------------------------------------------------------------
/installation.md:
--------------------------------------------------------------------------------
1 | # TED XML to eForms XML Converter: installation instructions
2 |
3 | Please see the [README.md](README.md) file for information about the files included in this repository.
4 |
5 |
6 | ## Installation instructions
7 |
8 | These instructions are for installation in a Unix environment.
9 |
10 |
11 |
12 | ## Summary
13 | To run the converter requires the following:
14 |
15 | ### Java
16 |
17 | The user's system must have either a Java Virtual Machine, or a Java development environment. At least Java SE 8 (also known as JDK 1.8) must be available. Java must be available to run from the Unix terminal. Type "java -version" to confirm.
18 |
19 |
20 |
21 | ### An XSLT processor
22 |
23 | A processor for XSLT version 2.0 is required. This converter has only been tested using the open-source version of Saxon, Saxon-9 HE, available from https://sourceforge.net/projects/saxon/files/Saxon-HE/9.9/. The installation instructions are here: https://www.saxonica.com/html/documentation9.9/about/installationjava/. Make sure the saxon9he.jar file is in the Java CLASSPATH environment variable.
24 |
25 | Documentation on running XSL using Saxon9 is available here: https://saxonica.com/documentation9.9/index.html#!using-xsl
26 |
27 |
28 |
29 | ### This repository
30 |
31 | Clone the TED XML Data Converter from https://github.com/OP-TED/ted-xml-data-converter.
32 |
33 |
34 |
35 | ## Running the converter
36 |
37 | A typical Unix command using Saxon HE to convert a file is:
38 |
39 | `java -Xms6291456 -cp [path to saxon folder]/saxon9he.jar net.sf.saxon.Transform -dtd:off -expand:off -strip:all -s:development-notices/ted-xml/21-000061-001-EXP.xml -xsl:xslt/ted-to-eforms.xslt -o:development-notices/eforms-xml/21-000061-001-EXP.xml`
40 |
41 | ### Warnings and comments
42 |
43 | Each leaf element in the output eForms XML will be preceded by an HTML comment naming the Business Term it is associated with.
44 | Where the eForms XML standard requires information that is not present in the source TED XML, or the information is not of the
45 | required format, the XSLT application will report a warning, and the warning will be included in the output XML as an HTML comment.
46 |
47 | These warnings and comments can be suppressed by the use of the "includecomments", "includewarnings" and "showwarnings" parameters:
48 |
49 | `java -Xms6291456 -cp [path to saxon folder]/saxon9he.jar net.sf.saxon.Transform -dtd:off -expand:off -strip:all -s:development-notices/ted-xml/21-000061-001-EXP.xml -xsl:xslt/ted-to-eforms.xslt -o:development-notices/eforms-xml/21-000061-001-EXP.xml includecomments=0 includewarnings=0 showwarnings=0`
50 |
51 |
--------------------------------------------------------------------------------
/usage-information.md:
--------------------------------------------------------------------------------
1 | # TED XML to eForms XML Converter Usage information
2 |
3 |
4 | ## Usage
5 |
6 | The TEDXDC Converter has been developed and tested using the Saxon-9 HE XSLT processor, available from https://sourceforge.net/projects/saxon/files/Saxon-HE/9.9/. However any XSLT 2 processor can be used. The main template is ted-to-eforms.xslt, the other templates and data XML files are called by the main template.
7 |
8 | Please see [development-methodology.md](development-methodology.md) for the approach and methodology for developing the conversion in XSLT.
9 |
10 | Please see [installation.md](installation.md) for installation and usage instructions.
11 |
12 | An API for the converter is temporarily available as part of the eNotices2 Publication API. Documentation is available at [TED API Documentation](https://docs.ted.europa.eu/api/endpoints/enotices2-ted-europa-eu-esenders.html) or the [eNotices2 Public API endpoints Documentation](https://enotices2.ted.europa.eu/esenders/webjars/swagger-ui/index.html).
13 |
14 |
15 |
16 |
17 | # About the converter
18 |
19 | ## Incomplete and invalid XML output
20 |
21 | The XML output from the TED XML Data Converter will not be complete, and will also contain some errors. It will not pass all the eForms Schematron checks. This is because:
22 |
23 | * Some information required by eForms is not used in the TED schemas (for example: Internal ID (BT-22) has no equivalent in the TED schema )
24 | * Some information present in the TED XML is in a different format from that required by eForms (for example: a textual description in TED XML, a specific code from a codelist in eForms XML)
25 |
26 | The TED XML Data Converter will report these issues as comments and application-level warnings.
27 |
28 |
29 | ## Limited Scope
30 |
31 | The current version of the TED XML Data Converter will convert a subset of published TED notices:
32 |
33 | * TED Schema: only TED schema R.2.0.9 is supported. Notices published under Directive 81 cannot be converted with this version of the Converter.
34 | * TED Schema version: only the latest versions of the TED schema R.2.0.9 (S01 to S05) are supported. Notices published under earlier versions of the schema may be converted, but may contain more errors.
35 | * Document Types: All the standard TED XML forms using the R2.0.9 TED XML schema (with the exceptions of F14 Corrigendum and F20 Modification) are currently supported
36 |
37 |
38 | ## HTML Comments in output eForms XML
39 |
40 | Each leaf element in the output eForms XML will be preceded by an HTML comment naming the Business Term it is associated with.
41 |
42 | Where the eForms XML standard requires information that is not present in the source TED XML, or the information is not of the required format, the XSLT application will report a warning.
43 |
44 | * An HTML comment will precede the XML element stating that required information was not found in the source TED XML.
45 | * A warning message will be sent to the XSLT processing application using \.
46 |
47 | ## External Parameters
48 |
49 | Parameters passed to the XSLT processor may be used to set values for some Business Terms, and some processing options.
50 |
51 | ### Parameters to set values for Business Terms
52 |
53 | * Use parameter `"notice-identifier"` to set `BT-701 Notice Identifier`
54 | * Use parameter `"procedure-identifier"` to set `BT-04 Procedure Identifier`
55 | * Use parameter `"sdk-version"` to set the SDK version
56 |
57 | ### Parameters to change display of Warnings and Business Term comments
58 |
59 | * Set parameter `"includecomments"` to 0 to suppress Business Terms as HTML comments
60 | * Set parameter `"includewarnings"` to 0 to suppress Warnings as HTML comments
61 | * Set parameter `"showwarnings"` to 0 to suppress Warnings as application messages
62 |
--------------------------------------------------------------------------------
/xslt/common.xslt:
--------------------------------------------------------------------------------
1 |
2 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 |
41 |
42 |
43 |
44 |
45 |
46 |
47 |
48 |
49 |
50 |
51 |
52 |
53 |
54 |
55 |
56 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |
2 | # Disclaimer
3 | This project is currently under development. We may update the current version and replace it with a new version at any time. For this reason, we recommend you retrieve the latest version in order to ensure technical compliance. The Publications Office of the European Union cannot guarantee the accuracy, adequacy, validity, reliability, availability or completeness of this information and accepts no responsibility for any use you may make of this project’s component parts.
4 |
5 | The code and data in this repository is created by the Publications Office of the European Union and is licensed under the terms of the [EUPL-1.2 license](LICENSE).
6 |
7 | # Summary
8 |
9 | This project is managed by the Publications Office of the European Union to assist organisations publishing procurement notices in their migration from TED XML to eForms.
10 |
11 | An organisation publishing procurement notices may wish to switch the production of notices in their system from the TED schemas to the eForms schema at a point in time. In this case, they will have published some initial notices (PIN, Contract Notice, etc.) for an ongoing Procedure using the TED schemas. They will want to publish following notices, continuing the Procedure, using the eForms schema.
12 |
13 | The TED XML Data Converter is designed to help with this process, by converting a notice published in the TED schemas, to a draft form of the same notice in eForms. The publisher can then correct and complete this notice, and use it as a basis for creating a following notice in eForms.
14 |
15 | The repository contains the following folders:
16 |
17 | | Folder | Purpose |
18 | | --- | --- |
19 | | `xslt` | The xslt and data for the conversion |
20 | | `development-notices` | Sample source TED XML files used for testing during development and their equivalent converted eForms XML files |
21 | | `eforms-structure-files` | Sample files for the structure of eForms XML |
22 | | `test-notices` | Sample notices in TED schema XML to be used for testing the converter |
23 |
24 | The repository contains the following documentation files in Markdown format:
25 |
26 | | File | Purpose |
27 | | --- | --- |
28 | | [README.md](README.md) | This file |
29 | | [usage-information.md](usage-information.md) | General information on usage of this repository |
30 | | [installation.md](installation.md) | Basic instructions on installation in a Unix environment |
31 | | [development-methodology.md](development-methodology.md) | The technical approach to developing this conversion |
32 | | [CHANGELOG.md](CHANGELOG.md) | The list of changes made since the last release |
33 |
34 | Each folder also contains a README.md file listing the files in that folder and their purpose.
35 |
36 |
37 | # How to use
38 |
39 | Basic usage instructions for developers to run the code in their own system is available [here](usage-information.md).
40 |
41 | An API for the converter is temporarily available as part of the eNotices2 Publication API. Documentation is available at [TED API Documentation](https://docs.ted.europa.eu/api/endpoints/enotices2-ted-europa-eu-esenders.html) or the [eNotices2 Public API endpoints Documentation](https://enotices2.ted.europa.eu/esenders/webjars/swagger-ui/index.html).
42 |
43 | ## Versioning scheme
44 |
45 | The versioning scheme which will be adopted for the TED XML Data Converter will be similar to that for the [eForms SDK](https://docs.ted.europa.eu/eforms/latest/versioning.html).
46 |
47 |
48 | ## Feedback
49 |
50 | Feedback on this converter is welcome. Please address questions, comments and bug reports using [Github Discussions](https://github.com/OP-TED/ted-xml-data-converter/discussions).
51 |
52 |
53 | ## Current status
54 |
55 | All the standard TED XML forms using the R2.0.9 TED XML schema (with the exceptions of F14 Corrigendum and F20 Modification) are now convertible:
56 |
57 | * PIN (Prior information notice / Periodic indicative notice)
58 | (F01, F04, F07, F08, F21 and F22)
59 |
60 | * Contract Notice
61 | (F02, F05, F12, F21, F22, F23 and F24)
62 |
63 | * Contract Award Notice
64 | (F03, F06, F13, F15, F21, F22, F23, F24 and F25)
65 |
66 | ### What's next?
67 |
68 | Work on the Defense TED XML forms using the R2.0.8 TED XML schema has begun.
69 |
70 |
--------------------------------------------------------------------------------
/ted-elements-not-convertible.md:
--------------------------------------------------------------------------------
1 | # TED schema elements which cannot be converted to eForms
2 |
3 | This table lists the elements defined in the TED R.2.0.9 schema for Contract Notices, but whose data cannot be converted to any data structures in eForms.
4 |
5 |
6 | | TED Element | TED schema | Content format Usage | Description | Reason for inability to convert |
7 | | --- | --- | --- | --- | --- |
8 | | CA_ACTIVITY_OTHER | R2.0.9 | Text | Alternative to CA_ACTIVITY, containing textual description | Cannot convert text to a code |
9 | | CE_ACTIVITY_OTHER | R2.0.9 | Text | Alternative to CE_ACTIVITY, containing textual description | Cannot convert text to a code |
10 | | CA_TYPE_OTHER | R2.0.9 | Text | Alternative to CA_TYPE, containing textual description | Cannot convert text to a code |
11 | | CRITERIA_CANDIDATE | R2.0.9 | Text | Objective criteria for choosing the limited number of candidates | eForms does not record the criteria used for selecting candidates for the second stage |
12 | | NO_OPTIONS | R2.0.9 | Empty | Information about options | No need to convert as no eForms output is required to state that there are no options available |
13 | | ECONOMIC_CRITERIA_DOC | R2.0.9 | Text | Selection criteria as stated in the procurement documents | eForms does not specify that Selection Criteria are contained in external documents |
14 | | TECHNICAL_CRITERIA_DOC | R2.0.9 | Text | Selection criteria as stated in the procurement documents | eForms does not specify that Selection Criteria are contained in external documents |
15 | | FT | R2.0.9 | Text | Subscript and Superscript text within P (paragraph) elements | eForms does not support emphasised text. |
16 | | LEGAL_BASIS_OTHER | R2.0.9 | Text | LEGAL_BASIS_OTHER contains text which describes the legal basis for the notice | Cannot convert text to a code; eForms uses a codelist for Procedure Legal Basis (BT-01) |
17 | | LOT_COMBINING_CONTRACT_RIGHT | R2.0.9 | Text | The contracting authority reserves the right to award concessions combining the following lots or groups of lots - Text | Group of Lots described as text cannot be converted into a structural group of lots |
18 | | NO_LOT_DIVISION | R2.0.9 | Boolean | This contract is not divided into lots | No need to convert as no eForms output is required to state that there is no lot division |
19 | | LOT_DIVISION | R2.0.9 | Boolean | This contract is divided into lots | There is no equivalent BT to LOT_DIVISION. There are no children of LOT_DIVISION in F03 to convert |
20 | | REFERENCE_TO_LAW | R2.0.9 | Text | Reference to the relevant law, regulation or administrative provision (Execution of the service is reserved to a particular profession) | eForms does not have a BT to hold the reference to law for reserving the procurement for a particular profession |
21 | | REFERENCE_NUMBER | R2.0.9 | Text | Reference number (Object section) | eForms does not have a BT to hold a reference number |
22 | | TECHNICAL_CRITERIA_DOC | R2.0.9 | Text | Selection criteria as stated in the procurement documents | eForms does not specify that Selection Criteria are contained in external documents |
23 | | PARTICULAR_PROFESSION | R2.0.9 | Text | Form F12 only: Participation is reserved to a particular profession | Equivalent eForms Reserved Participation (BT-71) is forbidden for Design Contest notices (subtypes 23 and 24) |
24 | | NO_PARTICULAR_PROFESSION | R2.0.9 | Empty | Form F12 only: Participation is reserved to a particular profession | Equivalent eForms Reserved Participation (BT-71) is forbidden for Design Contest notices (subtypes 23 and 24) |
25 | | URL_NATIONAL_PROCEDURE | R2.0.9 | URL | Information about national procedures is available at (URL) | eForms does not have a BT to hold a national procedure URL |
26 | | OBJECT_CONTRACT/VAL_RANGE_TOTAL/HIGH and OBJECT_CONTRACT/VAL_RANGE_TOTAL/LOW | R2.0.9 | Value | Total value of the procurement (excluding VAT) - Lowest offer / Highest offer taken into consideration | eForms does not have a BT to hold range values for offers across all lots |
27 | | AWARDED_CONTRACT/VALUE/VAL_ESTIMATED_TOTAL and AWARDED_CONTRACT/VALUES/VAL_ESTIMATED_TOTAL | R2.0.9 | Value | Initial estimated total value of the contract / lot (for framework agreements or dynamic purchasing systems – estimated total maximum value for the entire duration of this lot) | When the notice is not part of a Framework Agreement or DPS, there is no eForms equivalent of this element |
28 | | DATE_AWARD_SCHEDULED | R2.0.9 | Date | Present in forms F01, F04, F21 and F22 | eForms does not have a BT to hold a DATE_AWARD_SCHEDULED |
29 | | VAL_BARGAIN_PURCHASE | R2.0.9 | Value | Price paid for bargain purchases | eForms does not have a BT related to bargain purchases |
30 | | VAL_PRIZE | R2.0.9 | Value | Value of the prize(s) | eForms does not have a BT to hold prize value in the Results section |
31 |
--------------------------------------------------------------------------------
/development-notices/README.md:
--------------------------------------------------------------------------------
1 | # TED XML files selected for testing during development
2 |
3 | This table lists the TED XML files selected to test development of the Converter, and the reasons for their selection.
4 |
5 | | File | Form Type | Document Type | Topic | Reasons for selection |
6 | | --- | --- | --- | --- | --- |
7 | | 20-155018-001-EXP.xml | F01 | PIN | Subtype mapping | PRI_ONLY Maps to subtype 4 |
8 | | 21-000061-001-EXP.xml | F03 | CAN | CAN | First CAN |
9 | | 21-000934-001-EXP.xml | F03 | CAN | Translations | One original English, 23 translations |
10 | | 21-010961-001-EXP.xml | F03 | CAN | Legal Basis | Other Legal Basis for EIB - no eForms subtype mapping available for this Notice |
11 | | 21-050204-001-EXP.xml | F03 | CAN | Translations | One original English, 23 translations |
12 | | 21-064844-001-EXP.xml | F02 | CN | Addresses | All 7 Address elements, 1 duplicated address |
13 | | 20-587026-001-EXP.xml | F02 | CN | Procurement | PROCUREMENT_LAW -> BT-01 Legal Basis Local - Text |
14 | | 20-260117-001-EXP.xml | F02 | CN | Procurement | ACCELERATED_PROC -> BT-106 Procedure Accelerated |
15 | | 20-162034-001-EXP.xml | F02 | CN | Lot | Multiple Tendering languages |
16 | | 20-156049-001-EXP.xml | F02 | CN | Addresses | multiple URL_BUYER |
17 | | 20-377805-001-EXP.xml | F02 | CN | Lot | TIME_RECEIPT_TENDERS with one digit for hour |
18 | | 21-119240-001-EXP.xml | F05 | CN | Lot Selection Criteria | RULES_CRITERIA and REDUCTION_RECOURSE |
19 | | 20-566267-001-EXP.xml | F02 | CN | Lot | FRAMEWORK and DPS_ADDITIONAL_PURCHASERS |
20 | | 20-295737-001-EXP.xml | F21 | CN | Procedure | MAIN_FEATURES_AWARD |
21 | | 21-120407-001-EXP.xml | F02 | CN | Dates | DATE_TENDER_VALID |
22 | | 20-198944-001-EXP.xml | F02 | CN | NUTS | No NUTS3 codes, MAIN_SITE with 7 P |
23 | | 20-213571-001-EXP.xml | F02 | CN | NUTS | No NUTS3 codes, no MAIN_SITE |
24 | | 20-164186-001-EXP.xml | F02 | CN | NUTS | 1 NUTS3 code, no MAIN_SITE |
25 | | 20-560391-001-EXP.xml | F21 | CN | NUTS | 3 NUTS3 codes, no MAIN_SITE |
26 | | 21-051959-001-EXP.xml | F02 | CN | NUTS | 1 NUTS3 code, MAIN_SITE with 2 P |
27 | | 20-246700-001-EXP.xml | F02 | CN | NUTS | 1 NUTS3 code, MAIN_SITE with 3 P |
28 | | 20-156983-001-EXP.xml | F02 | CN | NUTS | 2 NUTS3 codes, MAIN_SITE with 1 P |
29 | | 21-077815-001-EXP.xml | F02 | CN | NUTS | 2 NUTS3 codes, MAIN_SITE with 2 P |
30 | | 20-343258-001-EXP.xml | F02 | CN | NUTS | 5 NUTS3 codes, MAIN_SITE with 5 P |
31 | | 21-363118-001-EXP.xml | F12 | CN | Lot Selection Criteria | CRITERIA_SELECTION |
32 | | 20-179994-001-EXP.xml | F12 | CN | Prize | NUMBER_VALUE_PRIZE and DETAILS_PAYMENT |
33 | | 21-364236-001-EXP.xml | F02 | CN | | |
34 | | 21-363066-001-EXP.xml | F02 | CN | | |
35 | | 21-363062-001-EXP.xml | F02 | CN | | |
36 | | 21-362774-001-EXP.xml | F02 | CN | | |
37 | | 21-364516-001-EXP.xml | F12 | CN | Award Criteria | MEMBER_NAME |
38 | | 21-364082-001-EXP.xml | F05 | CN | | |
39 | | 21-357646-001-EXP.xml | F03 | CAN | Contract award | PT_AWARD_CONTRACT_WITHOUT_CALL |
40 | | 21-362579-001-EXP.xml | F03 | CAN | Contract award | TERMINATION_PIN |
41 | | 21-364180-001-EXP.xml | F03 | CAN | | |
42 | | 21-364240-001-EXP.xml | F03 | CAN | | |
43 | | 20-157399-001-EXP.xml | F03 | CAN | SettledContract | No DPS, no FRAMEWORK |
44 | | 20-157543-001-EXP.xml | F03 | CAN | SettledContract | FRAMEWORK |
45 | | 22-086633-001-EXP.xml | F03 | CAN | SettledContract | Multiple AWARD_CONTRACT collated into one SettledContract |
46 | | 22-091559-001-EXP.xml | F03 | CAN | SettledContract | NO_AWARDED_CONTRACT |
47 | | 21-139343-001-EXP.xml | F15 | CAN | Award Criteria | DIRECTIVE_2014_24_EU/AC/AC_PRICE |
48 | | 22-023722-001-EXP.xml | F15 | CAN | Award Criteria | DIRECTIVE_2014_24_EU/AC/AC_COST |
49 | | 21-158592-001-EXP.xml | F15 | CAN | Award Criteria | DIRECTIVE_2014_25_EU/AC/AC_PRICE |
50 | | 21-149886-001-EXP.xml | F15 | CAN | Award Criteria | DIRECTIVE_2014_23_EU |
51 | | 21-298854-001-EXP.xml | F15 | CAN | Award Criteria | DIRECTIVE_2009_81_EC/AC/AC_PRICE |
52 | | 22-073124-001-EXP.xml | F15 | CAN | Award Criteria | DIRECTIVE_2009_81_EC/AC/AC_CRITERIA |
53 | | 21-119282-001-EXP.xml | F24 | CN | Award Criteria | AC/AC_CRITERION |
54 | | 21-205737-001-EXP.xml | F25 | CAN | Award Criteria | AC/AC_CRITERION |
55 | | 19-271873-001-EXP.xml | F03 | CAN | Framework | 109 Lots, 5 Awards |
56 | | 20-168879-001-EXP.xml | F03 | CAN | Performance analysis | 652 Lots, 1105 Awards |
57 | | 20-537923-001-EXP.xml | F03 | CAN | Performance analysis | 5 Lots, 178 Awards |
58 | | 22-104446-001-EXP.xml | F02 | CN | Multilingual | 3 ORIGINAL languages, 3 Lots |
59 | | 22-109282-001-EXP.xml | F03 | CAN | Multilingual | 1 ORIGINAL language, 23 TRANSLATION languages, 3 Lots, 6 Awards |
60 | | 21-419119-001-EXP.xml | F12 | CN | Multilingual | 1 ORIGINAL language, 23 TRANSLATION languages, DETAILS_PAYMENT and NUMBER_VALUE_PRIZE |
61 | | 22-011421-001-EXP.xml | F03 | CAN | Multilingual | 1 ORIGINAL language, 23 TRANSLATION languages, INFO_ADD_SUBCONTRACTING |
62 | | 21-635824-001-EXP.xml | F21 | CAN | Multilingual | 1 ORIGINAL language, 23 TRANSLATION languages, modified to add URL_NATIONAL_PROCEDURE |
63 | | 19-289373-001-EXP.xml | F22 | CN | Subtype mapping | Notice type QSU_CALL_COMPETITION |
64 | | 20-318547-001-EXP.xml | F22 | CN | Lot | QS/INDEFINITE_DURATION |
65 | | 21-048169-001-EXP.xml | F03 | CAN | Lot | EU_PROGR_RELATED |
66 | | 18-536293-001-EXP.xml | F13 | CAN | Design Result | Multiple WINNER elements |
67 | | 19-111211-001-EXP.xml | F13 | CAN | Design Result | NO_AWARDED_PRIZE |
68 | | 20-620029-001-EXP.xml | F07 | CN | Qualification System | Call for competition |
69 | | 20-271232-001-EXP.xml | F07 | CN | Qualification System | Call for competition |
70 | | 19-099886-001-EXP.xml | F08 | PIN | Buyer Profile | Example of F08 |
71 | | 18-412273-001-EXP.xml | F06 | CAN | Result | VAL_SUBCONTRACTING |
72 | | 22-434184-001-EXP.xml | F04 | PIN | PIN RTL | LOT_MAX_NUMBER |
73 | | 19-090974-001-EXP.xml | F21 | CN | Lot | RESERVED_ORGANISATIONS_SERVICE_MISSION, RESTRICTED_SHELTERED_PROGRAM, RESTRICTED_SHELTERED_WORKSHOP |
74 | | 19-318420-001-EXP.xml | F25 | CAN | Result | CALCULATION_METHOD, INFO_ADD_VALUE, VAL_PRICE_PAYMENT, VAL_REVENUE |
75 | | 18-151256-001-EXP.xml | F12 | CN | Design | DIRECTIVE, NB_MAX_PARTICIPANTS, NB_MIN_PARTICIPANTS, PARTICIPANT_NAME |
76 | | 23-119901-001-EXP.xml | F14 | XX | Corrigendum | F14 notices cannot be converted |
77 | | 18-156915-001-EXP.xml | F13 | CAN | Result | NB_PARTICIPANTS_OTHER_EU, NB_PARTICIPANTS_SME |
78 | | 18-168448-001-EXP.xml | F02 | CN | Lot | INFO_ADD_EAUCTION |
79 |
80 |
81 |
82 |
83 |
--------------------------------------------------------------------------------
/xslt/simple.xslt:
--------------------------------------------------------------------------------
1 |
2 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 |
41 |
42 |
43 |
44 |
45 |
46 |
47 |
48 |
49 |
50 |
51 |
52 |
53 |
54 |
55 |
56 |
57 |
58 |
59 |
60 |
61 |
62 |
63 |
64 |
65 |
66 |
67 |
68 |
69 |
70 |
71 |
72 |
73 |
74 |
75 |
76 |
77 |
78 |
79 |
80 |
81 |
82 |
83 |
84 |
85 |
86 | 1
87 |
88 |
89 |
90 | allowed
91 |
92 |
93 |
94 | not-allowed
95 |
96 |
97 |
98 | eu-funds
99 |
100 |
101 |
102 | no-eu-funds
103 |
104 |
105 |
106 |
107 |
108 |
109 |
110 | true
111 |
112 |
113 |
114 | false
115 |
116 |
117 |
118 |
119 |
120 |
121 |
122 |
123 |
124 |
125 |
126 |
127 |
128 |
129 | true
130 |
131 |
132 |
133 |
134 |
135 |
136 |
137 |
138 |
139 |
140 |
141 |
--------------------------------------------------------------------------------
/xslt/languages-map.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 | EN
5 | ENG
6 | English
7 |
8 |
9 | AR
10 | ARA
11 | Arabic
12 |
13 |
14 | BR
15 | BRE
16 | Breton
17 |
18 |
19 | BG
20 | BUL
21 | Bulgarian
22 |
23 |
24 | CA
25 | CAT
26 | Catalan
27 |
28 |
29 | CS
30 | CES
31 | Czech
32 |
33 |
34 | CO
35 | COS
36 | Corsican
37 |
38 |
39 | CY
40 | CYM
41 | Welsh
42 |
43 |
44 | DA
45 | DAN
46 | Danish
47 |
48 |
49 | DE
50 | DEU
51 | German
52 |
53 |
54 | EL
55 | ELL
56 | Greek
57 |
58 |
59 | ET
60 | EST
61 | Estonian
62 |
63 |
64 | EU
65 | EUS
66 | Basque
67 |
68 |
69 | FO
70 | FAO
71 | Faroese
72 |
73 |
74 | FI
75 | FIN
76 | Finnish
77 |
78 |
79 | FR
80 | FRA
81 | French
82 |
83 |
84 | FY
85 | FRY
86 | Frisian
87 |
88 |
89 | GD
90 | GLA
91 | Scottish Gaelic
92 |
93 |
94 | GA
95 | GLE
96 | Irish
97 |
98 |
99 | GL
100 | GLG
101 | Galician
102 |
103 |
104 | HE
105 | HEB
106 | Hebrew
107 |
108 |
109 | HR
110 | HRV
111 | Croatian
112 |
113 |
114 | HU
115 | HUN
116 | Hungarian
117 |
118 |
119 | HY
120 | HYE
121 | Armenian
122 |
123 |
124 | IS
125 | ISL
126 | Icelandic
127 |
128 |
129 | IT
130 | ITA
131 | Italian
132 |
133 |
134 | JA
135 | JPN
136 | Japanese
137 |
138 |
139 | KL
140 | KAL
141 | Greenlandic
142 |
143 |
144 | KO
145 | KOR
146 | Korean
147 |
148 |
149 | KU
150 | KUR
151 | Kurdish
152 |
153 |
154 | LV
155 | LAV
156 | Latvian
157 |
158 |
159 | LT
160 | LIT
161 | Lithuanian
162 |
163 |
164 | LB
165 | LTZ
166 | Luxembourgish
167 |
168 |
169 | MK
170 | MKD
171 | Macedonian
172 |
173 |
174 | MT
175 | MLT
176 | Maltese
177 |
178 |
179 | NL
180 | NLD
181 | Dutch
182 |
183 |
184 | NO
185 | NOR
186 | Norwegian
187 |
188 |
189 | OC
190 | OCI
191 | Occitan
192 |
193 |
194 | PL
195 | POL
196 | Polish
197 |
198 |
199 | PT
200 | POR
201 | Portuguese
202 |
203 |
204 | RM
205 | ROH
206 | Romansh
207 |
208 |
209 | RO
210 | RON
211 | Romanian
212 |
213 |
214 | SK
215 | SLK
216 | Slovak
217 |
218 |
219 | SL
220 | SLV
221 | Slovenian
222 |
223 |
224 | SE
225 | SME
226 | Northern Sami
227 |
228 |
229 | ES
230 | SPA
231 | Spanish
232 |
233 |
234 | SQ
235 | SQI
236 | Albanian
237 |
238 |
239 | SR
240 | SRP
241 | Serbian
242 |
243 |
244 | SV
245 | SWE
246 | Swedish
247 |
248 |
249 | TA
250 | TAM
251 | Tamil
252 |
253 |
254 | TR
255 | TUR
256 | Turkish
257 |
258 |
259 | WA
260 | WLN
261 | Walloon
262 |
263 |
264 | ZH
265 | ZHO
266 | Chinese
267 |
268 |
269 | MS
270 | MSA
271 | Malaysian
272 |
273 |
274 | ME
275 | CNR
276 | Montenegrin
277 |
278 |
279 |
--------------------------------------------------------------------------------
/development-methodology.md:
--------------------------------------------------------------------------------
1 | # TED XML to eForms XML Converter: methodology
2 |
3 | This page attemps to describe the technical approach to the conversion, and the process of analysis for determining the correct mapping and conversion between TED XML and eForms XML elements.
4 |
5 | ## Technical approach
6 |
7 | ### Business Terms
8 | The expression "Business Term" is exclusive to eForms. It has not been used previously for TED XML. It refers to an eForms business concept. Sometimes this will be expressed in only one structure/location in eForms XML. Often, it is relevant in multiple contexts ("top-level" Procedure, Lot, Result), and so could be expressed in more than one structure/location in eForms XML. The [Schema section of the eForms documentation](https://docs.ted.europa.eu/eforms/0.6.0/schema/index.html) groups these contexts together (see section [Procedure, Group of Lots, Lot & Part related information](https://docs.ted.europa.eu/eforms/0.6.0/schema/procedure-lot-part-information.html) ), so that each Business Term is described only once.
9 |
10 | Since this document is expressly about XSLT conversion, it will focus mainly on XML elements, and less about Business Terms. Hence, the term "XML structure" will be used to refer to a single XML element or XML structure; this may or may not be an expression of a single Business Term.
11 |
12 | ### Considerations
13 |
14 | There is not always a 1-to-1 mapping between a single TED XML structure and a single eForms XML structure.
15 |
16 | * Some TED XML elements have no equivalent in eForms XML
17 | * Some TED XML structures map to multiple XML structures and locations in eForms XML
18 | * Some eForms Business Terms are mandatory in some contexts; their expression as XML structures are thus also mandatory, even if no equivalent TED XML structure is present in the source XML notice.
19 |
20 |
21 | ### XSLT processing model
22 |
23 | In XSLT conversion, there are two main models. These can be mixed within one conversion.
24 |
25 | | Aspect | Push Model | Pull Model |
26 | | --- | --- | --- |
27 | | Language style | Declarative | Procedural |
28 | | Conversion driven by | Source XML | XSLT Stylesheet |
29 | | Structure provided by | Source XML | XSLT Stylesheet |
30 | | Order provided by | Source XML | XSLT Stylesheet |
31 | | 1-to-1 conversion of optional elements | Automatic | Test required |
32 | | 1-to-many element conversion | Contextual tests required | Driven by location |
33 | | Looping | Automatic | For-each required |
34 | | Output required when source elements missing | Not possible | Possible |
35 | | Same output in multiple locations | Automatic | Must be repeated |
36 | | Where multiple data points required | Very complex expressions; must be repeated in each required context | Calculated once and stored in variables |
37 |
38 |
39 |
40 |
41 | From the above comparison, it can be seen that the Push Model is used when there is great similarity between the structure and order of elements between the input XML and the output XML. The Pull Model is used when the structures or order differ significantly.
42 |
43 | In this conversion XSLT, the Pull Model dominates. This is because:
44 | * Higher-level structures are significantly different between eForms and TED XML
45 | * Results of complex data expressions can be used in multiple contexts
46 | * Some eForms elements are mandatory, while TED XML equivalents may not be
47 | * Some TED XML structures require expression in multiple locations in eForms XML
48 |
49 | However, where there is a consistent and simple mapping between TED XML elements and eForms XML elements, the Push Model is used. This is because:
50 | * Push Model templates can be easier to understand
51 | * Only one template is required if conversion is the same in multiple locations
52 |
53 |
54 |
55 | ## Information used for the conversion
56 |
57 | ### Multiple dimensions
58 |
59 | There are multiple dimensions to this conversion:
60 |
61 | * Two main distinct sets of TED XML schemas:
62 | * R.2.0.9 - "Standard" forms
63 | * R.2.0.8 - "Defence" forms
64 | * 22 TED XML Forms map to 45 eForms Forms
65 | * eForms schema is well written, consistent and well documented (but incomplete)
66 | * TED XML schema is less well written, inconsistent and poorly documented
67 | * Organisation of information differs between the schemas
68 | * TED XML schemas evolved over time -> differences in published TED XML notices
69 | * eForms schema has more information points than TED XML schemas
70 | * Element occurrence rules are defined differently between eForms and TED XML
71 | * Less than 20 eForms example XML notices exist (at time of writing), these are not complete and not fully definitive
72 |
73 | ### Information sources
74 |
75 | #### TED XML
76 |
77 | * TED XML Schemas
78 | * A million published XML notices
79 | * Validation Rules spreadsheets
80 | * The spreadsheets created from the April 2021 mapping of TED XML form items to business terms by European Commission
81 | * TED XML procurement PDF forms
82 |
83 | #### eForms
84 |
85 | * eForms XML Schemas
86 | * UBL documentation
87 | * eForms documentation
88 | * eForms Regulation Annex spreadsheet
89 |
90 |
91 | | Aspect | TED XML Sources | eForms sources |
92 | | --- | --- | --- |
93 | | Document structure | TED XML schemas Published notices | eForms XML Schemas eForms documentation |
94 | | Element occurrence variations | TED XML schemas Published notices Validation Rules spreadsheets TED XML form item mapping spreadsheets | **eForms documentation** eForms Regulation Annex spreadsheet |
95 | | Element purpose, definitions, documentation | Element names *partly* Validation Rules spreadsheets *poor and incomplete* TED PDF form item mapping spreadsheets *unreliable* TED PDF forms | eForms XML Schemas eForms documentation *eForms Regulation Annex spreadsheet* eForms codelists |
96 |
97 | ## Occurrence and priority
98 |
99 | There exists an extremely large number of variations of types of existing TED XML notice, arising from the combination of different TED XML schemas, the multiple Form types, and the historic schema evolution. These variations in types are far from evenly distributed. As it is considered not feasible to complete the conversion XSLT for all these variations, priority must be given to those with the greatest number of published notices.
100 |
101 | ### Published TED XML data set
102 |
103 | In preparation for this work, two years' worth (1,200,000 XML files) of TED XML notices were prepared for analysis. This set spans from March 2020 to February 2022. It covers the two TED XML schemas, but only the latest versions of these. Previous versions are thus not currently considered.
104 |
105 | ## Analysis process
106 |
107 | This section attempts to describe the analysis process used to determine the mapping and conversion templates required for each element. As the process relies heavily on analysis of the downloaded XML, which is currently only available on my laptop, this process is restricted to me.
108 |
109 |
110 | ### The main structures
111 |
112 | As explained above, for the overall structure of the XSLT a Pull Model based on the eForms XML schema has been used. The order of analysis follows the order of structures and elements of the eForms schema. This ensures that all required output elements are included, irrespective of any equivalent elements in the TED XML schema.
113 |
114 | Thus the main structures (of the first form to be analysed, the Contract Notice form) are:
115 |
116 | * Notice Information
117 | * Procurement Information
118 | * Organization Information
119 | * Procedure Tendering Terms
120 | * Procedure Tendering Process
121 | * Procedure Procurement Project
122 | * Lots
123 | * Lot Tendering Terms
124 | * Lot Tendering Process
125 | * Lot Procurement Project
126 |
127 | Within each structure, the steps taken are:
128 |
129 | #### 1. Identify the next structure in eForms
130 | In the eForms documentation for the section, read the table at the beginning of the section, which lists all the Business Terms used. Identify the next BT (or group of BTs) to work on. Read the occurrence symbol for that BT to ensure that it is relevant in the section context. Document this in a comment in the XSLT file.
131 | Check that the order matches with the element order defined in the eForms schema.
132 |
133 | #### 2. Check the Annex spreadsheet for eForms subtype relevance
134 | Review the Annex spreadsheet for the related BTs **and BGs**, determining which eForms subtypes they are allowed / forbidden / mandatory for. Document this in a comment in the XSLT file. If they are allowed for form 16, proceed with the next steps.
135 |
136 | #### 3. Determine the cardinality(-ies) of the eForms structure
137 | Identify the XML structure used for the selected BT or BTs. Examine the documentation for all the related BTs for the structure (those using the same parent elements or structures), reviewing the cardinalities of all the elements involved. It may be helpful to consider them together as a group. If the structure is repeated, either for the current BT or for other BTs, check which elements in the overall structure should be repeated by reviewing the documentation and the schema.
138 |
139 | #### 4. Determine the use / purpose of the eForms structure
140 | Review the documentation and Annex spreadsheet to understand what information the structure is used for.
141 |
142 | If the structure uses a codelist, extract the codes and labels for consideration. Consider adding the list of codes and labels as a comment in the XSLT file.
143 |
144 | #### 5. Identify the structure used in TED XML for the same purpose
145 | Review the information sources listed above for the TED XML to find the appropriate structures used for the same information. If none are found, document this in a comment in the XSLT, and move on to the next eForms structure.
146 | If an equivalent TED XML structure is found, check:
147 | * If the structure is used in only one, or more, locations in the TED XML schema
148 | * If the structure is an enumerated set of alternatives (consider mapping to an eForms codelist)
149 | * Which TED XML forms allow the structure, and for each the cardinality and requirement (Optional or Mandatory)
150 |
151 | #### 6. Optional: analyse text content of the TED XML structure
152 | If the identified TED XML structure contains text (such as a \
element), extract and collate all the text variations from the TED XML data set.
153 |
154 | If the text is an enumerated set (either an attribute with an enumerated set of values, list them. Determine the meaning behind each, and map to the equivalent eForms codelist code.
155 |
156 | If the text is expressed in the language of the form, consider only the English versions. Read enough to confirm understanding of the meaning / use of the structure.
157 |
158 | #### Choose the appropriate conversion approach (processing model and template structure)
159 |
160 | *This is more of a guide than definitive*
161 |
162 | * If the mapping is simple, and there is no mapping required for "missing" TED XML elements (that is, no eForms subtypes have this BT as mandatory), choose the Push model, and write \ and \ templates.
163 |
164 | * If the eForms element is mandatory according to either the Annex or the documentation (also consider the parent BG), and the TED XML element is not always present, choose the Pull model, and write \ and \ templates.
165 |
166 |
167 |
168 | ### TED XML elements which cannot be converted
169 |
170 | Some elements that exist in TED XML notices contain information which cannot be included in eForms XML. These, and the reasons they cannot be included in eForms, are listed in [ted-elements-not-convertible.md](ted-elements-not-convertible.md).
171 |
172 |
173 |
174 |
175 |
--------------------------------------------------------------------------------
/development-notices/ted-xml/20-318547-001-EXP.xml:
--------------------------------------------------------------------------------
1 |
2 |
10 |
11 | 20-318547-001
12 | 20210630
13 | IT
14 | From Convertor
15 |
16 |
17 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 | S
28 | 126
29 | 20200702
30 |
31 |
32 | 2020/S 126-309175
33 |
34 | http://ted.europa.eu/udl?uri=TED:NOTICE:309175-2020:TEXT:IT:HTML
35 |
36 | IT
37 |
38 | www.comune.acireale.ct.it
39 | https://acireale.trasparenza-valutazione-merito.it/web/trasparenza/dettaglio-trasparenza?p_p_id=jcitygovmenutrasversaleleftcolumn_WAR_jcitygovalbiportlet&p_p_lifecycle=0&p_p_state=normal&p_p_mode=view&p_p_col_id=column-2&p_p_col_count=1&_jcitygovmenu
40 | Social work services
41 | Catania
42 | Catania
43 |
44 |
45 | 20200630
46 | Utilities entity
47 | Qualification system without call for competition
48 | Services
49 | Not applicable
50 | European Union
51 | Not applicable
52 | Not applicable
53 | Other
54 | 01G22
55 | 01
56 |
57 |
58 |
59 |
60 |
61 | Итaлия
62 | Acireale
63 |
64 |
PON inclusione — avviso pubblico per l'accreditamento di enti promotori qualificati ai fini dell'attivazione di tirocini di inclusione sociale — azione B.2.B.
229 |
230 |
231 |
232 |
233 | Infraestruturas de Portugal, S. A.
234 |
235 |
236 |
237 |
238 |
239 |
240 |
241 | Infraestruturas de Portugal, S. A.
242 | 503933813
243 | Praça da Portagem
244 | Almada
245 | 2809-013
246 |
247 | contratos@infraestruturasdeportugal.pt
248 |
249 | http://www.infraestruturasdeportugal.pt/
250 |
251 |
252 |
253 |
254 |
Empreitada EN341 - ACESSO AO TERMINAL FERROVIÁRIO DE ALFARELOS (EN342) - 1ª FASE - SUPRESSÃO DA PN DA EN 342 (PK 219,597 DO RAMAL DE ALFARELOS) E NOVO ACESSO, PELA EN341, AO TERMINAL FERROVIÁRIO DE ALFARELOS
Syftet med detta dynamiska inköpssystem är att kunna avropa kommunens olika behov av arbetsbefrämjande insatser av skiftande karaktär på ett enhetlig sätt.
Syftet med detta dynamiska inköpssystem är att kunna avropa kommunens olika behov av arbetsbefrämjande insatser av skiftande karaktär på ett enhetlig sätt.
Gemeinde Veitshöchheim, Sportplatzbauarbeiten an der Freisportanlage
256 |
257 |
258 |
259 |
260 |
261 |
262 |
Gegenstand des Auftrages ist die Vergabe von Sportplatzbauarbeiten bei der Freisportanlage am Schulzentrum in der Günterslebener Str. 41, 97209 Veitshöchheim. Die Arbeiten sollen ab den Sommerferien 2020 stattfinden. Bisher ist die Fertigstellung Mitte 2021 geplant.
263 |
264 |
265 |
266 |
267 |
268 |
Günterslebener Straße 41
269 |
97209 Veitshöchheim
270 |
271 |
272 |
Die Gemeinde Veitshöchheim beabsichtigt bei der Freisportanlage am Schulzentrum (Günterslebener Str. 41, 97209 Veitshöchheim) eine Belagssanierung durchzuführen.
273 |
Folgende Arbeiten sind hauptsächlich notwendig:
274 |
— Abbruch und Neubau des Kunststoffbelags:
275 |
—— Belagstyp A ca. 5 200 m2;
276 |
—— Belagstyp B ca. 1 200 m2.
277 |
— Einbau einer neuen Bitu-Tragschicht in Teilbereichen der Sportflächen;
278 |
— Tiefenreinigung von zwei Kleinspielfeldern und punktuelle Ausbesserung von Schadstellen;
279 |
— Abbruch und Neubau von beschädigten Einfassungen;
280 |
— Abbruch und Neubau von zwei Weitsprunggruben;
281 |
— Ausbau von beschädigten Kastenrinnen der Rundlaufbahn;
282 |
— Montage von neuen Sporteinbauteilen wie z. B. Bodenhülsen, Basketballständern, Absprungbalken sowie Aufbringen von Spielfeldlinierungen;
283 |
— Einbau einer Wurzelschutzbahn seitlich der Weit-/Hochsprungbahn, um das Einwachsen von Wurzeln zu verhindern;
284 |
— Partieller Austausch von defekten Drainleitungen unter Sportflächen.
Conformément à l'article 36-i de l'ordonnance nº 2015-899 du 23.7.2015 relative aux marchés publics: «le présent marché est reservé aux entreprises adaptées mentionnées à l'article L. 5213-13 du code du travail, à des établissements et services d'aide par le travail mentionnés à l'article L. 344-2 du code de l'action sociale et des familles ainsi qu'à des structures équivalentes, lorsqu'ils emploient une proportion de 50 %, de travailleurs handicapés qui, en raison de la nature ou de la gravité de leurs defiences, ne peuvent exercer une activité professionnelle dans des conditions normales.»
The University of Copenhagen’s Center for Advanced Bioimaging (CAB) facility will establish new capacity to deliver spinning-disc confocal microscopy to users and partners. The purpose of this tender is to purchase a custom-built spinning-disc confocal microscope. On this basis, the purpose of the contract is to help the Contracting Entity achieve installation of a functional custom-built spinning disc confocal microscope in the assigned location.
The University of Copenhagen’s Center for Advanced Bioimaging (CAB) facility will establish new capacity to deliver spinning-disc confocal microscopy to users and partners. The purpose of this tender is to purchase a custom-built spinning-disc confocal microscope. On this basis, the purpose of the contract is to help the Contracting Entity achieve installation of a functional custom-built spinning disc confocal microscope in the assigned location.
This Dynamic Procurement System and the selection guidelines aim to inform interested prospective candidates with regard to the rules of procedure and criteria applicable to the Dynamic Procurement System for sequencing services. The suitability of a prospective candidate for each or all of the categories is determined during this first stage.
This Dynamic Procurement System and the selection guidelines aim to inform interested prospective candidates with regard to the rules of procedure and criteria applicable to the Dynamic Procurement System for sequencing services. The suitability of a prospective candidate for each or all of the categories is determined during this first stage.
The aim of the procurement is to get an operator in place for the temporary operation of the express boat between Bergen and Nordfjord/Sogn called 'express boat Bergen-Nordfjord/Sogn for the period 2022-2024'. The contracting authority would like to enter into a contract with one operator for the entire contract. The contract period is from the date the contract is signed until and including 30 November 2024, with an option for up to 2 years. The start-up of route will be 1 May 2022.
The aim of the procurement is to get an operator in place for the temporary operation of the express boat between Bergen and Nordfjord/Sogn called 'express boat Bergen-Nordfjord/Sogn for the period 2022-2024'. The contracting authority would like to enter into a contract with one operator for the entire contract. The contract period is from the date the contract is signed until and including 30 November 2024, with an option for up to 2 years. The start-up of route will be 1 May 2022.
286 |
287 |
288 | Price
289 | Water jet as the propulsion method
290 | Number of seats on board
291 | Play area
292 |
293 | 596000000
294 | 31
295 |
296 |
297 |
The contracting authority has the unilateral right to extend the option for up to 24 months split between 2 extensions, based on the same terms as stated in the contract.
298 |
299 |
300 |
301 |
302 |
303 |
Tenderers must have their tax, payroll tax and VAT payments in order.
304 |
Tenderers must be a legally established company.
305 |
306 |
307 |
Tenderers must have adequate economic and financial strength to fulfil the contract.
308 |
309 |
310 |
Tenderers must have good competence and experience from operation of express boats for passengers.