Add data contract definition and link both definitions to their standards

data contract.md

@@ -0,0 +1,5 @@
+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.
+
+**Source**: [Data contract - Wikipedia](https://en.wikipedia.org/wiki/Data_contract)

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)