Working Group meeting 07/06/2022

Date: 07/06/2022
Participants: Georgia Lodi, Natalie Muric, Giovanni Paolo Sellitto
Model editor: Eugeniu Costetchi
Note editor: Andreea Pasăre

Agenda

  • ePO 3.0.0. beta release

  • Preparing an worksheet with the new definitions for classes and attributes === Discussion

Discuss https://github.com/OP-TED/ePO/issues/349

9jTQW3QnAAAAAElFTkSuQmCC
  • The request is to change the name of predicate epo:involvesBuyer to a more representative naming, like epo:isResponsabilityOfBuyer.

  • Also, the boolean attribute epo:isResponsibleForProcedure won’t help in the case of knowing which is the procedure that the specific buyer is responsible for.

Indeed if we used a boolean attribute, it allowed for the possibility to have multiple buyers involved, none of which were responsible for the procedure. Using two relations, however, enables us to enforce that at least one buyer MUST be responsible for the procedure.

D1rqiAeIPxprAAAAAElFTkSuQmCC

Discuss https://github.com/OP-TED/ePO/issues/341

27oVAop1wnXWUUwSMIMqAkfvPQS7lvjyDIKCVxzjQUOMfgnV0AeAQZ8QA8goxR+gy+X6cWEAQZRAAeQcYoAI8gYxSAR5AxCsAjyBgF4BFkjALwCDJGAXgEGaMAPIKMUf4PJxS7VmKKG2cAAAAASUVORK5CYII=
  • Investigating how the ECLASS classification system describes items in a structured manner.

  • We should treat this as an additional custom description of an item.

Discuss https://github.com/OP-TED/ePO/issues/340

H3vdKWogwQquAAAAAElFTkSuQmCC
  • The relation dct:requires replaces epo-ecat:hasRequirementItem.

  • The relation dct:hasPart replaces epo-ecat:hasComponent.

Discuss https://github.com/OP-TED/ePO/issues/324

A Catalogue is provided by a CatalogueProvider, which is playedBy an Organisation, which has an Address.

AZc7Doe3l0b6AAAAAElFTkSuQmCC