Announcing ODPS v1.0.0

We are thrilled to announce the release of version 1.0.0 of the Open Data Product Standard (ODPS): a major milestone in shaping how the industry defines, shares, and manages data products.

ODPS is part of the Bitol initiative at the Linux Foundation, alongside the Open Data Contract Standard (ODCS). Together, these standards aim to provide a common foundation for modern data engineering: enabling interoperability, governance by design, and trust in data across organizations and industries.

Why ODPS Matters

Data products are quickly becoming the unit of value in modern data ecosystems. Without a standard, each organization reinvents its own definitions, making collaboration, discovery, and reuse difficult.

ODPS solves this by providing:

• A shared vocabulary for describing what a data product is.

• Interoperability across platforms, vendors, and organizations.

• Built-in alignment with data contracts (ODCS) to ensure that data products are not just technical assets, but governed, trustworthy entities.

• Extensibility, so organizations can adapt the standard to their needs while staying connected to a common core.

With ODPS, we move from ad-hoc, one-off data products to a sustainable, scalable ecosystem.

Bitol Governance

ODPS is governed through the Bitol Technical Steering Committee (TSC) under the Linux Foundation. This model ensures that:

• The standard is developed openly, with complete transparency.

• Decisions are made collectively, balancing input from industry, academia, and practitioners.

• No single vendor controls the standard — instead, it evolves through community consensus.

• Long-term stewardship is ensured by the Linux Foundation’s neutral governance framework, which has already proven its success in projects such as Kubernetes and OpenTelemetry.

This governance model provides organizations with confidence that ODPS will remain open, stable, and vendor-neutral, while continually improving to meet the evolving needs of adopters. Many thanks to Andrea Gioia, Andrew Jones, Andy Petrella, Atanas Iliev, Diego Carvallo, Dirk Van de Poel, Gene Stakhov, Jean-Georges Perrin, Jochen Christ, Manuel Destouesse, Martin Meermeyer, Peter Flook, Simon Harrer, Tom De Wolf, and all the volunteers.

A Word from Jean-Georges “jgp” Perrin, Chair of the Bitol TSC

“ODPS v1.0.0 is the result of years of exploration, iteration, and community effort. Starting from early drafts, through the proof-of-concept release in v0.9.0, to today’s stable milestone, we’ve worked toward one goal: giving organizations a practical, open, and extensible way to define data products. By aligning ODPS with ODCS, we are bridging the gap between data products and data contracts, the two pillars of modern, trustworthy data ecosystems.”

What’s Next

ODPS v1.0.0 is just the beginning. The Bitol community will continue to evolve the standard with:

• Real-world feedback from adopters.

• Tooling and reference implementations.

• Integration with catalogs, marketplaces, and control planes.

• Ongoing collaboration with industry partners, academics, and open-source contributors.

We invite everyone to explore ODPS v1.0.0, join the conversation, and help shape the future of open data standards. Learn more at bitol.io.

A Brief History of ODPS

The journey to v1.0.0 has been an iterative, community-driven effort:

• v0.1.0 (2023-09-01)

  An early draft capturing the first ideas of what a data product specification could look like. At this stage, ODPS was mostly exploratory — a way to test assumptions and start conversations about how to formally describe data products.

• v0.9.0 (2025-07-15)

  The first approved release marked ODPS as stable enough to test in real-world scenarios. While still “pre-1.0,” v0.9.0 provided the scaffolding:

  • Clearer structure for describing data products.

  • A governance framework aligned with ODCS.

  • Community validation through proof-of-concepts and pilots.

    This release was about proving that a data product standard was not only possible, but necessary.

• v1.0.0 (2025-09-24)

  Today’s milestone. With community feedback, hands-on experiments, and alignment with ODCS v3.1.0, ODPS now enters full maturity:

  • Custom properties & tags for input and output ports.

  • Authoritative definitions aligned with ODCS, moving from rigid enums to practical examples.

  • Improved documentation keys for clarity and usability.

  • Team and governance structures aligned with ODCS v3.1.0, ensuring consistency across standards.