ODPS (BITOL @ LF)
Open Data Product Standard
Judgement: Adopt
Winning data-product spec; ODCS-aligned.
YAML standard for describing data products. Mirrors ODCS on fundamentals, ownership, and terms, and adds input ports, output ports, and management ports.
Each port references an ODCS contract. Combined, ODCS + ODPS yield the full data-mesh dependency graph — consumers, products, sources — derived directly from YAML.
Acronym collision: "ODPS" is also used for the Open Data Product Specification, a separate LF project. Both display as ODPS here — disambiguate by governance (BITOL vs opendataproducts.org).
Example
A data product: input ports it consumes, output ports it promises, each bound to a data contract.
apiVersion: v1.0.0
kind: DataProduct
id: fbe8d147-28db-4f1d-bedf-a3fe9f458427
name: Customer Data Product
domain: seller
status: draft
description:
purpose: Enterprise view of a customer.
inputPorts:
- name: payments
version: 1.0.0
contractId: dbb7b1eb-7628-436e-8914-2a00638ba6db
outputPorts:
- name: rawtransactions
description: "Raw Transactions"
type: tables
version: v1.0.0
contractId: c2798941-1b7e-4b03-9e0d-955b1a872b32
At a glance
- Category
- Data Products
- Governance
- BITOL / Linux Foundation
- Status
- v1.0
- First released
- 2025
Links
Related standards
Other standards in Data Products.
- DPDS — Data Product Descriptor Specification
- DPROD — Data Product Vocabulary (DPROD)
- ODPS (LF) — Open Data Product Specification
See ODPS in context
Open the interactive Data Landscape to compare ODPS against every other open standard, or grab the raw JSON. Spotted something wrong? Open an issue.