Working Group meeting
Date: 08/02/2024
Participants: Giovanni Paolo Sellitto, Dragos Stoica, Pascaline Laure Tchienehom
Model editor: Andreea Pasăre
Note editor: Achilles Dougalis
Discussion
On eSubmission
-
The epo-sub:PreQualificationSystemData class was created to represent the cac:QualifyingParty class from the ESPD-EDM model.
-
It was noted that in UBL 2.3 cac:QualifyingParty has the following definition: "The party qualifying this economic operator."
-
It was decided that in ePO we do not model the QualifyingParty as a role but as data that is linked to the EconomicOperator role.
-
Next we discussed the ePO alignment with the CCCEV model.
-
It was noted that In ESPD sometimes there is no need to provide evidence, just a response to the question coming from an ESPD request.
-
The Response and Evidence concepts in the context of eSubmission were presented and aligned to the ESPD-EDM and CCCEV models.
-
There are 2 vocabularies that are used by CCCEV and ESPD-EDM
-
It was debated whether the at-voc:access-right or the at-voc:confidentiality-level vocabularies should be used as recommendations in ePO.
-
The ESPD-EDM uses a value from at-voc:access-right codelist as a cbc:ConfidentialityLevelCode.
-
-
-
In ePO the Evidence class has as a confidentiality-level type a value from at-voc:confidentiality-level codelist.
-
It was noted that the EvidenceType concept from CCCEV represents the TemplateEvidence from ESPD-EDM.
-
In the ESPD-EDM diagram, cac:Evidence is connected to a cac:DocumentReference which seems like a conflation of multiple concepts (Certificate, EvidenceDocument, Mandate, IdentityDocument). In ePO, a Certificate is a subclass of epo:Evidence which is not a document.
-
It was noted that cccev:Evidence inherits the Identifier attribute from dcat:Dataset which is not yet implemented in ePO (see CCCEV github issue). *
-
submission response diagram at the end of the meeting