Skip to content

Open Data Contract Standard

Executive Summary

This document describes the keys and values expected in a YAML data contract, per the Open Data Contract Standard. The standard is divided in multiple sections. Each section starts with at least an example, followed by the definition of each field/key. Since v3.1.0, each section has its own page for easier readability.

For more details, see the sections below:

  1. Fundamentals
  2. Schema
  3. References
  4. Data Quality
  5. Support & Communication Channels
  6. Pricing
  7. Team
  8. Roles
  9. Service-Level Agreement
  10. Infrastructures & Servers
  11. Custom & Other Properties

Notes

  • The sections above contain example values. We carefully reviewed the consistency of those values, but we cannot guarantee that there are no errors. If you spot one, please raise an issue.
  • Some fields have a null value: even if it is equivalent to not having the field in the contract, we wanted to have the field for illustration purposes.
  • The contract should be platform agnostic. If you think this is not the case, please raise an issue.
  • The provided JSON schemas are companions to the standards (ODCS or ODPS), it means that they do not define the standards and may include bugs. In case of conflict between the standard and the JSON Schema, the standard takes precedence.

Full example

Check full example here.

All trademarks are the property of their respective owners.