Updates to make prior to release of OCDS 1.2

[jpmckinney]

Add a note to extensions that are part of 1.2, basically saying to only use them in OCDS 1.1

Already merged, or partially merged

• Country code
• Organization scale
• Tender and contract identifiers
• Organization classification Merge the Organization classification extension standard#1622
• Submission terms (note: this might not be completely merged, in which case we just need a note about choosing the correct version to match the OCDS version) Merge the submissionTerms extension standard#1183

Planned

• Project Merge the Project and Location extension to encourage implementers to publish infrastructure project identifiers standard#1484
• Location Merge the Project and Location extension to encourage implementers to publish infrastructure project identifiers standard#1484

Noting that these third-party extensions were also merged:

• https://extensions.open-contracting.org/en/extensions/statusDetails/master/
• https://extensions.open-contracting.org/en/extensions/releasePublisher/master/
• https://extensions.open-contracting.org/en/extensions/tender_datePublished/master/

Edit:

• Merge any changes from 1.1 branches of extensions into their 1.2 branches (removing any unwanted changes)
• Manually re-run all extensions with standard-maintenance-scripts on both 1.1 and 1.2 branches

[jpmckinney]

✅︎

For status details, can link to https://standard.open-contracting.org/staging/1.2-dev/en/guidance/map/contract_suspension/ (once 1.2 is released) instead of copying the example.

Contract suspension is removed from OCDS 1.2, as it relies on the deprecated status field.

[jpmckinney]

country codelist:

• Beneficial owners has a master branch that copies the country codelist. That branch should be renamed to 1.1, and a 1.2 branch can be created that removes the copy, and uses the main codelist (otherwise, the copy acts as an override).
• The master branch of the bid extension also has a copy. That branch should be renamed to 1.1 and the same changes made.

[jpmckinney]

✅︎

Check the documentation of extensions that extend Planning (and Budget) and ensure they discuss "planning process" not "contracting process"

• budget_breakdown: Updated to "future contracting process"
• finance: Updated to "future contracting process"
• metrics: Updated to "future contracting process" when referring to planning
• project

[jpmckinney]

✅︎

Remove patternProperties for translation:

• ocds_project_extension
• ocds_qualification_extension

These are OK:

• ocds_budget_and_spend_extension: measures, classifications
• ocds_exchangeRate_extension: amounts in other currencies
• ocds_metrics_extension: dimensions
• ocds_tariffs_extension: dimensions

[odscjen]

• adding finalStatus and deprecating status in Lot Add finalStatus and finalStatusDetails open-contracting-extensions/ocds_lots_extension#51

[duncandewhurst]

@jpmckinney when can we start to work on the tasks in this issue?

[jpmckinney]

We should only branch extensions when 1.2 is ready. Keeping the 1.1 and 1.2 branches in sync for those few extensions that have already branched is a headache.

Even if the PR will be against the master branch of an unbranched extension, keeping a PR open for many months and then merging it when 1.2 is ready will similarly be a headache.