Merge pull request #1731 from open-contracting/1385-fix

jpmckinney · web-flow · commit 2b034a3de47d · 2025-01-24T15:49:13.000-05:00
releaseTag: Fix wording, since 'tender' must not be used for planning processes
diff --git a/docs/guidance/build.md b/docs/guidance/build.md
@@ -111,7 +111,7 @@ Contact the [Data Support Team](../support/index) for guidance on customizing a
 **Resource:** To learn about how to create a spreadsheet input template for OCDS, check out our blog series on prototyping OCDS data using spreadsheets ([Part 1](https://www.open-contracting.org/2020/04/24/prototyping-ocds-data-using-spreadsheets/), [Part 2](https://www.open-contracting.org/2020/05/11/prototyping-ocds-data-using-spreadsheets-part-ii/), [Part 3](https://www.open-contracting.org/2020/05/28/prototyping-ocds-data-using-spreadsheets-part-iii/)).
 
 ```{note}
-Re-using tools isn't always easy. [Tool Reuse in Open Contracting: A Primer](https://www.open-contracting.org/resources/tool-re-use-in-open-contracting-a-primer/) is a step-by-step guide to help you determine what you need, evaluate which tool is the right fit, and evaluate whether the right conditions are in place for successful reuse of a tool.
+Reusing tools isn't always easy. [Tool Reuse in Open Contracting: A Primer](https://www.open-contracting.org/resources/tool-re-use-in-open-contracting-a-primer/) is a step-by-step guide to help you determine what you need, evaluate which tool is the right fit, and evaluate whether the right conditions are in place for successful reuse of a tool.
 ```
 
 ## Build your extensions
diff --git a/docs/guidance/map/organization_classifications.md b/docs/guidance/map/organization_classifications.md
@@ -39,7 +39,7 @@ This example previously used the [party scale extension](https://extensions.open
 
 ### Option 2: Organization classification extension
 
-In the examples below, two different publishers have disclosed information about organizations involved in their contracting processes. An organization classification needs to consist of at least two parts: an identifier for the list (scheme) from which the classification is taken, and an identifier for the category from that list being applied. It is useful to also publish a text label and/or URI that users can draw on to interpret the classification. In the first example below, the publisher re-uses an existing `classification.scheme`. In the second example below, where a publisher wishes to track specific policy-related data, a local list of categories is used in preference to mapping to a generic set.
+In the examples below, two different publishers have disclosed information about organizations involved in their contracting processes. An organization classification needs to consist of at least two parts: an identifier for the list (scheme) from which the classification is taken, and an identifier for the category from that list being applied. It is useful to also publish a text label and/or URI that users can draw on to interpret the classification. In the first example below, the publisher reuses an existing `classification.scheme`. In the second example below, where a publisher wishes to track specific policy-related data, a local list of categories is used in preference to mapping to a generic set.
 
 #### Classification schemes
 
diff --git a/docs/guidance/publish.md b/docs/guidance/publish.md
@@ -36,7 +36,7 @@ The publication policy ought to also contain information about future plans for
 
 Publishing data under an open license is an important part of open contracting. Without this, restrictions on reuse can prevent many of the important [use cases](design/user_needs) for open contracting information being realized.
 
-A license statement sets out the permission that users have to access, use and reuse the data. This can take the form of a [Public Domain Dedication or Certification](https://creativecommons.org/publicdomain/) which transfers a dataset into the public domain, or re-asserts that there are no existing copyrights or database rights inherent in the dataset (which is the case for government datasets in some jurisdictions), or the application of a license which sets out the terms under which a dataset can be re-used.
+A license statement sets out the permission that users have to access, use and reuse the data. This can take the form of a [Public Domain Dedication or Certification](https://creativecommons.org/publicdomain/) which transfers a dataset into the public domain, or re-asserts that there are no existing copyrights or database rights inherent in the dataset (which is the case for government datasets in some jurisdictions), or the application of a license which sets out the terms under which a dataset can be reused.
 
 We encourage the use of either a public domain dedication/certification, or an attribution only license.
 
diff --git a/docs/history/changelog.md b/docs/history/changelog.md
@@ -172,7 +172,7 @@ Per the [normative and non-normative content and changes policy](../governance/n
 
 * `releaseTag.csv`:
   * [#1238](https://github.com/open-contracting/standard/pull/1238) Open the `releaseTag` codelist.
-  * [#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.
+  * [#1415](https://github.com/open-contracting/standard/pull/1415) [#1509](https://github.com/open-contracting/standard/pull/1509) ([#1731](https://github.com/open-contracting/standard/pull/1731)) Align descriptions of 'planning', 'tender', 'award' and 'contract' with the corresponding schema fields.
 
 * `unitClassificationScheme.csv`:
   * [#1689](https://github.com/open-contracting/standard/pull/1689) Update the instructions on how to find identifiers within the QUDT scheme.
diff --git a/docs/locale/es/LC_MESSAGES/guidance/build.po b/docs/locale/es/LC_MESSAGES/guidance/build.po
@@ -548,11 +548,11 @@ msgstr ""
 
 #: ../../docs/guidance/build.md:118
 msgid ""
-"Re-using tools isn't always easy. [Tool Re-Use in Open Contracting: A "
+"Reusing tools isn't always easy. [Tool Re-Use in Open Contracting: A "
 "Primer](https://www.open-contracting.org/resources/tool-re-use-in-open-"
 "contracting-a-primer/) is a step-by-step guide to help you determine what "
 "you need, evaluate which tool is the right fit, and evaluate whether the "
-"right conditions are in place for successful re-use of a tool."
+"right conditions are in place for successful reuse of a tool."
 msgstr ""
 "Reutilizar herramientas no siempre es fácil. [Reutilización de herramientas "
 "en contrataciones abiertas: Una introducción](https://www.open-"
diff --git a/docs/locale/es/LC_MESSAGES/guidance/map/organization_classifications.po b/docs/locale/es/LC_MESSAGES/guidance/map/organization_classifications.po
@@ -192,7 +192,7 @@ msgid ""
 "the list (scheme) from which the classification is taken, and an identifier "
 "for the category from that list being applied. It is useful to also publish "
 "a text label and/or URI that users can draw on to interpret the "
-"classification. In the first example below, the publisher re-uses an "
+"classification. In the first example below, the publisher reuses an "
 "existing `classification.scheme`. In the second example below, where a "
 "publisher wishes to track specific policy-related data, a local list of "
 "categories is used in preference to mapping to a generic set."
@@ -238,7 +238,7 @@ msgstr ""
 msgid ""
 "Where an appropriate scheme is not listed in the [itemClassificationScheme "
 "codelist](../../schema/codelists.md#item-classification-scheme), publishers "
-"can specify their own scheme. Publishers can either re-use an alternative "
+"can specify their own scheme. Publishers can either reuse an alternative "
 "scheme, or provide their own. Where publishers provide their own local "
 "schemes, they ought to prefix their `scheme` code with an [ISO-3166-1 "
 "alpha-3 country code](https://en.wikipedia.org/wiki/ISO_3166-1) to preserve "
diff --git a/docs/locale/es/LC_MESSAGES/guidance/map/pre-qualification.po b/docs/locale/es/LC_MESSAGES/guidance/map/pre-qualification.po
@@ -443,7 +443,7 @@ msgid ""
 "suppliers to pre-qualify for two tenders for road construction in different "
 "neighbourhoods](https://contrataciones.gov.py/licitaciones/convocatoria/338229-servicios-"
 "consultoria-estudios-factibilidad-diseno-final-ingenieria-tramos-"
-"caminos-1/precalificacion.html). Each tender will re-use the list of pre-"
+"caminos-1/precalificacion.html). Each tender will reuse the list of pre-"
 "qualified suppliers established as a result of this first procedure."
 msgstr ""
 "El Ministerio de Obras Públicas y Comunicaciones emite una [invitación a "
diff --git a/docs/locale/es/LC_MESSAGES/guidance/publish.po b/docs/locale/es/LC_MESSAGES/guidance/publish.po
@@ -136,7 +136,7 @@ msgstr "Licencia tus datos"
 #: ../../docs/guidance/publish.md:36
 msgid ""
 "Publishing data under an open license is an important part of open "
-"contracting. Without this, restrictions on re-use can prevent many of the "
+"contracting. Without this, restrictions on reuse can prevent many of the "
 "important [use cases](design/user_needs) for open contracting information "
 "being realized."
 msgstr ""
@@ -149,12 +149,12 @@ msgstr ""
 #: ../../docs/guidance/publish.md:38
 msgid ""
 "A license statement sets out the permission that users have to access, use "
-"and re-use the data. This can take the form of a [Public Domain Dedication "
+"and reuse the data. This can take the form of a [Public Domain Dedication "
 "or Certification](https://creativecommons.org/publicdomain/) which transfers"
 " a dataset into the public domain, or re-asserts that there are no existing "
 "copyrights or database rights inherent in the dataset (which is the case for"
 " government datasets in some jurisdictions), or the application of a license"
-" which sets out the terms under which a dataset can be re-used."
+" which sets out the terms under which a dataset can be reused."
 msgstr ""
 "Una declaración de licencia establece el permiso que los usuarios tienen "
 "para acceder, utilizar y volver a utilizar los datos. Esto puede tomar la "
diff --git a/docs/locale/es/LC_MESSAGES/schema/identifiers.po b/docs/locale/es/LC_MESSAGES/schema/identifiers.po
@@ -694,7 +694,7 @@ msgstr ""
 
 #: ../../docs/schema/identifiers.md:168
 msgid ""
-"The same `id` value may be re-used in another array of items within the same"
+"The same `id` value may be reused in another array of items within the same"
 " release, and no cross-reference between these identifiers is implied."
 msgstr ""
 "El mismo valor `id` puede reutilizarse en otra lista de artículos en la "
diff --git a/docs/locale/es/LC_MESSAGES/schema/reference.po b/docs/locale/es/LC_MESSAGES/schema/reference.po
@@ -846,7 +846,7 @@ msgstr "Referencia de los bloques"
 
 #: ../../docs/schema/reference.md:273
 msgid ""
-"The following building blocks are commonly re-used throughout the standard."
+"The following building blocks are commonly reused throughout the standard."
 msgstr ""
 "Los siguientes bloques de se reutilizan comúnmente en todo el estándar."
 
diff --git a/docs/locale/fr/LC_MESSAGES/guidance/build.po b/docs/locale/fr/LC_MESSAGES/guidance/build.po
@@ -366,11 +366,11 @@ msgstr ""
 
 #: ../../docs/guidance/build.md:3
 msgid ""
-"Re-using tools isn't always easy. [Tool Re-Use in Open Contracting: A "
+"Reusing tools isn't always easy. [Tool Re-Use in Open Contracting: A "
 "Primer](https://www.open-contracting.org/resources/tool-re-use-in-open-"
 "contracting-a-primer/) is a step-by-step guide to help you determine what "
 "you need, evaluate which tool is the right fit, and evaluate whether the "
-"right conditions are in place for successful re-use of a tool."
+"right conditions are in place for successful reuse of a tool."
 msgstr ""
 
 #: ../../docs/guidance/build.md:5
diff --git a/docs/locale/fr/LC_MESSAGES/guidance/map/organization_classifications.po b/docs/locale/fr/LC_MESSAGES/guidance/map/organization_classifications.po
@@ -129,7 +129,7 @@ msgid ""
 "the list (scheme) from which the classification is taken, and an identifier "
 "for the category from that list being applied. It is useful to also publish "
 "a text label and/or URI that users can draw on to interpret the "
-"classification. In the first example below, the publisher re-uses an "
+"classification. In the first example below, the publisher reuses an "
 "existing `classification.scheme`. In the second example below, where a "
 "publisher wishes to track specific policy-related data, a local list of "
 "categories is used in preference to mapping to a generic set."
@@ -155,7 +155,7 @@ msgstr ""
 msgid ""
 "Where an appropriate scheme is not listed in the [itemClassificationScheme "
 "codelist](../../schema/codelists.md#item-classification-scheme), publishers "
-"can specify their own scheme. Publishers can either re-use an alternative "
+"can specify their own scheme. Publishers can either reuse an alternative "
 "scheme, or provide their own. Where publishers provide their own local "
 "schemes, they ought to prefix their `scheme` code with an [ISO-3166-1 "
 "alpha-3 country code](https://en.wikipedia.org/wiki/ISO_3166-1) to preserve "
diff --git a/docs/locale/fr/LC_MESSAGES/guidance/map/pre-qualification.po b/docs/locale/fr/LC_MESSAGES/guidance/map/pre-qualification.po
@@ -346,7 +346,7 @@ msgid ""
 "suppliers to pre-qualify for two tenders for road construction in different "
 "neighbourhoods](https://contrataciones.gov.py/licitaciones/convocatoria/338229-servicios-"
 "consultoria-estudios-factibilidad-diseno-final-ingenieria-tramos-"
-"caminos-1/precalificacion.html). Each tender will re-use the list of pre-"
+"caminos-1/precalificacion.html). Each tender will reuse the list of pre-"
 "qualified suppliers established as a result of this first procedure."
 msgstr ""
 
diff --git a/docs/locale/fr/LC_MESSAGES/guidance/publish.po b/docs/locale/fr/LC_MESSAGES/guidance/publish.po
@@ -113,20 +113,20 @@ msgstr ""
 #: ../../docs/guidance/publish.md:36
 msgid ""
 "Publishing data under an open license is an important part of open "
-"contracting. Without this, restrictions on re-use can prevent many of the "
+"contracting. Without this, restrictions on reuse can prevent many of the "
 "important [use cases](design/user_needs) for open contracting information "
 "being realized."
 msgstr ""
 
 #: ../../docs/guidance/publish.md:38
 msgid ""
 "A license statement sets out the permission that users have to access, use "
-"and re-use the data. This can take the form of a [Public Domain Dedication "
+"and reuse the data. This can take the form of a [Public Domain Dedication "
 "or Certification](https://creativecommons.org/publicdomain/) which transfers"
 " a dataset into the public domain, or re-asserts that there are no existing "
 "copyrights or database rights inherent in the dataset (which is the case for"
 " government datasets in some jurisdictions), or the application of a license"
-" which sets out the terms under which a dataset can be re-used."
+" which sets out the terms under which a dataset can be reused."
 msgstr ""
 "Une déclaration de licence indique les autorisations dont jouissent les "
 "usagers pour accéder aux données, les utiliser et les réutiliser. La Licence"
diff --git a/docs/locale/fr/LC_MESSAGES/schema/identifiers.po b/docs/locale/fr/LC_MESSAGES/schema/identifiers.po
@@ -688,7 +688,7 @@ msgstr ""
 
 #: ../../docs/schema/identifiers.md:168
 msgid ""
-"The same `id` value may be re-used in another array of items within the same"
+"The same `id` value may be reused in another array of items within the same"
 " release, and no cross-reference between these identifiers is implied."
 msgstr ""
 "Le même identifiant peut être réutilisé dans une autre liste au sein d'une "
diff --git a/docs/locale/fr/LC_MESSAGES/schema/reference.po b/docs/locale/fr/LC_MESSAGES/schema/reference.po
@@ -840,7 +840,7 @@ msgstr "Documentation sur les composants essentiels"
 
 #: ../../docs/schema/reference.md:273
 msgid ""
-"The following building blocks are commonly re-used throughout the standard."
+"The following building blocks are commonly reused throughout the standard."
 msgstr ""
 "Les composants essentiels sont des composants couramment réutilisés dans le "
 "standard."
diff --git a/docs/schema/identifiers.md b/docs/schema/identifiers.md
@@ -196,7 +196,7 @@ Contracts must cross-reference a related award (using the `awardID` field), as k
 
 An item, document or milestone identifier must be unique within a given array of items, and must be used consistently across all the releases in a (contracting or planning) process.
 
-The same `id` value may be re-used in another array of items within the same release, and no cross-reference between these identifiers is implied.
+The same `id` value may be reused in another array of items within the same release, and no cross-reference between these identifiers is implied.
 
 The use of an identifier means that subsequent releases can update prior identified items, documents or milestones, without needing to republish all the items, documents or milestones.
 
diff --git a/docs/schema/reference.md b/docs/schema/reference.md
@@ -377,7 +377,7 @@ See the [amendment implementation guidance](../guidance/map/amendments) for more
 
 ## Building block reference
 
-The following building blocks are commonly re-used throughout the standard.
+The following building blocks are commonly reused throughout the standard.
 
 ### OrganizationReference
 
diff --git 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 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, or revised details or timelines for a proposed contracting process."
-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."
+tender,Tender,"Information about, for example, the needed items and their estimated value, procurement method, award criteria, and various deadlines. This information concerns the 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."
 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."
