Merge 1.1-dev into 1.2-dev

docs/examples/merging/example02-field-record.json

@@ -5,10 +5,6 @@
   },
   "publishedDate": "",
   "version": "1.1",
-  "packages": [
-    "https://standard.open-contracting.org/examples/releases/ocds-k50g02-13-9-368828-planning.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-k50g02-13-9-368828-tender.json"
-  ],
   "records": [
     {
       "ocid": "ocds-k50g02-13-9-368828",

docs/examples/merging/example02-object-record.json

@@ -5,10 +5,6 @@
   },
   "publishedDate": "",
   "version": "1.1",
-  "packages": [
-    "https://standard.open-contracting.org/examples/releases/ocds-k50g02-11-13-651832-tenderUpdate.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-k50g02-11-13-651832-tender.json"
-  ],
   "records": [
     {
       "ocid": "ocds-k50g02-11-13-651832",

docs/examples/merging/example03-record.json

@@ -5,10 +5,6 @@
   },
   "publishedDate": "",
   "version": "1.1",
-  "packages": [
-    "https://standard.open-contracting.org/examples/releases/ocds-23g63a01-200502-awardAmendment.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-23g63a01-200502-award.json"
-  ],
   "records": [
     {
       "ocid": "ocds-23g63a01-200502",

docs/examples/merging/merged-tender.json

@@ -10,13 +10,6 @@
   "license": "http://opendatacommons.org/licenses/pddl/1.0/",
   "publicationPolicy": "https://github.com/open-contracting/sample-data/",
   "version": "1.1",
-  "packages": [
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00002-01-award1.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00002-01-award2.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00002-01-tender.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00002-01-tender-update.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00002-01-tender-amendment.json"
-  ],
   "records": [
     {
       "ocid": "ocds-213czf-000-00002",

docs/examples/merging/merged.json

@@ -10,13 +10,6 @@
   "license": "http://opendatacommons.org/licenses/pddl/1.0/",
   "publicationPolicy": "https://github.com/open-contracting/sample-data/",
   "version": "1.1",
-  "packages": [
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00002-01-award1.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00002-01-award2.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00002-01-tender.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00002-01-tender-update.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00002-01-tender-amendment.json"
-  ],
   "records": [
     {
       "ocid": "ocds-213czf-000-00002",

docs/examples/merging/versioned.json

@@ -10,13 +10,6 @@
   "license": "http://opendatacommons.org/licenses/pddl/1.0/",
   "publicationPolicy": "https://github.com/open-contracting/sample-data/",
   "version": "1.1",
-  "packages": [
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00002-01-award1.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00002-01-award2.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00002-01-tender.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00002-01-tender-update.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00002-01-tender-amendment.json"
-  ],
   "records": [
     {
       "ocid": "ocds-213czf-000-00002",

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

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

docs/examples/record-embedded-releases.json

@@ -1,14 +1,5 @@
 {
   "extensions": [],
-  "packages": [
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-01-planning.json#ocds-213czf-000-00001-01-planning",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-02-tender.json#ocds-213czf-000-00001-02-tender",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-03-tenderAmendment.json#ocds-213czf-000-00001-03-tenderAmendment",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-03-tenderAmendment.json#ocds-213czf-000-00001-03-tenderUpdate",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-04-award.json#ocds-213czf-000-00001-04-award",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-05-contract.json#ocds-213czf-000-00001-05-contract",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-05-contract.json#ocds-213czf-000-00001-06-implementation"
-  ],
   "publishedDate": "2014-02-02T13:02:00Z",
   "publisher": {
     "name": "Open Data Services Co-operative Limited",

docs/examples/record.json

@@ -1,14 +1,5 @@
 {
   "extensions": [],
-  "packages": [
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-01-planning.json#ocds-213czf-000-00001-01-planning",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-02-tender.json#ocds-213czf-000-00001-02-tender",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-03-tenderAmendment.json#ocds-213czf-000-00001-03-tenderAmendment",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-03-tenderAmendment.json#ocds-213czf-000-00001-03-tenderUpdate",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-04-award.json#ocds-213czf-000-00001-04-award",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-05-contract.json#ocds-213czf-000-00001-05-contract",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-05-contract.json#ocds-213czf-000-00001-06-implementation"
-  ],
   "publishedDate": "2014-02-02T13:02:00Z",
   "publisher": {
     "name": "Open Data Services Co-operative Limited",

docs/examples/records/award.json

@@ -10,12 +10,6 @@
   "license": "http://opendatacommons.org/licenses/pddl/1.0/",
   "publicationPolicy": "https://github.com/open-contracting/sample-data/",
   "version": "1.1",
-  "packages": [
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-01-planning.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-02-tender.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-03-tenderUpdate.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-04-award.json"
-  ],
   "records": [
     {
       "ocid": "ocds-213czf-000-00001",

docs/examples/records/contract.json

@@ -10,13 +10,6 @@
   "license": "http://opendatacommons.org/licenses/pddl/1.0/",
   "publicationPolicy": "https://github.com/open-contracting/sample-data/",
   "version": "1.1",
-  "packages": [
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-01-planning.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-02-tender.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-03-tenderUpdate.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-04-award.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-05-contract.json"
-  ],
   "records": [
     {
       "ocid": "ocds-213czf-000-00001",

docs/examples/records/contractAmendment.json

@@ -10,15 +10,6 @@
   "license": "http://opendatacommons.org/licenses/pddl/1.0/",
   "publicationPolicy": "https://github.com/open-contracting/sample-data/",
   "version": "1.1",
-  "packages": [
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-01-planning.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-02-tender.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-03-tenderUpdate.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-04-award.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-05-contract.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-06-implementation.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-07-contractAmendment.json"
-  ],
   "records": [
     {
       "ocid": "ocds-213czf-000-00001",

docs/examples/records/implementation.json

@@ -10,14 +10,6 @@
   "license": "http://opendatacommons.org/licenses/pddl/1.0/",
   "publicationPolicy": "https://github.com/open-contracting/sample-data/",
   "version": "1.1",
-  "packages": [
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-01-planning.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-02-tender.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-03-tenderUpdate.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-04-award.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-05-contract.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-06-implementation.json"
-  ],
   "records": [
     {
       "ocid": "ocds-213czf-000-00001",

docs/examples/records/planning.json

@@ -10,9 +10,6 @@
   "license": "http://opendatacommons.org/licenses/pddl/1.0/",
   "publicationPolicy": "https://github.com/open-contracting/sample-data/",
   "version": "1.1",
-  "packages": [
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-01-planning.json"
-  ],
   "records": [
     {
       "ocid": "ocds-213czf-000-00001",

docs/examples/records/tender.json

@@ -10,10 +10,6 @@
   "license": "http://opendatacommons.org/licenses/pddl/1.0/",
   "publicationPolicy": "https://github.com/open-contracting/sample-data/",
   "version": "1.1",
-  "packages": [
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-01-planning.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-02-tender.json"
-  ],
   "records": [
     {
       "ocid": "ocds-213czf-000-00001",

docs/examples/records/tenderUpdate.json

@@ -10,11 +10,6 @@
   "license": "http://opendatacommons.org/licenses/pddl/1.0/",
   "publicationPolicy": "https://github.com/open-contracting/sample-data/",
   "version": "1.1",
-  "packages": [
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-01-planning.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-02-tender.json",
-    "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-03-tenderUpdate.json"
-  ],
   "records": [
     {
       "ocid": "ocds-213czf-000-00001",

docs/getting_started/releases_and_records.md

@@ -18,7 +18,7 @@ There are major events that mark the progress from one stage to another, like an
 
 Releases are **immutable**. Each change is documented in a **new** release, rather than by updating an existing one. The collection of releases for a particular process makes its change history.
 
-**Records** are JSON documents that act as an index of all releases for a single contracting process. While releases are never updated, records are updated each time there is a change. A record is updated by adding a new release to this index.
+**Records** are JSON documents that act as an index of releases for a single contracting process. While releases are never updated, records can be updated each time there is a change. A record is updated by adding a new release to this index.
 
 ![Contracting Process with releases and a record](../_static/png/changehistory_process_record.png)
 
@@ -29,7 +29,7 @@ Records can also contain:
 
 These structures are designed to help users to access:
 
-* The current state of the contracting process 
+* The current state of the contracting process
 * The detailed history of changes for individual fields
 
 In accounting terms, releases are analogous to individual transactions in an account. A record represents both the ledger of all transactions and the closing balance. The ledger is the releases list, and the closing balance is the compiled release.
@@ -51,7 +51,7 @@ Each release contains an [ocid](../schema/identifiers.md#contracting-process-ide
 
 A release also needs a release identifier, unique in the scope of the contracting process. A release id can be built in several ways. Publishers can use any generation strategy, as long as the ids don’t collide within the same process.
 
-The [easy releases](../guidance/build/easy_releases) section introduces two strategies that can be used in any scenario. 
+The [easy releases](../guidance/build/easy_releases) section introduces two strategies that can be used in any scenario.
 
 #### Packaging
 
@@ -66,7 +66,7 @@ Each release also provides one or more tags. Tags provide information about the
 For example:
 
 * When an invitation to tender is published, the publisher uses the 'tender' tag . The release includes the relevant details in the `tender` section. It can also contain information about the budget in the planning section.
-* When a contract is awarded, the publisher uses the 'award' tag. The release includes the relevant details in the `award` section. It can also update the tender section with the list of tenderers that submitted a bid. 
+* When a contract is awarded, the publisher uses the 'award' tag. The release includes the relevant details in the `award` section. It can also update the tender section with the list of tenderers that submitted a bid.
 
 The [release tag codelist](../schema/codelists.md#release-tag) contains the list of all tags provided by OCDS. Note that it is allowed to use more than one tag in the same release. For example, a release with new data in the `tender` and `award` sections can use the 'tender' and 'award' tags together.
 
@@ -79,9 +79,9 @@ It might be more appropriate to repeat data when processes have fewer releases.
 ````{admonition} Example
 :class: hint
 
-The following example shows releases with minimal changes on each update. 
+The following example shows releases with minimal changes on each update.
 
-1. The first release presents tender data. 
+1. The first release presents tender data.
 1. The second introduces a new document in the `tender` section with the 'tenderUpdate' tag. Note that the release ignores all the nonmandatory fields. The tender document present in the previous release is also ignored.
 1. The third release presents award data, and ignores the tender section.
 
@@ -160,4 +160,4 @@ Records are published wrapped in a record package. The `uri` field in the packag
 
 The following shows how to update a record as releases are published over time.
 
-![Record updates](../_static/change_history_animation.gif)
+![Record updates](../_static/change_history_animation.gif)