The future of data contracts: Standardizing Access, Tracking Change, and Embracing Openness
Data contracts are evolving. Open Data Contract Standard (ODCS) is evolving too. A recent meeting of Bitol* (Linux Foundation AI & Data Sandbox project) TSC** members saw lively debate and voting on proposals to shape the next iteration: ODCS Version 3.0
Discussions focused on improving clarity, traceability, and interoperability.
A key issue was streamlining data access. Suggestions included separating data access information into its own section. This would make it easier for users to find what they need. Another critical area was data typing. Distinguishing between logical and physical data types could improve data interpretation and reduce ambiguity. The terminology used in data contracts was also on the table. Replacing “stakeholders” with “product team structure” was suggested to better reflect the modern collaborative data management landscape. A hierarchical approach to data descriptions was suggested, which could improve organization and navigation. Another suggestion was version tracking at the field level, which would allow users to identify specific changes within a data contract over time. Interoperability was also discussed, with the idea of allowing data contracts to reference values from other contracts. This would streamline data exchange and reduce redundancy. Openness was also an important theme. Suggestions included using open data standards and referencing upstream data contracts. These encourage collaboration and wider adoption of standard data practices.
The final decisions.
Are to be announced, but the discussions highlight ongoing efforts to refine data contracts. Standardizing access methods, enabling efficient change tracking, and embracing open standards are all important steps toward a more robust data exchange ecosystem.
Members of the Technical Steering Committee
In alphabetical order by first name.
• Andrew Jones, GoCardless, GMT
• Atanas Iliev, atanas@aida.org, Central European Time
• Dieter Wachters, dieter@raito.io, Raito, Central European Time
• Dirk Van de Poel, dirk.vandepoel@klarrio.com, Klarrio, Central European Time
• Gene Stakhov, gstakhov@gmail.com, enChoice, Eastern Standard Time
• Jean-Georges Perrin (Chair), jgp@…, AbeaData, Eastern Standard Time
• Jochen Christ, jochen.christ@innoq.com, INNOQ, Central European Time
• Manuel Destouesse, mdsoftengr@gmail.com, itracHealth, Eastern Standard Time
• Martin Meermeyer, m.meermeyer@gmail.com, Lidl e-commerce, Central European Time
• Peter Flook, peter.flook@data.catering, Data Catering, Taipei Standard Time
• Simon Harrer, simon.harrer@innoq.com, INNOQ, Central European Time
More resources to explore:
You can check all RFCs suggested by our working group on
We share with you our TSC meetings. They are not public, but open to all of our followers.
Authors notes:
*Bitol — https://bitol.io/
** TSC — Technical Steering Committee
