⚠️ The TED schema forms are the former standard forms and have been replaced by eForms, newer RML rules for eForms can be found at OP-TED/ted-rdf-mapping-eforms.
This repository contains RML rules to transform Standard TED schema forms to RDF that conforms to version 3.0 of the eProcurement Ontology (ePO) and are currently used by the TED RDF Conversion Pipeline to produce RDF for forms sent before 25 October 2023.
The artefacts provided in this repository are used or generated by the TED-SWS system in the form provided here. They are organised in packages called Mapping Suites.
Project documentation available here.
The following table indicates the implementation status of TED Standard Forms, split by Notice Type and Directive.
| Notice Type | Is implemented | Directive 24 | Directive23 | Directive 25 |
|---|---|---|---|---|
| pin-buyer | F8 | F8 | F8 | |
| pin-only | F1 | na | F4 | |
| pin-rtl | F1 | na | F4 | |
| pin-cfc-standard | F1 | na | F4 | |
| pin-cfc-social | F21 | F23 | F22 | |
| qu-sy | na | na | F7 & F22 (social) | |
| cn-standard | F2 | F24 | F5 | |
| cn-social | F21 | F22 | ||
| subco | na | na | na | |
| cn-desg | F12 | F12 | ||
| veat | F15 | F15 | F15 | |
| can-standard | Yes | F3 | F25 | F6 |
| can-social | Yes | F21 | F23 | F22 |
| can-desg | Yes | F13 | na | F13 |
| can-modif | F20 | F20 | F20 | |
| corr | F14 | F14 | F14 | |
| pin-tran | na | na | na | |
| can-tran | na | na | na |
To assist the semantic engineers in the development of mapping suites a toolchain has been developed. The toolchain is documented on the documentation page. In order to install it open a terminal and follow the instructions below.
- Clone the project from GitHub
git clone https://github.com/OP-TED/ted-rdf-mapping
cd ted-rdf-mapping- Create and activate a virtual environment
python -m venv venv
source venv/bin/activate- Use makefile target to install the requirements
make installYou are more than welcome to help expand and mature this project.
When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
Please note we adhere to Apache code of conduct, please follow it in all your interactions with the project.
Each milestone corresponds to a foreseen release of the ontology.
The issues are classified based on for classification dimensions:
- type label
- bug - something implemented incorrectly in a release
- missing feature - something expected but missing from a release
- feature request - something requested to be implemented in a future release
- implementation question - something needs clarified, refined or decided before the implementation can continue
- release question - something needs clarified before a release is considered accepted
- action label
- for implementation - it can be implemented and closed, all is clear
- for closing - it can be closed but an additional confirmation is needed
- auxiliary label
- ppds - it is related to the PPDS project
- bdti - it is related to the BDTI project
The documents, such as reports and specifications are licenced under a CC BY 4.0 licence.
The source code and other scripts are licenced under EUPL v1.2 licence.