Add tender.variants (array-of-variants)

[jpmckinney]

Each item of the array would be a Variants object, which has an id, description, and relatedLot.

Related to:

• II.2.10 Information about variants
  • Variants will be accepted /OBJECT_CONTRACT/OBJECT_DESCR/ACCEPTED_VARIANTS

[jpmckinney]

Note: In eForms:

BT-63 | Variants | Code | No | Whether tenderers are required, allowed or forbidden to submit tenders which fulfil the buyer's needs differently than as proposed in the procurement documents. Further conditions for submitting variant tenders are in the procurement documents.

The change was made from a boolean to a code due to the wording of Article 45 or 2014/24/EU, identified in https://github.com/eForms/eForms/issues/212

We may therefore need a boolean required field or similar.

[ColinMaudry]

I'm creating a submissionTerms extension, where this Variant object would be added to a SubmissionTerms object that could be attached to Tender or Lot. Does that work for you?

[ColinMaudry]

Actually, I don't see why we need a description. I'm thinking of adding a variantPolicy field on SubmissionTerms and not creating (yet) a Variant object.

[ColinMaudry]

The "policy" suffix is for terms linked to the permissions codelist (required, allowed, notAllowed).

[jpmckinney]

Sounds good to me. I can't find where description came from – maybe I was just mirroring the options extension without thinking.