Data model / schema · 1.3 Recommendation · 2026-06-22

RO-Crate

Maintained by Research Object community

What it helps you do

Use RO-Crate when you need a JSON-LD metadata document that aggregates data, code, workflows, people, instruments, and contextual entities into a research object.

  • Discovery
  • Omics
  • Cross-cutting
PlanAcquireHarmonizeExchangeLearn + reuse

01

Where it fits—and where it doesn’t

Use these four checks before committing implementation time.

Use it when
Portable dataset packages, workflow exchange, preservation, publication, and handoff between repositories and compute environments.
Do not use it as
Do not treat RO-Crate as a complete solution on its own. Core conformance is deliberately lightweight; interoperability depends on shared profiles and validation beyond the base crate.
Best for
Teams working with Discovery and Omics and Cross-cutting data across 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

    Discovery and Omics and Cross-cutting data, metadata, and the local decisions around them

  2. RO-CrateWhat changes

    RO-Crate applies a shared data model / schema across Exchange → Learn + reuse

  3. OutputWhat becomes possible

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

Readiness gateBefore scaling: Core conformance is deliberately lightweight; interoperability depends on shared profiles and validation beyond the base crate.

03

A concrete example

A model-training release packages source datasets, preprocessing workflow, environment, outputs, authors, license, and citations.

Why it matters: Bundles the context an agent needs to inspect and reuse a dataset or workflow, but does not standardize table-level ML semantics.

04

What it fits with

Uses Schema.org and Bioschemas terms; profiles add workflow-run or domain detail; PROV-O can deepen lineage.

05

Implementation starter

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

  1. Name an accountable owner and the decision RO-Crate must support.

  2. Pin the exact version and companion artifacts: 1.3 Recommendation · 2026-06-22.

  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

Core conformance is deliberately lightweight; interoperability depends on shared profiles and validation beyond the base crate.

Test

Run one representative end-to-end pilot and record exactly where RO-Crate 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. Bundles the context an agent needs to inspect and reuse a dataset or workflow, but does not standardize table-level ML semantics.

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
Community Recommendation 1.3
Confidence
Medium
Review state
Source-checked · watch
Reviewed by
Research-object packaging reviewer
Last verified
13 July 2026
Review again when
Core erratum or workflow/domain profile update
How the evidence method works

08

Source shelf

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

  • Primary source1.3 Recommendation · 2026-06-22

    RO-Crate 1.3 specification

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

    Publisher
    Research Object community
    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.