Deprecate 'funder' and update buyer description in partyRole

docs/examples/organizational-units/moldova-tender.json

@@ -98,7 +98,6 @@
  "roles": [
  "payer",
  "procuringEntity",
- "funder",
  "buyer"
  ],
  "details": {

docs/guidance/map/awards_contracts_buyers_suppliers.md

@@ -54,20 +54,6 @@ OCDS defines the buyer as:
 .. field-description:: ../../../build/current_lang/release-schema.json /properties/buyer
 ```
 
-```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.
-
-```
-
 ### Suppliers
 
 OCDS defines a supplier as:

docs/history/changelog.md

@@ -37,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.
@@ -46,20 +48,24 @@ Per the [normative and non-normative content and changes policy](https://docs.go
 ### Schema
 
 * [#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
 

schema/codelists/partyRole.csv

@@ -1,11 +1,11 @@
-Code,Title,Description
-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 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 entity providing money or finance for this contracting process.
-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."
+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'.",
+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.",

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 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": {