Tools, Implementation and Documentation (2025)

Generic Tools Deliverables Summary

Tools Roadmap - Google Doc - Currently drafting (Deirdre,,Pasca , BPnjamincal, Benjamin)

Working group organisation proposal - to be drafted (Deirdre, PascaSlava, Benjamin, Slava)

Tools list - Google Doc, to be transferred into Landscape (initial content in Github, and dem- Google Doc

DDI-CDI Implementation Patterns Deliverables Summary

, DDI-CDI Documentation Deliverables Summhis group is really organized along two distinct axes: technical implementation through software tools, and trables Summary

Inshe documentation of implementation approaches. While these topics are closely related, and will require coordination, the deliverables produced are likely to fall squarely into one axis or the other. (It should be noted that coordination with the standards group is also likely in some cases, but not as pronounced.)

Anticipated possible areas of work include the following:

DDI-CDI Implementation Patterns: This topic is per Darren’s document, looking at the inputs and outputs of data repositories publishing data as DDI-CDI, and how specific features are selected for use. Further, it looks at the implementation issues around working with different features of the standard.
DDI-CDI Features Documentation: Several topics in DDI-CDI have been highlighted as requiring more documentation, and some initial drafting has taken place. Topics here include the Variable Cascade, the use of different Data Structures, and the creation of community profiles. This topic would attempt to produce finished drafts of these documents.
Dataverse Implementation: Dataverse has committed to implementing DDI-CDI, and in the Dagstuhl workshop last year some basic functionality and a roadmap for implementation were defined. This group would focus on pushing that work forward, especially in the context of a group of technical implementers.
Generic Tools and Services: This group would focus on defining (or refining) tools and services which could generically be used in different DDI-CDI implementations. These would include the services and Python library developed by Pascal Heus, the Nectar tool, generic APIs, and so on. This group could also begin an exploration of how an agile Acceleo-4 backed production process, creating XSD, RDF, SHACL, JSON-LD, JSON-Schema (and possibly Pydantic) artifacts, could facilitate CDI tool prototyping, and in doing so, test proposed model changes before a new release.
CDIF Implementation in XAS: The OSCAR project looking at XAS has produced a set of recommendations and issues around the use of DDI-CDI. Further, they are using Nectar as a testing tool for their implementation of DDI-CDI, which will ultimately result in a service integrated with the Galaxy system employed within EOSC. This group woll look at the recommendations coming out of this effort to see what changes are needed in the DDI-CDI model, and how this informs tools and documentation regarding implementation.

It is unlikely that all of these topics will be addressed, but having a single umbrella working group to coordinate some subset of these efforts seems to make sense. Ideally, this would be a “big room” group which would allow specific people to easily interact, even though they might be working on different things at the same time.

Shared Google folder (Please use a Google doc in the folder to create notes of your discussion)

A Methodology for the Development of DDI-CDI Implementation Guides (from a previous workshop)

Characterising schema -

DDI-CDI Tools in Development PLUS Group working notes - Google Doc