Tips when querying eProcurement data using SPARQL

Tips and useful information

What data is available (from which notices and over what time period)?

eForms Standard Forms (TEDXML)
  • From 1st March 2023 until current day - 1

  • From 28th August 2023 until 26th January 2024

  • conforms to the eProcurement Ontology V4
    (to be upgraded to ePO v5)

  • conforms to the eProcurement Ontology v3.1
    (to be upgraded to ePO v5)

Current transformation

  • Daily eForms notices of all SDK versions except 1.14

Current transformation

  • A limited number of XML notices are available in Cellar. These were produced during the initial TED Open Data Service Pipeline proof of concept.

  • Form types F3, F6, F21, F22, F23, F25

Support for SDK version 1.14 coming in 2026

Support for the remaining form types coming in 2026

Refer back to this page regularly to check if there have been updates. Use the ePO resources of the versions mentioned above to find the classes you wish to use in your queries.

Any comments on the documentation?

Lots

All purchases are organised in into lots. Lots are effectively supply packages that enable supply to e.g., different locations, a subset of goods over time, etc. Even if only one delivery is stipulated, there is still a single lot. When querying, this can be confusing because it can look like data with the same notice number is duplicated in the results table, when actually it is showing rows of lots rather than the whole order in one row.

To clarify, you might want to add a column for lot number in your query.

Duplicate data in results

Apart from the appearance of duplication caused by lots, there are other reasons why there might be a duplication in the results. Notices could be published more than one language, so unless you filter for language in the query, the same notice might be listed several times in different languages.


Any comments on the documentation?