Skip to content

This document tracks the history and evolution of the Open Data Product Standard.

v1.1.0 "Peter Flook" - APPROVED

This release is dedicated to the memory of our friend and longtime contributor Peter Flook, whose work shaped the Bitol standards — from data quality testing to schema validation, documentation, and vendor onboarding. We carry his contributions forward in this version and beyond.

  • Add optional top-level type field categorising data products by architectural alignment (e.g., sourceAligned, aggregate, consumerAligned) — RFC-0029.
  • Add optional context block at the data product and output port levels for AI / semantic interoperability (instructions, verifiedStatements, constraints) — RFC-0038, shared with ODCS v3.2.0.
  • Add optional synonyms array at the data product and output port levels, recording alternative names for catalogs, AI/LLM tools, and natural language interfaces. Each entry has a required synonym plus optional id, description, locale (BCP 47), source, status, and customProperties — RFC-0041, shared with ODCS v3.2.0.
  • Add optional deprecated boolean at the data product, input port, output port, and management port levels, signalling an element is no longer recommended for use. Defaults to false; deprecated elements remain documented and validated for backward compatibility — RFC-0051, shared with ODCS v3.2.0.
  • Add optional tags, customProperties and authoritativeDefinitions on outputPorts[].sbom[] entries, so each SBOM can be labelled, carry vendor-specific context, and link to its authoritative build record. The object stays closed (additionalProperties: false); only its property list grows, and every valid v1.1.0 document stays valid — RFC-0061.
  • Add optional vendor string on customProperties items, associating a custom property with a specific vendor, provider, or external system. SHOULD be a stable, lowercase identifier (^[a-z0-9][a-z0-9-]*$); not enforced, and tools MUST preserve unknown vendor values — RFC-0035, shared with ODCS v3.2.0 and OORS v1.0.0.
  • Standardize variable interpolation: any string value MAY contain ${VAR_NAME} references resolved at runtime by tooling, with the POSIX ${VAR_NAME:-default} form for inline defaults. Keeps secrets and environment-specific values out of the document; tools MUST resolve references before use, MUST NOT silently substitute empty strings, and MUST preserve unresolved tokens verbatim on round-trip. No new section or field — RFC-0050, shared with ODCS v3.2.0 and OORS v1.0.0.
  • Every object inside an array now carries an optional id for stable, refactor-safe references — aligned with ODCS.
  • inputPorts and outputPorts now require only name; version and contractId are optional, and sbom no longer requires url.
  • Documentation: modernize the full customer example to v1.1.0, including type and context (#15).
  • Documentation: split the standard into one page per section; document outputPorts[].inputContracts; cross-link the shared sections (team, support, custom & other properties, authoritative definitions) to their ODCS definitions.

v1.0.0 - 2025-09-24 - APPROVED

  • Add customProperties, tags and authoritativeDefinitions for outputPorts, inputPorts (top level).
  • Team structure aligned on ODCS v3.1.0.
  • AuthoritativeDefinitions type changed from enum to examples, aligned with ODCS v3.1.0.
  • Add keys in documentation where it makes sense.

v0.9.0 - 2025-07-15 - DEPRECATED

  • Approved release as v0.9.0.

v0.1.0 - 2023-09-01 - DEPRECATED

  • Very early draft, part of the discussions of creating Bitol within the Linux Foundation.