From fcf2e5049176fba86d0e3ec25314014c5f1e248d Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Fri, 13 May 2022 10:54:51 +0200
Subject: [PATCH 01/35] Chronologically reordered
---
schema/codelists/contractStatus.csv | 5 +++--
schema/codelists/tenderStatus.csv | 2 +-
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/schema/codelists/contractStatus.csv b/schema/codelists/contractStatus.csv
index c77e2426e..c3b1d9eb2 100644
--- a/schema/codelists/contractStatus.csv
+++ b/schema/codelists/contractStatus.csv
@@ -1,7 +1,8 @@
Code,Title,Description
pending,Pending,"This contract has been proposed, but is not yet in force. It might be awaiting signature."
active,Active,"This contract has been concluded by all the parties, and is now legally in force."
-cancelled,Cancelled,This contract has been cancelled prior to being concluded.
terminated,Terminated,"This contract was concluded and in force, and has now come to a close. This might be due to the successful completion of the contract, or might be early termination due to some non-completion."
-terminatedEarly,Terminated early,"This contract was concluded and in force, and is terminated early due to some non-completion."
terminatedSuccessfully,Terminated successfuly,"This contract was concluded and in force, and is terminated due to its successful completion."
+terminatedEarly,Terminated early,"This contract was concluded and in force, and is terminated early due to some non-completion."
+cancelled,Cancelled,This contract has been cancelled prior to being concluded.
+
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index 36a22ea17..7032a06dd 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -2,7 +2,7 @@ Code,Title,Description
planning,Planning,"A future contracting process is being considered. Early information about the process can be provided in the tender section. A process with this status might provide information on early engagement or consultation opportunities, during which the details of a subsequent tender can be shaped."
planned,Planned,"A contracting process is scheduled, but is not yet taking place. Details of the anticipated dates can be provided in the tender block."
active,Active,A tender process is currently taking place.
+complete,Complete,The tender process is complete.
cancelled,Cancelled,The tender process has been cancelled.
unsuccessful,Unsuccessful,The tender process was unsuccessful.
-complete,Complete,The tender process is complete.
withdrawn,Withdrawn,No further information on this process is available under this ocid.
From 0ab657925683cccbc899bfbbc2f6b558593cde37 Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Fri, 13 May 2022 10:56:01 +0200
Subject: [PATCH 02/35] Remove 'planning' from `tenderStatus`
---
schema/codelists/tenderStatus.csv | 1 -
1 file changed, 1 deletion(-)
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index 7032a06dd..637c2d4b7 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -1,5 +1,4 @@
Code,Title,Description
-planning,Planning,"A future contracting process is being considered. Early information about the process can be provided in the tender section. A process with this status might provide information on early engagement or consultation opportunities, during which the details of a subsequent tender can be shaped."
planned,Planned,"A contracting process is scheduled, but is not yet taking place. Details of the anticipated dates can be provided in the tender block."
active,Active,A tender process is currently taking place.
complete,Complete,The tender process is complete.
From c916e90c98c100bcaac9624d7310af4421bc8b06 Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Fri, 13 May 2022 11:21:35 +0200
Subject: [PATCH 03/35] Update status codelists
---
schema/codelists/awardStatus.csv | 9 +++++----
schema/codelists/contractStatus.csv | 14 +++++++-------
schema/codelists/tenderStatus.csv | 12 ++++++------
3 files changed, 18 insertions(+), 17 deletions(-)
diff --git a/schema/codelists/awardStatus.csv b/schema/codelists/awardStatus.csv
index 21a5efd12..067c89bda 100644
--- a/schema/codelists/awardStatus.csv
+++ b/schema/codelists/awardStatus.csv
@@ -1,5 +1,6 @@
Code,Title,Description
-pending,Pending,"This award has been proposed, but is not yet in force. This can be due to a cooling off period, or some other process."
-active,Active,"This award has been made, and is currently in force."
-cancelled,Cancelled,This award has been cancelled.
-unsuccessful,Unsuccessful,"This award could not be successfully made. If items or supplier details are included within the award section, then these narrow the scope of the unsuccessful award (i.e. the award of noted items, or an award to the noted supplier, was unsuccessful, but there can be other successful awards for different items listed in the tender, or to different suppliers)."
+active,Active,"The bid submission deadline has passed, but the award has not yet been made or the standstill period, if any, has not yet ended."
+complete,Complete,"The award has been made and the standstill period, if any, has ended."
+cancelled,Cancelled,"This award has been cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the bid submission deadline, but before the award had been made or before the standstill period, if any, had ended."
+unsuccessful,Unsuccessful,"The award failed (e.g. a review body cancelled the process during the standstill period) after the bid submission deadline, but before the award had been made or before the standstill period, if any, had ended."
+withdrawn,Withdrawn,"No further information on the award is available under this ocid."
diff --git a/schema/codelists/contractStatus.csv b/schema/codelists/contractStatus.csv
index c3b1d9eb2..c5904f66a 100644
--- a/schema/codelists/contractStatus.csv
+++ b/schema/codelists/contractStatus.csv
@@ -1,8 +1,8 @@
Code,Title,Description
-pending,Pending,"This contract has been proposed, but is not yet in force. It might be awaiting signature."
-active,Active,"This contract has been concluded by all the parties, and is now legally in force."
-terminated,Terminated,"This contract was concluded and in force, and has now come to a close. This might be due to the successful completion of the contract, or might be early termination due to some non-completion."
-terminatedSuccessfully,Terminated successfuly,"This contract was concluded and in force, and is terminated due to its successful completion."
-terminatedEarly,Terminated early,"This contract was concluded and in force, and is terminated early due to some non-completion."
-cancelled,Cancelled,This contract has been cancelled prior to being concluded.
-
+active,Active,"The award has been made and the standstill period, if any, has ended. The contract has not yet terminated."
+terminated,Terminated,"The contract was concluded and in force, and has now come to a close. This might be due to the successful completion of the contract, or might be early termination due to some non-completion."
+terminatedSuccessfully,Terminated successfuly,"The contract was concluded and in force, and is terminated due to its successful completion."
+terminatedEarly,Terminated early,"The contract was concluded and in force, and is terminated early due to some non-completion."
+cancelled,Cancelled,"The contracting process has been cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the award has been made and the standstill period, if any, has ended.".
+unsuccessful,Unsuccessful,"The contract failed (e.g. the winning bidder(s) refused to sign the contract) after the award had been made and the standstill period, if any, had ended, but before the contract was signed and in force."
+withdrawn,Withdrawn,"No further information on the contract is available under this ocid."
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index 637c2d4b7..0319f02e7 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -1,7 +1,7 @@
Code,Title,Description
-planned,Planned,"A contracting process is scheduled, but is not yet taking place. Details of the anticipated dates can be provided in the tender block."
-active,Active,A tender process is currently taking place.
-complete,Complete,The tender process is complete.
-cancelled,Cancelled,The tender process has been cancelled.
-unsuccessful,Unsuccessful,The tender process was unsuccessful.
-withdrawn,Withdrawn,No further information on this process is available under this ocid.
+planned,Planned,"The contracting process is scheduled, but is not yet taking place. Details of the anticipated dates can be provided in the tender block."
+active,Active,The procurement documents have been published and the bid submission deadline has not yet passed.
+complete,Complete,The bid submission deadline has passed.
+cancelled,Cancelled,"The contracting process has been cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the procurement documents have been published, but not later than the bid submission deadline."
+unsuccessful,Unsuccessful,"The contracting process failed after the procurement documents have been published, but not later than the bid submission deadline (e.g. no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity)."
+withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.
From c24b42fb7f4233bc392519471669a7f2fb02ec2f Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Fri, 13 May 2022 11:40:21 +0200
Subject: [PATCH 04/35] Update changelog.md
---
docs/history/changelog.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/docs/history/changelog.md b/docs/history/changelog.md
index abff6c18c..17511661b 100644
--- a/docs/history/changelog.md
+++ b/docs/history/changelog.md
@@ -146,6 +146,7 @@ Per the [normative and non-normative content and changes policy](https://docs.go
* [#1200](https://github.com/open-contracting/standard/pull/1200) Deprecate the `submissionMethod` codelist, because its codes were either not submission methods, or not supported by use cases.
* [#1209](https://github.com/open-contracting/standard/pull/1209) Replace "electronic goods" with "digital goods" in the description of 'goods' from the `procurementCategory` codelist, to align with the description in the World Trade Organization's Agreement on Government Procurement, and to avoid confusion between electronic goods like computers and digital goods like software.
* [#1389](https://github.com/open-contracting/standard/pull/1389) Deprecate the `initiationType` codelist, because the approach to data modelling that it supports was not pursued.
+* [#1509](https://github.com/open-contracting/standard/pull/1509) Update the `tenderStatus`, `awardStatus` and `contractStatus` codelists, including major change of descriptions, removal of 'planning' and 'pending' and the addition of 'withdrawn', 'complete', 'cancelled' and 'unsuccessful' to codelists where they were not before.
### Schema
From c93eb57ecfb3bd3edc79277d2671ed89e0d78493 Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Fri, 13 May 2022 11:42:35 +0200
Subject: [PATCH 05/35] Typo
---
schema/codelists/contractStatus.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schema/codelists/contractStatus.csv b/schema/codelists/contractStatus.csv
index c5904f66a..3e1afaf83 100644
--- a/schema/codelists/contractStatus.csv
+++ b/schema/codelists/contractStatus.csv
@@ -3,6 +3,6 @@ active,Active,"The award has been made and the standstill period, if any, has en
terminated,Terminated,"The contract was concluded and in force, and has now come to a close. This might be due to the successful completion of the contract, or might be early termination due to some non-completion."
terminatedSuccessfully,Terminated successfuly,"The contract was concluded and in force, and is terminated due to its successful completion."
terminatedEarly,Terminated early,"The contract was concluded and in force, and is terminated early due to some non-completion."
-cancelled,Cancelled,"The contracting process has been cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the award has been made and the standstill period, if any, has ended.".
+cancelled,Cancelled,"The contracting process has been cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the award has been made and the standstill period, if any, has ended."
unsuccessful,Unsuccessful,"The contract failed (e.g. the winning bidder(s) refused to sign the contract) after the award had been made and the standstill period, if any, had ended, but before the contract was signed and in force."
withdrawn,Withdrawn,"No further information on the contract is available under this ocid."
From 1e8fe3fea566ba6f5f3672fb96785da298779cbf Mon Sep 17 00:00:00 2001
From: James McKinney <26463+jpmckinney@users.noreply.github.com>
Date: Fri, 20 May 2022 17:02:00 -0400
Subject: [PATCH 06/35] release-schema: Add new codes to status enums. Restore
deprecated codes, with Deprecated and Deprecation note columns.
---
schema/codelists/awardStatus.csv | 13 +++++++------
schema/codelists/contractStatus.csv | 17 +++++++++--------
schema/codelists/tenderStatus.csv | 15 ++++++++-------
schema/dereferenced-release-schema.json | 16 ++++++++++++----
schema/release-schema.json | 8 ++++++--
schema/versioned-release-validation-schema.json | 8 ++++++--
6 files changed, 48 insertions(+), 29 deletions(-)
diff --git a/schema/codelists/awardStatus.csv b/schema/codelists/awardStatus.csv
index 067c89bda..f5539298f 100644
--- a/schema/codelists/awardStatus.csv
+++ b/schema/codelists/awardStatus.csv
@@ -1,6 +1,7 @@
-Code,Title,Description
-active,Active,"The bid submission deadline has passed, but the award has not yet been made or the standstill period, if any, has not yet ended."
-complete,Complete,"The award has been made and the standstill period, if any, has ended."
-cancelled,Cancelled,"This award has been cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the bid submission deadline, but before the award had been made or before the standstill period, if any, had ended."
-unsuccessful,Unsuccessful,"The award failed (e.g. a review body cancelled the process during the standstill period) after the bid submission deadline, but before the award had been made or before the standstill period, if any, had ended."
-withdrawn,Withdrawn,"No further information on the award is available under this ocid."
+Code,Title,Description,Deprecated,Deprecation note
+pending,Pending,"This award has been proposed, but is not yet in force. This can be due to a cooling off period, or some other process.",1.2,
+active,Active,"The bid submission deadline has passed, but the award has not yet been made or the standstill period, if any, has not yet ended.",,
+complete,Complete,"The award has been made and the standstill period, if any, has ended.",,
+cancelled,Cancelled,"This award has been cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the bid submission deadline, but before the award had been made or before the standstill period, if any, had ended.",,
+unsuccessful,Unsuccessful,"The award failed (e.g. a review body cancelled the process during the standstill period) after the bid submission deadline, but before the award had been made or before the standstill period, if any, had ended.",,
+withdrawn,Withdrawn,No further information on the award is available under this ocid.,,
diff --git a/schema/codelists/contractStatus.csv b/schema/codelists/contractStatus.csv
index 3e1afaf83..ddc2d2569 100644
--- a/schema/codelists/contractStatus.csv
+++ b/schema/codelists/contractStatus.csv
@@ -1,8 +1,9 @@
-Code,Title,Description
-active,Active,"The award has been made and the standstill period, if any, has ended. The contract has not yet terminated."
-terminated,Terminated,"The contract was concluded and in force, and has now come to a close. This might be due to the successful completion of the contract, or might be early termination due to some non-completion."
-terminatedSuccessfully,Terminated successfuly,"The contract was concluded and in force, and is terminated due to its successful completion."
-terminatedEarly,Terminated early,"The contract was concluded and in force, and is terminated early due to some non-completion."
-cancelled,Cancelled,"The contracting process has been cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the award has been made and the standstill period, if any, has ended."
-unsuccessful,Unsuccessful,"The contract failed (e.g. the winning bidder(s) refused to sign the contract) after the award had been made and the standstill period, if any, had ended, but before the contract was signed and in force."
-withdrawn,Withdrawn,"No further information on the contract is available under this ocid."
+Code,Title,Description,Deprecated,Deprecation note
+pending,Pending,"This contract has been proposed, but is not yet in force. It might be awaiting signature.",1.2,
+active,Active,"The award has been made and the standstill period, if any, has ended. The contract has not yet terminated.",,
+terminated,Terminated,"The contract was concluded and in force, and has now come to a close. This might be due to the successful completion of the contract, or might be early termination due to some non-completion.",,
+terminatedSuccessfully,Terminated successfully,"The contract was concluded and in force, and is terminated due to its successful completion.",,
+terminatedEarly,Terminated early,"The contract was concluded and in force, and is terminated early due to some non-completion.",,
+cancelled,Cancelled,"The contracting process has been cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the award has been made and the standstill period, if any, has ended.",,
+unsuccessful,Unsuccessful,"The contract failed (e.g. the winning bidder(s) refused to sign the contract) after the award had been made and the standstill period, if any, had ended, but before the contract was signed and in force.",,
+withdrawn,Withdrawn,No further information on the contract is available under this ocid.,,
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index 0319f02e7..0a7d43fea 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -1,7 +1,8 @@
-Code,Title,Description
-planned,Planned,"The contracting process is scheduled, but is not yet taking place. Details of the anticipated dates can be provided in the tender block."
-active,Active,The procurement documents have been published and the bid submission deadline has not yet passed.
-complete,Complete,The bid submission deadline has passed.
-cancelled,Cancelled,"The contracting process has been cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the procurement documents have been published, but not later than the bid submission deadline."
-unsuccessful,Unsuccessful,"The contracting process failed after the procurement documents have been published, but not later than the bid submission deadline (e.g. no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity)."
-withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.
+Code,Title,Description,Deprecated,Deprecation note
+planning,Planning,"A future contracting process is being considered. Early information about the process can be provided in the tender section. A process with this status might provide information on early engagement or consultation opportunities, during which the details of a subsequent tender can be shaped.",1.2,
+planned,Planned,"The contracting process is scheduled, but is not yet taking place. Details of the anticipated dates can be provided in the tender block.",,
+active,Active,The procurement documents have been published and the bid submission deadline has not yet passed.,,
+complete,Complete,The bid submission deadline has passed.,,
+cancelled,Cancelled,"The contracting process has been cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the procurement documents have been published, but not later than the bid submission deadline.",,
+unsuccessful,Unsuccessful,"The contracting process failed after the procurement documents have been published, but not later than the bid submission deadline (e.g. no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity).",,
+withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.,,
diff --git a/schema/dereferenced-release-schema.json b/schema/dereferenced-release-schema.json
index 049bd102e..7d5e86cff 100644
--- a/schema/dereferenced-release-schema.json
+++ b/schema/dereferenced-release-schema.json
@@ -2454,9 +2454,9 @@
"planning",
"planned",
"active",
+ "complete",
"cancelled",
"unsuccessful",
- "complete",
"withdrawn",
null
]
@@ -6459,8 +6459,10 @@
"enum": [
"pending",
"active",
+ "complete",
"cancelled",
"unsuccessful",
+ "withdrawn",
null
],
"codelist": "awardStatus.csv",
@@ -9043,10 +9045,12 @@
"enum": [
"pending",
"active",
- "cancelled",
"terminated",
"terminatedEarly",
"terminatedSuccessfully",
+ "cancelled",
+ "unsuccessful",
+ "withdrawn",
null
],
"codelist": "contractStatus.csv",
@@ -15668,9 +15672,9 @@
"planning",
"planned",
"active",
+ "complete",
"cancelled",
"unsuccessful",
- "complete",
"withdrawn",
null
]
@@ -19669,8 +19673,10 @@
"enum": [
"pending",
"active",
+ "complete",
"cancelled",
"unsuccessful",
+ "withdrawn",
null
],
"codelist": "awardStatus.csv",
@@ -22247,10 +22253,12 @@
"enum": [
"pending",
"active",
- "cancelled",
"terminated",
"terminatedEarly",
"terminatedSuccessfully",
+ "cancelled",
+ "unsuccessful",
+ "withdrawn",
null
],
"codelist": "contractStatus.csv",
diff --git a/schema/release-schema.json b/schema/release-schema.json
index a17bf6c2b..7e26b1634 100644
--- a/schema/release-schema.json
+++ b/schema/release-schema.json
@@ -245,9 +245,9 @@
"planning",
"planned",
"active",
+ "complete",
"cancelled",
"unsuccessful",
- "complete",
"withdrawn",
null
]
@@ -603,8 +603,10 @@
"enum": [
"pending",
"active",
+ "complete",
"cancelled",
"unsuccessful",
+ "withdrawn",
null
],
"codelist": "awardStatus.csv",
@@ -780,10 +782,12 @@
"enum": [
"pending",
"active",
- "cancelled",
"terminated",
"terminatedEarly",
"terminatedSuccessfully",
+ "cancelled",
+ "unsuccessful",
+ "withdrawn",
null
],
"codelist": "contractStatus.csv",
diff --git a/schema/versioned-release-validation-schema.json b/schema/versioned-release-validation-schema.json
index 07dac8a4d..dd74d5c9b 100644
--- a/schema/versioned-release-validation-schema.json
+++ b/schema/versioned-release-validation-schema.json
@@ -239,9 +239,9 @@
"planning",
"planned",
"active",
+ "complete",
"cancelled",
"unsuccessful",
- "complete",
"withdrawn",
null
]
@@ -683,8 +683,10 @@
"enum": [
"pending",
"active",
+ "complete",
"cancelled",
"unsuccessful",
+ "withdrawn",
null
],
"codelist": "awardStatus.csv",
@@ -867,10 +869,12 @@
"enum": [
"pending",
"active",
- "cancelled",
"terminated",
"terminatedEarly",
"terminatedSuccessfully",
+ "cancelled",
+ "unsuccessful",
+ "withdrawn",
null
],
"codelist": "contractStatus.csv",
From eb933c7a154c39b27239aaaf3cab7601be77d9f0 Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Mon, 23 May 2022 14:18:54 +0200
Subject: [PATCH 07/35] `tenderStatus` 'active' Add comma and change tense
Co-authored-by: James McKinney <26463+jpmckinney@users.noreply.github.com>
---
schema/codelists/tenderStatus.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index 0a7d43fea..abcbb06d1 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -1,7 +1,7 @@
Code,Title,Description,Deprecated,Deprecation note
planning,Planning,"A future contracting process is being considered. Early information about the process can be provided in the tender section. A process with this status might provide information on early engagement or consultation opportunities, during which the details of a subsequent tender can be shaped.",1.2,
planned,Planned,"The contracting process is scheduled, but is not yet taking place. Details of the anticipated dates can be provided in the tender block.",,
-active,Active,The procurement documents have been published and the bid submission deadline has not yet passed.,,
+active,Active,"The procurement documents are published, and the bid submission deadline has not yet passed.",,
complete,Complete,The bid submission deadline has passed.,,
cancelled,Cancelled,"The contracting process has been cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the procurement documents have been published, but not later than the bid submission deadline.",,
unsuccessful,Unsuccessful,"The contracting process failed after the procurement documents have been published, but not later than the bid submission deadline (e.g. no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity).",,
From 1d804f7cb7c25b542be4b836f4998da1caefc8b8 Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Mon, 23 May 2022 14:20:29 +0200
Subject: [PATCH 08/35] tenderStatus 'unsuccessful' Change tense
Co-authored-by: James McKinney <26463+jpmckinney@users.noreply.github.com>
---
schema/codelists/tenderStatus.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index abcbb06d1..7d40b22ca 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -4,5 +4,5 @@ planned,Planned,"The contracting process is scheduled, but is not yet taking pla
active,Active,"The procurement documents are published, and the bid submission deadline has not yet passed.",,
complete,Complete,The bid submission deadline has passed.,,
cancelled,Cancelled,"The contracting process has been cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the procurement documents have been published, but not later than the bid submission deadline.",,
-unsuccessful,Unsuccessful,"The contracting process failed after the procurement documents have been published, but not later than the bid submission deadline (e.g. no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity).",,
+unsuccessful,Unsuccessful,"The contracting process failed after the procurement documents were published, but not later than the bid submission deadline (e.g. no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity).",,
withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.,,
From ffe76df3b99d7e25b0201e221ccca8997a9025cd Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Mon, 23 May 2022 14:21:11 +0200
Subject: [PATCH 09/35] tenderStatus 'cancelled': Change tense
Co-authored-by: James McKinney <26463+jpmckinney@users.noreply.github.com>
---
schema/codelists/tenderStatus.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index 7d40b22ca..98936b6ff 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -3,6 +3,6 @@ planning,Planning,"A future contracting process is being considered. Early infor
planned,Planned,"The contracting process is scheduled, but is not yet taking place. Details of the anticipated dates can be provided in the tender block.",,
active,Active,"The procurement documents are published, and the bid submission deadline has not yet passed.",,
complete,Complete,The bid submission deadline has passed.,,
-cancelled,Cancelled,"The contracting process has been cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the procurement documents have been published, but not later than the bid submission deadline.",,
+cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the procurement documents were published, but not later than the bid submission deadline.",,
unsuccessful,Unsuccessful,"The contracting process failed after the procurement documents were published, but not later than the bid submission deadline (e.g. no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity).",,
withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.,,
From ec0ce21adb3ce50b37c3fd39a12b019b21f22c5b Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Mon, 23 May 2022 14:21:46 +0200
Subject: [PATCH 10/35] `awardStatus` 'active': Change tense
Co-authored-by: James McKinney <26463+jpmckinney@users.noreply.github.com>
---
schema/codelists/awardStatus.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schema/codelists/awardStatus.csv b/schema/codelists/awardStatus.csv
index f5539298f..1166901a9 100644
--- a/schema/codelists/awardStatus.csv
+++ b/schema/codelists/awardStatus.csv
@@ -1,6 +1,6 @@
Code,Title,Description,Deprecated,Deprecation note
pending,Pending,"This award has been proposed, but is not yet in force. This can be due to a cooling off period, or some other process.",1.2,
-active,Active,"The bid submission deadline has passed, but the award has not yet been made or the standstill period, if any, has not yet ended.",,
+active,Active,"The bid submission deadline has passed, but the award is not yet made or the standstill period, if any, has not yet ended.",,
complete,Complete,"The award has been made and the standstill period, if any, has ended.",,
cancelled,Cancelled,"This award has been cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the bid submission deadline, but before the award had been made or before the standstill period, if any, had ended.",,
unsuccessful,Unsuccessful,"The award failed (e.g. a review body cancelled the process during the standstill period) after the bid submission deadline, but before the award had been made or before the standstill period, if any, had ended.",,
From e238cb6169494525a226671e0123ac30f3f3755f Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Mon, 23 May 2022 14:22:13 +0200
Subject: [PATCH 11/35] `awardStatus` 'cancelled': Change tense
Co-authored-by: James McKinney <26463+jpmckinney@users.noreply.github.com>
---
schema/codelists/awardStatus.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schema/codelists/awardStatus.csv b/schema/codelists/awardStatus.csv
index 1166901a9..6b4af2c89 100644
--- a/schema/codelists/awardStatus.csv
+++ b/schema/codelists/awardStatus.csv
@@ -2,6 +2,6 @@ Code,Title,Description,Deprecated,Deprecation note
pending,Pending,"This award has been proposed, but is not yet in force. This can be due to a cooling off period, or some other process.",1.2,
active,Active,"The bid submission deadline has passed, but the award is not yet made or the standstill period, if any, has not yet ended.",,
complete,Complete,"The award has been made and the standstill period, if any, has ended.",,
-cancelled,Cancelled,"This award has been cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the bid submission deadline, but before the award had been made or before the standstill period, if any, had ended.",,
+cancelled,Cancelled,"The award was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",,
unsuccessful,Unsuccessful,"The award failed (e.g. a review body cancelled the process during the standstill period) after the bid submission deadline, but before the award had been made or before the standstill period, if any, had ended.",,
withdrawn,Withdrawn,No further information on the award is available under this ocid.,,
From f13de9e058a1a96f597d5f4b2ec25f6e7a4ba234 Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Mon, 23 May 2022 14:22:44 +0200
Subject: [PATCH 12/35] `awardStatus` 'unsuccessful': Change tense
Co-authored-by: James McKinney <26463+jpmckinney@users.noreply.github.com>
---
schema/codelists/awardStatus.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schema/codelists/awardStatus.csv b/schema/codelists/awardStatus.csv
index 6b4af2c89..e9c0c5b71 100644
--- a/schema/codelists/awardStatus.csv
+++ b/schema/codelists/awardStatus.csv
@@ -3,5 +3,5 @@ pending,Pending,"This award has been proposed, but is not yet in force. This can
active,Active,"The bid submission deadline has passed, but the award is not yet made or the standstill period, if any, has not yet ended.",,
complete,Complete,"The award has been made and the standstill period, if any, has ended.",,
cancelled,Cancelled,"The award was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",,
-unsuccessful,Unsuccessful,"The award failed (e.g. a review body cancelled the process during the standstill period) after the bid submission deadline, but before the award had been made or before the standstill period, if any, had ended.",,
+unsuccessful,Unsuccessful,"The award failed (e.g. a review body cancelled the process during the standstill period) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",,
withdrawn,Withdrawn,No further information on the award is available under this ocid.,,
From bc4331f828dc2de697c1047c582a412ffdfd1f16 Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Mon, 23 May 2022 14:23:05 +0200
Subject: [PATCH 13/35] `awardStatus` 'complete': Change tense
Co-authored-by: James McKinney <26463+jpmckinney@users.noreply.github.com>
---
schema/codelists/awardStatus.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schema/codelists/awardStatus.csv b/schema/codelists/awardStatus.csv
index e9c0c5b71..2349b14a7 100644
--- a/schema/codelists/awardStatus.csv
+++ b/schema/codelists/awardStatus.csv
@@ -1,7 +1,7 @@
Code,Title,Description,Deprecated,Deprecation note
pending,Pending,"This award has been proposed, but is not yet in force. This can be due to a cooling off period, or some other process.",1.2,
active,Active,"The bid submission deadline has passed, but the award is not yet made or the standstill period, if any, has not yet ended.",,
-complete,Complete,"The award has been made and the standstill period, if any, has ended.",,
+complete,Complete,"The award was made and the standstill period, if any, has ended.",,
cancelled,Cancelled,"The award was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",,
unsuccessful,Unsuccessful,"The award failed (e.g. a review body cancelled the process during the standstill period) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",,
withdrawn,Withdrawn,No further information on the award is available under this ocid.,,
From 366bb13d2678b1bf583dbcaea0ad86ce7b92ddd0 Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Mon, 23 May 2022 14:23:35 +0200
Subject: [PATCH 14/35] `contractStatus` 'active': Change tense
Co-authored-by: James McKinney <26463+jpmckinney@users.noreply.github.com>
---
schema/codelists/contractStatus.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schema/codelists/contractStatus.csv b/schema/codelists/contractStatus.csv
index ddc2d2569..709b206b5 100644
--- a/schema/codelists/contractStatus.csv
+++ b/schema/codelists/contractStatus.csv
@@ -1,6 +1,6 @@
Code,Title,Description,Deprecated,Deprecation note
pending,Pending,"This contract has been proposed, but is not yet in force. It might be awaiting signature.",1.2,
-active,Active,"The award has been made and the standstill period, if any, has ended. The contract has not yet terminated.",,
+active,Active,"The award was made and the standstill period, if any, has ended. The contract is not yet terminated.",,
terminated,Terminated,"The contract was concluded and in force, and has now come to a close. This might be due to the successful completion of the contract, or might be early termination due to some non-completion.",,
terminatedSuccessfully,Terminated successfully,"The contract was concluded and in force, and is terminated due to its successful completion.",,
terminatedEarly,Terminated early,"The contract was concluded and in force, and is terminated early due to some non-completion.",,
From 4d702683c456d4d1902a7fbb774f21c4d823046a Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Mon, 23 May 2022 14:24:10 +0200
Subject: [PATCH 15/35] `contractStatus` 'cancelled': Change tense
Co-authored-by: James McKinney <26463+jpmckinney@users.noreply.github.com>
---
schema/codelists/contractStatus.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schema/codelists/contractStatus.csv b/schema/codelists/contractStatus.csv
index 709b206b5..e20683f30 100644
--- a/schema/codelists/contractStatus.csv
+++ b/schema/codelists/contractStatus.csv
@@ -4,6 +4,6 @@ active,Active,"The award was made and the standstill period, if any, has ended.
terminated,Terminated,"The contract was concluded and in force, and has now come to a close. This might be due to the successful completion of the contract, or might be early termination due to some non-completion.",,
terminatedSuccessfully,Terminated successfully,"The contract was concluded and in force, and is terminated due to its successful completion.",,
terminatedEarly,Terminated early,"The contract was concluded and in force, and is terminated early due to some non-completion.",,
-cancelled,Cancelled,"The contracting process has been cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the award has been made and the standstill period, if any, has ended.",,
+cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the award was made and the standstill period, if any, had ended.",,
unsuccessful,Unsuccessful,"The contract failed (e.g. the winning bidder(s) refused to sign the contract) after the award had been made and the standstill period, if any, had ended, but before the contract was signed and in force.",,
withdrawn,Withdrawn,No further information on the contract is available under this ocid.,,
From efa269418208e4fe99ef5536ad61dadb87bbfd3f Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Mon, 23 May 2022 14:24:36 +0200
Subject: [PATCH 16/35] `contractStatus` 'unsuccessful': Change tense
Co-authored-by: James McKinney <26463+jpmckinney@users.noreply.github.com>
---
schema/codelists/contractStatus.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schema/codelists/contractStatus.csv b/schema/codelists/contractStatus.csv
index e20683f30..8a19e02d8 100644
--- a/schema/codelists/contractStatus.csv
+++ b/schema/codelists/contractStatus.csv
@@ -5,5 +5,5 @@ terminated,Terminated,"The contract was concluded and in force, and has now come
terminatedSuccessfully,Terminated successfully,"The contract was concluded and in force, and is terminated due to its successful completion.",,
terminatedEarly,Terminated early,"The contract was concluded and in force, and is terminated early due to some non-completion.",,
cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the award was made and the standstill period, if any, had ended.",,
-unsuccessful,Unsuccessful,"The contract failed (e.g. the winning bidder(s) refused to sign the contract) after the award had been made and the standstill period, if any, had ended, but before the contract was signed and in force.",,
+unsuccessful,Unsuccessful,"The contract failed (e.g. the winning bidder(s) refused to sign the contract) after the award was made and the standstill period, if any, had ended, but before the contract was signed and in force.",,
withdrawn,Withdrawn,No further information on the contract is available under this ocid.,,
From f5aa66f42d8c05bc4935a78be96f0850b7d1f7c4 Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Mon, 23 May 2022 17:36:12 +0200
Subject: [PATCH 17/35] Add deprecation notes and improve changelog
---
docs/history/changelog.md | 11 +++++++++--
schema/codelists/awardStatus.csv | 2 +-
schema/codelists/contractStatus.csv | 2 +-
schema/codelists/tenderStatus.csv | 2 +-
4 files changed, 12 insertions(+), 5 deletions(-)
diff --git a/docs/history/changelog.md b/docs/history/changelog.md
index 17511661b..6905d86b8 100644
--- a/docs/history/changelog.md
+++ b/docs/history/changelog.md
@@ -142,11 +142,18 @@ Per the [normative and non-normative content and changes policy](https://docs.go
* [#1238](https://github.com/open-contracting/standard/pull/1238) Open the `releaseTag` codelist.
* [#1415](https://github.com/open-contracting/standard/pull/1415) Align descriptions of 'planning', 'tender', 'award' and 'contract' with the corresponding schema fields.
-* [#1201](https://github.com/open-contracting/standard/pull/1201) Add 'terminatedEarly' and 'terminatedSuccessfully' codes to the `contractStatus` codelist, to distinguish between successful completion and early termination of the contract.
+* `tenderStatus`, `awardStatus` and `contractStatus`:
+ * [#1509](https://github.com/open-contracting/standard/pull/1509) Major change of descriptions, adding and deprecating the following codes.
+ * Deprecated: 'planning' in `tenderStatus`. Deprecated because it is unnecessary since contracting processes are now split from planning processes (which do not have any states themselves).
+ * Deprecated: 'pending' in `awardStatus` and `contractStatus`. Deprecated because the code (which would follow 'active') does not provide any additional information compared to `awardDate` and `dateSigned` and, in the case of `contractStatus` has unclear semantics ("proposed").
+ * Added: 'withdrawn' in `awardStatus` and `contractStatus`, as information can stop being published at any moment also for only individual awards / contracts.
+ * Added: 'complete' in `awardStatus`, as there was no code suggesting that the award successfully happened and was done (the equivalent in `contractStatus` is 'terminated'.)
+ * Added 'unsuccessful' in `contractStatus`, as a failure not caused by the buyer can happen also in the contract stage (e.g. the winning bidder(s) refuses to sign the contract).
+ * [#1201](https://github.com/open-contracting/standard/pull/1201) Add 'terminatedEarly' and 'terminatedSuccessfully' to the `contractStatus` codelist, to distinguish between successful completion and early termination of the contract.
+
* [#1200](https://github.com/open-contracting/standard/pull/1200) Deprecate the `submissionMethod` codelist, because its codes were either not submission methods, or not supported by use cases.
* [#1209](https://github.com/open-contracting/standard/pull/1209) Replace "electronic goods" with "digital goods" in the description of 'goods' from the `procurementCategory` codelist, to align with the description in the World Trade Organization's Agreement on Government Procurement, and to avoid confusion between electronic goods like computers and digital goods like software.
* [#1389](https://github.com/open-contracting/standard/pull/1389) Deprecate the `initiationType` codelist, because the approach to data modelling that it supports was not pursued.
-* [#1509](https://github.com/open-contracting/standard/pull/1509) Update the `tenderStatus`, `awardStatus` and `contractStatus` codelists, including major change of descriptions, removal of 'planning' and 'pending' and the addition of 'withdrawn', 'complete', 'cancelled' and 'unsuccessful' to codelists where they were not before.
### Schema
diff --git a/schema/codelists/awardStatus.csv b/schema/codelists/awardStatus.csv
index 2349b14a7..327c0755c 100644
--- a/schema/codelists/awardStatus.csv
+++ b/schema/codelists/awardStatus.csv
@@ -1,5 +1,5 @@
Code,Title,Description,Deprecated,Deprecation note
-pending,Pending,"This award has been proposed, but is not yet in force. This can be due to a cooling off period, or some other process.",1.2,
+pending,Pending,"This award has been proposed, but is not yet in force. This can be due to a cooling off period, or some other process.",1.2,"This code is deprecated because it does not provide any additional information compared to 'active' and `awardDate`."
active,Active,"The bid submission deadline has passed, but the award is not yet made or the standstill period, if any, has not yet ended.",,
complete,Complete,"The award was made and the standstill period, if any, has ended.",,
cancelled,Cancelled,"The award was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",,
diff --git a/schema/codelists/contractStatus.csv b/schema/codelists/contractStatus.csv
index 8a19e02d8..4e40f67ef 100644
--- a/schema/codelists/contractStatus.csv
+++ b/schema/codelists/contractStatus.csv
@@ -1,5 +1,5 @@
Code,Title,Description,Deprecated,Deprecation note
-pending,Pending,"This contract has been proposed, but is not yet in force. It might be awaiting signature.",1.2,
+pending,Pending,"This contract has been proposed, but is not yet in force. It might be awaiting signature.",1.2,"This code is deprecated because of unclear meaning ("contract proposed") and likely does not provide any additional information compared to `dateSigned`."
active,Active,"The award was made and the standstill period, if any, has ended. The contract is not yet terminated.",,
terminated,Terminated,"The contract was concluded and in force, and has now come to a close. This might be due to the successful completion of the contract, or might be early termination due to some non-completion.",,
terminatedSuccessfully,Terminated successfully,"The contract was concluded and in force, and is terminated due to its successful completion.",,
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index 98936b6ff..0f928cfde 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -1,5 +1,5 @@
Code,Title,Description,Deprecated,Deprecation note
-planning,Planning,"A future contracting process is being considered. Early information about the process can be provided in the tender section. A process with this status might provide information on early engagement or consultation opportunities, during which the details of a subsequent tender can be shaped.",1.2,
+planning,Planning,"A future contracting process is being considered. Early information about the process can be provided in the tender section. A process with this status might provide information on early engagement or consultation opportunities, during which the details of a subsequent tender can be shaped.",1.2,"This code has been deprecated, because it is unnecessary since contracting processes are split from planning processes (which do not have any states themselves)."
planned,Planned,"The contracting process is scheduled, but is not yet taking place. Details of the anticipated dates can be provided in the tender block.",,
active,Active,"The procurement documents are published, and the bid submission deadline has not yet passed.",,
complete,Complete,The bid submission deadline has passed.,,
From 7722294d340880bb8ce1355b349dec1577db040b Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Mon, 23 May 2022 17:59:17 +0200
Subject: [PATCH 18/35] `tenderStatus` 'planned' Remove reference to different
field
---
schema/codelists/tenderStatus.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index 0f928cfde..8b30afd24 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -1,6 +1,6 @@
Code,Title,Description,Deprecated,Deprecation note
planning,Planning,"A future contracting process is being considered. Early information about the process can be provided in the tender section. A process with this status might provide information on early engagement or consultation opportunities, during which the details of a subsequent tender can be shaped.",1.2,"This code has been deprecated, because it is unnecessary since contracting processes are split from planning processes (which do not have any states themselves)."
-planned,Planned,"The contracting process is scheduled, but is not yet taking place. Details of the anticipated dates can be provided in the tender block.",,
+planned,Planned,"The contracting process is scheduled, but is not yet taking place.",,
active,Active,"The procurement documents are published, and the bid submission deadline has not yet passed.",,
complete,Complete,The bid submission deadline has passed.,,
cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the procurement documents were published, but not later than the bid submission deadline.",,
From ee1630e7554421a77272351a79538061b3b7321c Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Mon, 23 May 2022 18:32:23 +0200
Subject: [PATCH 19/35] Fix "signed" to "concluded"
---
schema/codelists/contractStatus.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schema/codelists/contractStatus.csv b/schema/codelists/contractStatus.csv
index 4e40f67ef..0ef91ae2f 100644
--- a/schema/codelists/contractStatus.csv
+++ b/schema/codelists/contractStatus.csv
@@ -5,5 +5,5 @@ terminated,Terminated,"The contract was concluded and in force, and has now come
terminatedSuccessfully,Terminated successfully,"The contract was concluded and in force, and is terminated due to its successful completion.",,
terminatedEarly,Terminated early,"The contract was concluded and in force, and is terminated early due to some non-completion.",,
cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the award was made and the standstill period, if any, had ended.",,
-unsuccessful,Unsuccessful,"The contract failed (e.g. the winning bidder(s) refused to sign the contract) after the award was made and the standstill period, if any, had ended, but before the contract was signed and in force.",,
+unsuccessful,Unsuccessful,"The contract failed (e.g. the winning bidder(s) refused to sign the contract) after the award was made and the standstill period, if any, had ended, but before the contract was concluded and in force.",,
withdrawn,Withdrawn,No further information on the contract is available under this ocid.,,
From 8aee47456cc68f8907f997c7801245201f29b81e Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Mon, 23 May 2022 21:17:36 +0200
Subject: [PATCH 20/35] `tenderStatus` 'unsuccessful' put parentheses
consistently
---
schema/codelists/tenderStatus.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index 8b30afd24..b1940b26a 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -4,5 +4,5 @@ planned,Planned,"The contracting process is scheduled, but is not yet taking pla
active,Active,"The procurement documents are published, and the bid submission deadline has not yet passed.",,
complete,Complete,The bid submission deadline has passed.,,
cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the procurement documents were published, but not later than the bid submission deadline.",,
-unsuccessful,Unsuccessful,"The contracting process failed after the procurement documents were published, but not later than the bid submission deadline (e.g. no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity).",,
+unsuccessful,Unsuccessful,"The contracting process failed (e.g. no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity) after the procurement documents were published, but not later than the bid submission deadline.",,
withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.,,
From eac08ae99ea305bc9ba502dae2d733c97c512d7c Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Mon, 23 May 2022 21:22:13 +0200
Subject: [PATCH 21/35] Fix formatting
---
schema/codelists/awardStatus.csv | 2 +-
schema/codelists/contractStatus.csv | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/schema/codelists/awardStatus.csv b/schema/codelists/awardStatus.csv
index 327c0755c..60f7be9b8 100644
--- a/schema/codelists/awardStatus.csv
+++ b/schema/codelists/awardStatus.csv
@@ -1,5 +1,5 @@
Code,Title,Description,Deprecated,Deprecation note
-pending,Pending,"This award has been proposed, but is not yet in force. This can be due to a cooling off period, or some other process.",1.2,"This code is deprecated because it does not provide any additional information compared to 'active' and `awardDate`."
+pending,Pending,"This award has been proposed, but is not yet in force. This can be due to a cooling off period, or some other process.",1.2,"This code is deprecated because it does not provide any additional information compared to 'active' and `awardDate`."
active,Active,"The bid submission deadline has passed, but the award is not yet made or the standstill period, if any, has not yet ended.",,
complete,Complete,"The award was made and the standstill period, if any, has ended.",,
cancelled,Cancelled,"The award was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",,
diff --git a/schema/codelists/contractStatus.csv b/schema/codelists/contractStatus.csv
index 0ef91ae2f..fd3418b5d 100644
--- a/schema/codelists/contractStatus.csv
+++ b/schema/codelists/contractStatus.csv
@@ -1,5 +1,5 @@
Code,Title,Description,Deprecated,Deprecation note
-pending,Pending,"This contract has been proposed, but is not yet in force. It might be awaiting signature.",1.2,"This code is deprecated because of unclear meaning ("contract proposed") and likely does not provide any additional information compared to `dateSigned`."
+pending,Pending,"This contract has been proposed, but is not yet in force. It might be awaiting signature.",1.2,"This code is deprecated because of unclear meaning (contract proposed) and likely does not provide any additional information compared to dateSigned."
active,Active,"The award was made and the standstill period, if any, has ended. The contract is not yet terminated.",,
terminated,Terminated,"The contract was concluded and in force, and has now come to a close. This might be due to the successful completion of the contract, or might be early termination due to some non-completion.",,
terminatedSuccessfully,Terminated successfully,"The contract was concluded and in force, and is terminated due to its successful completion.",,
From 3f35c23785498321ddb17137ccd4dbb8a649b009 Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Thu, 26 May 2022 09:07:37 +0200
Subject: [PATCH 22/35] Change "procurement documents" to "contracting
documents (for example, procurement documents)"
---
docs/guidance/design/user_needs.md | 2 +-
schema/codelists/releaseTag.csv | 4 ++--
schema/codelists/tenderStatus.csv | 6 +++---
schema/release-schema.json | 8 ++++----
4 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/docs/guidance/design/user_needs.md b/docs/guidance/design/user_needs.md
index ceb55b126..d61d13b8c 100644
--- a/docs/guidance/design/user_needs.md
+++ b/docs/guidance/design/user_needs.md
@@ -27,7 +27,7 @@ Comparable data using common codelists and the availability of unit prices are p
## Detecting fraud and corruption
-All stakeholders (civil society, the private sector, government and donors) have an interest in identifying and combating corruption in public contracting. Open contracting data can be used to scrutinize procurement documents and data for ‘red flags’ that might indicate public monies are being mis-used.
+All stakeholders (civil society, the private sector, government and donors) have an interest in identifying and combating corruption in public contracting. Open contracting data can be used to scrutinize contracting documents (for example, procurement documents) and data for ‘red flags’ that might indicate public monies are being mis-used.
There are two main approaches to fraud and corruption monitoring. A ‘micro’ approach closely scrutinizes individual procurements.
diff --git a/schema/codelists/releaseTag.csv b/schema/codelists/releaseTag.csv
index 8d96d6a9d..c1f353c0e 100644
--- a/schema/codelists/releaseTag.csv
+++ b/schema/codelists/releaseTag.csv
@@ -1,7 +1,7 @@
Code,Title,Description
-planning,Planning,"Information about, for example, needs identification, budget planning and market research. This information concerns the planning process. This information typically concerns the period before the publication of procurement documents."
+planning,Planning,"Information about, for example, needs identification, budget planning and market research. This information concerns the planning process. This information typically concerns the period before the publication of contracting documents (for example, procurement documents)."
planningUpdate,Planning update,"Details of a proposed or planned contracting process are being updated. This might include addition of information and documents from consultation engagement activities, revised details or timelines for a proposed contracting process, or a tender.status update to indicate that a pipeline proposal has been withdrawn."
-tender,Tender,"Information about, for example, the needed items and their estimated value, procurement method, award criteria, and various deadlines. This information concerns either the contracting process or the planning process. For a contracting process, this information typically concerns the period starting with the publication of procurement documents and ending with the bid submission deadline. For a planning process, this information typically concerns the period before the publication of procurement documents."
+tender,Tender,"Information about, for example, the needed items and their estimated value, procurement method, award criteria, and various deadlines. This information concerns either the contracting process or the planning process. For a contracting process, this information typically concerns the period starting with the publication of contracting documents (for example, procurement documents) and ending with the bid submission deadline. For a planning process, this information typically concerns the period before the publication of contracting documents."
tenderAmendment,Tender amendment,"An amendment to an existing tender release. There should be at least one tender release with the same ocid, but an earlier release date, before a tenderAmendment is published. The term amendment has legal meaning in many jurisdictions."
tenderUpdate,Tender update,"An update to an existing tender release. There should be at least one tender release with the same ocid, but an earlier release date, before a tenderUpdate is published. An update may add new information or make corrections to prior published information. It should not be used for formal legal amendments to a tender, for which the tenderAmendment tag should be used."
tenderCancellation,Tender cancellation,"The cancellation of an existing tender. There should be at least one release with the same ocid, but an earlier release date, which provides details of the tender being cancelled."
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index b1940b26a..4c8c7d479 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -1,8 +1,8 @@
Code,Title,Description,Deprecated,Deprecation note
planning,Planning,"A future contracting process is being considered. Early information about the process can be provided in the tender section. A process with this status might provide information on early engagement or consultation opportunities, during which the details of a subsequent tender can be shaped.",1.2,"This code has been deprecated, because it is unnecessary since contracting processes are split from planning processes (which do not have any states themselves)."
planned,Planned,"The contracting process is scheduled, but is not yet taking place.",,
-active,Active,"The procurement documents are published, and the bid submission deadline has not yet passed.",,
+active,Active,"The contracting documents (for example, procurement documents) are published, and the bid submission deadline has not yet passed.",,
complete,Complete,The bid submission deadline has passed.,,
-cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the procurement documents were published, but not later than the bid submission deadline.",,
-unsuccessful,Unsuccessful,"The contracting process failed (e.g. no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity) after the procurement documents were published, but not later than the bid submission deadline.",,
+cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the contracting documents (for example, procurement documents) were published, but not later than the bid submission deadline.",,
+unsuccessful,Unsuccessful,"The contracting process failed (e.g. no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity) after the contracting documents (for example, procurement documents) were published, but not later than the bid submission deadline.",,
withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.,,
diff --git a/schema/release-schema.json b/schema/release-schema.json
index 7e26b1634..58f882e30 100644
--- a/schema/release-schema.json
+++ b/schema/release-schema.json
@@ -73,12 +73,12 @@
},
"planning": {
"title": "Planning",
- "description": "Information about, for example, needs identification, budget planning and market research. This information concerns the planning process. This information typically concerns the period before the publication of procurement documents.",
+ "description": "Information about, for example, needs identification, budget planning and market research. This information concerns the planning process. This information typically concerns the period before the publication of contracting documents (for example, procurement documents).",
"$ref": "#/definitions/Planning"
},
"tender": {
"title": "Tender",
- "description": "Information about, for example, the needed items and their estimated value, procurement method, award criteria, and various deadlines. This information concerns either the contracting process or the planning process. For a contracting process, this information typically concerns the period starting with the publication of procurement documents and ending with the bid submission deadline. For a planning process, this information typically concerns the period before the publication of procurement documents.",
+ "description": "Information about, for example, the needed items and their estimated value, procurement method, award criteria, and various deadlines. This information concerns either the contracting process or the planning process. For a contracting process, this information typically concerns the period starting with the publication of contracting documents (for example, procurement documents) and ending with the bid submission deadline. For a planning process, this information typically concerns the period before the publication of contracting documents.",
"$ref": "#/definitions/Tender"
},
"awards": {
@@ -139,7 +139,7 @@
"definitions": {
"Planning": {
"title": "Planning",
- "description": "Information about, for example, needs identification, budget planning and market research. This information concerns the planning process. This information typically concerns the period before the publication of procurement documents.",
+ "description": "Information about, for example, needs identification, budget planning and market research. This information concerns the planning process. This information typically concerns the period before the publication of contracting documents (for example, procurement documents).",
"type": "object",
"properties": {
"id": {
@@ -191,7 +191,7 @@
},
"Tender": {
"title": "Tender",
- "description": "Information about, for example, the needed items and their estimated value, procurement method, award criteria, and various deadlines. This information concerns either the contracting process or the planning process. For a contracting process, this information typically concerns the period starting with the publication of procurement documents and ending with the bid submission deadline. For a planning process, this information typically concerns the period before the publication of procurement documents.",
+ "description": "Information about, for example, the needed items and their estimated value, procurement method, award criteria, and various deadlines. This information concerns either the contracting process or the planning process. For a contracting process, this information typically concerns the period starting with the publication of contracting documents (for example, procurement documents) and ending with the bid submission deadline. For a planning process, this information typically concerns the period before the publication of contracting documents.",
"type": "object",
"required": [
"id"
From 1699662925a8888a77e6486c245d5e178556a08d Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Thu, 26 May 2022 10:08:55 +0200
Subject: [PATCH 23/35] Change "Publication" to "being available to potential
suppliers"
---
schema/codelists/releaseTag.csv | 4 ++--
schema/codelists/tenderStatus.csv | 6 +++---
schema/release-schema.json | 8 ++++----
3 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/schema/codelists/releaseTag.csv b/schema/codelists/releaseTag.csv
index c1f353c0e..312542ea8 100644
--- a/schema/codelists/releaseTag.csv
+++ b/schema/codelists/releaseTag.csv
@@ -1,7 +1,7 @@
Code,Title,Description
-planning,Planning,"Information about, for example, needs identification, budget planning and market research. This information concerns the planning process. This information typically concerns the period before the publication of contracting documents (for example, procurement documents)."
+planning,Planning,"Information about, for example, needs identification, budget planning and market research. This information concerns the planning process. This information typically concerns the period before contracting documents (for example, procurement documents) are available to potential suppliers."
planningUpdate,Planning update,"Details of a proposed or planned contracting process are being updated. This might include addition of information and documents from consultation engagement activities, revised details or timelines for a proposed contracting process, or a tender.status update to indicate that a pipeline proposal has been withdrawn."
-tender,Tender,"Information about, for example, the needed items and their estimated value, procurement method, award criteria, and various deadlines. This information concerns either the contracting process or the planning process. For a contracting process, this information typically concerns the period starting with the publication of contracting documents (for example, procurement documents) and ending with the bid submission deadline. For a planning process, this information typically concerns the period before the publication of contracting documents."
+tender,Tender,"Information about, for example, the needed items and their estimated value, procurement method, award criteria, and various deadlines. This information concerns either the contracting process or the planning process. For a contracting process, this information typically concerns the period starting with contracting documents (for example, procurement documents) being available to potential suppliers and ending with the bid submission deadline. For a planning process, this information typically concerns the period before the contracting documents are available to potential suppliers."
tenderAmendment,Tender amendment,"An amendment to an existing tender release. There should be at least one tender release with the same ocid, but an earlier release date, before a tenderAmendment is published. The term amendment has legal meaning in many jurisdictions."
tenderUpdate,Tender update,"An update to an existing tender release. There should be at least one tender release with the same ocid, but an earlier release date, before a tenderUpdate is published. An update may add new information or make corrections to prior published information. It should not be used for formal legal amendments to a tender, for which the tenderAmendment tag should be used."
tenderCancellation,Tender cancellation,"The cancellation of an existing tender. There should be at least one release with the same ocid, but an earlier release date, which provides details of the tender being cancelled."
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index 4c8c7d479..eb36d1a63 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -1,8 +1,8 @@
Code,Title,Description,Deprecated,Deprecation note
planning,Planning,"A future contracting process is being considered. Early information about the process can be provided in the tender section. A process with this status might provide information on early engagement or consultation opportunities, during which the details of a subsequent tender can be shaped.",1.2,"This code has been deprecated, because it is unnecessary since contracting processes are split from planning processes (which do not have any states themselves)."
planned,Planned,"The contracting process is scheduled, but is not yet taking place.",,
-active,Active,"The contracting documents (for example, procurement documents) are published, and the bid submission deadline has not yet passed.",,
+active,Active,"The contracting documents (for example, procurement documents) are available to potential suppliers, and the bid submission deadline has not yet passed.",,
complete,Complete,The bid submission deadline has passed.,,
-cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the contracting documents (for example, procurement documents) were published, but not later than the bid submission deadline.",,
-unsuccessful,Unsuccessful,"The contracting process failed (e.g. no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity) after the contracting documents (for example, procurement documents) were published, but not later than the bid submission deadline.",,
+cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the contracting documents (for example, procurement documents) were available to potential supppliers, but not later than the bid submission deadline.",,
+unsuccessful,Unsuccessful,"The contracting process failed (e.g. no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity) after the contracting documents (for example, procurement documents) were available to potential suppliers, but not later than the bid submission deadline.",,
withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.,,
diff --git a/schema/release-schema.json b/schema/release-schema.json
index 58f882e30..53451f8a6 100644
--- a/schema/release-schema.json
+++ b/schema/release-schema.json
@@ -73,12 +73,12 @@
},
"planning": {
"title": "Planning",
- "description": "Information about, for example, needs identification, budget planning and market research. This information concerns the planning process. This information typically concerns the period before the publication of contracting documents (for example, procurement documents).",
+ "description": "Information about, for example, needs identification, budget planning and market research. This information concerns the planning process. This information typically concerns the period before contracting documents (for example, procurement documents) are available to potential suppliers.",
"$ref": "#/definitions/Planning"
},
"tender": {
"title": "Tender",
- "description": "Information about, for example, the needed items and their estimated value, procurement method, award criteria, and various deadlines. This information concerns either the contracting process or the planning process. For a contracting process, this information typically concerns the period starting with the publication of contracting documents (for example, procurement documents) and ending with the bid submission deadline. For a planning process, this information typically concerns the period before the publication of contracting documents.",
+ "description": "Information about, for example, the needed items and their estimated value, procurement method, award criteria, and various deadlines. This information concerns either the contracting process or the planning process. For a contracting process, this information typically concerns the period starting with contracting documents (for example, procurement documents) being available to potential suppliers and ending with the bid submission deadline. For a planning process, this information typically concerns the period before contracting documents are available to potential suppliers.",
"$ref": "#/definitions/Tender"
},
"awards": {
@@ -139,7 +139,7 @@
"definitions": {
"Planning": {
"title": "Planning",
- "description": "Information about, for example, needs identification, budget planning and market research. This information concerns the planning process. This information typically concerns the period before the publication of contracting documents (for example, procurement documents).",
+ "description": "Information about, for example, needs identification, budget planning and market research. This information concerns the planning process. This information typically concerns the period before contracting documents (for example, procurement documents) are available to potential suppliers.",
"type": "object",
"properties": {
"id": {
@@ -191,7 +191,7 @@
},
"Tender": {
"title": "Tender",
- "description": "Information about, for example, the needed items and their estimated value, procurement method, award criteria, and various deadlines. This information concerns either the contracting process or the planning process. For a contracting process, this information typically concerns the period starting with the publication of contracting documents (for example, procurement documents) and ending with the bid submission deadline. For a planning process, this information typically concerns the period before the publication of contracting documents.",
+ "description": "Information about, for example, the needed items and their estimated value, procurement method, award criteria, and various deadlines. This information concerns either the contracting process or the planning process. For a contracting process, this information typically concerns the period starting with contracting documents (for example, procurement documents) being available to potential suppliers and ending with the bid submission deadline. For a planning process, this information typically concerns the period before contracting documents are available to potential suppliers.",
"type": "object",
"required": [
"id"
From e33c21c0b255bc337879c92a63028f03f00435aa Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Thu, 26 May 2022 10:14:17 +0200
Subject: [PATCH 24/35] `tenderStatus` update 'planned'
---
schema/codelists/tenderStatus.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index eb36d1a63..cda720530 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -1,6 +1,6 @@
Code,Title,Description,Deprecated,Deprecation note
planning,Planning,"A future contracting process is being considered. Early information about the process can be provided in the tender section. A process with this status might provide information on early engagement or consultation opportunities, during which the details of a subsequent tender can be shaped.",1.2,"This code has been deprecated, because it is unnecessary since contracting processes are split from planning processes (which do not have any states themselves)."
-planned,Planned,"The contracting process is scheduled, but is not yet taking place.",,
+planned,Planned,"The contracting process is scheduled, but contracting documents (for example, planning documents) are not yet available to potential suppliers.",,
active,Active,"The contracting documents (for example, procurement documents) are available to potential suppliers, and the bid submission deadline has not yet passed.",,
complete,Complete,The bid submission deadline has passed.,,
cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the contracting documents (for example, procurement documents) were available to potential supppliers, but not later than the bid submission deadline.",,
From 939d491d367cf1964b7e04daff88f15252e49754 Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Thu, 26 May 2022 10:15:44 +0200
Subject: [PATCH 25/35] Fix "e.g." to "for example,"
---
schema/codelists/tenderStatus.csv | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index cda720530..be95bab7c 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -3,6 +3,6 @@ planning,Planning,"A future contracting process is being considered. Early infor
planned,Planned,"The contracting process is scheduled, but contracting documents (for example, planning documents) are not yet available to potential suppliers.",,
active,Active,"The contracting documents (for example, procurement documents) are available to potential suppliers, and the bid submission deadline has not yet passed.",,
complete,Complete,The bid submission deadline has passed.,,
-cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the contracting documents (for example, procurement documents) were available to potential supppliers, but not later than the bid submission deadline.",,
-unsuccessful,Unsuccessful,"The contracting process failed (e.g. no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity) after the contracting documents (for example, procurement documents) were available to potential suppliers, but not later than the bid submission deadline.",,
+cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (for example, because of a change in needs, insufficient funds, or technical or procedural errors) after the contracting documents (for example, procurement documents) were available to potential supppliers, but not later than the bid submission deadline.",,
+unsuccessful,Unsuccessful,"The contracting process failed (for example, no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity) after the contracting documents (for example, procurement documents) were available to potential suppliers, but not later than the bid submission deadline.",,
withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.,,
From 469e540a26b26e6e8a2e30e59485ca67cf0cab48 Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Sat, 28 May 2022 15:42:56 +0200
Subject: [PATCH 26/35] `status` codelists: remove new draft codes, update
wording with semantics closer to old codes, deprecate end codes
---
schema/codelists/awardStatus.csv | 10 ++++------
schema/codelists/contractStatus.csv | 12 ++++--------
schema/codelists/tenderStatus.csv | 6 +++---
3 files changed, 11 insertions(+), 17 deletions(-)
diff --git a/schema/codelists/awardStatus.csv b/schema/codelists/awardStatus.csv
index 60f7be9b8..86151bd58 100644
--- a/schema/codelists/awardStatus.csv
+++ b/schema/codelists/awardStatus.csv
@@ -1,7 +1,5 @@
Code,Title,Description,Deprecated,Deprecation note
-pending,Pending,"This award has been proposed, but is not yet in force. This can be due to a cooling off period, or some other process.",1.2,"This code is deprecated because it does not provide any additional information compared to 'active' and `awardDate`."
-active,Active,"The bid submission deadline has passed, but the award is not yet made or the standstill period, if any, has not yet ended.",,
-complete,Complete,"The award was made and the standstill period, if any, has ended.",,
-cancelled,Cancelled,"The award was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",,
-unsuccessful,Unsuccessful,"The award failed (e.g. a review body cancelled the process during the standstill period) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",,
-withdrawn,Withdrawn,No further information on the award is available under this ocid.,,
+pending,Pending,"The award was made, but the standstill period has not yet ended.",,
+active,Active,"The award was made and the standstill period, if any, has ended.",,
+cancelled,Cancelled,"The award was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",1.2,"OCDS 1.2 replaces this code with a new field for final states."
+unsuccessful,Unsuccessful,"The award failed (e.g. a review body cancelled the process during the standstill period) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",1.2,"OCDS 1.2 replaces this code with a new field for final states."
diff --git a/schema/codelists/contractStatus.csv b/schema/codelists/contractStatus.csv
index fd3418b5d..386f1a587 100644
--- a/schema/codelists/contractStatus.csv
+++ b/schema/codelists/contractStatus.csv
@@ -1,9 +1,5 @@
Code,Title,Description,Deprecated,Deprecation note
-pending,Pending,"This contract has been proposed, but is not yet in force. It might be awaiting signature.",1.2,"This code is deprecated because of unclear meaning (contract proposed) and likely does not provide any additional information compared to dateSigned."
-active,Active,"The award was made and the standstill period, if any, has ended. The contract is not yet terminated.",,
-terminated,Terminated,"The contract was concluded and in force, and has now come to a close. This might be due to the successful completion of the contract, or might be early termination due to some non-completion.",,
-terminatedSuccessfully,Terminated successfully,"The contract was concluded and in force, and is terminated due to its successful completion.",,
-terminatedEarly,Terminated early,"The contract was concluded and in force, and is terminated early due to some non-completion.",,
-cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the award was made and the standstill period, if any, had ended.",,
-unsuccessful,Unsuccessful,"The contract failed (e.g. the winning bidder(s) refused to sign the contract) after the award was made and the standstill period, if any, had ended, but before the contract was concluded and in force.",,
-withdrawn,Withdrawn,No further information on the contract is available under this ocid.,,
+pending,Pending,"The award was made and the standstill period, if any, has ended. The contract is not yet concluded (for example, not signed by all parties).",,
+active,Active,"The contract was concluded (for example, signed by all parties). The contract is not yet terminated.",,
+terminated,Terminated,"The contract was concluded (for example, signed), and has now come to a close. This might be due to the successful completion of the contract, or might be early termination due to some non-completion.",,
+cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the award was made and the standstill period, if any, had ended.",1.2,"OCDS 1.2 replaces this code with a new field for final states."
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index be95bab7c..7126435fb 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -3,6 +3,6 @@ planning,Planning,"A future contracting process is being considered. Early infor
planned,Planned,"The contracting process is scheduled, but contracting documents (for example, planning documents) are not yet available to potential suppliers.",,
active,Active,"The contracting documents (for example, procurement documents) are available to potential suppliers, and the bid submission deadline has not yet passed.",,
complete,Complete,The bid submission deadline has passed.,,
-cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (for example, because of a change in needs, insufficient funds, or technical or procedural errors) after the contracting documents (for example, procurement documents) were available to potential supppliers, but not later than the bid submission deadline.",,
-unsuccessful,Unsuccessful,"The contracting process failed (for example, no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity) after the contracting documents (for example, procurement documents) were available to potential suppliers, but not later than the bid submission deadline.",,
-withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.,,
+cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (for example, because of a change in needs, insufficient funds, or technical or procedural errors) after the contracting documents (for example, procurement documents) were available to potential supppliers, but not later than the bid submission deadline.",1.2,"OCDS 1.2 replaces this code with a new field for final states."
+unsuccessful,Unsuccessful,"The contracting process failed (for example, no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity) after the contracting documents (for example, procurement documents) were available to potential suppliers, but not later than the bid submission deadline.",1.2,"OCDS 1.2 replaces this code with a new field for final states."
+withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.,1.2,"OCDS 1.2 replaces this code with a new field for final states."
From aa5c706065ec20e94f16b0c9b9a28ef4b086318b Mon Sep 17 00:00:00 2001
From: JachymHercher <jachym.hercher@gmail.com>
Date: Sat, 28 May 2022 15:56:48 +0200
Subject: [PATCH 27/35] Deprecate the status fields and the codes in status
codelists
---
schema/codelists/awardStatus.csv | 4 ++--
schema/codelists/contractStatus.csv | 6 +++---
schema/codelists/tenderStatus.csv | 6 +++---
schema/release-schema.json | 18 +++++++++++++++---
4 files changed, 23 insertions(+), 11 deletions(-)
diff --git a/schema/codelists/awardStatus.csv b/schema/codelists/awardStatus.csv
index 86151bd58..020221311 100644
--- a/schema/codelists/awardStatus.csv
+++ b/schema/codelists/awardStatus.csv
@@ -1,5 +1,5 @@
Code,Title,Description,Deprecated,Deprecation note
-pending,Pending,"The award was made, but the standstill period has not yet ended.",,
-active,Active,"The award was made and the standstill period, if any, has ended.",,
+pending,Pending,"The award was made, but the standstill period has not yet ended.",1.2,"Deprecated because the same information can be determined by comparing the sum of `awards/date` and `tender/standstillPeriod/durationInDays` (new in 1.2) to `date`."
+active,Active,"The award was made and the standstill period, if any, has ended.",1.2,"Deprecated because the same information can be determined by comparing the sum of `awards/date` and `tender/standstillPeriod/durationInDays` (new in 1.2) to `date`."
cancelled,Cancelled,"The award was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",1.2,"OCDS 1.2 replaces this code with a new field for final states."
unsuccessful,Unsuccessful,"The award failed (e.g. a review body cancelled the process during the standstill period) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",1.2,"OCDS 1.2 replaces this code with a new field for final states."
diff --git a/schema/codelists/contractStatus.csv b/schema/codelists/contractStatus.csv
index 386f1a587..68f64bd63 100644
--- a/schema/codelists/contractStatus.csv
+++ b/schema/codelists/contractStatus.csv
@@ -1,5 +1,5 @@
Code,Title,Description,Deprecated,Deprecation note
-pending,Pending,"The award was made and the standstill period, if any, has ended. The contract is not yet concluded (for example, not signed by all parties).",,
-active,Active,"The contract was concluded (for example, signed by all parties). The contract is not yet terminated.",,
-terminated,Terminated,"The contract was concluded (for example, signed), and has now come to a close. This might be due to the successful completion of the contract, or might be early termination due to some non-completion.",,
+pending,Pending,"The award was made and the standstill period, if any, has ended. The contract is not yet concluded (for example, not signed by all parties).",1.2,"Deprecated because the same information can be determined by the absence of a `contracts.dateSigned`."
+active,Active,"The contract was concluded (for example, signed by all parties). The contract is not yet terminated.",1.2,"Deprecated because the same information can be determined by comparing `contracts.period` to `date`."
+terminated,Terminated,"The contract was concluded (for example, signed), and has now come to a close. This might be due to the successful completion of the contract, or might be early termination due to some non-completion.",1.2,"OCDS 1.2 replaces this code with a new field for final states."
cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the award was made and the standstill period, if any, had ended.",1.2,"OCDS 1.2 replaces this code with a new field for final states."
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index 7126435fb..d62f81d6f 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -1,8 +1,8 @@
Code,Title,Description,Deprecated,Deprecation note
planning,Planning,"A future contracting process is being considered. Early information about the process can be provided in the tender section. A process with this status might provide information on early engagement or consultation opportunities, during which the details of a subsequent tender can be shaped.",1.2,"This code has been deprecated, because it is unnecessary since contracting processes are split from planning processes (which do not have any states themselves)."
-planned,Planned,"The contracting process is scheduled, but contracting documents (for example, planning documents) are not yet available to potential suppliers.",,
-active,Active,"The contracting documents (for example, procurement documents) are available to potential suppliers, and the bid submission deadline has not yet passed.",,
-complete,Complete,The bid submission deadline has passed.,,
+planned,Planned,"The contracting process is scheduled, but contracting documents (for example, planning documents) are not yet available to potential suppliers.",1.2,"Deprecated because the same information can be determined by comparing `tender/datePublished` (new in 1.2) to `date` (or its absence)"
+active,Active,"The contracting documents (for example, procurement documents) are available to potential suppliers, and the bid submission deadline has not yet passed.",1.2,"Deprecated because the same information can be determined by comparing `tender/datePublished` (new in 1.2) and `tender/tenderPeriod/endDate` to `date`."
+complete,Complete,The bid submission deadline has passed.,1.2,"Deprecated because the same information can be determined by comparing `tender/tenderPeriod/endDate` to `date`"
cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (for example, because of a change in needs, insufficient funds, or technical or procedural errors) after the contracting documents (for example, procurement documents) were available to potential supppliers, but not later than the bid submission deadline.",1.2,"OCDS 1.2 replaces this code with a new field for final states."
unsuccessful,Unsuccessful,"The contracting process failed (for example, no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity) after the contracting documents (for example, procurement documents) were available to potential suppliers, but not later than the bid submission deadline.",1.2,"OCDS 1.2 replaces this code with a new field for final states."
withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.,1.2,"OCDS 1.2 replaces this code with a new field for final states."
diff --git a/schema/release-schema.json b/schema/release-schema.json
index 53451f8a6..033474bfe 100644
--- a/schema/release-schema.json
+++ b/schema/release-schema.json
@@ -250,7 +250,11 @@
"unsuccessful",
"withdrawn",
null
- ]
+ ],
+ "deprecated": {
+ "description": "Deprecated because the same information can be provided by filling in the relevant date fields.",
+ "deprecatedVersion": "1.2"
+ }
},
"statusDetails": {
"title": "Status details",
@@ -610,7 +614,11 @@
null
],
"codelist": "awardStatus.csv",
- "openCodelist": false
+ "openCodelist": false,
+ "deprecated": {
+ "description": "Deprecated because the same information can be provided by filling in the relevant date fields.",
+ "deprecatedVersion": "1.2"
+ }
},
"statusDetails": {
"title": "Status details",
@@ -791,7 +799,11 @@
null
],
"codelist": "contractStatus.csv",
- "openCodelist": false
+ "openCodelist": false,
+ "deprecated": {
+ "description": "Deprecated because the same information can be provided by filling in the relevant date fields.",
+ "deprecatedVersion": "1.2"
+ }
},
"statusDetails": {
"title": "Status details",
From e18170859b70d9064a198b4e67f52c498bd02e85 Mon Sep 17 00:00:00 2001
From: James McKinney <26463+jpmckinney@users.noreply.github.com>
Date: Tue, 20 Jun 2023 10:31:00 -0400
Subject: [PATCH 28/35] chore: Lint CSV and schema files. Run ./manage.py
pre-commit.
---
schema/codelists/awardStatus.csv | 8 +--
schema/codelists/contractStatus.csv | 8 +--
schema/codelists/tenderStatus.csv | 12 ++--
schema/dereferenced-release-schema.json | 56 +++++++++++--------
schema/release-schema.json | 6 --
.../versioned-release-validation-schema.json | 24 +++++---
6 files changed, 63 insertions(+), 51 deletions(-)
diff --git a/schema/codelists/awardStatus.csv b/schema/codelists/awardStatus.csv
index 020221311..efa14576a 100644
--- a/schema/codelists/awardStatus.csv
+++ b/schema/codelists/awardStatus.csv
@@ -1,5 +1,5 @@
Code,Title,Description,Deprecated,Deprecation note
-pending,Pending,"The award was made, but the standstill period has not yet ended.",1.2,"Deprecated because the same information can be determined by comparing the sum of `awards/date` and `tender/standstillPeriod/durationInDays` (new in 1.2) to `date`."
-active,Active,"The award was made and the standstill period, if any, has ended.",1.2,"Deprecated because the same information can be determined by comparing the sum of `awards/date` and `tender/standstillPeriod/durationInDays` (new in 1.2) to `date`."
-cancelled,Cancelled,"The award was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",1.2,"OCDS 1.2 replaces this code with a new field for final states."
-unsuccessful,Unsuccessful,"The award failed (e.g. a review body cancelled the process during the standstill period) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",1.2,"OCDS 1.2 replaces this code with a new field for final states."
+pending,Pending,"The award was made, but the standstill period has not yet ended.",1.2,Deprecated because the same information can be determined by comparing the sum of `awards/date` and `tender/standstillPeriod/durationInDays` (new in 1.2) to `date`.
+active,Active,"The award was made and the standstill period, if any, has ended.",1.2,Deprecated because the same information can be determined by comparing the sum of `awards/date` and `tender/standstillPeriod/durationInDays` (new in 1.2) to `date`.
+cancelled,Cancelled,"The award was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",1.2,OCDS 1.2 replaces this code with a new field for final states.
+unsuccessful,Unsuccessful,"The award failed (e.g. a review body cancelled the process during the standstill period) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",1.2,OCDS 1.2 replaces this code with a new field for final states.
diff --git a/schema/codelists/contractStatus.csv b/schema/codelists/contractStatus.csv
index 68f64bd63..9a45758e4 100644
--- a/schema/codelists/contractStatus.csv
+++ b/schema/codelists/contractStatus.csv
@@ -1,5 +1,5 @@
Code,Title,Description,Deprecated,Deprecation note
-pending,Pending,"The award was made and the standstill period, if any, has ended. The contract is not yet concluded (for example, not signed by all parties).",1.2,"Deprecated because the same information can be determined by the absence of a `contracts.dateSigned`."
-active,Active,"The contract was concluded (for example, signed by all parties). The contract is not yet terminated.",1.2,"Deprecated because the same information can be determined by comparing `contracts.period` to `date`."
-terminated,Terminated,"The contract was concluded (for example, signed), and has now come to a close. This might be due to the successful completion of the contract, or might be early termination due to some non-completion.",1.2,"OCDS 1.2 replaces this code with a new field for final states."
-cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the award was made and the standstill period, if any, had ended.",1.2,"OCDS 1.2 replaces this code with a new field for final states."
+pending,Pending,"The award was made and the standstill period, if any, has ended. The contract is not yet concluded (for example, not signed by all parties).",1.2,Deprecated because the same information can be determined by the absence of a `contracts.dateSigned`.
+active,Active,"The contract was concluded (for example, signed by all parties). The contract is not yet terminated.",1.2,Deprecated because the same information can be determined by comparing `contracts.period` to `date`.
+terminated,Terminated,"The contract was concluded (for example, signed), and has now come to a close. This might be due to the successful completion of the contract, or might be early termination due to some non-completion.",1.2,OCDS 1.2 replaces this code with a new field for final states.
+cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the award was made and the standstill period, if any, had ended.",1.2,OCDS 1.2 replaces this code with a new field for final states.
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index d62f81d6f..5ae9fd018 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -1,8 +1,8 @@
Code,Title,Description,Deprecated,Deprecation note
planning,Planning,"A future contracting process is being considered. Early information about the process can be provided in the tender section. A process with this status might provide information on early engagement or consultation opportunities, during which the details of a subsequent tender can be shaped.",1.2,"This code has been deprecated, because it is unnecessary since contracting processes are split from planning processes (which do not have any states themselves)."
-planned,Planned,"The contracting process is scheduled, but contracting documents (for example, planning documents) are not yet available to potential suppliers.",1.2,"Deprecated because the same information can be determined by comparing `tender/datePublished` (new in 1.2) to `date` (or its absence)"
-active,Active,"The contracting documents (for example, procurement documents) are available to potential suppliers, and the bid submission deadline has not yet passed.",1.2,"Deprecated because the same information can be determined by comparing `tender/datePublished` (new in 1.2) and `tender/tenderPeriod/endDate` to `date`."
-complete,Complete,The bid submission deadline has passed.,1.2,"Deprecated because the same information can be determined by comparing `tender/tenderPeriod/endDate` to `date`"
-cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (for example, because of a change in needs, insufficient funds, or technical or procedural errors) after the contracting documents (for example, procurement documents) were available to potential supppliers, but not later than the bid submission deadline.",1.2,"OCDS 1.2 replaces this code with a new field for final states."
-unsuccessful,Unsuccessful,"The contracting process failed (for example, no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity) after the contracting documents (for example, procurement documents) were available to potential suppliers, but not later than the bid submission deadline.",1.2,"OCDS 1.2 replaces this code with a new field for final states."
-withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.,1.2,"OCDS 1.2 replaces this code with a new field for final states."
+planned,Planned,"The contracting process is scheduled, but contracting documents (for example, planning documents) are not yet available to potential suppliers.",1.2,Deprecated because the same information can be determined by comparing `tender/datePublished` (new in 1.2) to `date` (or its absence)
+active,Active,"The contracting documents (for example, procurement documents) are available to potential suppliers, and the bid submission deadline has not yet passed.",1.2,Deprecated because the same information can be determined by comparing `tender/datePublished` (new in 1.2) and `tender/tenderPeriod/endDate` to `date`.
+complete,Complete,The bid submission deadline has passed.,1.2,Deprecated because the same information can be determined by comparing `tender/tenderPeriod/endDate` to `date`
+cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (for example, because of a change in needs, insufficient funds, or technical or procedural errors) after the contracting documents (for example, procurement documents) were available to potential supppliers, but not later than the bid submission deadline.",1.2,OCDS 1.2 replaces this code with a new field for final states.
+unsuccessful,Unsuccessful,"The contracting process failed (for example, no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity) after the contracting documents (for example, procurement documents) were available to potential suppliers, but not later than the bid submission deadline.",1.2,OCDS 1.2 replaces this code with a new field for final states.
+withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.,1.2,OCDS 1.2 replaces this code with a new field for final states.
diff --git a/schema/dereferenced-release-schema.json b/schema/dereferenced-release-schema.json
index 1df7ade63..ea0cf8e80 100644
--- a/schema/dereferenced-release-schema.json
+++ b/schema/dereferenced-release-schema.json
@@ -1193,7 +1193,7 @@
},
"planning": {
"title": "Planning",
- "description": "Information about, for example, needs identification, budget planning and market research. This information concerns the planning process. This information typically concerns the period before the publication of procurement documents.",
+ "description": "Information about, for example, needs identification, budget planning and market research. This information concerns the planning process. This information typically concerns the period before contracting documents (for example, procurement documents) are available to potential suppliers.",
"type": "object",
"properties": {
"id": {
@@ -2379,7 +2379,7 @@
},
"tender": {
"title": "Tender",
- "description": "Information about, for example, the needed items and their estimated value, procurement method, award criteria, and various deadlines. This information concerns either the contracting process or the planning process. For a contracting process, this information typically concerns the period starting with the publication of procurement documents and ending with the bid submission deadline. For a planning process, this information typically concerns the period before the publication of procurement documents.",
+ "description": "Information about, for example, the needed items and their estimated value, procurement method, award criteria, and various deadlines. This information concerns either the contracting process or the planning process. For a contracting process, this information typically concerns the period starting with contracting documents (for example, procurement documents) being available to potential suppliers and ending with the bid submission deadline. For a planning process, this information typically concerns the period before contracting documents are available to potential suppliers.",
"type": "object",
"required": [
"id"
@@ -2459,7 +2459,11 @@
"unsuccessful",
"withdrawn",
null
- ]
+ ],
+ "deprecated": {
+ "description": "Deprecated because the same information can be provided by filling in the relevant date fields.",
+ "deprecatedVersion": "1.2"
+ }
},
"statusDetails": {
"title": "Status details",
@@ -6459,14 +6463,16 @@
"enum": [
"pending",
"active",
- "complete",
"cancelled",
"unsuccessful",
- "withdrawn",
null
],
"codelist": "awardStatus.csv",
- "openCodelist": false
+ "openCodelist": false,
+ "deprecated": {
+ "description": "Deprecated because the same information can be provided by filling in the relevant date fields.",
+ "deprecatedVersion": "1.2"
+ }
},
"statusDetails": {
"title": "Status details",
@@ -9046,15 +9052,15 @@
"pending",
"active",
"terminated",
- "terminatedEarly",
- "terminatedSuccessfully",
"cancelled",
- "unsuccessful",
- "withdrawn",
null
],
"codelist": "contractStatus.csv",
- "openCodelist": false
+ "openCodelist": false,
+ "deprecated": {
+ "description": "Deprecated because the same information can be provided by filling in the relevant date fields.",
+ "deprecatedVersion": "1.2"
+ }
},
"statusDetails": {
"title": "Status details",
@@ -14411,7 +14417,7 @@
"definitions": {
"Planning": {
"title": "Planning",
- "description": "Information about, for example, needs identification, budget planning and market research. This information concerns the planning process. This information typically concerns the period before the publication of procurement documents.",
+ "description": "Information about, for example, needs identification, budget planning and market research. This information concerns the planning process. This information typically concerns the period before contracting documents (for example, procurement documents) are available to potential suppliers.",
"type": "object",
"properties": {
"id": {
@@ -15597,7 +15603,7 @@
},
"Tender": {
"title": "Tender",
- "description": "Information about, for example, the needed items and their estimated value, procurement method, award criteria, and various deadlines. This information concerns either the contracting process or the planning process. For a contracting process, this information typically concerns the period starting with the publication of procurement documents and ending with the bid submission deadline. For a planning process, this information typically concerns the period before the publication of procurement documents.",
+ "description": "Information about, for example, the needed items and their estimated value, procurement method, award criteria, and various deadlines. This information concerns either the contracting process or the planning process. For a contracting process, this information typically concerns the period starting with contracting documents (for example, procurement documents) being available to potential suppliers and ending with the bid submission deadline. For a planning process, this information typically concerns the period before contracting documents are available to potential suppliers.",
"type": "object",
"required": [
"id"
@@ -15677,7 +15683,11 @@
"unsuccessful",
"withdrawn",
null
- ]
+ ],
+ "deprecated": {
+ "description": "Deprecated because the same information can be provided by filling in the relevant date fields.",
+ "deprecatedVersion": "1.2"
+ }
},
"statusDetails": {
"title": "Status details",
@@ -19673,14 +19683,16 @@
"enum": [
"pending",
"active",
- "complete",
"cancelled",
"unsuccessful",
- "withdrawn",
null
],
"codelist": "awardStatus.csv",
- "openCodelist": false
+ "openCodelist": false,
+ "deprecated": {
+ "description": "Deprecated because the same information can be provided by filling in the relevant date fields.",
+ "deprecatedVersion": "1.2"
+ }
},
"statusDetails": {
"title": "Status details",
@@ -22254,15 +22266,15 @@
"pending",
"active",
"terminated",
- "terminatedEarly",
- "terminatedSuccessfully",
"cancelled",
- "unsuccessful",
- "withdrawn",
null
],
"codelist": "contractStatus.csv",
- "openCodelist": false
+ "openCodelist": false,
+ "deprecated": {
+ "description": "Deprecated because the same information can be provided by filling in the relevant date fields.",
+ "deprecatedVersion": "1.2"
+ }
},
"statusDetails": {
"title": "Status details",
diff --git a/schema/release-schema.json b/schema/release-schema.json
index 34edd21f1..a23360e61 100644
--- a/schema/release-schema.json
+++ b/schema/release-schema.json
@@ -607,10 +607,8 @@
"enum": [
"pending",
"active",
- "complete",
"cancelled",
"unsuccessful",
- "withdrawn",
null
],
"codelist": "awardStatus.csv",
@@ -791,11 +789,7 @@
"pending",
"active",
"terminated",
- "terminatedEarly",
- "terminatedSuccessfully",
"cancelled",
- "unsuccessful",
- "withdrawn",
null
],
"codelist": "contractStatus.csv",
diff --git a/schema/versioned-release-validation-schema.json b/schema/versioned-release-validation-schema.json
index 255829622..7b9550ef8 100644
--- a/schema/versioned-release-validation-schema.json
+++ b/schema/versioned-release-validation-schema.json
@@ -244,7 +244,11 @@
"unsuccessful",
"withdrawn",
null
- ]
+ ],
+ "deprecated": {
+ "description": "Deprecated because the same information can be provided by filling in the relevant date fields.",
+ "deprecatedVersion": "1.2"
+ }
},
"releaseTag": {
"type": "array",
@@ -683,14 +687,16 @@
"enum": [
"pending",
"active",
- "complete",
"cancelled",
"unsuccessful",
- "withdrawn",
null
],
"codelist": "awardStatus.csv",
- "openCodelist": false
+ "openCodelist": false,
+ "deprecated": {
+ "description": "Deprecated because the same information can be provided by filling in the relevant date fields.",
+ "deprecatedVersion": "1.2"
+ }
},
"releaseTag": {
"type": "array",
@@ -870,15 +876,15 @@
"pending",
"active",
"terminated",
- "terminatedEarly",
- "terminatedSuccessfully",
"cancelled",
- "unsuccessful",
- "withdrawn",
null
],
"codelist": "contractStatus.csv",
- "openCodelist": false
+ "openCodelist": false,
+ "deprecated": {
+ "description": "Deprecated because the same information can be provided by filling in the relevant date fields.",
+ "deprecatedVersion": "1.2"
+ }
},
"releaseTag": {
"type": "array",
From 5fd7ac0a4dc30535f63a80b87c77620afcb597d8 Mon Sep 17 00:00:00 2001
From: Duncan Dewhurst <duncan.dewhurst@opendataservices.coop>
Date: Fri, 13 Oct 2023 11:44:49 +1300
Subject: [PATCH 29/35] Apply suggestions from code review
Co-authored-by: James McKinney <26463+jpmckinney@users.noreply.github.com>
---
schema/codelists/contractStatus.csv | 2 +-
schema/codelists/tenderStatus.csv | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/schema/codelists/contractStatus.csv b/schema/codelists/contractStatus.csv
index 9a45758e4..895a2c317 100644
--- a/schema/codelists/contractStatus.csv
+++ b/schema/codelists/contractStatus.csv
@@ -1,5 +1,5 @@
Code,Title,Description,Deprecated,Deprecation note
-pending,Pending,"The award was made and the standstill period, if any, has ended. The contract is not yet concluded (for example, not signed by all parties).",1.2,Deprecated because the same information can be determined by the absence of a `contracts.dateSigned`.
+pending,Pending,"The award was made and the standstill period, if any, has ended. The contract is not yet concluded (for example, not signed by all parties).",1.2,Deprecated because the same information can be determined by the absence of `contracts.dateSigned`.
active,Active,"The contract was concluded (for example, signed by all parties). The contract is not yet terminated.",1.2,Deprecated because the same information can be determined by comparing `contracts.period` to `date`.
terminated,Terminated,"The contract was concluded (for example, signed), and has now come to a close. This might be due to the successful completion of the contract, or might be early termination due to some non-completion.",1.2,OCDS 1.2 replaces this code with a new field for final states.
cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the award was made and the standstill period, if any, had ended.",1.2,OCDS 1.2 replaces this code with a new field for final states.
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index 5ae9fd018..f1156a746 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -1,8 +1,8 @@
Code,Title,Description,Deprecated,Deprecation note
-planning,Planning,"A future contracting process is being considered. Early information about the process can be provided in the tender section. A process with this status might provide information on early engagement or consultation opportunities, during which the details of a subsequent tender can be shaped.",1.2,"This code has been deprecated, because it is unnecessary since contracting processes are split from planning processes (which do not have any states themselves)."
+planning,Planning,"A future contracting process is being considered. Early information about the process can be provided in the tender section. A process with this status might provide information on early engagement or consultation opportunities, during which the details of a subsequent tender can be shaped.",1.2,"Deprecated as unnecessary, since contracting processes are separate from planning processes (which do not have any states)."
planned,Planned,"The contracting process is scheduled, but contracting documents (for example, planning documents) are not yet available to potential suppliers.",1.2,Deprecated because the same information can be determined by comparing `tender/datePublished` (new in 1.2) to `date` (or its absence)
active,Active,"The contracting documents (for example, procurement documents) are available to potential suppliers, and the bid submission deadline has not yet passed.",1.2,Deprecated because the same information can be determined by comparing `tender/datePublished` (new in 1.2) and `tender/tenderPeriod/endDate` to `date`.
-complete,Complete,The bid submission deadline has passed.,1.2,Deprecated because the same information can be determined by comparing `tender/tenderPeriod/endDate` to `date`
-cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (for example, because of a change in needs, insufficient funds, or technical or procedural errors) after the contracting documents (for example, procurement documents) were available to potential supppliers, but not later than the bid submission deadline.",1.2,OCDS 1.2 replaces this code with a new field for final states.
+complete,Complete,The bid submission deadline has passed.,1.2,Deprecated because the same information can be determined by comparing `tender/tenderPeriod/endDate` to `date`.
+cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (for example, because of a change in needs, insufficient funds, or technical or procedural errors) after the contracting documents (for example, procurement documents) were available to potential suppliers, but not later than the bid submission deadline.",1.2,OCDS 1.2 replaces this code with a new field for final states.
unsuccessful,Unsuccessful,"The contracting process failed (for example, no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity) after the contracting documents (for example, procurement documents) were available to potential suppliers, but not later than the bid submission deadline.",1.2,OCDS 1.2 replaces this code with a new field for final states.
withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.,1.2,OCDS 1.2 replaces this code with a new field for final states.
From 10a4612e992dc2fe3941a515fab7e10610c9f11f Mon Sep 17 00:00:00 2001
From: Duncan Dewhurst <duncan.dewhurst@opendataservices.coop>
Date: Fri, 13 Oct 2023 12:07:27 +1300
Subject: [PATCH 30/35] Update changelog
---
docs/history/changelog.md | 12 ++++--------
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/docs/history/changelog.md b/docs/history/changelog.md
index ccd00bdf0..a860ce7a5 100644
--- a/docs/history/changelog.md
+++ b/docs/history/changelog.md
@@ -142,16 +142,10 @@ Per the [normative and non-normative content and changes policy](https://docs.go
* `releaseTag.csv`:
* [#1238](https://github.com/open-contracting/standard/pull/1238) Open the `releaseTag` codelist.
- * [#1415](https://github.com/open-contracting/standard/pull/1415) Align descriptions of 'planning', 'tender', 'award' and 'contract' with the corresponding schema fields.
+ * [#1415](https://github.com/open-contracting/standard/pull/1415), [#1509](https://github.com/open-contracting/standard/pull/1509) Align descriptions of 'planning', 'tender', 'award' and 'contract' with the corresponding schema fields.
* `tenderStatus`, `awardStatus` and `contractStatus`:
- * [#1509](https://github.com/open-contracting/standard/pull/1509) Major change of descriptions, adding and deprecating the following codes.
- * Deprecated: 'planning' in `tenderStatus`. Deprecated because it is unnecessary since contracting processes are now split from planning processes (which do not have any states themselves).
- * Deprecated: 'pending' in `awardStatus` and `contractStatus`. Deprecated because the code (which would follow 'active') does not provide any additional information compared to `awardDate` and `dateSigned` and, in the case of `contractStatus` has unclear semantics ("proposed").
- * Added: 'withdrawn' in `awardStatus` and `contractStatus`, as information can stop being published at any moment also for only individual awards / contracts.
- * Added: 'complete' in `awardStatus`, as there was no code suggesting that the award successfully happened and was done (the equivalent in `contractStatus` is 'terminated'.)
- * Added 'unsuccessful' in `contractStatus`, as a failure not caused by the buyer can happen also in the contract stage (e.g. the winning bidder(s) refuses to sign the contract).
- * [#1201](https://github.com/open-contracting/standard/pull/1201) Add 'terminatedEarly' and 'terminatedSuccessfully' to the `contractStatus` codelist, to distinguish between successful completion and early termination of the contract.
+ * [#1509](https://github.com/open-contracting/standard/pull/1509) Clarify semantics and deprecate codes.
* [#1200](https://github.com/open-contracting/standard/pull/1200) Deprecate the `submissionMethod` codelist, because its codes were either not submission methods, or not supported by use cases.
* [#1389](https://github.com/open-contracting/standard/pull/1389) Deprecate the `initiationType` codelist, because the approach to data modelling that it supports was not pursued.
@@ -203,6 +197,7 @@ Per the [normative and non-normative content and changes policy](https://docs.go
* [#1372](https://github.com/open-contracting/standard/pull/1372) `Address.countryName` in favor of the new `Address.country` field, to promote standardized country codes instead of non-standardized country names.
* [#1389](https://github.com/open-contracting/standard/pull/1389) `initiationType`, because the approach to data modelling that it supports was not pursued.
* [#1380](https://github.com/open-contracting/standard/pull/1380) `Document.language` in favor of the new `Document.languages` field, to support documents in which multiple languages are used.
+ * [#1509](https://github.com/open-contracting/standard/pull/1509) `tender.status`, `Award.status`, `Contract.status`, because the same information can be provided by filling in the relevant date fields.
* Update and clarify field descriptions:
* [#1113](https://github.com/open-contracting/standard/pull/1113) `ocid`, to recommend a hyphen after the ocid prefix.
@@ -218,6 +213,7 @@ Per the [normative and non-normative content and changes policy](https://docs.go
* [#1528](https://github.com/open-contracting/standard/pull/1528) `tender.id`, `tender.hasEnquiries`, to reduce ambiguity and use consistent wording in the description of procurement stages.
* [#1618](https://github.com/open-contracting/standard/pull/1618) `tender.enquiryPeriod`, to remove the suggestion to use `tender.submissionMethodDetails` for information about how to submit enquiries.
* [#1618](https://github.com/open-contracting/standard/pull/1618) Normalize field descriptions according to a style guide.
+ * [#1509](https://github.com/open-contracting/standard/pull/1509) `planning`, `Planning`, `tender` and `Tender` to clarify relationships with the availability of documents.
* Remove confusing terminology:
* [#1487](https://github.com/open-contracting/standard/pull/1487) `planning.budget.project`, to remove sentence about translation options.
From f6217cc57e6c6ab6121d8f681d29366e1bd86ced Mon Sep 17 00:00:00 2001
From: Duncan Dewhurst <duncan.dewhurst@opendataservices.coop>
Date: Tue, 24 Oct 2023 11:43:35 +1300
Subject: [PATCH 31/35] Update schema/codelists/tenderStatus.csv
Co-authored-by: James McKinney <26463+jpmckinney@users.noreply.github.com>
---
schema/codelists/tenderStatus.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index f1156a746..280c9adcc 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -1,6 +1,6 @@
Code,Title,Description,Deprecated,Deprecation note
planning,Planning,"A future contracting process is being considered. Early information about the process can be provided in the tender section. A process with this status might provide information on early engagement or consultation opportunities, during which the details of a subsequent tender can be shaped.",1.2,"Deprecated as unnecessary, since contracting processes are separate from planning processes (which do not have any states)."
-planned,Planned,"The contracting process is scheduled, but contracting documents (for example, planning documents) are not yet available to potential suppliers.",1.2,Deprecated because the same information can be determined by comparing `tender/datePublished` (new in 1.2) to `date` (or its absence)
+planned,Planned,"The contracting process is scheduled, but contracting documents (for example, planning documents) are not yet available to potential suppliers.",1.2,Deprecated because the same information can be determined by the absence of `tender/datePublished` (new in 1.2) or by comparing it to `date`.
active,Active,"The contracting documents (for example, procurement documents) are available to potential suppliers, and the bid submission deadline has not yet passed.",1.2,Deprecated because the same information can be determined by comparing `tender/datePublished` (new in 1.2) and `tender/tenderPeriod/endDate` to `date`.
complete,Complete,The bid submission deadline has passed.,1.2,Deprecated because the same information can be determined by comparing `tender/tenderPeriod/endDate` to `date`.
cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (for example, because of a change in needs, insufficient funds, or technical or procedural errors) after the contracting documents (for example, procurement documents) were available to potential suppliers, but not later than the bid submission deadline.",1.2,OCDS 1.2 replaces this code with a new field for final states.
From 34ee1350796350408d617c0bc89739949fd1f78e Mon Sep 17 00:00:00 2001
From: Duncan Dewhurst <duncan.dewhurst@opendataservices.coop>
Date: Tue, 24 Oct 2023 11:44:38 +1300
Subject: [PATCH 32/35] schema/codelists/tenderStatus.csv: Update description
of 'planned'
---
schema/codelists/tenderStatus.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index 280c9adcc..4945ff517 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -1,6 +1,6 @@
Code,Title,Description,Deprecated,Deprecation note
planning,Planning,"A future contracting process is being considered. Early information about the process can be provided in the tender section. A process with this status might provide information on early engagement or consultation opportunities, during which the details of a subsequent tender can be shaped.",1.2,"Deprecated as unnecessary, since contracting processes are separate from planning processes (which do not have any states)."
-planned,Planned,"The contracting process is scheduled, but contracting documents (for example, planning documents) are not yet available to potential suppliers.",1.2,Deprecated because the same information can be determined by the absence of `tender/datePublished` (new in 1.2) or by comparing it to `date`.
+planned,Planned,"The contracting process is scheduled, but contracting documents (for example, procurement documents) are not yet available to potential suppliers.",1.2,Deprecated because the same information can be determined by the absence of `tender/datePublished` (new in 1.2).
active,Active,"The contracting documents (for example, procurement documents) are available to potential suppliers, and the bid submission deadline has not yet passed.",1.2,Deprecated because the same information can be determined by comparing `tender/datePublished` (new in 1.2) and `tender/tenderPeriod/endDate` to `date`.
complete,Complete,The bid submission deadline has passed.,1.2,Deprecated because the same information can be determined by comparing `tender/tenderPeriod/endDate` to `date`.
cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (for example, because of a change in needs, insufficient funds, or technical or procedural errors) after the contracting documents (for example, procurement documents) were available to potential suppliers, but not later than the bid submission deadline.",1.2,OCDS 1.2 replaces this code with a new field for final states.
From e9a80194b721ad961389d567d027075e134786f0 Mon Sep 17 00:00:00 2001
From: Duncan Dewhurst <duncan.dewhurst@opendataservices.coop>
Date: Tue, 24 Oct 2023 11:47:30 +1300
Subject: [PATCH 33/35] schema/codelists: Use dot notation in deprecation
notices
---
schema/codelists/awardStatus.csv | 4 ++--
schema/codelists/tenderStatus.csv | 6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/schema/codelists/awardStatus.csv b/schema/codelists/awardStatus.csv
index efa14576a..485859050 100644
--- a/schema/codelists/awardStatus.csv
+++ b/schema/codelists/awardStatus.csv
@@ -1,5 +1,5 @@
Code,Title,Description,Deprecated,Deprecation note
-pending,Pending,"The award was made, but the standstill period has not yet ended.",1.2,Deprecated because the same information can be determined by comparing the sum of `awards/date` and `tender/standstillPeriod/durationInDays` (new in 1.2) to `date`.
-active,Active,"The award was made and the standstill period, if any, has ended.",1.2,Deprecated because the same information can be determined by comparing the sum of `awards/date` and `tender/standstillPeriod/durationInDays` (new in 1.2) to `date`.
+pending,Pending,"The award was made, but the standstill period has not yet ended.",1.2,Deprecated because the same information can be determined by comparing the sum of `awards.date` and `tender.standstillPeriod.durationInDays` (new in 1.2) to `date`.
+active,Active,"The award was made and the standstill period, if any, has ended.",1.2,Deprecated because the same information can be determined by comparing the sum of `awards.date` and `tender.standstillPeriod.durationInDays` (new in 1.2) to `date`.
cancelled,Cancelled,"The award was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",1.2,OCDS 1.2 replaces this code with a new field for final states.
unsuccessful,Unsuccessful,"The award failed (e.g. a review body cancelled the process during the standstill period) after the bid submission deadline, but before the award was made or before the standstill period, if any, had ended.",1.2,OCDS 1.2 replaces this code with a new field for final states.
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index 4945ff517..37d3641e7 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -1,8 +1,8 @@
Code,Title,Description,Deprecated,Deprecation note
planning,Planning,"A future contracting process is being considered. Early information about the process can be provided in the tender section. A process with this status might provide information on early engagement or consultation opportunities, during which the details of a subsequent tender can be shaped.",1.2,"Deprecated as unnecessary, since contracting processes are separate from planning processes (which do not have any states)."
-planned,Planned,"The contracting process is scheduled, but contracting documents (for example, procurement documents) are not yet available to potential suppliers.",1.2,Deprecated because the same information can be determined by the absence of `tender/datePublished` (new in 1.2).
-active,Active,"The contracting documents (for example, procurement documents) are available to potential suppliers, and the bid submission deadline has not yet passed.",1.2,Deprecated because the same information can be determined by comparing `tender/datePublished` (new in 1.2) and `tender/tenderPeriod/endDate` to `date`.
-complete,Complete,The bid submission deadline has passed.,1.2,Deprecated because the same information can be determined by comparing `tender/tenderPeriod/endDate` to `date`.
+planned,Planned,"The contracting process is scheduled, but contracting documents (for example, procurement documents) are not yet available to potential suppliers.",1.2,Deprecated because the same information can be determined by the absence of `tender.datePublished` (new in 1.2).
+active,Active,"The contracting documents (for example, procurement documents) are available to potential suppliers, and the bid submission deadline has not yet passed.",1.2,Deprecated because the same information can be determined by comparing `tender.datePublished` (new in 1.2) and `tender/tenderPeriod/endDate` to `date`.
+complete,Complete,The bid submission deadline has passed.,1.2,Deprecated because the same information can be determined by comparing `tender.tenderPeriod.endDate` to `date`.
cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (for example, because of a change in needs, insufficient funds, or technical or procedural errors) after the contracting documents (for example, procurement documents) were available to potential suppliers, but not later than the bid submission deadline.",1.2,OCDS 1.2 replaces this code with a new field for final states.
unsuccessful,Unsuccessful,"The contracting process failed (for example, no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity) after the contracting documents (for example, procurement documents) were available to potential suppliers, but not later than the bid submission deadline.",1.2,OCDS 1.2 replaces this code with a new field for final states.
withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.,1.2,OCDS 1.2 replaces this code with a new field for final states.
From e9dfad73aaf407b54b49b8fd014f8bd170b648cc Mon Sep 17 00:00:00 2001
From: Duncan Dewhurst <duncan.dewhurst@opendataservices.coop>
Date: Tue, 24 Oct 2023 13:23:33 +1300
Subject: [PATCH 34/35] Apply suggestions from code review
Co-authored-by: James McKinney <26463+jpmckinney@users.noreply.github.com>
---
schema/codelists/contractStatus.csv | 2 +-
schema/codelists/tenderStatus.csv | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/schema/codelists/contractStatus.csv b/schema/codelists/contractStatus.csv
index 895a2c317..3bf735e08 100644
--- a/schema/codelists/contractStatus.csv
+++ b/schema/codelists/contractStatus.csv
@@ -1,5 +1,5 @@
Code,Title,Description,Deprecated,Deprecation note
pending,Pending,"The award was made and the standstill period, if any, has ended. The contract is not yet concluded (for example, not signed by all parties).",1.2,Deprecated because the same information can be determined by the absence of `contracts.dateSigned`.
-active,Active,"The contract was concluded (for example, signed by all parties). The contract is not yet terminated.",1.2,Deprecated because the same information can be determined by comparing `contracts.period` to `date`.
+active,Active,"The contract was concluded (for example, signed by all parties). The contract is not yet terminated.",1.2,Deprecated because the same information can be determined by the presence of `contracts.dateSigned` and by comparing `contracts.period` to `date`.
terminated,Terminated,"The contract was concluded (for example, signed), and has now come to a close. This might be due to the successful completion of the contract, or might be early termination due to some non-completion.",1.2,OCDS 1.2 replaces this code with a new field for final states.
cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (e.g. because of a change in needs, insufficient funds, or technical or procedural errors) after the award was made and the standstill period, if any, had ended.",1.2,OCDS 1.2 replaces this code with a new field for final states.
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index 37d3641e7..85e4e936a 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -1,8 +1,8 @@
Code,Title,Description,Deprecated,Deprecation note
planning,Planning,"A future contracting process is being considered. Early information about the process can be provided in the tender section. A process with this status might provide information on early engagement or consultation opportunities, during which the details of a subsequent tender can be shaped.",1.2,"Deprecated as unnecessary, since contracting processes are separate from planning processes (which do not have any states)."
planned,Planned,"The contracting process is scheduled, but contracting documents (for example, procurement documents) are not yet available to potential suppliers.",1.2,Deprecated because the same information can be determined by the absence of `tender.datePublished` (new in 1.2).
-active,Active,"The contracting documents (for example, procurement documents) are available to potential suppliers, and the bid submission deadline has not yet passed.",1.2,Deprecated because the same information can be determined by comparing `tender.datePublished` (new in 1.2) and `tender/tenderPeriod/endDate` to `date`.
-complete,Complete,The bid submission deadline has passed.,1.2,Deprecated because the same information can be determined by comparing `tender.tenderPeriod.endDate` to `date`.
+active,Active,"The contracting documents (for example, procurement documents) are available to potential suppliers, and the bid submission deadline has not yet passed.",1.2,Deprecated because the same information can be determined by the presence of `tender.datePublished` (new in 1.2) and by comparing `tender/tenderPeriod/endDate` to `date`.
+complete,Complete,The bid submission deadline has passed.,1.2,Deprecated because the same information can be determined by the presence of `tender.datePublished` (new in 1.2) and by comparing `tender.tenderPeriod.endDate` to `date`.
cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (for example, because of a change in needs, insufficient funds, or technical or procedural errors) after the contracting documents (for example, procurement documents) were available to potential suppliers, but not later than the bid submission deadline.",1.2,OCDS 1.2 replaces this code with a new field for final states.
unsuccessful,Unsuccessful,"The contracting process failed (for example, no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity) after the contracting documents (for example, procurement documents) were available to potential suppliers, but not later than the bid submission deadline.",1.2,OCDS 1.2 replaces this code with a new field for final states.
-withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.,1.2,OCDS 1.2 replaces this code with a new field for final states.
+withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.,1.2,This code is deprecated, because it describes the status of the publication, not of the contracting process.
From 7747008fc8a880f03f05a134cad61d27c5ada715 Mon Sep 17 00:00:00 2001
From: Duncan Dewhurst <duncan.dewhurst@opendataservices.coop>
Date: Tue, 24 Oct 2023 13:28:07 +1300
Subject: [PATCH 35/35] schema/codelists/tenderStatus.csv: Quote deprecation
note for withdrawn
---
schema/codelists/tenderStatus.csv | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schema/codelists/tenderStatus.csv b/schema/codelists/tenderStatus.csv
index 85e4e936a..fcab442a9 100644
--- a/schema/codelists/tenderStatus.csv
+++ b/schema/codelists/tenderStatus.csv
@@ -5,4 +5,4 @@ active,Active,"The contracting documents (for example, procurement documents) ar
complete,Complete,The bid submission deadline has passed.,1.2,Deprecated because the same information can be determined by the presence of `tender.datePublished` (new in 1.2) and by comparing `tender.tenderPeriod.endDate` to `date`.
cancelled,Cancelled,"The contracting process was cancelled by the buyer or the procuring entity (for example, because of a change in needs, insufficient funds, or technical or procedural errors) after the contracting documents (for example, procurement documents) were available to potential suppliers, but not later than the bid submission deadline.",1.2,OCDS 1.2 replaces this code with a new field for final states.
unsuccessful,Unsuccessful,"The contracting process failed (for example, no bids were received, all bids were withdrawn by the bidders, all bids were rejected by the buyer or the procuring entity) after the contracting documents (for example, procurement documents) were available to potential suppliers, but not later than the bid submission deadline.",1.2,OCDS 1.2 replaces this code with a new field for final states.
-withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.,1.2,This code is deprecated, because it describes the status of the publication, not of the contracting process.
+withdrawn,Withdrawn,No further information on the contracting process is available under this ocid.,1.2,"This code is deprecated, because it describes the status of the publication, not of the contracting process."