WG meeting
Date: 31/10/2024
Participants: Catia Miguel, Natalie Muric
Model editor: Achilles Dougalis
Note editor: Grzegorz Kostkowski
Discussions
-
One important assumption that is relevant for the modelling activities was recapped: Even if a Procedure doesn’t have a Lot it is still treated as a one with a one Lot.
-
The ePO ontology fundamentals were presented to fill the new WG member in. The following resources were presented and commented:
-
GitHub space: ePO repository and eForm Requirements board.
The WG worked on the following GitHub tickets:
-
-
The WG discussed whether to place the SDK at the epo:Notice or epo:Document level. The decision was to place it at the epo:Document level.
-
The relation between eForms and UBL was discussed. It was concluded that eForms customises UBL but an actual eForm does not customise, but rather implements it.
-
A similar mapping case was reviewed to verify if there are any similar predicates that have been introduced that could have informed the decision about the predicates to be introduced in the context of the reported case.
-
The agreed proposal was to introduce epo:implementsSpecification property for the epo:Document class. This was recorded as the WG approval in the ticket description:
-
The WG tried to understand the problem that was reported, but it was difficult without having more information, that is:
-
Complete technical description of the related notice, The notice XML file, that is input for mapping process (instead of having an RDF payload that is the partial result of mapping).
-
The analysis of the reported example provided in the ticket to support the reported issue led to another topic of analysing alignment between eForms and ePO in the context of Tender, Lot and LotGroup. The Working Group expected each Lot within a LotGroup to have its own corresponding Tender. However, eForms does not currently support this. It is not possible to indicate that a specific part of a Tender belongs to one Lot and another part to another Lot. Instead, eForms requires a single Tender to be created for the entire LotGroup, regardless of the number of individual Lots it contains.
It was concluded that the root cause of the misalignment between eForms and the ePO ontology is that ePO scope covers more information that is currently captured in eForms.
-
-
The ticket analysis was concluded with the statement that what was requested in the ticket is not possible because of the misalignment between ePO and eForms (that will be further discussed during a dedicated meeting).
