Working Group meeting
Date: 05/10/2023
Participants: Pascaline Laure Tchienehom
Model editor: Andreea Pasăre
Note editor: Andreea Pasăre
Discussion
The CCCEV explanatory example presented was https://semiceu.github.io/CCCEV/releases/2.00/html/CCCEV_AnExplanatoryExample.pdf
Neither in the ESPD Request nor in the ESPD Response is the Evidence mandatory.
It is the same with CCCEV, as all cardinalities are [0..*].
Reference Framework
Since cccev:ReferenceFramework represents the legislative part in CCCEV, epo-acc:Legislation and epo-acc:Article were added as subclasses of cccev:ReferenceFramework.
This implies that we no longer need epo:ProcurementCriterion epo-acc:implementsLegislation epo-acc:Legislation and epo:ProcurementCriterion epo-acc:implementsArticle epo-acc:Article.
These two relations are deleted and _cccev:Requirement cccev:isDerivedFrom cccev:ReferenceFramework _is implemented instead.
From the explanatory example, we can see that CCCEV uses ELI for the Reference Framework, making them able to point directly to an article by using an URI.
The ESPD Request does not have an use case for providing the issuer of the Criterion.
Question: In the ESPD Request does the LEGISLATION apply to all the concepts nested within a given CRITERION tag?
The only link that the ESPD provide is the link between the CRITERION and LEGISATION. They do not need to represent the links between LEGISLATION and REQUIREMENT or QUESTION.
Question: What is the difference between cccev:InformationRequirement and cccev:InformationConcept?
Definition for Information Requirement is: "Requested data that is to be proven by Evidence."
Definition for Information Concept is: "Piece of information that the Evidence provides or the Requirement needs."
Based on the diagram above, the InformationConcept will be used to link to the SupportedValue of the Evidence in the ESPD Response.
REQUIREMENT_GROUP
(cac::TenderingCriterionPropertyGroup)
In the ESPD Request, cac::TenderingCriterionPropertyGroup is defined as "the sets of properties that can be used to fulfil the tendering criterion."
Financial ratio criterion (finan-rat) has a REQUIREMENT_GROUP with a cardinality of [1..n], meaning that we should have an additional layer between the instance of epo:SelectionCriterion and cccev:InformationRequirement instances. This instance will only provide an Identifier and will group together all the InformationRequirement instances for that specific Criterion.
After discussing the REQUIREMENTS from the ESPD Request side, all the related InformationRequirement instances have been moved at the level of the Group instance as per the diagram below:
The meeting ended with presenting the first QUESTION_SUBGROUP from the General Yearly Turnover:
