QD meeting minutes
Noemi Betancort Cabrera
Hilde suggested that we work on a more specific use case template to describe implementation approaches (in contrast to the use case template that we have from the EOSC, that is very general) → a template for implementation examples
Like the Twitter use case provided by Libby, where some data is depicted and where we see the relationship between different types of datums and what the requirements are for describing them.
This template could be used not only in the context of CDI, but across the DDI Alliance to facilitate the work of people developing implementation guides, for example.
The template should illustrate how to describe, introduce and present the use cases in such a way that these descriptions can help people who want to implement CDI in similar cases, and also for presenting our use cases to the modelling group.
Representing examples in a JSON-LD serialization is easier
It would make sense to wait until the amendment document is ready so that we can provide concrete JSON-LD examples for our/next use cases.
Questions for the main CDI-group:
do we know if the issue Support for non-traditional data formats · Issue #18 · ddi-cdi/ddi-cdi is related to our work? If it is, how can we help? which information can we provide to help?
(to Achim) Is there a tool that can help to create application profiles / select subsets of the model (not only, but specially) for defining how a community makes use of the CDI-Standard?
If a cross-product working group dealing with qualitative data issues is to be set up under the DDI Alliance, we should do so by formally specifying a set of parameters, such as where it should be bounded, the types of things we want to do, etc.
If this is set up, having a subgroup under CDI wouldn't make much sense (after we finish our current work with the proposed changes) and also because most of the members will be the same in one and the other; however, we should have a liaison of this general Quali group within CDI.
Darren will send us a template for this, which we will review offline and discuss at the next meeting.
In a later step, the Scientific Board will create the groups that are deemed necessary according to the group profile.
Regarding our amendment document, it will go to TC first, and if accepted, the proposal should be documented accordingly so that CDI will be able to implement it.
How to send it to TC? Email to Wendy to put it on the agenda
Discussion and approval?
Implementation
How should people propose changes, make suggestions, report bugs to the CDI model?
Here there are the workflow and links: https://ddialliance.org/file_an_issue
Is still open, if it will be a Jira issue tracker (there is already a project for CDI) or the GitHub issue process
If we are an independent group in the future, we might need an issue tracker for the things we might develop (suggestions for other groups, as amendments to the CDI model, belong in those groups' issue trackers).
Question from Kati if and how we will be working on the use cases?
Wait for Edwardians use case example to provide real CDI examples, so that the other use cases can learn what it is needed from them, and see if it could be applied in the same way
The Twitter use case should be completed with a CDI example, but as it can be represented with the W3C Annotation Model, it seems to be possible with the proposed CDI extension as well (Hilde provided CDI examples thanks to the tool that Benjamin Buster ist developing)