These release notes describe what’s new in each version. OCDS adheres to Semantic Versioning.
Per the normative and non-normative content and changes policy, iterative improvements to non-normative content can be made outside the release cycle.
Getting Started section:
#955 Split the Guidance section into sub-sections. Add a new History section, and move the Changelog, Credits, and History and Development pages to it.
#958 Governance page: Change responsibility for prioritization review to OCP’s Head of Data Products & Services. Change “technical team” to “standard development team”.
#986 Add implementation guidance from OCP website.
#1013 Replace guidance on publication levels.
#963 Remove guidance on web discovery.
#1016 Add links to OCDS profiles and linked standards.
#986 Merge Registration page into Build page.
#960 Support section: Merge Tools page into Support page.
#959 History section: Merge Credits and History of OCDS pages into Development and Appreciation page. Update history from present perspective.
#908 Rename Validator to Data Review Tool.
#975 Add a Make target to generate PDFs of the documentation.
[1.1.5] - 2020-08-20¶
The Translation and localization policy is amended to read “normative content will be translated into all core supported languages as soon as possible” instead of “before the release”. A Spanish translation is ready for release, and a French translation will be ready as soon as possible.
#1000 Update description of ‘financing’ code, and add ‘payment’ code.
#966 Move Governance and Deprecation pages to new Governance section.
#970 Add links to access the release schema as a CSV spreadsheet and via the Field-Level Mapping Template. Add notes to describe the alternatives for browsing the schemas.
#965 Release Reference page: Add extensions list for the Transaction object.
#970 Release Schema page: Correct the description of compiled releases.
#996 Record Reference page: Rewrite page to improve clarity.
#972 Clarify the norms around open and closed codelists.
#973 Describe the
codelistJSON Schema properties.
#1036 Add instruction for OCDS publishers to contact the OCDS Helpdesk to add list codes to org-id.guide.
[1.1.4] - 2019-06-25¶
OCDS 1.0 uses the whole-list merge strategy for
Award.suppliers, whereas OCDS 1.1 uses the identifier merge strategy. As a consequence, the OCDS 1.1 versioned release schema is not backward compatible with OCDS 1.0.
Action: Versioned releases respecting the OCDS 1.0 schema that set
Award.supplierswill need to be re-created to validate against the OCDS 1.1 schema.
Action: No change is required, but we recommend that publishers update the URLs of these extensions in their release packages and record packages.
#831 OCDS now has a Normative and non-normative content and changes policy.
#738 1.1.3 changed the merging and versioning behaviors of
Item.unit, such that it could be removed by setting it to
null, and such that it was versioned as a whole. 1.1.4 restores the behaviors from 1.1.2, such that only its sub-fields can be removed by setting them to
null, and such that its sub-fields are versioned individually.
Action: If you had upgraded to OCDS 1.1.3, then compiled releases and versioned releases that set
Item.unitwill likely need to be re-created to validate against the OCDS 1.1.4 schema.
Classification.idare now versioned, consistent with the documentation.
Action: Versioned releases that set these fields will likely need to be re-created to validate against the OCDS 1.1.4 schema.
#769 The versioned release schema now matches the release schema in: having a
minLengthvalidation property for
RelatedProcess.scheme; and having a
descriptionmetadata properties are removed from the versioned release schema.
omitWhenMerged, consistent with the reference implementation in OCDS Merge.
#824 Canonical codelist files are available at URLs like https://standard.open-contracting.org/schema/1__1__5/codelists/, and translations are available at URLs like https://standard.open-contracting.org/1.1/en/codelists/, for OCDS 1.1.4 and up.
#725 Add a ‘plannedProcurementNotice’ code to the
documentTypecodelist, ‘CUCOP’ to
itemClassificationScheme, ‘interestedParty’ to
#725 Update the descriptions of the ‘tenderNotice’ and ‘technicalSpecifications’ codes in the
documentTypecodelist to align with the text of the Agreement on Government Procurement (GPA) of the World Trade Organization (WTO).
#725 Apply the style guide and OCDS glossary to the ‘procuringEntity’ and ‘supplier’ codes in the
#725 Add examples to the description of the ‘environmentalImpact’ code in the
#829 Use sentence case for code titles and end code descriptions with periods.
#852 Use the correct normative keywords in code descriptions.
#712 Add missing titles for
urland description for
recordin the record package schema, and missing description for
releasesin release package schema.
#838 Eliminate the conflicting rule that release identifiers must be unique within release packages. Uniqueness within the scope of a release package either implies that release identifiers must be globally unique, or imposes an arbitrary restriction on the contents of release packages, as there is no rule preventing release packages from containing releases from different contracting processes. Release identifiers are only required to be locally unique within the scope of a contracting process. The
idvalues of a release can be used together to disambiguate releases within a release package.
#810 Add a dereferenced release schema to ease the implementation of the merge routine.
"versionId": truehint to
#845 Remove a reference to a closed issue and a note about a field name.
#855 Use the correct normative keywords in field descriptions.
#855 Rephrase field descriptions as definitions rather than instructions.
#855 Align the descriptions of the
licensefields in the release package schema and record package schema.
#797 Fix examples of versioned releases.
#831 Use the correct normative keywords in the documentation.
#869 Move normative statements into normative sections.
#835 Display the canonical schema URLs in the documentation.
#838 Clarify the uniqueness of release, award and contract identifiers.
#831 Improve the description of iterating the release
#783 Add missing email address for the standard governance working group.
Replace ambiguous or incorrect terms:
#831 Use “release
id” and “release
date”, instead of “
releaseID” and “
#831 Use “ocid prefix”, instead of “publisher prefix”
#831 Use “minor versions”, instead of “decimal versions” on deprecation page
#823 Fix incorrect uses of “records”, “codelists” and “gazetteers” on identifiers and codelists pages
Fix out-of-date content:
Add links to:
[1.1.3] - 2018-04-16¶
#646 Disallow use of
nullas an entry in the array for
namefield optional for
#630 Allow optional field
null. (Reverted in 1.1.4)
codelistproperty to reference
releaseTag.csv, and update the
Update the currency codelist for ISO4217 amendment 165 (2017-12-14).
#633 Update schema reference page to display
#634 Clarify definitions of core, community and local extensions.
Old and unused scripts have been removed from the documentation repository, and a number of script dependencies have been updated.
[1.1.2] - 2017-11-10¶
[1.1.1] - 2017-07-31¶
#471 Update the milestoneType codelist, replacing ‘planning’ with ‘preProcurement’ and ‘adjudication’ with ‘assessment’, and introducing ‘approval’ and ‘financing’. This is an open codelist, so the old codes remain valid, but publishers able to update to the new codes should do so.
#489 Change the milestone documents extension to a core extension. This extension is only needed by publishers with legacy data containing documents within milestones.
make_field_definitions.pyfrom the utility scripts, as it is no longer required.
Fix typographic errors throughout the documentation and codelist descriptions.
Add docstrings to utility scripts.
[1.1.0] - 2017-05-01¶
#368 Updates to organization handling in OCDS - We have updated the approach to include organization information in the standard from having embedded blocks of organization information, to using embedded cross-references to a top-level ‘parties’ array where full organization details are stored. This change reduces duplication of organization information, and enables more flexible disclosure of information on all the parties to a contracting process, including multiple buyers.
#357 Amendment handling - We have replace amendment with an array of amendments, and have updated schema and guidance to remove the option of providing semi-structured changes in an amendment object. Changes between amendments should now be provided using multiple releases, with the option to explicitly declare how releases relate to an amendment included in the new amendments array.
Schema validation updates¶
#323 Standard should specify use of UTF-8 for encoding JSON - We now recommend use of I-JSON and UTF-8 for JSON publication
#336 Codelist properties in schema - We have included explicit references to the codelist files (CSV versions) in the schema. This will be used in future versions of the validator to support validation against codelists.
#301 Specifying versions and extensions in package metadata - We have updated the package schemas to require that version is declared, and to provide a means of declaring extensions in use. This will be used in future versions of the validator to support validation against extensions.
Schema definition updates¶
#372 Updates to transactions terminology - We have replaced receiverOrganization and providerOrganization with payee and payer, to align with more familiar terminology, and have replaced ‘amount’ with ‘value’ for consistency with other areas of the standard.
Closed codelist updates¶
Open codelist updates¶
#335 Core and community extensions - We have introduced widespread use of extensions throughout the standard. An extension provides fields and data structures that are optional, either because (a) they are only relevant in particular contexts or contracting processes; or (b) they represent a ‘stretch goal’ for most data publishers, and so are not currently suitable for inclusion in the main standard. We divide these extensions into ‘core extensions’ which have wide enough relevance, and technical maturity to be included in the main standard documentation (and which are versioned along with the standard documentation), and ‘community extensions’ which may have less technical maturity, or which might be versioned independently of the main standard.
#379 Bids and Bid Statistics - We have introduced a core extension which provides a top level Bids section, with BidStatistics and Bid building blocks for detailed information on individual bids. This supersedes the current tender/tenderers section.
#33 Participation fees (bid document and submission costs) - We have introduced a core extension for declaring the participation fees related to a contracting process.
#355 Deprecating milestone documents - We have deprecated milestone documents from core, and added a milestone documents extension for those who wish to continue to use documents at the milestone level.
[1.0.3] - 2017-07-31¶
[1.0.2] - 2016-11-22¶
#362 Add a
titleproperty to all fields.
#221 Add the missing
#391 Fix typo in
#271 Fix link to Fiscal Data Package.
#314 Add a
descriptionproperty to the
#244 Fix the
descriptionproperty of the
#228 Update the documentation to use “Object” not “Reference” in Format column of field tables.
Add CSV download links for registered ocids and publication levels.
Update the publication levels spreadsheet to reflect above changes.
Remove the old Spanish documentation translations from
[1.0.1] - 2016-03-14¶
#295 Allow optional fields
#267 Rename codes in documentType codelist: ‘Tender notice’ to ‘tenderNotice’, ‘Award notice’ to ‘awardNotice’, ‘Contract notice’ to ‘contractNotice’.
Fix bugs in versioned release schema.
Remove reference to non-existent
statusDescriptionfield in awardStatus codelist.
Add or update
Restructure the documentation, including: expanding Getting Started section, adding more examples.
Fix broken links.
Make changes to how the documentation is built, including: improving the translation process, adding some schema tests.
[1.0.0] - 2015-07-29¶
#199 Add the
Award.contractPeriodfield, to disclose the anticipated contract period without creating a
descriptionproperty of the
Fix typos in Markdown text and JSON examples.