Working Group meeting
Date: 15/10/2024
Participants: Ioannis Fountoukidis, Natalie Muric
Model editor: Achilles Dougalis
Note editor: Grzegorz Kostkowski
Agenda
-
Discuss GitHub issues for ePO 4.2.0:
-
Discuss selected GitHub issues with the aux: mapping label:
Discussions
-
The following decisions regarding organization of GitHub ePO repository were made:
-
Creation of GitHub projects for 4.2.0 and 5.0.0 versions.
-
Creation of two boards for the two new projects. The goal is to help track the status of tickets.
-
-
Decision on a way of recording WG decisions in a GitHub ticket: A WG decision will appear at the top of the description (or will overwrite the original description).
Anyone interested in the original description can display it by browsing the ticket history:
Addressing GitHub issues for ePO 4.2.0
-
#705 It was clarified that the ticket goal is to remove new predicates accidentaly added to ePO 4.2.0-rc.1 and recreate them in the version 5.0.0.
It was discovered that there is no ticket for recreating the predicates and such a ticket must be created as well. -
#703 The ticket is similar to #705: it aims to revert new changes in 4.2.0 and redo them in 5.0.0 version.
Changes will be reapplied in 5.0.0 version based on the #704 ticket. -
#607 This ticket is about work that has been done for 4.1.0 version but needs to be reimplemented for 4.2.0 version. The corresponding ticket (#688) was added to ePO 4.2.0 tickets project.
-
#689 This ticket is about work that has been done for 4.1.0 version but needs to be reimplemented for 4.2.0 version. The ticket was added to ePO 4.2.0 tickets project.
The following comment has been posted in the ticket:
-
#624 The epo:SubcontractingEstimate class was verified in the conceptual model and it was found out that the task has been already resolved. The following properties addresses what was requested:
A proper comment informing that the properties have been implemented for 4.2.0 version was added. The ticket was moved to ePO 4.2.0 tickets project.
Addressing mapping issues (tickets with the aux: mapping label)
-
#667 The ticket was analyzed and the WG decision was posted:
-
-
WGM 11/07/2024 meeting notes were reviewed to understand the context.
-
Definition of epo:isSMESuitable attribute of epo:ProcurementObject class was inspected in the conceptual model:
-
-
It was decided to remove additional information stored for epo:isSMESuitable attribute because the definition is self-explainable.
-
It was decided that the change will be included in the 5.0.0 version.
-
The same modification was applied to epo:isSMESuitable attribute of epo:LotGroup.
-
The decision was posted in the ticket as a new description of the ticket:
#686 After analysis one possible way of tackling the issue was suggested. The proposal assumed creation of a new reflexive association for org:Organization class with the name epo:foreseesSubContractor.
Some concerns about the new name were stated. The working group consulted a domain expert to ensure that the proposed name is suitable.
The recommendation was published in the ticket description:
A new Other request was created in OP-TED/ESPD-EDM repository to inform about the change:
#665 New association between epo:ConcessionContract and epo:LotAwardOutcome classes was created.
Cardinality was set to 0..* (and not 0..1) due to possible amendments to epo:LotAwardOutcome.
The new definition was also set for the two associations having the same name defined in the existing epo:DirectContract and epo:FrameworkAgreement classes.
Outcome was commented in the ticket description:
