Add OrionBelt (OBML) converter#153
Open
ralfbecher wants to merge 1 commit into
Open
Conversation
Add a bidirectional converter between the OSI semantic model format and OrionBelt's OBML (OrionBelt Markup Language) under converters/orionbelt/. - OBML -> OSI: emits OrionBelt-proprietary constructs under the ORIONBELT vendor custom_extensions; preserves third-party vendor extensions verbatim. - OSI -> OBML: restores OSI-native fields stashed under the OSI vendor on a full roundtrip; carries unrepresentable OBML topology without loss. - Also supports the OSI ontology export direction. - CLI (osi-orionbelt) with obml-to-osi / osi-to-obml subcommands, mirroring osi-dbt. - Self-contained: vendors the OSI, OBML, and OSI-ontology JSON schemas. - 120 tests, including a TPC-DS baseline against examples/tpcds_semantic_model.yaml. vendor_name is free-form in the core spec, so no specification change is required for the ORIONBELT vendor tag. Register the converter in ROADMAP.md alongside the other reference converters.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a bidirectional converter between OSI and OrionBelt's OBML (OrionBelt Markup Language) under
converters/orionbelt/, following the hub-and-spoke guidance inconverters/index.md.ORIONBELTvendor incustom_extensionsso nothing is dropped.ai_context) via anOSIvendor stash, so a full OSI to OBML to OSI roundtrip is lossless. Third-party vendor extensions (SNOWFLAKE,DBT,SALESFORCE,GOODDATA, ...) are preserved verbatim at every level.Layout
Mirrors the existing Python converters (
gooddata,dbt):src/osi_orionbelt/(converter, CLI, vendored OSI/OBML/ontology JSON schemas for self-contained builds)tests/with 120 tests, including a TPC-DS baseline againstexamples/tpcds_semantic_model.yaml(byte-identical fixture)pyproject.toml,README.md, and OBML <-> OSI mapping analysis docsCLI (
osi-orionbelt) exposesobml-to-osiandosi-to-obmlsubcommands, mirroringosi-dbt.Spec impact
None.
vendor_nameis free-form in the core spec, so theORIONBELTvendor tag needs no schema or specification change. This is a converter-only (non-spec) contribution.Notes
The canonical converter source is maintained in the orionbelt-semantic-layer repository (
packages/osi-orionbelt) and published to PyPI asosi-orionbelt(Apache-2.0). Documented limitations (many-to-many joins, named secondary join paths, ontology-layer value concepts) are carried losslessly incustom_extensionsand listed in the README.