Working Group meeting 25/10/2022

Date: 25/10/2022
Participants: David Chaves, Maria Navas Loro, Giovanni Paolo Sellito
Model editor: Eugeniu Costetchi
Note editor: Andreea Pasăre

Agenda

Discussion

Github issue 381

  • Usually define domain for properties that have a skos:Concept in range.

  • At the moment when generating the artefacts from UML model:

    • OWL core (lightweight)

    • SHACL shapes

    • Restrictions (lightweight)

  • In model2owl transformation scripts should we add subclasses in the OWL core file or should these be in the restrictions?

    • rdfs:domain

    • Rdfs:range

  • In the uml2owl transformation document (https://github.com/OP-TED/model2owl/blob/master/doc/uml2owl-transformation/uml2owl-transformation.pdf) are presented all the transformation rules and in which layer they belong: core ontology, data shape (SHACL shape) and reasoning (restrictions) layer.

  • Below is a snippet from that document where we can see that the domain and range of associations are in the reasoning layer and the range is also in SHACL shapes layer.

D5pWwXyi1Zp1AAAAAElFTkSuQmCC

  • But there seems to be a bug because the domain for properties derived from the "dependency connectors" are missing.

  • This bug should be fixed.

Github issue 383

  • In the latest release version, ePO 3.0.1, a Result Notice belongs to the Notice module.

  • Only the epo:Notice class is now in the ePO core module.

r5YSwJrAPywokNaYA1KBf6+WEsCa1Aq8PfFWhJYQxACf2usJYE1KBL4m2ItCaxBqcDfF2tJYA2Anx9d0QEAAAAAgKZY0QEAAAAA0AVWdAAAAAAAdIEVHQAAAAAAXWBFBwAAAABAF1jRAQAAAADQBVZ0AAAAAAB0gRUdAAAAAABd+P8BCvWg3UjhECgAAAAASUVORK5CYII=

Github issues 382

  • There is a list of more specific comments regarding this issue.

  • In OCDS, the term Tender refers to something else than in ePO. We have a class from Procedure, which is the process, and we also have a term of the actual Tender as a noun. In OCDS, Tender refers to the entire process of tendering.

  • ePO 3.0.1 was used to get the following comments:

    1. A Contract includes one or more Lots. Why not use LotGroup for this case? A LotGroup is actually a combination of several lots to conduct comparative assessment of the tenders. Is used in cases when the total value of the offers for lots in particular is higher than the value of the offer per a group of the same lots.
      For example, assuming we have two lots, the LotGroup is used when the value of the offer for Lot 1 plus the value of the offer per Lot 2 is higher than the value of the offer for LotGroup containing Lot 1 and Lot 2.

    2. To revise the definition for epo:Procedure. Explicitly mention that a Procedure should have at least one Lot, even though this is derived from the cardinality.

    3. Do we consider epo:Procedure as the central part of the ontology? Essentially, a Notice will always be linked to one and only one Procedure. We do not model processes, but we have modelled objects over time.

    4. What do Terms represent? What is the relation to the Documents? The terms may be published in the notice mainly in the competition phase (some of them may be in planning as well). There are three types of terms: lot specific, procedure specific and contract specific (post-award related terms).
      Terms are not actual documents. They are the rules of the game. And they have attributes that link to different documents.

    5. The specification documents for each Lot are not yet modelled.

    6. In the epo:ProcurementCriterion we might need to add an URL attribute in case we need to add a reference to a procurement document (PDFs) specifying the award or selection criteria.

    7. The class Winner depends on the class Tenderer. We can not instantiate a Winner before having an insurance of Tenderer. The term “depends” doesn’t represent a logical dependency.

    8. epo:Contract epo:includesTender epo:Tender has a cardinality of 0..* because of standard form mappings. To be checked if it is still needed in the mappings.

    9. Description of the class Contract is very abstract. Suggestion to add some general information in the definition: include the main parts and refer to the procurement process.

Dynamic Purchasing System Technique

  • What is a Dynamic Purchasing System (DPS)? DPS is open during the whole duration of the procedure. If a DPS is a setup to last for 2 years, then eC can register and apply under this DPS. DPS is a kind of FA where the procedure is open for a long period.
    And when needed, a CA can launch a mini-competition, like the FA, whereas the EC that has the capability to submit a tender can submit its tender in that specific sub-competition.
    QUESTION: Is there a specific notice to set up a DPS? To be checked in D24?

  • Set up a meeting with who is the coordinator of the DPS subgroup.

eAuction Technique

  • What is an eAuction Technique? Contracting authority can be set up on a digital platform (exclusively). Very similar to eBay, but the offer is not increasing, but decreasing.
    Sometimes they organise the auction in rounds.

  • This technique influences ONLY the submission stage.

  • Procedure types that can have eAuction:

    • Competitive Dialogue (NOT)

    • Competitive tendering (Yes)

    • Innovation partnership (don t know)

    • Negotiated - both types can have eAuction