Data Readiness
Knowledge BaseLife-sciences R&D
93 profiles ·
practical standards guide

Ontology / data model · 2.2 · W3C Recommendation · 2018-02-15

W3C ODRL Information Model

Maintained by W3C

What it helps you do

ODRL supports policies containing permissions, prohibitions, duties, parties, assets, constraints, inheritance, and conflict strategies.

  • AI / ML
  • Cross-cutting
PlanAcquireHarmonizeExchangeLearn + reuse

01

Where it fits and where it does not

Use these four checks before committing implementation time.

Use it when
Machine-readable usage conditions for datasets and distributions, including research-purpose, redistribution, attribution, retention, and temporal or jurisdictional constraints.
Limits
A syntactically valid policy does not prove the assigner has authority, make the policy legally enforceable, or provide the system that evaluates and enforces it.
Best for
AI / ML and Cross-cutting teams working across Plan → Exchange → Learn + reuse.
Maturity
EstablishedSuitable for production assessment. Pin the exact release and any implementation profile.

02

See it in the workflow

This view shows the input, the change the standard introduces, and the resulting output.

  1. InputWhat starts

    AI / ML and Cross-cutting source data, metadata, and local mappings

  2. ODRLWhat changes

    Use ODRL as a pinned ontology / data model across Plan → Exchange → Learn + reuse

  3. OutputWhat becomes possible

    A handoff the next system or team can validate against the same release

Readiness gateA syntactically valid policy does not prove the assigner has authority, make the policy legally enforceable, or provide the system that evaluates and enforces it.

03

A concrete example

A controlled dataset links a versioned ODRL policy stating permitted research, prohibited re-identification or redistribution, applicable constraints, and duties such as attribution, deletion, or reporting.

Why it matters: Supports agent-readable use screening and obligations, while accountable approval and technical enforcement remain separate controls.

04

What it fits with

Profiles can reuse DPV privacy concepts and DUO biomedical use terms; DCMI terms describe policy metadata, while DCAT or RO-Crate can link policies to assets.

05

Implementation starter

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

  1. Define one handoff, its accountable owner, and the decision ODRL must support.

  2. Pin the exact version and companion artifacts: 2.2 · W3C Recommendation · 2018-02-15.

  3. Map one representative input to the required ontology / data model 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

Test the main limitation

Risk

A syntactically valid policy does not prove the assigner has authority, make the policy legally enforceable, or provide the system that evaluates and enforces it.

Test

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

Risk

Machine-readable output may still be unfit for analysis or ML.

Test

Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Supports agent-readable use screening and obligations, while accountable approval and technical enforcement remain separate controls.

07

Official resources

Specifications, diagrams, examples, and guides from the organizations that maintain them.

  • Primary source2.2 · W3C Recommendation · 2018-02-15

    W3C ODRL Information Model 2.2

    Official publisher or steward guidance for this ontology / data model profile.

    Publisher
    W3C
    Open official 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.