We should revisit the design of the Exclusion, Selection and Award Criterion sub-models- The current proposal is not "professional" from the design perspective:
Having three structures (sub-models) that are identical amongst themselves implies imposing a triple UNNECESSARY maintenance.
This is what is hapenning right now with the splitting of Criterion into Exclusion, Selection and Award Criterion. The solution to this is:
Having one generic model that is business-agnostic named "Criterion", as we have now in the ePO CDM; (this is OK in the model);
Having one domain-specific submodel named "Procurement Criterion" that extend the generic "Criterion" model with the inclusion of references to Lots.
Having three classes that inherit from Procurement Criterion and per each one, have (or not) specific restrictions on the properties (e.g. onProperty "refersToLot" allow or not the linking to the Lot; e.g. in the case of the Exclusion Criteria references to Lots shall not be allowed).
We should revisit the design of the Exclusion, Selection and Award Criterion sub-models- The current proposal is not "professional" from the design perspective:
Having three structures (sub-models) that are identical amongst themselves implies imposing a triple UNNECESSARY maintenance.
This is what is hapenning right now with the splitting of Criterion into Exclusion, Selection and Award Criterion. The solution to this is:
To be discussed with you ASAP.