Adding invitationsForInterestDispatchDate and invitationsForBidsDispatchDate to Tender

[ColinMaudry]

TED IV.2.3) Estimated date of dispatch of invitations to tender or to participate to selected candidates (if this information is known)

Both dates are consequently mixed, when eForms distiguish them as BT-631 and BT-130.

Possible structure:

{
"Tender":
{
        "invitationsForInterestDispatchDate": {
          "title": "Invitation for interest dispatch date",
          "description": "The estimated date of dispatch of the invitations to confirm interest.",
          "type": "string",
          "format": "date-time"
        },
        "invitationsForBidsDispatchDate": {
          "title": "Invitation for bids dispatch date",
          "description": "The estimated date of dispatch of the invitations to submit bids in two (or more) stage procedures.",
          "type": "string",
          "format": "date-time"
        }
}

[jpmckinney]

From reading the law, an invitation to confirm interest is only used in the case were the PIN (that preceded the CN) was used as a means for calling competition. I'll update the guidance so that it's clearer when each is used.

[jpmckinney]

Having read the law again, I don't think TED has a field regarding "The estimated date of dispatch of the invitations to confirm interest." It only has the other two kinds of invitations:

• "invitations to tender" (restricted procedures, innovation partnerships and competitive procedures with negotiation)
• "invitations to participate [in the dialogue]" (competitive dialogue)

These are both "Dispatch Invitation Tender" in eForms, which I'd consider to be semantically the same as the start of the tender/submission period (or similar) for the second stage.

[jpmckinney]

I'll map it to tender.secondStage.invitationDate.