The eProcurement Ontology
What is the eProcurement Ontology?
The eProcurement Ontology (ePO) is a vocabulary that models the concepts used in EU public procurement. It does not represent the eProcurement process itself, it defines the concepts used in the different parts of the public procurement lifecycle.
The ePO conceptualises, formally encodes, and provides structured data about public procurement in both human and machine-readable formats. It is modelled in alignment with EU Directives and Regulations and is a formal standard.
Why do we need an eProcurement Ontology?
The eProcurement Ontology ensures that every participant in the procurement process is speaking the same language i.e., that the concepts and definitions are the same and have the same meaning for all parties.
More detail and background can be found in the Motivation for the development of an ePO.
The Scope of the eProcurement Ontology
ePO covers public Procurement from end to end i.e., from notification, through tendering, awarding, ordering, invoicing, and payment.
How the eProcurement Ontology is created and developed
To build and maintain the ontology, The European Commission’s Publications Office (OP) formed a Working Group (WG) of experts with the mission of building consensus on the analysis, results, and deliverables developed by the OP’s teams.
New to the eProcurement Ontology?
Start here for an introduction:
-
Introductory info sessions on the ePO and Linked Open Data
-
The ePO
A short info session on the ePO -
Linked Open Data
A short info session on Linked Open Data
-
-
Github page
The ePO resources on GitHub
The following topics are included in this version of the eProcurement Ontology documentation:
General Documentation
-
User Guides
Guides for using the ePO and its features. -
Conceptual Models
The release specific conceptual Model(s) of the ontology. -
Glossaries
The release specific glossaries -
Release Notes
Release notes for the specific ePO version -
The ePO in other Projects
How the ePO underpins other projects
Reference Documentation
-
Methodology
How the ePO is developed and maintained -
ePO Versioning Rules
An overview of the versioning rules for releases -
User Stories and Natural Language Statements
Ontology Requirements Specification Documents (ORSD), containing user stories and natural language statements used when developing new modules-
eAccess (ESPD Request)
ORSD for eAccess module -
eSubmission (ESPD Response)
ORSD for eSubmission module
-
-
Other Reference Documents
Useful reference documents in the development of the ePO -
History and Planned Developments
Milestones in the project and future development plans
Working Group Documents
-
Quarterly Meetings
Minutes, Presentations, etc from the quarterly Working Group Meetings -
Cumulative Reports (by year)
All weekly meetings minutes collated into yearly documents -
Individual Meeting Reports
All weekly meeting minutes and documents saved individually