Glossary of mapping terms

  • Conceptual Mapping, often abbreviated as CM, is an abstract level mapping of XPaths in the input data to those ePO classes that need to be instantiated and properties are used to link the instances in the output RDF graph

  • eProcurement Ontology (ePO) is an ontology that defines the concepts and relations that are needed to fully describe the eProcurement domain of the EU. For more information check out the eProcurement Ontology Documentation.

  • eForms is the notification standard for public procurement procedures in the EU. For more information on this, see the eForms SDK documentation

  • Form - To enable the publishing of the EU public procurement data in the Official Journal, the European Commission has created standard forms aligned with each of the EU legal bases in place for publishing this data, namely: the TED schema forms set out in Regulation (EU) 2015/1986, and the eForms set out in Regulation (EU) 2019/1780. In this documentation the term "form", if not otherwise specified, will refer to Standard Form

  • Mapping package - see Mapping suite package

  • Mapping suite package is a collection of files, organised in a folder hierarchy, that fully specify how the mapping of a certain category of notices (e.g. notices created according to specific XSD version of a specific TED Standard form) is being converted to RDF. This collection includes the conceptual mapping (CM), the technical mappings (realised as RML files), additional resources that are needed to complement the mappings, some test data, the generated output from the test data, the validation queries and validation reports generated based on the mappings and on the generated RDF output. For more details please see the Mapping Suite Structure.

  • Notice, short for public procurement notice, refers to a procurement notice published on TED. To explore some of these notices please visit: https://ted.europa.eu/TED/

  • Package - often used as a short name for Mapping suite package

  • RDF Mapping Language (RML) is a generic mapping language defined to express customised mapping rules from heterogeneous data structures and serializations to the RDF data model. RML is defined as a superset of the W3C-standardised mapping language [R2RML] and follows exactly the same syntax as R2RML; therefore, RML mappings are themselves RDF graphs. For more information on RML, please see https://rml.io/specs/rml/.

  • Standard Form - see TED Standard Form

  • Technical Mapping, often abbreviated as TM, is set of RML rules that can be used to transform notice XML, into its which are split in multiple reusable modules that can be combined to represent a full RML

  • Tenders Electronic Daily (TED), is an online portal that publishes hundreds of thousands of public procurement notices per year. A cornerstone of European public procurement, TED helps economic operators find business opportunities from around the EU. For more information see: https://ted.europa.eu.

  • TED Standard Form or TED schema forms refers to the "TED Standard forms for public procurement" described here: https://simap.ted.europa.eu/en_GB/web/simap/standard-forms-for-public-procurement. These forms are numbered F01-F08, F12-F25 and T01-T02, and must conform to a specific version the TED XML Schema.

  • TED XML schema refers to the XML schema (XSD) specified for validating the notices that are published according to the Regulation (EU) 2015/1986. For a full documentation of the various XSD schemas, and their versions, please check out: https://op.europa.eu/en/web/eu-vocabularies/e-procurement/tedschemas

  • Test data - a carefully selected, representative sample of real notices published on TED, which, together, cover all the different XPaths that can appear in the entire set of Public Procurement Data (PPD) of a certain type (i.e. created based on a specific Form, specific XSD version), and published in a certain date range. For more detailed documentation, please check out the Preparing Test Data section

  • XPath - the XML Path Language (XPath) Version 1.0. See https://www.w3.org/TR/xpath-10/


Any comments on the documentation?