Working Group meeting

Date: 08/02/2022
Participants: Cecile Guasch, Hilde Kjølset, Giorgia Lodi, Natalie Muric, Giovanni Paolo Sellitto
Model editor: Eugeniu Costetchi
Note editor: Andreea Pasăre

Agenda

  • Present overview of the refactored model.

Discussion

  • We started grouping all classes from the ePO model, like in the image below:

2OLUeyh62FsAAAAAElFTkSuQmCC
  • Provide a narrative for all the packages in order to make it more understandable by the business people.

  • Short discussion regarding the documents diagram which was also discussed last time.

    • Kept only the top level of notices in the model: planning, competition, DAP, result, completion and contract modification.

    • Predicates epo:relatesToNotice and epo:relatedToNotice are from the 2.0.1 version:

      • Why not include them at the class level?

      • epo:refersToResultNotice is a specific type of the predicate epo:relatesToNotice? This can be deleted because this relation exists at the level of an epo:Notice class. But this has a different cardinality (mandatory 1) so we can keep it and use it for an AP of notices.

  • Discussion about the structure of phases in the Procurement domain.

  • Is it valuable to have a Result Notice or just a Contract Award Notice?

    • Mentioning that a Result Notice contains CAN general, CAN social and also design.

    • It is good to have this classification.

  • Showing the situation usage example for Winner BG:

vUOQihfZ4c5L4hBwEAADAUynUjQccCAICxIQdRN+QgyEEAAAD0hHLdSNCxAABgbMhB1A05CHIQAAAAPSnKdTQjNWJfAwAAvCnkIOqGHAQ5CAAAAAAAAHxsyEHUDTkIchAAAAAAAAD42JCDqBtyEOQgAAAAAAAA8LEhB1E35CDIQQAAAAAAAOBjQw6ibshBkIMAAAAAAADAx4Yc5P9vxw5OAISBIIr2rxaRUhUEF3KUCGbyHtPBnvbXdBAdBAAAgGw6SE0H0UEAAADIpoPUdBAdBAAAgGw6SE0H0UEAAADIpoPUdBAdBAAAgGw6SE0H0UEAAADIpoPUdBAdBAAAgGw6SE0H0UEAAADINlMHacdxvcqWurZvOggAAACfmqmDPO5vmVT9vQEAAGAQHYTf6e8NAAAAg0zZQQAAAABe0EEAAACAVeggAAAAwCp0EAAAAGAVOggAAACwihMncLPKF7chfwAAAABJRU5ErkJggg==
  • If we decide that we don’t want to keep the Notice subclasses in the model, we should find a way to move the attributes from some of them.

  • Prepare a list with all the problems that we found while doing the mappings of the content to eForms notices. (publish a future agenda; maybe as a GH issue, with priority if possible.)