We reviewed the key changes in RDA DMP Common Standard (maDMP) v1.2 and their impact on tools. DSW, DAMAP, and Argos are waiting for the API work to be finalized before starting migration. DMP OPIDoR is already progressing with its migration to DCS v1.2.

OSTrails is finalizing a consultation on potential additional fields to propose to the RDA Common Standard WG. This may trigger another update to the recommendation before summer.

We went through all open issues. Thanks to Vojtech and Valentin for their pre‑meeting reviews.

• Three issues were closed with no changes required to the maDMP specification.
• Two issues will be addressed by improving documentation with a mechanism to notify clients of unprocessed fields:
  https://github.com/RDA-DMP-Common/common-madmp-api/issues/23

We also discussed input from Paul Walk on using webhooks and COAR Notify (Paul co‑authored RDA DCS and COAR Notify). Details:
https://github.com/RDA-DMP-Common/common-madmp-api/issues/5

Next steps

• Close the remaining issues, including housekeeping items. We have found “volunteers”, but inputs are always welcomed:
  https://github.com/RDA-DMP-Common/common-madmp-api/issues/22
  https://github.com/RDA-DMP-Common/common-madmp-api/issues/19
• Implement the API in tools to validate the specification.

Reminder: RDA accepts group outputs as recommendations only when sufficient adoption is demonstrated. Stabilizing and implementing the specs in tools is now essential.