selectionCriteria: Should this be removed in favor of requirements?

[jpmckinney]

https://extensions.open-contracting.org/en/extensions/requirements/master/
https://extensions.open-contracting.org/en/extensions/selectionCriteria/master/

If so, we need to update the EU profile.

[yolile]

Note that if that is done, we will need to introduce selectionCriterionType as part of requirements, and add "subcontractor" as another code for relatesTo

[jpmckinney]

Here's another issue about adding a new field to SelectionCriterion: open-contracting/european-union-support#72 It might be hard to harmonize the two ways of expression criteria.

[yolile]

And another one about adding more fields to the requirements extension #132 (including criterionType)

[jpmckinney]

Yes, instead of comparing requirements (as it is now) to selectionCriteria, we can compare CCCEV to selectionCriteria, and then just improve requirements with the missing parts of CCCEV (and remove some of our own inventions if appropriate).

[jpmckinney]

Okay, I'm resolving this issue by having the extensions point to each other, with the suggestion that if your data follows CCCEV, use Requirements, and if not, use Selection criteria.

Since CCCEV is outside our control, I think it's fine to offer our own model – similar to how we have profiles for the EU that aren't expected to be used globally.