Extension: make selectionDetails structured

[practicalparticipation]

From Mihaly Fazekas:

selectionDetails: break down into selection criteria text and selection criteria weight (it is often shown in a table format in Europe). These should be explicit and clearly broken down per selection criteria item. This is crucial for bidders to clearly see what they are evaluated against and it is very useful for the researcher to see corruption risks in subjective evaluation criteria for example.

This is a good suggestion, though I suggest we consider this as a good candidate for an extension (it would need a new object type, and probably new property for structuredSelectionDetails, or selectionDetailBreakdown) and we've not had examples of this in supply side published data yet.

(I.e. a third-party is encouraged to work up a schema definition for this based on existing example data)

[LindseyAM]

@practicalparticipation if Mihaly says that this is commonly shown in Europe, is that not an evidence from the supply side? @marcelarozo what have you seen in your experience? Is the issue the burden on the publisher to convert the table into open data?

[birdsarah]

@LindseyAM "if Mihaly says that this is commonly shown in Europe, is that not an evidence from the supply side?" I don't remember seeing it in the published standardized data, it is definitely present in the actual systems themselves.

[marcelarozo]

It is regular practice that tenders establish different selection criteria (some technical, some financial) and assign different weights to them. As Mihali says in the tender notice this would probably come as a table

[AlCollier]

Need to allow for pass/fail (ie Boolean) as well as weighted criteria

[timgdavies]

Covered in #36. selectionDetails was an earlier property name for the concept picked up in evaluationCriteria. Through the features extension we may be able to find a good structured way to capture this information.