Data Readiness
Knowledge BaseLife-sciences R&D
54 profiles ·
source-checked 13 Jul 2026

Data model / schema · Living specification · documentation 1.50.0

OpenLineage

Maintained by OpenLineage project

What it helps you do

Use OpenLineage when you need runtime and design-time events for jobs, runs, and datasets, with extensible facets for source code, schemas, versions, quality metrics, assertions, and other lineage context.

  • AI / ML
  • Cross-cutting
PlanAcquireHarmonizeExchangeLearn + reuse

01

Where it fits—and where it doesn’t

Use these four checks before committing implementation time.

Use it when
Operational lineage instrumentation across ETL, ELT, laboratory, feature-engineering, and model-data pipelines.
Do not use it as
Do not treat OpenLineage as a complete solution on its own. Lineage is only as complete as its instrumentation; inconsistent naming, missing events, facet-version drift, and backend retention can leave an incomplete history.
Best for
Teams working with AI / ML and Cross-cutting data across Acquire → Harmonize → Exchange → Learn + reuse.
Maturity
ScalingUsable today, with adoption or tooling still scaling; pilot the exact stack you plan to run.

02

See it in the workflow

A standard creates value by changing a handoff, not by existing in a catalog.

  1. InputWhat starts

    AI / ML and Cross-cutting data, metadata, and the local decisions around them

  2. OpenLineageWhat changes

    OpenLineage applies a shared data model / schema across Acquire → Harmonize → Exchange → Learn + reuse

  3. OutputWhat becomes possible

    A more consistent, reviewable handoff for the next system or team

Readiness gateBefore scaling: Lineage is only as complete as its instrumentation; inconsistent naming, missing events, facet-version drift, and backend retention can leave an incomplete history.

03

A concrete example

An orchestrated transformation emits stable job, run, and dataset identities plus source revision, input and output versions, schemas, quality assertions, and lifecycle events to a lineage backend.

Why it matters: Supports dataset and feature traceability and quality evidence, but does not establish scientific semantics, consent, label validity, or model fitness.

04

What it fits with

Provides event capture that can feed a PROV-O graph; snapshots and summaries can be linked from RO-Crate, DataCite, DQV, or catalog metadata.

05

Implementation starter

Start with one bounded handoff. Pin, test, and review it before scaling.

  1. Name an accountable owner and the decision OpenLineage must support.

  2. Pin the exact version and companion artifacts: Living specification · documentation 1.50.0.

  3. Map one representative input to the required data model / schema artifacts.

  4. Test the result against the canonical source and record every exception.

  5. Preserve the source data, mappings, and review evidence before scaling.

06

Limitation to test first—and the tests that catch it

Risk

Lineage is only as complete as its instrumentation; inconsistent naming, missing events, facet-version drift, and backend retention can leave an incomplete history.

Test

Run one representative end-to-end pilot and record exactly where OpenLineage loses context, needs an extension, or depends on another standard.

Risk

A structured or machine-readable result can still be unfit for analysis or AI.

Test

Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Supports dataset and feature traceability and quality evidence, but does not establish scientific semantics, consent, label validity, or model fitness.

07

Why we believe this

Checked against the canonical source plus implementation or adoption evidence reported by the steward or its community.

Evidence notation: E1 + E3. The code is shorthand; the plain-language statement above is the claim.

Formal status
Actively maintained living specification · documentation 1.50.0
Confidence
Medium
Review state
Source-checked · watch
Reviewed by
Operational lineage reviewer
Last verified
13 July 2026
Review again when
Core event, facet, naming, or compatibility release
How the evidence method works

08

Source shelf

Official diagrams, examples, specifications, and explainers. Nothing external loads until you choose to open it.

  • Primary sourceLiving specification · documentation 1.50.0

    OpenLineage 1.50.0 object model

    The canonical publisher or steward source used to verify this data model / schema profile.

    Publisher
    OpenLineage project
    Rights
    Rights remain with the publisher; this knowledge base links to the source rather than copying it.
    Access
    Opens the publisher's source in a new tab; no external media loads on this page.
    Verified
    2026-07-13
    Open at source

Next action

Put this profile in context

Compare its role with adjacent standards or place it inside an end-to-end data pathway before choosing an implementation.