From 5d29c84fdd37d8ff0d476cf2f6cca771302a5b2f Mon Sep 17 00:00:00 2001 From: JachymHercher Date: Sun, 24 Jan 2021 16:21:10 +0100 Subject: [PATCH 01/12] Funder deprecated (also removed it from an example that doesn't seem to need it to avoid confusion) --- docs/examples/organizational-units/moldova-tender.json | 1 - schema/codelists/partyRole.csv | 4 ++-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/examples/organizational-units/moldova-tender.json b/docs/examples/organizational-units/moldova-tender.json index b0ffa349a..8df1f270f 100644 --- a/docs/examples/organizational-units/moldova-tender.json +++ b/docs/examples/organizational-units/moldova-tender.json @@ -98,7 +98,6 @@ "roles": [ "payer", "procuringEntity", - "funder", "buyer" ], "details": { diff --git a/schema/codelists/partyRole.csv b/schema/codelists/partyRole.csv index 03ec37fba..e945a1115 100644 --- a/schema/codelists/partyRole.csv +++ b/schema/codelists/partyRole.csv @@ -1,9 +1,9 @@ -Code,Title,Description +Code,Title,Description,Deprecated buyer,Buyer,"A buyer is an entity whose budget will be used to pay for goods, works or services related to a contract." procuringEntity,Procuring entity,"The entity managing the procurement. This can be different from the buyer who pays for, or uses, the items being procured." supplier,Supplier,"An entity awarded or contracted to provide goods, works or services." tenderer,Tenderer,All entities who submit a tender. -funder,Funder,The funder is an entity providing money or finance for this contracting process. +funder,Funder,The funder is an organisation providing money or finance for this contracting process.,1.2 enquirer,Enquirer,A party who has made an enquiry during the enquiry phase of a contracting process. payer,Payer,A party making a payment from a transaction. payee,Payee,A party in receipt of a payment from a transaction. From 1c54a3bcbedd8d5beae4c6eda2f03b93ab757ccc Mon Sep 17 00:00:00 2001 From: JachymHercher Date: Sun, 24 Jan 2021 16:46:05 +0100 Subject: [PATCH 02/12] buyer new description --- .../map/awards_contracts_buyers_suppliers.md | 16 +--------------- schema/codelists/partyRole.csv | 2 +- schema/release-schema.json | 2 +- 3 files changed, 3 insertions(+), 17 deletions(-) diff --git a/docs/guidance/map/awards_contracts_buyers_suppliers.md b/docs/guidance/map/awards_contracts_buyers_suppliers.md index 0d96d7a74..4a6c8a9b8 100644 --- a/docs/guidance/map/awards_contracts_buyers_suppliers.md +++ b/docs/guidance/map/awards_contracts_buyers_suppliers.md @@ -50,21 +50,7 @@ In OCDS, the `Contract` object is intended to communicate a legally binding agre OCDS defines the buyer as: -> *an entity whose budget will be used to pay for goods, works or services related to a contract. This may be different from the procuring entity who may be specified in the tender data.* - -```eval_rst -.. admonition:: Note - :class: note - - .. markdown:: - - Elsewhere in the OCDS schema the buyer is described as: - - > *The entity managing the procurement. This may be different from the buyer who pays for, **or uses**, the items being procured.* - - There is a proposal to align this description with the above definition. - -``` +> *The organisation aiming to conclude a contract with a supplier or to use the goods, works or services resulting from the contract.* ### Suppliers diff --git a/schema/codelists/partyRole.csv b/schema/codelists/partyRole.csv index e945a1115..83da17ec1 100644 --- a/schema/codelists/partyRole.csv +++ b/schema/codelists/partyRole.csv @@ -1,5 +1,5 @@ Code,Title,Description,Deprecated -buyer,Buyer,"A buyer is an entity whose budget will be used to pay for goods, works or services related to a contract." +buyer,Buyer,"The organisation aiming to conclude a contract with a supplier or to use the goods, works or services resulting from the contract." procuringEntity,Procuring entity,"The entity managing the procurement. This can be different from the buyer who pays for, or uses, the items being procured." supplier,Supplier,"An entity awarded or contracted to provide goods, works or services." tenderer,Tenderer,All entities who submit a tender. diff --git a/schema/release-schema.json b/schema/release-schema.json index b9d7984fd..613ebe19b 100644 --- a/schema/release-schema.json +++ b/schema/release-schema.json @@ -76,7 +76,7 @@ }, "buyer": { "title": "Buyer", - "description": "A buyer is an entity whose budget will be used to pay for goods, works or services related to a contract. This may be different from the procuring entity who may be specified in the tender data.", + "description": "The organisation aiming to conclude a contract with a supplier or to use the goods, works or services resulting from the contract.", "$ref": "#/definitions/OrganizationReference" }, "planning": { From 7ff12fa117945a888e361dc5d48995afe0311d46 Mon Sep 17 00:00:00 2001 From: JachymHercher Date: Sun, 24 Jan 2021 16:58:03 +0100 Subject: [PATCH 03/12] Updated changelog --- docs/history/changelog.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/history/changelog.md b/docs/history/changelog.md index a96ed19ef..987567c7b 100644 --- a/docs/history/changelog.md +++ b/docs/history/changelog.md @@ -7,7 +7,6 @@ These release notes describe what's new in each version. OCDS adheres to [Semant Per the [normative and non-normative content and changes policy](https://docs.google.com/document/d/1xjlAneqgewZvHh6_hwuQ98hbjxRcA2IUqOTJiNGcOf8/edit), iterative improvements to non-normative content can be made outside the release cycle. ### Documentation - * Getting Started section: * [#980](https://github.com/open-contracting/standard/pull/980) Remove references to ☆ levels. * [#1017](https://github.com/open-contracting/standard/pull/1017) Add link to bulk downloads in Guidance section. @@ -34,6 +33,7 @@ Per the [normative and non-normative content and changes policy](https://docs.go ### Schema +* [#1182](https://github.com/open-contracting/standard/pull/1182) Update the description of 'Buyer' and deprecate 'Funder' * [#1086](https://github.com/open-contracting/standard/pull/1086) Recommend the use of strings rather than integers for identifiers. * [#1094](https://github.com/open-contracting/standard/pull/1094) Clarify the uniqueness of `Organization.id` * [#1113](https://github.com/open-contracting/standard/pull/1113) Add recommendation to put hyphen after the ocid prefix @@ -47,7 +47,7 @@ Per the [normative and non-normative content and changes policy](https://docs.go * [#1067](https://github.com/open-contracting/standard/pull/1067) Clarify the description of `Publisher.name` to indicate that it is the organization or department responsible for publishing the OCDS version of the data. ### Documentation - +* [#1182](https://github.com/open-contracting/standard/pull/1182) Update the description of 'Buyer' in the [guidance](https://standard.open-contracting.org/latest/en/guidance/map/awards_contracts_buyers_suppliers/) * [#1094](https://github.com/open-contracting/standard/pull/1094) Add guidance on populating `Organization.id` for parties without an organization identifier * [#1115](https://github.com/open-contracting/standard/pull/1115) Add guidance on when having multiple suppliers per award * [#1161](https://github.com/open-contracting/standard/pull/1161) Change recommendation for unknown time component From 1d00c19dd91dfdf4cae112dad0591a2ee47bec19 Mon Sep 17 00:00:00 2001 From: JachymHercher Date: Sun, 31 Jan 2021 20:44:01 +0100 Subject: [PATCH 04/12] Funder - corrected table formatting --- schema/codelists/partyRole.csv | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/schema/codelists/partyRole.csv b/schema/codelists/partyRole.csv index 83da17ec1..562822dbe 100644 --- a/schema/codelists/partyRole.csv +++ b/schema/codelists/partyRole.csv @@ -1,11 +1,11 @@ Code,Title,Description,Deprecated -buyer,Buyer,"The organisation aiming to conclude a contract with a supplier or to use the goods, works or services resulting from the contract." -procuringEntity,Procuring entity,"The entity managing the procurement. This can be different from the buyer who pays for, or uses, the items being procured." -supplier,Supplier,"An entity awarded or contracted to provide goods, works or services." -tenderer,Tenderer,All entities who submit a tender. -funder,Funder,The funder is an organisation providing money or finance for this contracting process.,1.2 -enquirer,Enquirer,A party who has made an enquiry during the enquiry phase of a contracting process. -payer,Payer,A party making a payment from a transaction. -payee,Payee,A party in receipt of a payment from a transaction. -reviewBody,Review body,A party responsible for the review of this procurement process. This party often has a role in any challenges made to the contract award. -interestedParty,Interested party,"A party that has expressed an interest in the contracting process: for example, by purchasing tender documents or submitting clarification questions." +buyer,Buyer,"The organisation aiming to conclude a contract with a supplier or to use the goods, works or services resulting from the contract.", +procuringEntity,Procuring entity,"The entity managing the procurement. This can be different from the buyer who pays for, or uses, the items being procured.", +supplier,Supplier,"An entity awarded or contracted to provide goods, works or services.", +tenderer,Tenderer,All entities who submit a tender., +funder,Funder,The funder is an organization providing money or finance for this contracting process.,1.2 +enquirer,Enquirer,A party who has made an enquiry during the enquiry phase of a contracting process., +payer,Payer,A party making a payment from a transaction., +payee,Payee,A party in receipt of a payment from a transaction., +reviewBody,Review body,A party responsible for the review of this procurement process. This party often has a role in any challenges made to the contract award., +interestedParty,Interested party,"A party that has expressed an interest in the contracting process: for example, by purchasing tender documents or submitting clarification questions.", From 8a19c14c1e47626912e01663ee715d3f14efc622 Mon Sep 17 00:00:00 2001 From: JachymHercher Date: Sun, 31 Jan 2021 20:53:41 +0100 Subject: [PATCH 05/12] US English --- docs/guidance/map/awards_contracts_buyers_suppliers.md | 2 +- schema/codelists/partyRole.csv | 2 +- schema/release-schema.json | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/guidance/map/awards_contracts_buyers_suppliers.md b/docs/guidance/map/awards_contracts_buyers_suppliers.md index 4a6c8a9b8..a613bdb57 100644 --- a/docs/guidance/map/awards_contracts_buyers_suppliers.md +++ b/docs/guidance/map/awards_contracts_buyers_suppliers.md @@ -50,7 +50,7 @@ In OCDS, the `Contract` object is intended to communicate a legally binding agre OCDS defines the buyer as: -> *The organisation aiming to conclude a contract with a supplier or to use the goods, works or services resulting from the contract.* +> *The organization aiming to conclude a contract with a supplier or to use the goods, works or services resulting from the contract.* ### Suppliers diff --git a/schema/codelists/partyRole.csv b/schema/codelists/partyRole.csv index 562822dbe..2efd16400 100644 --- a/schema/codelists/partyRole.csv +++ b/schema/codelists/partyRole.csv @@ -1,5 +1,5 @@ Code,Title,Description,Deprecated -buyer,Buyer,"The organisation aiming to conclude a contract with a supplier or to use the goods, works or services resulting from the contract.", +buyer,Buyer,"The organization aiming to conclude a contract with a supplier or to use the goods, works or services resulting from the contract.", procuringEntity,Procuring entity,"The entity managing the procurement. This can be different from the buyer who pays for, or uses, the items being procured.", supplier,Supplier,"An entity awarded or contracted to provide goods, works or services.", tenderer,Tenderer,All entities who submit a tender., diff --git a/schema/release-schema.json b/schema/release-schema.json index 613ebe19b..8ebada82b 100644 --- a/schema/release-schema.json +++ b/schema/release-schema.json @@ -76,7 +76,7 @@ }, "buyer": { "title": "Buyer", - "description": "The organisation aiming to conclude a contract with a supplier or to use the goods, works or services resulting from the contract.", + "description": "The organization aiming to conclude a contract with a supplier or to use the goods, works or services resulting from the contract.", "$ref": "#/definitions/OrganizationReference" }, "planning": { From 3353e306648e665daa120d9a4d1cc3a222207d91 Mon Sep 17 00:00:00 2001 From: JachymHercher Date: Sun, 31 Jan 2021 21:16:19 +0100 Subject: [PATCH 06/12] Added contractImplementationManager --- schema/codelists/partyRole.csv | 1 + 1 file changed, 1 insertion(+) diff --git a/schema/codelists/partyRole.csv b/schema/codelists/partyRole.csv index 2efd16400..5fb476135 100644 --- a/schema/codelists/partyRole.csv +++ b/schema/codelists/partyRole.csv @@ -9,3 +9,4 @@ payer,Payer,A party making a payment from a transaction., payee,Payee,A party in receipt of a payment from a transaction., reviewBody,Review body,A party responsible for the review of this procurement process. This party often has a role in any challenges made to the contract award., interestedParty,Interested party,"A party that has expressed an interest in the contracting process: for example, by purchasing tender documents or submitting clarification questions.", +contractImplementationManager,"The organization responsible for managing the implementation of the contract on behalf of the buyer. (This may be different from the procuring entity that manages the contracting process.)", From 7ad5501cf213514ab02273db677829d5fcecccc9 Mon Sep 17 00:00:00 2001 From: JachymHercher Date: Sun, 31 Jan 2021 21:19:05 +0100 Subject: [PATCH 07/12] Updated changelog --- docs/history/changelog.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/history/changelog.md b/docs/history/changelog.md index 987567c7b..9fb5426b6 100644 --- a/docs/history/changelog.md +++ b/docs/history/changelog.md @@ -32,7 +32,7 @@ Per the [normative and non-normative content and changes policy](https://docs.go ## [1.2] - YYYY-MM-DD ### Schema - +* [#1187](https://github.com/open-contracting/standard/pull/1187) partyRole: added contractImplementationManager * [#1182](https://github.com/open-contracting/standard/pull/1182) Update the description of 'Buyer' and deprecate 'Funder' * [#1086](https://github.com/open-contracting/standard/pull/1086) Recommend the use of strings rather than integers for identifiers. * [#1094](https://github.com/open-contracting/standard/pull/1094) Clarify the uniqueness of `Organization.id` From 79b9f770983a6cb328576c9476dab43fe2df7848 Mon Sep 17 00:00:00 2001 From: JachymHercher Date: Sun, 31 Jan 2021 21:21:25 +0100 Subject: [PATCH 08/12] Update changelog --- docs/history/changelog.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/history/changelog.md b/docs/history/changelog.md index 9fb5426b6..59d32e8a5 100644 --- a/docs/history/changelog.md +++ b/docs/history/changelog.md @@ -32,7 +32,7 @@ Per the [normative and non-normative content and changes policy](https://docs.go ## [1.2] - YYYY-MM-DD ### Schema -* [#1187](https://github.com/open-contracting/standard/pull/1187) partyRole: added contractImplementationManager +* [#1187](https://github.com/open-contracting/standard/pull/1187) partyRole: add contractImplementationManager * [#1182](https://github.com/open-contracting/standard/pull/1182) Update the description of 'Buyer' and deprecate 'Funder' * [#1086](https://github.com/open-contracting/standard/pull/1086) Recommend the use of strings rather than integers for identifiers. * [#1094](https://github.com/open-contracting/standard/pull/1094) Clarify the uniqueness of `Organization.id` From d7b76257ed4a4be9e22f37a624473747e418c767 Mon Sep 17 00:00:00 2001 From: JachymHercher Date: Sun, 31 Jan 2021 21:24:28 +0100 Subject: [PATCH 09/12] Table formatting --- schema/codelists/partyRole.csv | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/schema/codelists/partyRole.csv b/schema/codelists/partyRole.csv index 5fb476135..fd538f54b 100644 --- a/schema/codelists/partyRole.csv +++ b/schema/codelists/partyRole.csv @@ -9,4 +9,4 @@ payer,Payer,A party making a payment from a transaction., payee,Payee,A party in receipt of a payment from a transaction., reviewBody,Review body,A party responsible for the review of this procurement process. This party often has a role in any challenges made to the contract award., interestedParty,Interested party,"A party that has expressed an interest in the contracting process: for example, by purchasing tender documents or submitting clarification questions.", -contractImplementationManager,"The organization responsible for managing the implementation of the contract on behalf of the buyer. (This may be different from the procuring entity that manages the contracting process.)", +contractImplementationManager, Contract implementation manager, The organization responsible for managing the implementation of the contract on behalf of the buyer. (This may be different from the procuring entity that manages the contracting process.), From edae0470ed9c8d1e6cb689dd62149bdef240efc0 Mon Sep 17 00:00:00 2001 From: JachymHercher Date: Sun, 31 Jan 2021 21:45:45 +0100 Subject: [PATCH 10/12] table formatting --- schema/codelists/partyRole.csv | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/schema/codelists/partyRole.csv b/schema/codelists/partyRole.csv index fd538f54b..bb19b6752 100644 --- a/schema/codelists/partyRole.csv +++ b/schema/codelists/partyRole.csv @@ -9,4 +9,4 @@ payer,Payer,A party making a payment from a transaction., payee,Payee,A party in receipt of a payment from a transaction., reviewBody,Review body,A party responsible for the review of this procurement process. This party often has a role in any challenges made to the contract award., interestedParty,Interested party,"A party that has expressed an interest in the contracting process: for example, by purchasing tender documents or submitting clarification questions.", -contractImplementationManager, Contract implementation manager, The organization responsible for managing the implementation of the contract on behalf of the buyer. (This may be different from the procuring entity that manages the contracting process.), +contractImplementationManager,Contract implementation manager,The organization responsible for managing the implementation of the contract on behalf of the buyer. (This may be different from the procuring entity that manages the contracting process.), From af308a258e993e03416fded5d95ac7c1c57a5804 Mon Sep 17 00:00:00 2001 From: James McKinney <26463+jpmckinney@users.noreply.github.com> Date: Wed, 17 Feb 2021 14:12:11 -0500 Subject: [PATCH 11/12] partyRole: Fix missing trailing comma --- schema/codelists/partyRole.csv | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/schema/codelists/partyRole.csv b/schema/codelists/partyRole.csv index 6634a5cf7..b182fab5e 100644 --- a/schema/codelists/partyRole.csv +++ b/schema/codelists/partyRole.csv @@ -1,6 +1,6 @@ Code,Title,Description,Deprecated buyer,Buyer,"The organization aiming to conclude a contract with a supplier or to use the goods, works or services resulting from the contract.", -procuringEntity,Procuring entity,"The organization managing the contracting process. If an organization is both a buyer and a procuring entity (as can be the case in simple contracting processes), its roles should include 'buyer', but not 'procuringEntity'." +procuringEntity,Procuring entity,"The organization managing the contracting process. If an organization is both a buyer and a procuring entity (as can be the case in simple contracting processes), its roles should include 'buyer', but not 'procuringEntity'.", supplier,Supplier,"An entity awarded or contracted to provide goods, works or services.", tenderer,Tenderer,All entities who submit a tender., funder,Funder,The funder is an organization providing money or finance for this contracting process.,1.2 From 8c45403cbe38c189edc6a4ced5533e50c86d1c68 Mon Sep 17 00:00:00 2001 From: James McKinney <26463+jpmckinney@users.noreply.github.com> Date: Wed, 17 Feb 2021 14:24:37 -0500 Subject: [PATCH 12/12] changelog: Add structure and update changelog entries for #1182 --- docs/history/changelog.md | 32 +++++++++++++++++++------------- 1 file changed, 19 insertions(+), 13 deletions(-) diff --git a/docs/history/changelog.md b/docs/history/changelog.md index c5c35902f..2ae8ccc93 100644 --- a/docs/history/changelog.md +++ b/docs/history/changelog.md @@ -7,6 +7,7 @@ These release notes describe what's new in each version. OCDS adheres to [Semant Per the [normative and non-normative content and changes policy](https://docs.google.com/document/d/1xjlAneqgewZvHh6_hwuQ98hbjxRcA2IUqOTJiNGcOf8/edit), iterative improvements to non-normative content can be made outside the release cycle. ### Documentation + * Getting Started section: * [#980](https://github.com/open-contracting/standard/pull/980) Remove references to ☆ levels. * [#1017](https://github.com/open-contracting/standard/pull/1017) Add link to bulk downloads in Guidance section. @@ -36,7 +37,9 @@ Per the [normative and non-normative content and changes policy](https://docs.go * [#1186](https://github.com/open-contracting/standard/pull/1186) Deprecate contractSchedule and edit contractAnnexe in the documentType codelist. * `partyRole.csv`: - * [#1163](https://github.com/open-contracting/standard/pull/1163) Improve the description of `procuringEntity` + * [#1163](https://github.com/open-contracting/standard/pull/1163) Improve the description of 'procuringEntity' + * [#1182](https://github.com/open-contracting/standard/pull/1182) Update the description of 'buyer' + * [#1182](https://github.com/open-contracting/standard/pull/1182) Deprecate 'funder' * [#1200](https://github.com/open-contracting/standard/pull/1200) Deprecate all the codes of the `submissionMethod` codelist, because they were either not submission methods, or not supported by use cases. * [#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. * [#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. @@ -44,25 +47,28 @@ Per the [normative and non-normative content and changes policy](https://docs.go ### Schema -* [#1182](https://github.com/open-contracting/standard/pull/1182) Update the description of 'Buyer' and deprecate 'Funder' * [#1086](https://github.com/open-contracting/standard/pull/1086) Recommend the use of strings rather than integers for identifiers. -* [#1094](https://github.com/open-contracting/standard/pull/1094) Clarify the uniqueness of `Organization.id` -* [#1113](https://github.com/open-contracting/standard/pull/1113) Add recommendation to put hyphen after the ocid prefix -* [#1109](https://github.com/open-contracting/standard/pull/1109) Remove "selection criteria" from the description of `Tender.awardCriteriaDetails`. +* [#1115](https://github.com/open-contracting/standard/pull/1115) Clarify when to have multiple suppliers per award +* [#1200](https://github.com/open-contracting/standard/pull/1200) Deprecate the `tender.submissionMethod` field, because all codes from the `submissionMethod` codelist are deprecated. +* Add new fields to the release schema: + * [#1125](https://github.com/open-contracting/standard/pull/1125) `weight` to `Item.unit` + * [#1165](https://github.com/open-contracting/standard/pull/1165) `statusDetails` to `Tender`, `Award` and `Contract` +* Update and improve the clarity of field descriptions in the release schema: + * [#1113](https://github.com/open-contracting/standard/pull/1113) `ocid`, to recommend a hyphen after the ocid prefix. + * [#1094](https://github.com/open-contracting/standard/pull/1094) `Organization.id`, to clarify its uniqueness. + * [#1182](https://github.com/open-contracting/standard/pull/1182) `buyer` + * [#1163](https://github.com/open-contracting/standard/pull/1163) `tender.procuringEntity` + * [#1109](https://github.com/open-contracting/standard/pull/1109) `tender.awardCriteriaDetails`, to remove "selection criteria". + * [#1167](https://github.com/open-contracting/standard/pull/1167) `Budget`,` Budget.id`, `Budget.description`, `Budget.amount` * [#1112](https://github.com/open-contracting/standard/pull/1112) Strengthen normative statements in the descriptions of the following fields: * `Organization.id`: "This field need only be unique within the scope of the contracting process, but **should** be built with the following structure {identifier.scheme}-{identifier.id}(-{department-identifier}) where an organization identifier is available" ("may" replaced with "should") * `Period.durationInDays`: "If a startDate and endDate are set, this field, if used, **must** be equal to the difference between startDate and endDate. Otherwise, if a startDate and maxExtentDate are set, this field, if used, **must** be equal to the difference between startDate and maxExtentDate." ("should" replaced with "must") * `Contract.items`: "If the items contracted are identical to the items awarded, this field **should** be omitted." (rephrased) -* [#1125](https://github.com/open-contracting/standard/pull/1125) Add `weight` to `Item.unit` -* [#1115](https://github.com/open-contracting/standard/pull/1115) Clarify when to have multiple suppliers per award -* [#1067](https://github.com/open-contracting/standard/pull/1067) Clarify the description of `Publisher.name` to indicate that it is the organization or department responsible for publishing the OCDS version of the data. -* [#1200](https://github.com/open-contracting/standard/pull/1200) Deprecate the `tender.submissionMethod` field, because all codes from the `submissionMethod` codelist are deprecated. -* [#1163](https://github.com/open-contracting/standard/pull/1163) Improve the description of `tender.procuringEntity` -* [#1165](https://github.com/open-contracting/standard/pull/1165) Add `statusDetails` to Tender, Award, Contract -* [#1167](https://github.com/open-contracting/standard/pull/1167) Improve the description of `Budget`,` Budget.id`, `Budget.description`, `Budget.amount` +* Improve the clarity of field descriptions in the release package schema and record package schema: + * [#1067](https://github.com/open-contracting/standard/pull/1067) `Publisher.name`, to indicate that it is the organization or department responsible for publishing the OCDS version of the data. ### Documentation -* [#1182](https://github.com/open-contracting/standard/pull/1182) Update the description of 'Buyer' in the [guidance](https://standard.open-contracting.org/latest/en/guidance/map/awards_contracts_buyers_suppliers/) + * [#1094](https://github.com/open-contracting/standard/pull/1094) Add guidance on populating `Organization.id` for parties without an organization identifier * [#1115](https://github.com/open-contracting/standard/pull/1115) Add guidance on when having multiple suppliers per award * [#1161](https://github.com/open-contracting/standard/pull/1161) Change recommendation for unknown time component