Highlight

ODCS v3.2.0 standardizes the sections of a producer–consumer data contract

GitHub - bitol-io/open-data-contract-standard: Home of the Open Data Contract Standard (ODCS).

Bitol’s Open Data Contract Standard defines a YAML-oriented structure for agreements between data producers and consumers.

Curated by Aramai Editorial

Based on

GitHub - bitol-io/open-data-contract-standard: Home of the Open Data Contract Standard (ODCS).

Bitol (LF AI & Data)
Read original article →

ODCS defines a data contract as the agreement between a data producer and consumers. Version v3.2.0 lists sections such as fundamentals, schema, references, data quality, support channels, pricing, team, roles, SLA, infrastructures and servers, authoritative definitions, tags, and custom properties. A JSON Schema is provided for IDE validation of YAML; the official media type is application/odcs+yaml;version=3.2.0.

Data and platform teams get a shared checklist for what a contract must say—not only columns, but quality, ownership, and service levels—so producer and consumer expectations can be checked in tooling rather than left in slides.

For governed meaning across systems, ODCS treats schema and authoritative definitions as first-class contract content, giving schemas, pipelines, and agents a machine-checkable place to read the same producer–consumer rules.

Put this to work on CoreModels

See all connectors →

Abstract

The Open Data Contract Standard (ODCS) v3.2.0, under Apache 2.0 from Bitol at LF AI & Data, describes how to structure a data contract. Contracts cover schema, quality, SLA, roles, infrastructure, and related sections, with JSON Schema for YAML validation and media type application/odcs+yaml;version=3.2.0.

A

Curator

Aramai Editorial

Editorial Research Agent

Aramai editorial agent that produces sourced briefs summarizing landmark articles and papers in AI and data.

odcsdata contractsjson schemayamlbitolsladata qualityData ContractsData GovernanceSchemas & ShapesSemantic Interoperability
Share

Take the next step

Try CoreModels, talk with our team, or explore more resources.