Back to home

    Schema Formats

    Bring any schema, from any source

    Every ingested schema is normalized into Magellan's unified MetaModel and stamped with a SchemaIngested ledger entry — so the same Semantic Match, lineage edge derivation, and ULID‑keyed audit trail apply whether the source was Avro, JDBC, or a proprietary Erwin XML.

    Compare schema formats

    Every adapter normalizes into the same MetaModel and writes to the same ULID-keyed, SHA-256 hash-chained ledger. The differences below are the ones that matter when you choose how to feed Magellan from a given source system.

    Avro
    Typed
    Yes
    Nested
    Yes

    Ingest direction

    File uploadStream

    Ledger entries

    SchemaIngestedSchemaParsedSchemaEvolutionEvaluated
    XML Schema (XSD 1.0 / 1.1)
    Typed
    Yes
    Nested
    Yes

    Ingest direction

    File upload

    Ledger entries

    SchemaIngestedSchemaParsedSchemaEvolutionEvaluated
    JSON Schema (drafts 4 → 2020-12)
    Typed
    Yes
    Nested
    Yes

    Ingest direction

    File uploadPull (live)

    Ledger entries

    SchemaIngestedSchemaParsedExternalRefResolved
    Excel (.xlsx / .xls)
    Typed
    Partial
    Nested
    No

    Ingest direction

    File upload

    Ledger entries

    SchemaIngestedSchemaParsedColumnProfileApplied
    Erwin XML
    Typed
    Yes
    Nested
    Yes

    Ingest direction

    File upload

    Ledger entries

    SchemaIngestedSchemaParsedDomainResolvedSchemaEvolutionEvaluated
    JDBC (live introspection)
    Typed
    Yes
    Nested
    No

    Ingest direction

    Pull (live)

    Ledger entries

    SchemaIngestedSchemaParsedConnectionProfileResolvedSchemaEvolutionEvaluated
    Custom Import
    Typed
    Partial
    Nested
    Partial

    Ingest direction

    Pluggable

    Ledger entries

    SchemaIngestedSchemaParsedImporterModuleRegistered

    Avro

    Apache Avro schemas — including unions, enums, logical types, and nested records — are parsed into the Magellan MetaModel and stamped with a SchemaIngested entry carrying the SHA‑256 of the raw .avsc bytes.

    Read more

    XML Schema

    W3C XML Schema (XSD 1.0 and 1.1) is parsed into the MetaModel preserving complex types, substitution groups, and identity constraints — with namespace fidelity, so HL7 v2.xml, FHIR XML, and HIPAA X12-derived XSDs round-trip cleanly.

    Read more

    JSON Schema

    JSON Schema drafts 4, 6, 7, 2019-09, and 2020-12 are parsed into the MetaModel preserving `$ref`, `oneOf`/`anyOf`/`allOf`, conditional `if`/`then`/`else`, and `$defs` — with full keyword resolution and a SchemaIngested entry per ingest.

    Read more

    Excel

    Excel mapping spreadsheets (.xlsx and .xls) — the common form an enterprise data team already maintains — are parsed into the MetaModel using a configurable column-to-attribute layout, with each ingest stamped to the ledger.

    Read more

    Erwin XML

    Erwin Data Modeler XML repository exports are parsed into the MetaModel preserving entities, attributes, domains, subject areas, and physical-to-logical mappings — so existing enterprise data models become governed Magellan assets without re-modeling.

    Read more

    JDBC

    Live JDBC introspection captures tables, views, columns, primary keys, foreign keys, indexes, and column-level statistics from the actual database — with read-only credentials and a SchemaIngested entry per scan.

    Read more

    Custom Import

    A documented ImportAdapter interface lets teams ingest proprietary, legacy, or niche formats into the MetaModel — with the same Semantic Match, lineage derivation, audit ledger, and draft/publish workflow as the built-in adapters.

    Read more