HypothesisVery high confidenceCurrent
A common semantic-model file format does not by itself guarantee equal results across analytical runtimes.
Define an explicit portable subset.
Valid from2026-08-23
Last reviewed2026-08-23
Review again2026-11-21
Dataheart stanceexploring
Evidence for
Ossie 0.2 permits multiple expression dialects and arbitrary vendor extensions.
Apache Ossie core metadata specification · github.com ↗Apache Ossie Incubator proposal · cwiki.apache.org ↗Power BI relationship semantics · learn.microsoft.com ↗The Ossie roadmap still lists a formal metrics language, semantic query standard and reference query engines as future work.
Apache Ossie core metadata specification · github.com ↗Apache Ossie Incubator proposal · cwiki.apache.org ↗Power BI relationship semantics · learn.microsoft.com ↗Power BI calculation results depend on runtime-specific filter and relationship semantics.
Apache Ossie core metadata specification · github.com ↗Apache Ossie Incubator proposal · cwiki.apache.org ↗Power BI relationship semantics · learn.microsoft.com ↗Evidence against
A sufficiently narrow expression subset with identical source data can be portable.
Apache Ossie core metadata specification · github.com ↗Apache Ossie Incubator proposal · cwiki.apache.org ↗Power BI relationship semantics · learn.microsoft.com ↗A single shared execution engine can provide consistency to multiple consumer tools.
Apache Ossie core metadata specification · github.com ↗Apache Ossie Incubator proposal · cwiki.apache.org ↗Power BI relationship semantics · learn.microsoft.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.