Add Ossie → wisdom domain export direction#14
Closed
mwu-wisdom wants to merge 3 commits into
Closed
Conversation
Adds converters/wisdom, a one-way converter from a WisdomAI domain export JSON (format 1.0) to an Ossie semantic model YAML, following the layout of the dbt converter. Mapping: domain -> semantic model; domain knowledge and system instructions -> model-level ai_context; tables/columns/formulas -> datasets/fields; relationship graph -> relationships (cardinality folded into edge direction, compound AND-joins flattened to composite keys); per-table measures -> model-level metrics. Expressions are emitted verbatim under the dialect mapped from the table's connection (snowflake, databricks), falling back to ANSI_SQL with a warning for unsupported dialects. Information loss is reported through the same ConverterResult/ConverterIssue pattern as ossie-dbt. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Adds WISDOM to the OSIVendor enum, the vendor examples in the spec documents and JSON schema, and the supported-vendors table in the converter guide. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Adds osi-to-wisdom, the reverse of the wisdom converter: an Ossie document becomes a wisdom domain export (format 1.0) consumable by wisdom's importDomain API. The mapping inverts wisdom-to-osi so round-trips are stable in both directions: model ai_context splits back into system instructions and knowledge items, fields split into columns and formulas, relationship direction is read as many-to-one with ai_context notes restoring one-to-one/many-to-many and composite keys becoming compound AND join conditions, and metrics attach to the table their expression references. IDs are deterministic (derived from names) and connections are per-dialect placeholders remapped at import time. Verified: Ossie -> wisdom -> Ossie round-trips of two real domain exports are byte-identical. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Author
|
Folding this into #13 as a single PR covering both directions — the reverse converter edits files introduced there, so they can't be reviewed independently. |
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.
Note
Stacked on #13 — review only the top commit (
Add Ossie -> wisdom domain export direction); the first two commits belong to #13. I'll rebase this branch once #13 merges.What
Adds the reverse direction to the wisdom converter:
ossie-wisdom osi-to-wisdom -i semantic_model.yaml -o domain-export.jsonturns an Ossie document into a WisdomAI domain export (format1.0) that wisdom'simportDomainAPI can consume.Design
The mapping is the exact inverse of
wisdom-to-osi, so round-trips are stable in both directions:ai_contextsplits back intodomainSystemInstructions(leading text) + one knowledge item per-bullet.dimension.is_timemaps to aTIMESTAMPdata type (wisdom re-derives exact types from the warehouse).MANY_TO_ONEedges (Ossie'sfrom= many side); theai_contextnotes written by the import direction restoreONE_TO_ONE/MANY_TO_MANY, and composite keys become compoundANDjoin conditions.METRIC_TABLE_UNRESOLVEDwarning).et-connection-snowflake, …) expected to be remapped at import.ConverterIssuepattern: semantic models beyond the first,unique_keys,custom_extensions, andai_contexton fields/metrics (plus synonyms/examples anywhere).Testing
OSI → wisdom → OSIyields an identicalOSIDocument) and determinism of the emitted export.OSI → wisdom → OSIround-trips are byte-identical YAML for both.