Documentation on the eProcurement Ontology can be found here.

Ontology reference URI: http://data.europa.eu/a4g/ontology

Ontology namespace: http://data.europa.eu/a4g/ontology#

Preferred prefix: epo

Note: If you have any questions, or you would like to make a suggestion or share an idea, please use Discussions. If you discover any bugs please put them on GitHub issues and we will address them. Also, we have reorganised the GitHub repository and if you experience problems or need assistance feel free to contact us by email.

1. eForms Regulation and Annex
2. Report on policy support for e-Procurement (landscaping report, 2016)
3. EU Directives:

• Directive 2014/23/EU, on the award of concession contracts Text
• Directive 2014/24/EU, on public procurement and repealing Directive 2004/18/EC
• Directive 2014/25/EU, on procurement by entities operating in the water, energy, transport and postal services sectors and repealing Directive 2004/17/EC
• Directive 2014/55/EU, on electronic invoicing in public procurement Text with EEA relevance
• Directive 2009/81/EC, on the coordination of procedures for the award of certain works contracts, supply contracts and service contracts by contracting authorities or entities in the fields of defence and security, and amending Directives 2004/17/EC and 2004/18/EC

You 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:

• module label
  • core - core module
  • extension-* a specific extension module
    • ePO core
    • eNotice
    • eOrdering
    • eCatalogue
    • eFulfillment
    • eAccess
    • eContract
    • eSubmission
  • generic - no module in particular because the issue is of technical or documentation nature
• type label
  • bug - something implemented incorrectly in a release
  • feature request - something requested to be implemented in a future release
  • question - something needs clarified, refined or decided
  • use case - something describing usage scenario that shall be supported
• action label
  • for implementation - it can be implemented and closed, all is clear
  • for internal discussion - it needs to be discussed within the team
  • for WG discussion - it needs to be discussed within the Working Group
  • for closing - it can be closed but an additional confirmation is needed
• auxiliary label
  • mappings - it is related to the TED-SWS mappings project
  • 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.