From d4864d73418cb804ff6ddfc2306101cc04454b7d Mon Sep 17 00:00:00 2001 From: odscjen Date: Wed, 15 Jun 2022 11:03:04 +0100 Subject: [PATCH 1/5] clarifying language in description of release ID --- schema/dereferenced-release-schema.json | 2 +- schema/release-schema.json | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/schema/dereferenced-release-schema.json b/schema/dereferenced-release-schema.json index acb083a95..a7178cf04 100644 --- a/schema/dereferenced-release-schema.json +++ b/schema/dereferenced-release-schema.json @@ -13,7 +13,7 @@ }, "id": { "title": "Release ID", - "description": "The identifier of the release. The release ID must be unique within the scope of the (contracting or planning) process, for a given version of OCDS. In other words, a publisher may publish datasets for different versions of OCDS, and repeat releases within each dataset. The release ID must not contain the number sign (#). For a compiled release, the `ocid` and the maximum `date` among the individual releases used to create the compiled release, separated by a hyphen: {ocid}-{date}.", + "description": "The identifier of the release or a compiled release. For an individual release, the release ID must be unique within the scope of the contracting (or planning) process, for a given version of OCDS. In other words, a publisher may publish datasets for different versions of OCDS, and repeat releases within each dataset. The release ID must not contain the number sign (#). For a compiled release, the release ID should be the `ocid` and the maximum `date` among the individual releases used to create the compiled release, separated by a hyphen: {ocid}-{date}.", "type": "string", "minLength": 1, "omitWhenMerged": true diff --git a/schema/release-schema.json b/schema/release-schema.json index 6d526dc43..44884cbc9 100644 --- a/schema/release-schema.json +++ b/schema/release-schema.json @@ -13,7 +13,7 @@ }, "id": { "title": "Release ID", - "description": "The identifier of the release. The release ID must be unique within the scope of the (contracting or planning) process, for a given version of OCDS. In other words, a publisher may publish datasets for different versions of OCDS, and repeat releases within each dataset. The release ID must not contain the number sign (#). For a compiled release, the `ocid` and the maximum `date` among the individual releases used to create the compiled release, separated by a hyphen: {ocid}-{date}.", + "description": "The identifier of the release or a compiled release. For an individual release, the release ID must be unique within the scope of the contracting (or planning) process, for a given version of OCDS. In other words, a publisher may publish datasets for different versions of OCDS, and repeat releases within each dataset. The release ID must not contain the number sign (#). For a compiled release, the release ID should be the `ocid` and the maximum `date` among the individual releases used to create the compiled release, separated by a hyphen: {ocid}-{date}.", "type": "string", "minLength": 1, "omitWhenMerged": true From 45831240bd74ad0aaaec2374c880a600493b993c Mon Sep 17 00:00:00 2001 From: odscjen Date: Wed, 15 Jun 2022 11:07:02 +0100 Subject: [PATCH 2/5] update changelog --- docs/history/changelog.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/history/changelog.md b/docs/history/changelog.md index a9dae36aa..e9f259c19 100644 --- a/docs/history/changelog.md +++ b/docs/history/changelog.md @@ -201,6 +201,7 @@ Per the [normative and non-normative content and changes policy](https://docs.go * [#1189](https://github.com/open-contracting/standard/pull/1189) `Document.url`, to use precise wording and to describe how to indicate a part of a document. * [#1229](https://github.com/open-contracting/standard/pull/1229) Standardize the descriptions of `planning.documents`, `tender.documents`, `awards.documents`, `contracts.documents`, and `contracts.implementation.documents`. * [#1335](https://github.com/open-contracting/standard/pull/1335) Standardize the descriptions of `planning`, `planning.rationale`, `planning.budget`, `planning.documents`, and `planning.milestones`. + * [#1527](https://github.com/open-contracting/standard/pull/1527) `id`, to clarify use in releases and compiled releases. * Remove confusing terminology: * [#1487](https://github.com/open-contracting/standard/pull/1487) `planning.budget.project`, to remove sentence about translation options. From 77047cf5166bcb482827682670d784686548b4a4 Mon Sep 17 00:00:00 2001 From: odscjen <95221058+odscjen@users.noreply.github.com> Date: Fri, 17 Jun 2022 09:08:33 +0100 Subject: [PATCH 3/5] Update schema/release-schema.json Co-authored-by: James McKinney <26463+jpmckinney@users.noreply.github.com> --- schema/release-schema.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/schema/release-schema.json b/schema/release-schema.json index 44884cbc9..63153bc44 100644 --- a/schema/release-schema.json +++ b/schema/release-schema.json @@ -13,7 +13,7 @@ }, "id": { "title": "Release ID", - "description": "The identifier of the release or a compiled release. For an individual release, the release ID must be unique within the scope of the contracting (or planning) process, for a given version of OCDS. In other words, a publisher may publish datasets for different versions of OCDS, and repeat releases within each dataset. The release ID must not contain the number sign (#). For a compiled release, the release ID should be the `ocid` and the maximum `date` among the individual releases used to create the compiled release, separated by a hyphen: {ocid}-{date}.", + "description": "The identifier of the individual release or compiled release. For an individual release, the release ID must be unique within the scope of the (contracting or planning) process, for a given version of OCDS. In other words, a publisher may publish datasets for different versions of OCDS, and repeat releases within each dataset. The release ID must not contain the number sign (#). For a compiled release, the release ID should be the `ocid` and the maximum `date` among the individual releases used to create the compiled release, separated by a hyphen: {ocid}-{date}.", "type": "string", "minLength": 1, "omitWhenMerged": true From 867d905c91fbf7a6f1d342b48060416529777ab5 Mon Sep 17 00:00:00 2001 From: odscjen Date: Fri, 17 Jun 2022 09:10:16 +0100 Subject: [PATCH 4/5] update changelog.md --- 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 e9f259c19..3058fd127 100644 --- a/docs/history/changelog.md +++ b/docs/history/changelog.md @@ -195,13 +195,13 @@ Per the [normative and non-normative content and changes policy](https://docs.go * Update and clarify field descriptions: * [#1113](https://github.com/open-contracting/standard/pull/1113) `ocid`, to recommend a hyphen after the ocid prefix. + * [#1527](https://github.com/open-contracting/standard/pull/1527) `id`, to clarify use in releases and compiled releases. * [#1094](https://github.com/open-contracting/standard/pull/1094) `Organization.id`, to clarify its uniqueness. * [#1510](https://github.com/open-contracting/standard/pull/1510) `Organization.additionalIdentifiers`, to clarify its potential use for organizational units. * [#1167](https://github.com/open-contracting/standard/pull/1167) `Budget`,` Budget.id`, `Budget.description`, `Budget.amount`, to reduce ambiguity and use consistent wording. * [#1189](https://github.com/open-contracting/standard/pull/1189) `Document.url`, to use precise wording and to describe how to indicate a part of a document. * [#1229](https://github.com/open-contracting/standard/pull/1229) Standardize the descriptions of `planning.documents`, `tender.documents`, `awards.documents`, `contracts.documents`, and `contracts.implementation.documents`. * [#1335](https://github.com/open-contracting/standard/pull/1335) Standardize the descriptions of `planning`, `planning.rationale`, `planning.budget`, `planning.documents`, and `planning.milestones`. - * [#1527](https://github.com/open-contracting/standard/pull/1527) `id`, to clarify use in releases and compiled releases. * Remove confusing terminology: * [#1487](https://github.com/open-contracting/standard/pull/1487) `planning.budget.project`, to remove sentence about translation options. From 514d201b499b2e7185e1e14366727fef7c02f205 Mon Sep 17 00:00:00 2001 From: odscjen Date: Fri, 17 Jun 2022 09:18:04 +0100 Subject: [PATCH 5/5] updated dereferenced-release-schema.json --- schema/dereferenced-release-schema.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/schema/dereferenced-release-schema.json b/schema/dereferenced-release-schema.json index a7178cf04..07df73d0f 100644 --- a/schema/dereferenced-release-schema.json +++ b/schema/dereferenced-release-schema.json @@ -13,7 +13,7 @@ }, "id": { "title": "Release ID", - "description": "The identifier of the release or a compiled release. For an individual release, the release ID must be unique within the scope of the contracting (or planning) process, for a given version of OCDS. In other words, a publisher may publish datasets for different versions of OCDS, and repeat releases within each dataset. The release ID must not contain the number sign (#). For a compiled release, the release ID should be the `ocid` and the maximum `date` among the individual releases used to create the compiled release, separated by a hyphen: {ocid}-{date}.", + "description": "The identifier of the individual release or compiled release. For an individual release, the release ID must be unique within the scope of the (contracting or planning) process, for a given version of OCDS. In other words, a publisher may publish datasets for different versions of OCDS, and repeat releases within each dataset. The release ID must not contain the number sign (#). For a compiled release, the release ID should be the `ocid` and the maximum `date` among the individual releases used to create the compiled release, separated by a hyphen: {ocid}-{date}.", "type": "string", "minLength": 1, "omitWhenMerged": true