Examples
Worked examples
- Is an instance
A DMP with versions 1.0, 1.1, and 2.0 each assigned a DMP ID and timestamped.
- Is an instance
A funder portal showing the DMP version in force at each project reporting period.
Counter-examples
Looks similar, but isn't
- Not an instance
A Static DMP.
- Not an instance
A wiki page edited without version history.
Editorial commentary
Living DMPs combine the lifecycle properties of an Active DMP with persistent identification of each version (e.g., a DMP ID resolving to current and historical versions). This supports traceability ('which DMP was in force when consent was collected?') and longitudinal analysis ('did the commitment change after the ethics amendment?').
References
- Burnette, Mannheimer et al., 'A vision for living, citable DMPs' (Data Science Journal, 2022).
Also known as
versioned DMP · evolving DMP
Machine-readable encodings
Use in your systems
xml
<role vocab="credit"
vocab-identifier="https://casrai.org/dictionary/"
vocab-term="Living DMP"
vocab-term-identifier="https://casrai.org/dictionary/term/living-dmp" />json
{
"@context": "https://schema.org",
"@type": "DefinedTerm",
"name": "Living DMP",
"identifier": "https://casrai.org/dictionary/term/living-dmp",
"description": "A DMP that is versioned, citable, and intended to evolve over the life of the project, with each significant change captured as a new version of the plan.",
"inDefinedTermSet": "https://casrai.org/dictionary/domain/machine-actionable-data-management-plans-madmp/",
"url": "https://casrai.org/dictionary/term/living-dmp",
"sameAs": [
"versioned DMP",
"evolving DMP"
],
"license": "https://creativecommons.org/licenses/by/4.0/"
}
