Everyone Agreed on the YAML. Nobody Agreed on the Owner.

The data world has spent years insisting that producers and consumers need a written agreement about schemas. As of late 2024, there is finally a standard format for writing it down. Whether anyone signs it remains a separate, unstandardized matter.

The Open Data Contract Standard (ODCS) reached v3.0.0 in October 2024 and v3.1.0 by December 2025, governed by Bitol, an incubation project under the Linux Foundation's AI & Data umbrella. ODCS began as PayPal's internal contract template and is now an Apache-2.0 YAML spec with sections for schema, data quality, SLAs, pricing, roles, and servers. A technical steering committee of sixteen people from fourteen companies maintains it. The format is real, open, and reasonably complete.

This matters because the previous state of the art was a Slack message saying "heads up, we're changing the events table." A shared schema, expressed in a file both sides can parse and a pipeline can check, is genuinely better than tribal memory. ODCS gives the agreement a body. It can be versioned, diffed, and validated, which is most of what a contract is supposed to enable in the first place.

What it reveals is where the actual disagreement lives. A standard can specify the fields of a contract; it cannot specify who is accountable when one breaks, who pays the cost of a migration, or how long consumers get before a column disappears. The spec has a "roles" section and an "SLA" section, which is the standard quietly admitting that ownership is the hard part and politely leaving the answer blank. The format is settled. The negotiation is not.

Watch whether organizations adopting ODCS also name a human who is on the hook when the contract is violated, with a notice period written next to the schema. A contract file with eleven well-formed sections and no enforceable owner is a very tidy way to document that nobody is responsible. The YAML is the easy 20 percent.