OP-TED / ePO

The eProcurement Ontology provides the formal, semantic foundation for the creation and reuse of linked open data in the domain of public procurement in the EU.
European Union Public License 1.2
58 stars 18 forks source link

Procurement Criteria #236

Closed jseguraf closed 2 years ago

jseguraf commented 4 years ago

The WG came up with 2 solutions on how to model the different criteria:

1) to have each criterion (Selection Criterion, Award Criterion and Exclusion Criterion) linked to each taxonomy of subcriterion. For example: Selection Criterion has the following subcriterion as a code list: Suitability, Economic and financila standing, Technical and professional ability, other.

2) to have criterion represented as subclasses instead of having taxonomies. For example: Selection Criterion has the following subcriterion as subclasses: Suitability, Economic and financila standing, Technical and professional ability, other.

WG comments/discussion: it makes no difference whether to have or not classes instead of enumerations. It makes sense that each class adds something special which makes it different, but this is not the case. WG decision: the model will be kept using the code list and the subcriterion will not be represented as classes.

muricna commented 3 years ago

Becareful v.2.0.1 does not have a criterion class. The frozen branch 2.0.2 has a criterion class that should correspond in some way to the criterion in cccev we then need to find how we fit all the requirements and evidences with the procurement criterion.

andreea-pasare commented 2 years ago

In ePO 3.0.1, the criterion was aligned with CCCEV. Below is a diagram that depicts how Criterion is modeled:

image