ePO
ePO copied to clipboard
OP-TED
The eProcurement Ontology provides the formal, semantic foundation for the creation and reuse of linked open data in the domain of public procurement in the EU.
During the working group meeting on 3/7/2024, It was discovered that the 'Environmental Emission' concept is missing from ePO.
From the WG-meeting on 7/3/24: It was discussed that the epo-ful:hasOnCarriageShipmentStage and epo-ful:hasPreCarriageShipmentStage should be deleted, as we should only care about the 'last mile' of the shipment stage. We...
See details in the following issue: https://github.com/OP-TED/ted-rdf-mapping/issues/95
The alignment between PEPPOL business term requirements and ePO eFulfilment module is a work in progress. This alignment is done by linking ePO concepts that correspond to each Business Term...
Should the predicate Read hasResponseStatus Rather than hasAcceptanceStatus
- It is about data and not the data transactions/processes/technical implementations - Present the module (use cases, resources) - Present conceptual model on the documentation page. - Sharepoint structure description
This attribute was an oversight on ePO's side. The classes to be used instead are in the eNotice module: 
It was decided in the WG meeting on 6/2/23 that epo:OtherEntity should be renamed to epo:reliedUponEntity.
In ePO 4.0.0 the `epo:Period` class is modelled like this:  **Questions:** 1. What is the meaning of the `epo:hasTimePeriod` property, and **why is it mandatory** (cardinality `1..*`) ? Looking...
