Skip to main content

DMP Interoperability Framework

Making Data Management Plans machine-actionable

The DMP-IF turns Data Management Plans from static documents into living, machine-readable connectors that link repositories, services, and tools, so data management happens continuously, not just once at the start of a project.

Today: A one-time document

A DMP is typically a PDF filled in at the start of a project to satisfy a funder. It goes stale immediately and has no connection to actual data workflows.

With DMP-IF: A living hub

A DMP becomes machine-readable (DMP-IF). Repositories, services, and platforms read and write to it continuously. It stays current throughout the project lifecycle.

Architecture

Three layers, building up

The DMP-IF consists of three core components. Each layer builds on the one below it, from a shared data model at the base, through domain-specific extensions, to a common API at the top. The structure and content of maDMPs are based on real-world use cases and pilot implementations, and build upon the RDA (Research Data Alliance) recommendations.

RDA DMP Common Standard

The Foundation

An RDA recommendation defining the minimum set of concepts needed to describe a DMP in a machine-actionable way. Provides a shared vocabulary and structure for core DMP concepts common across domains, funders, and infrastructures. Intentionally avoids domain-specific constraints, keeping it stable and broadly applicable.

Cross-institutional FAIR-aligned Auto-validation

OSTrails Application Profile for maDMPs

The context

A Europe/EOSC-specific extension of the Common Standard. Introduces additional entities, fields, and constraints to support funder requirements, national practices, and institutional needs. Every maDMP conforming to the AP is also compliant with the broader Common Standard. Developed iteratively based on pilot feedback.

Metadata Vocabularies Policy compliance

maDMP API Specification

The Interface

A standardised interface for programmatically interacting with maDMPs across platforms. Enables uniform operations: searching, retrieving, creating, updating, and archiving DMPs. Built on top of the Common Standard and compatible with the Application Profile. Being developed jointly within the RDA Common API for maDMPs Working Group.

Real-time exchange Repositories Knowledge graphs FAIR Assesors

What this enables

Practical applications

Automated workflows

Repositories and services read the DMP directly. Researchers get access to equipment and storage described in the plan automatically, without manual steps.

Platform independence

Any platform implementing the maDMP API can exchange DMPs with any other. The API does not replace existing platform APIs; it standardises the common interactions.

Better DMPs for researchers

Creating a DMP primarily benefits researchers by facilitating data management of typical tasks, rather than being a one-time exercise to meet formal requirements.

Participating platforms

Argos OpenCDMP DAMAP DMPonline DMP OPIDoR DMP Tuuli Data Stewardship Wizard DataPLAN FAIR Wizard

The DMP Commons

A shared foundation for machine-actionable DMPs

The DMP Commons define how DMP information is structured, constrained, and exchanged, without prescribing how individual systems are internally designed. They are aimed at software developers building DMP platforms and services that consume or produce maDMPs, and at data stewards who need to structure RDM information.

RDA DMP Common Standard

The minimum set of concepts for machine-actionable DMPs. Maintained by the RDA DMP Common Standards WG.

OSTrails Application Profile

Extends the Common Standard with EOSC and funder-specific entities, fields, constraints, and controlled vocabularies.

maDMP API Specification

Standardised interface for searching, retrieving, creating, updating, and archiving DMPs.

Mappings

Structured translations of traditional DMP templates into machine-actionable format. Published as commons for any platform to integrate.
Explore the full DMP Commons