Glossary · 7 · Product information systems and data roles
Data contract
Also known as: Data agreement (producer–consumer)
A data contract is an agreement between a data producer and its consumers that defines the structure (schema), meaning, quality expectations, service levels and change rules of the data delivered, often written in a machine-readable form so it can be checked automatically.
- Data management
- System integration
In one sentence
An agreement between a data producer and its consumers on schema, meaning, quality, service levels and change rules of the data delivered.
Example
The contract for the parts feed states that the field “status” only carries released, in-change or withdrawn, and that a new value is announced four weeks before it appears.
Explained in context
Context cards connect this term with others to answer one question. Also in British English and German.
How it applies
- Change rules: For documentation systems, the most important part of a data contract is often what happens when the data changes: which changes are announced, how far ahead, and how removed or renamed values are handled.
- Meaning, not only schema: A schema says a field is text; the contract also says what it means and which values are allowed, which is what a document assembled from it depends on.
- Standards: Data contracts are established practice without a single binding standard. Open specifications, such as the Open Data Contract Standard maintained by the Bitol project of the LF AI & Data Foundation, offer a common format.
Data contract vs. interface specification
An interface specification describes how to call or read a system. A data contract adds the producer’s commitments about the data itself — meaning, quality, service levels and change — and names who answers for them.
External references
- Open Data Contract Standard (ODCS): https://github.com/bitol-io/open-data-contract-standard