HypothesisVery high confidenceCurrent
A glossary or ontology improves shared terminology but does not govern executable metric behavior without a metric contract and runtime.
Link concept identities to executable metrics.
Valid from2026-08-23
Last reviewed2026-08-23
Review again2026-11-21
Dataheart stanceexploring
Evidence for
SKOS defines labels, semantic relations and mappings rather than analytical evaluation.
W3C SKOS Reference · w3.org ↗ISO/IEC 11179-31:2023, data specification registration · iso.org ↗MetricFlow metric semantics · github.com ↗ISO 11179 separates concepts, value domains and derivation metadata from physical execution.
W3C SKOS Reference · w3.org ↗ISO/IEC 11179-31:2023, data specification registration · iso.org ↗MetricFlow metric semantics · github.com ↗MetricFlow separately defines evaluation scope, dimensions, entities and filters.
W3C SKOS Reference · w3.org ↗ISO/IEC 11179-31:2023, data specification registration · iso.org ↗MetricFlow metric semantics · github.com ↗Evidence against
Formal ontologies can validate or infer parts of an analytical model.
W3C SKOS Reference · w3.org ↗ISO/IEC 11179-31:2023, data specification registration · iso.org ↗MetricFlow metric semantics · github.com ↗A glossary can substantially improve discovery and stewardship.
W3C SKOS Reference · w3.org ↗ISO/IEC 11179-31:2023, data specification registration · iso.org ↗MetricFlow metric semantics · github.com ↗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.