HypothesisVery high confidenceCurrent
No single open standard currently covers contracts, discovery, runtime lineage, CDC checkpoints, profiling, deletion and connector conformance.
Dataheart needs a small standards composition and translation layer.
Valid from2026-08-23
Last reviewed2026-08-23
Review again2026-11-21
Dataheart stanceexploring
Evidence for
ODCS covers contract structure.
Open Data Contract Standard 3.1.0 · github.com ↗W3C DCAT Version 3 · w3.org ↗OpenLineage object model · openlineage.io ↗Apache Arrow ADBC · arrow.apache.org ↗DCAT covers catalog exchange.
Open Data Contract Standard 3.1.0 · github.com ↗W3C DCAT Version 3 · w3.org ↗OpenLineage object model · openlineage.io ↗Apache Arrow ADBC · arrow.apache.org ↗OpenLineage covers runtime lineage facets.
Open Data Contract Standard 3.1.0 · github.com ↗W3C DCAT Version 3 · w3.org ↗OpenLineage object model · openlineage.io ↗Apache Arrow ADBC · arrow.apache.org ↗ADBC covers analytical database access but not CDC.
Open Data Contract Standard 3.1.0 · github.com ↗W3C DCAT Version 3 · w3.org ↗OpenLineage object model · openlineage.io ↗Apache Arrow ADBC · arrow.apache.org ↗Debezium and Iceberg supply implementation-specific change and storage semantics.
Open Data Contract Standard 3.1.0 · github.com ↗W3C DCAT Version 3 · w3.org ↗OpenLineage object model · openlineage.io ↗Apache Arrow ADBC · arrow.apache.org ↗Evidence against
Individual metadata platforms increasingly bundle several of these capabilities behind one API.
Open Data Contract Standard 3.1.0 · github.com ↗W3C DCAT Version 3 · w3.org ↗OpenLineage object model · openlineage.io ↗Apache Arrow ADBC · arrow.apache.org ↗How this claim can fall
Replace this placeholder during human review with an observable result that would materially weaken or falsify the claim.
A published claim remains useful only while it remains possible to prove it wrong.