Connect Open Semantic Interchange
Put two revenue numbers next to the same definition.
How CoreModels works with Open Semantic Interchange
Open Semantic Interchange exists so semantic models can move between platforms without becoming folklore. That only helps if the interchange document is governed — versioned, imported, audited — rather than pasted into another tool’s proprietary layer.
CoreModels decodes OSI into the same model that dbt semantic manifests and warehouse contracts already use. Metrics become reusable definitions. Dimensions become shared elements. Drift is a finding when a BI extract no longer matches the interchange file.
The meeting that used to spend forty minutes on archaeology becomes a review of one governed document.
Recipes
No recipes yet for Open Semantic Interchange. The articles below still describe the problem this connector is built to close.
Uses
Problems this connector fixes
Articles that explain the gap, then point at the recipe that closes it.
Two Numbers, One Word
Someone puts a slide on the screen: revenue for the quarter, from the finance dashboard. Someone else has the same metric open in a notebook, sourced from the warehouse, and the figure differs by a little under two percent. Both are right, in the sense that each number is exactly what its definition says it is. One nets out returns; the other does not.
OutcomesA Tuesday With a Governed Semantic Model
The clearest way to describe an after-state is to walk through an ordinary day in it. Nothing dramatic happens on this Tuesday; that is the point. Here is the day, with the before-state noted each time, for a team whose Apache Ossie semantic model is a projection of a governed graph rather than a file inside one tool.
GovernanceA Definition Is a Privileged Change
There is a sentence in our own API documentation that decides how the whole surface behaves: *"`success: true` does not mean 'nothing changed.' It means 'it ran.' Always read `lossiness`."*
EcosystemThe Missing Artifact
Take the modern data stack layer by layer and ask one question of each: can I have that as a file?
AgentsWhat an Agent Decides Before It Answers
Ask an AI agent connected to a bare warehouse what revenue was last week, and watch the decisions it makes before writing a line of SQL.
QuickstartTen Minutes to Your First Apache Ossie Transform
A semantic model lands in your repository: a YAML file with datasets, fields, a primary key, and a couple of time dimensions. It is the analytics team's description of what the warehouse *means*. Now somebody needs it as a table definition, or as JSON Schema for a validator, or as the JSON serialization dbt ingests. This walkthrough takes you from that file to a converted schema with one HTTP call — and, just as importantly, to a machine-readable ledger of everything the conversion did and did not preserve.
APIThe Ossie HTTP Surface: Import, Export, Map, Replay
Four verbs cover everything you will do with an Apache Ossie semantic model through the CoreModels API, and picking the right one is mostly a question of *where the schema lives*. Is it a file you have? Import it, or map it statelessly. Is it a governed model in a CoreModels project? Export it. Do you need the same conversion again next month, byte for byte? Replay a stored plan.
MCP"Convert Our Semantic Model for dbt" — Ossie Through the transform_schema Tool
Here is the request, as an analyst actually phrases it: *"Take the billing semantic model in our repo, give me the JSON form our dbt project ingests, and tell me what didn't survive the conversion."*
AutomationOssie Conversions That Belong in CI: Plans as Artifacts, Ledgers as Gates
Run an Ossie conversion twice and diff the two outputs. If the bytes differ, the conversion cannot live in a pipeline — you would be re-reviewing generated files every build. CoreModels (by ARAMAI) gives you the other answer, and it comes from three deliberate design choices: the encoder is hand-written with fixed key order, the mapping plan is returned as an artifact you can store, and replaying a stored plan runs the same validation gate as the call that produced it.
Deep diveEvery Key, Every Record: How the Ossie Coder Maps to the IR
An Apache Ossie semantic model and a typed intermediate representation disagree about the world in one fundamental way: an Ossie field has no type. It is a name, an optional expression, an optional description, and optional dimension metadata. The IR that CoreModels (by ARAMAI) moves schemas through is typed, and so is every neighboring format — SQL, Avro, JSON Schema, LinkML.