Converts an MSI SemanticManifest into an Ossie Document.

Converts an Ossie Document into a PydanticSemanticManifest. The conversion is inherently lossy: Ossie stores metrics as raw SQL expressions a

Raised when an input cannot be converted.

Raised when an Ossie YAML cannot be converted to Snowflake format.

Raised when conversion between OSI and Honeydew fails.

Row-level attribute for grouping, filtering, and metric expressions.

Convert an OBML semantic model YAML to OSI format.

Collects schema errors, semantic errors, and warnings.

Records a single instance of information loss during conversion.

Return value of a converter's convert() method, pairing the output with any conversion issues.

Logical dataset representing a business entity (fact or dimension table).

Expression in a specific dialect.

Dimension metadata on a field.

Root Ossie document.

Expression definition with multi-dialect support.

Quantitative measure defined on business data.

Foreign key relationship between datasets.

Top-level container representing a complete semantic model.

Convert an OSI semantic model YAML to OBML format.

The `Rnd` interface backed by a seeded `random.Random`.

The Rnd interface driven by hypothesis' `data` strategy.

Hands out globally-unique names with a given prefix.

Derive an OSI **ontology** document from an OBML semantic model. Produces a document conforming to ``osi-ontology-schema.json`` (OSI version

Abstract base class for converters that provides common functionality for YAML and JSON conversion with property mapping support.

Enum representing the direction of conversion.

Exception thrown when a conversion operation fails. This can happen during YAML to JSON or JSON to YAML conversion.

Interface for converting between data formats (YAML and JSON). <p>This is the external API for conversion. Implementations handle the conversion of d

Constants used across converters for property names and structure keys.

Factory for creating converters based on conversion direction.

Unified converter that executes pipelines configured in osi-salesforce-converter-config.yaml.

Identifies the kind of information loss that occurred during conversion.

Handler for adding and restoring custom_extensions in the Semantic Model. <p>Handles identifying unmapped properties during Salesforce-to-Ossie conve

Utility class for working with generic Map/List data structures. Provides type-safe accessors to reduce casting boilerplate.

Bidirectional handler for mapping datasets between Ossie and Salesforce formats. <p>Supports both conversion directions: <ul> <li>Ossie → Salesforc

Configuration for a specific conversion direction.

Helper record to return expression value along with its dialect type.

Bidirectional handler for mapping fields between Ossie and Salesforce formats. <p>Ossie → SF: Maps dataset fields to SemanticDimensions and SemanticM

Enum representing the four possible field types in Salesforce Semantic Model.

Property mapper that loads mappings from a YAML configuration file. <p>This mapper reads the bundled mappings.yaml which defines Ossie-Salesforce pro

Simplified mapping engine that applies straightforward property mappings from mappings.yaml. <p>Supports: - Simple property mappings (apiName -> name

Factory for creating handler instances using a hardcoded registry. pipeline configuration specifies which handlers to run and in what order.

Exception thrown when the input is invalid. This includes cases where the file does not exist, is not readable, or if the file/String contains invalid

Enum representing the level at which custom extensions can be stored or restored.

Utility class for filtering and processing property mappings.

Bidirectional handler for mapping metrics between Ossie and Salesforce formats. <p>Supports both conversion directions: <ul> <li>Ossie → Salesforce

Structured AI context with instructions, synonyms, and examples.

Vendor-specific metadata as a serialized JSON string.

Supported SQL and expression language dialects.

Well-known vendor names for custom extensions.

Java representation of an Ossie semantic model parsed from YAML.

Parses an Ossie YAML file into an {@link OsiModel}.

CLI entry point for the Ossie Polaris converter. <p> Supports two modes: <ul> <li><b>import</b>: Reads from a Polaris catalog and generates an Ossie

Main application class for the Ossie-Salesforce Converter. <p>Converts between Salesforce Semantic Model and Ossie formats. Output file is placed in

Comprehensive integration test for Ossie → Salesforce conversion. Uses real example file: osiToSalesforce.yaml

Generates Ossie YAML from an {@link OsiModel}. <p> Produces well-formatted YAML that conforms to the Ossie specification.

Utility class for working with nested property paths. <p>Provides methods for getting and setting values in nested maps using dot-notation paths (e.g

Root configuration model matching pipeline-config.yaml structure.

Loads pipeline configuration from YAML. Uses Jackson to deserialize osi-salesforce-converter-config.yaml into PipelineConfig model.

Base interface for pipeline steps. Both mapping handlers and special wrapper steps implement this interface.

REST client for the Apache Polaris catalog. <p> Polaris implements the Iceberg REST Catalog specification. This client communicates with the catalog e

Exports an Ossie semantic model to an Apache Polaris catalog. <p> Creates namespaces and Iceberg tables in Polaris based on the Ossie model's datasets

Imports Apache Polaris catalog metadata into an Ossie semantic model. <p> Reads namespaces and tables from a Polaris catalog via the Iceberg REST API,

Interface for mapping properties between Ossie and Salesforce formats during conversion. <p>Implementations of this interface define bidirectional ma

Bidirectional handler for mapping relationships between Ossie and Salesforce formats. <p>Supports both conversion directions: <ul> <li>Ossie → Sale

Helper record to return updated data object arrays.

Comprehensive integration test for Salesforce → Ossie conversion. Uses real example file: salesforceToOsi.json

Validates Ossie semantic model data against JSON Schema. <p>Uses networknt/json-schema-validator for schema validation. Collects all validation error

Bidirectional handler for mapping top-level semantic model properties. <p>Supports both conversion directions: <ul> <li>Ossie → Salesforce: name →

Column properties roundtrip. Note: OSI uses column *code* as field name, so after roundtrip the OBML column keys become the physical codes (A