Architecture
Data contracts
A data contract makes expectations explicit: what a dataset contains, what each field means, how fresh and complete it will be, and how changes will be communicated.
What a contract covers
- Schema and field definitions
- Quality rules and service levels (freshness, completeness)
- Ownership and support contacts
- Versioning and how breaking changes are announced
- Terms of use and access
Contracts are often written as code (for example YAML) and checked automatically, so a producer cannot silently break consumers. The Open Data Contract Standard is one community specification.
Work with ex omnia
Contact details for ex omnia will be published here once confirmed.