Working Group meeting

Date: 22/08/2023
Participants: Peter Borresen, Natalie Muric, Giovanni Paolo Selitto
Model editor: Andreea Pasăre
Note editor: Alexandros Vassiliades

Agenda:

  • Present 1st draft of eAccess

  • Discuss use cases and user stories for eAccess

Discussion:

1st Draft of eAccess

  • Question: Does the procurement service provider take part in the ESPDRequest or only in the ESPDResponse? Answer: The procurement service provider offers a platform that can be used by both the Buyer and Economic Operator.

  • The relation between epo-acc:ESPDRequest and epo:ProcurementCriterion was named as epo:announcesProcurementCriterion with a cardinality of 1..*.

  • Legislation has an official language. It was suggested to consider Legislation as a Document, this would imply that many of the properties could be inherited from Documen:

    • dct:title

    • dct:description

    • epo:hasURL

    • epo:hasOfficialLanguage However, this needs to be looked into more depth to see the correctness of this idea.

  • epo:ProcurementSubcriterion was deleted from the proposed draft because it is a redundancy of the epo:Criteria.

  • Based on the ESPD data model Criterion has one or many requirement groups, according to CCCEV a Criterion is a type of Requirement (see below the CCCEV model).

Awp6VJ9T8k0GAAAAAElFTkSuQmCC

An Instance diagram showing the modeling of a requirement for a epo:ProcurementCriterion, by using the epo:hasRequirement property defined in the cccev:Requirement.