Working Group Meeting

Date: 27/05/2025
Participants: Natalie Muric, Paul Donohoe
Model editor: Andreea Passare
Note editor: Achilles Dougalis

Agenda

Discuss Github issues with milestone 5.1.0.

Discussion

The “Offer” folder in the Conceptual Model file was moved to the sandbox folder because an Offer module is not foreseen due to the fact that epo:Offer is implemented in the ePO-core module.

#793 was discussed: As seen in the picture below, eForms have a section tagged as “ProcurementProject”

40RoYJn5FUrAAAAAElFTkSuQmCC

The eForms mappings map the information on the ProcurementProject as an epo:Procedure which is not correct. There should be a new concept in ePO representing the ProcurementProject accounting for the following fields:
- Title
- Description
- Internal Identifier
- Estimated Value
- classification code
- purpose
Class epo:PlannedProcurement was created as a subclass of epo:ProcurementElement. It was also made sure that the attributes on epo:ProcurementElement cover the needs of epo:PlannedProcurement.
Concepts epo:hasLegalBasis and epo:hasLegalBasisDescription were moved from epo:ProcurementObject to epo:ProcurementElement.
There is a problem with LocalLegalBasis in the mappings.An eform does not have a locallegalBasis, although it used to be in epo:Notice as a standard form requirement.
A a new concept called epo:LocalLegalBasisInformation was created, with the following attributes and Object properties:
- dct:description : rdf:PlainLiteral [1..1]
- epo:concernsProcurementElement : epo:ProcurementElement [1]
- `epo:hasLegalBasis : at-voc:legal-basis [0..1]

9aEJ0LbSBHIAAAAASUVORK5CYII=