Author an ODCS v3 Data Contract
From governed model to Bitol Open Data Contract Standard - no retyping.
A neutral hub between fourteen schema formats, with an honest lossiness ledger.
Recipes
Recipes for Schema Converter
From governed model to Bitol Open Data Contract Standard - no retyping.
A neutral hub between fourteen schema formats - start empty or seed it with a schema.
From the JSON world's common tongue to CREATE TABLE - in your dialect.
The LinkML-to-Synapse toolchain every DCC currently hand-builds - with the subset losses declared.
Move a contract across the registry triad without retyping it.
Export your governed meaning as osi-json - the serialization dbt ingests.
schematic sunsets at the end of 2026. Migrate your data model with a fidelity report, not a rewrite.
Connector summary
Start a conversion project and CoreModels decodes a schema into its neutral model, then encodes it into another format.
Every translation ships a lossiness ledger: what was preserved, what was approximated, and what could not travel.
CoreModels conversion is not a best-effort pretty-printer. Decode understands JSON Schema, ShEx, Avro, JSON-LD, SQL, OSI, OWL, LinkML, Protobuf, ODCS, and ODM. Encode covers the same set minus ODM (entity docs are authored, not generated), and adds Synapse as encode-only draft-07 JSON Schema.
Recipes cover the conversions teams actually fight: JSON Schema to SQL, LinkML to Synapse, Protobuf to Avro, semantic models to dbt, Synapse schema migration, and ODCS contract authoring. Each run lands in a project you can audit, map, and regenerate.
If you only need a one-off file, you will still get the ledger. If you need a pipeline, the same project becomes the place later translations are checked against.
Guides
Articles that explain the gap, then point at the recipe that closes it.
Use articles for Schema Converter will appear here as they are published.