From fe116ad48d59a011d56c3dd79ff619955f5b8989 Mon Sep 17 00:00:00 2001 From: Claude Date: Sat, 14 Feb 2026 00:10:44 +0000 Subject: [PATCH 1/2] Add data contract definition and link both definitions to their standards - Add data contract definition sourced from Wikipedia with link to ODCS standard - Add links to ODPS standard and Wikipedia source on data product definition https://claude.ai/code/session_01QiVDE6eE8fs54Vcvo5ibfR --- data contract.md | 5 +++++ data product.md | 4 ++++ 2 files changed, 9 insertions(+) create mode 100644 data contract.md diff --git a/data contract.md b/data contract.md new file mode 100644 index 0000000..c35525e --- /dev/null +++ b/data contract.md @@ -0,0 +1,5 @@ +A **data contract** is an agreement between data producers and data consumers on the structure, format, semantics, quality, and service-level expectations of the exchanged data. It contains a detailed schema creating a link between business (logical representation of the data) and technology (its physical implementation). A data contract focuses on a single dataset, describing its tables and columns, data quality rules and their parameters, pricing, stakeholders, roles, service-level agreements (SLAs), and custom properties. Most data contracts are implemented using a YAML file, which is both human- and computer-readable and language-agnostic, making them enforceable and actionable by tools and services. A data contract is designed to be enhanced iteratively — data engineers can start with basic elements like fundamentals and schema, then over time add more information like data quality and SLAs. + +**Standard**: [Open Data Contract Standard (ODCS)](https://github.com/bitol-io/open-data-contract-standard) by [Bitol](https://bitol.io/), a Linux Foundation project. + +**Source**: [Data contract - Wikipedia](https://en.wikipedia.org/wiki/Data_contract) diff --git a/data product.md b/data product.md index d845fa1..52c8d92 100644 --- a/data product.md +++ b/data product.md @@ -1 +1,5 @@ A **data product** is a reusable, active, and standardized data asset designed to deliver measurable value to its users — whether internal or external — by applying the rigorous principles of product thinking and management. It comprises one or more data artifacts (e.g., datasets, models, pipelines) and is enriched with metadata, including governance policies, data quality rules, data contracts, and, where applicable, a Software Bill of Materials (SBOM) to document its dependencies and components. Ownership of a data product is aligned to a specific domain or use case, ensuring accountability, stewardship, and its continuous evolution throughout its lifecycle. Adhering to the FAIR principles — Findable, Accessible, Interoperable, and Reusable — a data product is designed to be discoverable, scalable, reusable, and aligned with both business and regulatory standards, driving innovation and efficiency in modern data ecosystems. + +**Standard**: [Open Data Product Standard (ODPS)](https://github.com/bitol-io/open-data-product-standard) by [Bitol](https://bitol.io/), a Linux Foundation project. + +**Source**: [Data product - Wikipedia](https://en.wikipedia.org/wiki/Data_product) From d759ccceb7729a03e10f562d388ee89920305893 Mon Sep 17 00:00:00 2001 From: Claude Date: Sat, 14 Feb 2026 00:12:31 +0000 Subject: [PATCH 2/2] Update data contract definition to match Wikipedia source Use the exact Wikipedia definition rather than a paraphrased version. https://claude.ai/code/session_01QiVDE6eE8fs54Vcvo5ibfR --- data contract.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data contract.md b/data contract.md index c35525e..0a8c70a 100644 --- a/data contract.md +++ b/data contract.md @@ -1,4 +1,4 @@ -A **data contract** is an agreement between data producers and data consumers on the structure, format, semantics, quality, and service-level expectations of the exchanged data. It contains a detailed schema creating a link between business (logical representation of the data) and technology (its physical implementation). A data contract focuses on a single dataset, describing its tables and columns, data quality rules and their parameters, pricing, stakeholders, roles, service-level agreements (SLAs), and custom properties. Most data contracts are implemented using a YAML file, which is both human- and computer-readable and language-agnostic, making them enforceable and actionable by tools and services. A data contract is designed to be enhanced iteratively — data engineers can start with basic elements like fundamentals and schema, then over time add more information like data quality and SLAs. +In data management, a **data contract** is an agreement between data producers and data consumers. It contains a detailed schema creating a link between business (logical representation of the data) and technology (its physical implementation). A data contract also describes advanced metadata, such as data quality rules, SLA, and behavior. Data contracts can take several forms, but YAML is very common. **Standard**: [Open Data Contract Standard (ODCS)](https://github.com/bitol-io/open-data-contract-standard) by [Bitol](https://bitol.io/), a Linux Foundation project.