OCDS provides a common core of sections and building blocks for describing contracting processes.
Many publishers will have additional data that they could publish. Instead of ignoring this data and leaving it unpublished, OCDS encourages publishers to collaborate on the creation of extensions to the standard.
Extensions are divided into two types:
- Core extensions are maintained as part of the standard governance process, documented as part of the standard and reviewed by the OCDS technical team with each version upgrade of OCDS. They are likely to be relevant to a large number of publishers and users.
- Community and local extension are maintained by third-parties, or are maintained outside of the standard governance process. They might provide features needed by only a small number of publishers or users, or might be used to document a publisher’s additional fields or codelist values.
All core and community extensions are listed in the Extension Explorer. The standard technical team approves extensions for inclusion in the Extension Explorer (distinguishing community from local extensions) and for inclusion in the governance process (distinguishing core from community extensions).
Using existing extensions¶
Extensions are applied by adding their URLs to the
extensions array in the release package or record package. You can discover extensions, read their documentation and find the URL to add using the Extension Explorer.
This version of OCDS uses these specific versions of core extensions:
Groups of extensions can be combined into profiles. Profiles are adaptations of OCDS to suit the disclosure requirements and user needs of a particular sector, type of contracting process or legal framework. View the list of profiles.
Developing new extensions¶
If you have additional fields which cannot be mapped to the OCDS schema or an existing extension, you ought to include these in your OCDS data and create a new extension to document their structure and meaning.