Definitions of CCCEV concepts and concepts in the ESPD were discussed.

Definition for epo-acc: Requirement was proposed:

"Data that a Buyer requests of a Tenderer."

In the actual ESPD-EDM Technical Overview model there is no difference in the definitions between the requirement, question and caption. However, the name of the Business element changes in each case.

How the CCCEV deals with entitlement to marriage with regard to legal age was used as an example of the CCCEV works:

In was stated that in the ESPD-EDM model, the Group tags are used to gather information based on semantics. Therefore, we should either specialise everything or nothing at all.

It was noted that in the ESPD-EDM documentation, a Requirement does not need an answer but a question requires an answer.

The ESPD-EDM technical documentation defines the code list CriterionElementType with the following values:

We need to write down how the questions are related to a specific set of requirements and can be sequential.

The Requirement Group are "needs", whereas the Question Group is how the "needs" are fufilled.

In the ESPD-EDM there seems to be two dimensions:

However the ontology should just look at the data and not the application.
Therefore, we need to have an XML example of data, both for a given request and its corresponding response.

Examples to be provided for General Yearly Turnover and OTHER-EO-SME Selection Criteria.
The reason behind choosing these two Criteria is because the first one contains Requirement Group that gathers Requirements, Question Subgroups and Questions, while the second one contains only Question Groups and Questions.