Appendix D: Potential Data Director Agentic AI Tool Blueprint Implementors¶
Based on discussions with working group members, there is interest in further developing this Blueprint and using it to set up implementations of the tool, or variations of it. Microsoft has also confirmed its intention to adopt the Blueprint within its own commercial context, bringing significant organisational capacity and reach to early implementation efforts.
| Name/Affiliation | Description |
|---|---|
| Paty Buendia Lifetime Omics |
A separate initiative associated with the EOSC-Future/RDA Artificial Intelligence and Data Visitation (AIDV) Working Group and the related TIGER project DV4RDA is developing software components focused on implementing data visitation policies in practice. This includes a tool called Vantage, with plans to extend to restricted access data. Members of the working group are also discussing potential use of this Blueprint within a new agentic AI working group whose scope of work is currently being developed. They have expressed willingness to collaborate with implementers. |
| Timothy Cook, with co-author Christopher Steven Marcum Axius SDC, Inc. |
On behalf of Axius SDC, Inc., Timothy Cook and Christopher Steven Marcum have completed a detailed mapping of the Semantic Data Charter (SDC) to the Data Director Agentic AI Blueprint,1 presented as a candidate open reference implementation aligned to the Blueprint's requirements for FAIR compliance, interoperability without re-mapping, persistent identifiers, sovereignty, and deterministic governance enforcement. The mapping documents supporting evidence including the FAIR Data Demo, the MTCP×SDC integration, and the CordovaOS interoperability demonstration, and states current limitations and next steps. The authors have expressed willingness to contribute a worked conformance example toward v2.0. |
| Francis P. Crawley EOSC-Future/RDA Artificial Intelligence & Data Visitation Working Group (AIDV); RDA BIDT IG, Human Genome Project II (HGP2); AI4GHR; GCPA; SIDCER |
The Data Director Blueprint has been adopted as a reference resource for the Global Ethics and Regulatory Preparedness for Emerging Health Technologies (GERP) initiative. It was implemented as part of the National Conference and Workshop: Towards a Safe, Equitable and Accountable Future of AI-Health Ecosystem in Indonesia, held at the Ministry of Health in Jakarta on 8–9 June 2026. The conference brought together ethics committees, regulators, and national health bodies to develop policy, SOPs, and assessment frameworks across AI and emerging health technologies. GERP will continue to reference the Blueprint in work across other countries, with a particular focus on the Global South. |
| Francis P. Crawley EOSC-Future/RDA Artificial Intelligence & Data Visitation Working Group (AIDV); GCPA; SIDCER |
Members of the EOSC-Future/RDA AIDV Working Group are discussing potential use of this Blueprint within a new agentic AI working group whose Statement of Work is currently being developed. They have expressed willingness to collaborate with implementers. |
| Joe Heffer University of Sheffield Monica Palmero Fernandez University of Oxford |
Two UK-based universities, Sheffield and Oxford, have expressed interest in exploring implementation of the Data Director. Both have indicated that collaboration between institutions could be beneficial. While no formal implementation plan has yet been established, they have indicated willingness to engage further with the Blueprint community. |
| Marco Rorro EGI Foundation |
The EGI Foundation and its federated members provide research services2 that could serve as components for implementing the Data Director, including identity and secret management infrastructure. A federated large language model inference service is also expected to become available in the near term, which could provide the model runtime required for deployment. |
| Pengyin Shan NCSA, University of Illinois Urbana-Champaign |
A research software engineer at a large academic computing centre is engaging with the Blueprint in two ways. First, through their own research on research software metadata, where the Blueprint's grounding of quality checks in existing validators, and its recognition that schema compliance alone does not confirm semantic correctness, maps onto ongoing work on cross-record metadata consistency; the Blueprint's framing will be applied and findings reported back. Second, through dissemination within their institution, introducing the Blueprint to research software engineering and data support colleagues and gathering informal feedback. This is a personal commitment and does not commit the institution, nor extend to deploying a Data Director instance. |
| Slava Tykhonov CODATA |
A member of the Data Director Agentic AI Tool Blueprint Working Group is working on data management planning tools and have indicated they do not plan to implement the Data Director in full but have existing components that align with its requirements. These include an ODRL-based implementation addressing capability C12 and Croissant support addressing R2 and R4. They have expressed willingness to share these components and collaborate with other implementers. |
| Raymond Uzwyshyn University of California |
A member of the Data Director Agentic AI Tool Blueprint Working Group is developing a prototype that takes a persona-based approach3 as a complement to the capabilities-based model set out in this Blueprint. The prototype draws on the working group's outputs while adopting a different structural approach. Feedback from the wider community is being sought over the coming months and the developer has indicated willingness to collaborate with implementers. |
| Carlo Maria Zwölf LUX Observatoire de Paris |
A suggestion has been raised to use the Blueprint specification itself as an informal test of its clarity and completeness, by providing it to a coding agent to assess whether it is sufficiently detailed to support AI-assisted implementation. This experiment has not yet been carried out but offers a practical means of evaluating the specification's rigour and identifying gaps ahead of broader implementation. |