In attendance: Deirdre Lungley, Hilde Orten, Wendy Thomas, Benjamin Beuster, Dan Gillman, Darren Bell, Flavio Rizzolo

Agenda and minutes

GitHub issues discussion

Second discussion of the backlog to determine how much effort is required. There will be a prioritization later on.

Issue #21: simple technical fix, to be assigned to Darren to be updated.

Issue #20: it’s about RDF namespace content negotiation. Darren to update issue when implemented.

Issue #9: Can CDI support data reorganization in the context of household and person-level data? Yes, the standard supports different types of records and how to move content from one to another. However, it’s necessary to provide some guidance document explaining how to do it given that users may not always understand the implications. Flavio to update issue.

Issue #10: Having all attributes with default values as required have become a pain point. Decision: make attributes with “false” default value as optional, while keeping those with “true” default value as required. Flavio to update issue.

Issue #11: Signification pattern is not the issue. Rather, the issue is that the UML model is conceptual and platform-independent, which means that implementing all classes in the same way in the syntax representations is sub-optimal and makes the representation unnecessary complicated (e.g. Notation or Position shouldn’t be represented like Code or List just because they are all classes in the conceptual model). As long as we use the current platform-independent model (PIM) as if it were a platform-specific model (PSM) we’ll see these issues. Flavio to close and create new issue about the need for platform-specific models for syntax representations.

Note: no need to add issue for long association names.

Discussion will continue in the next meeting.

Update from sub-groups

Documentation: Reviewed existing CDI documentation and found most materials are advanced and technical, leading to a decision to create introductory-level documentation. Existing training materials and webinars can be supplementary resources. Look at how to use existing training material. Gaps for the training group.

Tools: Discussed the Nectar tool's implementation of CDIF, focusing on code list concepts and variable classification. The tool needs further development to validate against the current SHACL DDI CDIF standard. Acceleo development will continue.

Qualitative: getting closer to establish a DDI-wide qualitative working group (it currently focuses on CDI). Need to compile CDI requirements to be included in the model as soon as possible.

W3C: Darren to complete a W3C collaboration justification document to be discussed in the Scientific Board.

Next meeting: Wednesday June 25^th

In attendance: Deirdre Lungley, Noemi Betancort, Hilde Orten, Joachim Wackerow, Wendy Thomas, Benjamin Beuster, Dan Gillman, Darren Bell, Flavio Rizzolo

Agenda and minutes

GitHub issues discussion

First attempt at trying to organize the work in the repo backlog.

Just going over the issues for quick discussion to determine how much effort is required. There will be a prioritization later on.

Issue #2: just a technical task related to the upgrade to the latest EA Sparx. No decision yet on when the upgrade will be in place.

Issue #3: pertains the duplication that occurs when an association with the same name is defined both in a class and its super-class. More problematic when dealing with two inheritance hierarchies connected by associations because it requires constraints, either as notes in the model or in a formal language, to indicate which of all combinations are valid (see variable and unit cascade as an example). Related to issue #4

Issue #6: the issue has likely been solved, Flavio will check the UML model.

Issue #7: requires a separate discussion on how to better remodel some parts of the process model to capture both prospective and retrospective provenance. The main concern is how parameters are instantiated at runtime. Flavio to update issue with more details.

Issue #8: pertains to the complexity of identification and reference. There are dozens of attributes, with the large majority targeting corner cases. Developers are not pleased. The (small) set of most common attributes need to be identified to separate from the rest. Unclear yet which is the best way to handle the separation of concerns (inheritance vs composition vs something else). Flavio to update issue with more details.

Discussion will continue in the next meeting.

Update from sub-groups

Documentation: initial meeting. Discussion of the template brought by Noemi and initial review of the existing documentation to get a sense of what’s the extent of the work.

W3C: IP & governance need to be discussed. It started (and will continue to be for the time being) as a CDI project, but it will eventually include profiles of other products. Darren to draft 2-pager on current state and goals.

W3C and ISO activities need to be aligned/coordinated. Ideally the same CDI profile/fragments will be the core of both standards. A discussion between both groups will be scheduled.

Qualitative: presentation at the DDI scientific meeting

Tools: knowledge sharing between Benjamin and Deirdre (Bergen meeting). How to handle microdata at data point granularity was discussed (billons of triples in some cases). Most use cases don’t need to include all data points in CDI format, just those that require annotations and/or traceability individually. In most cases record-level, or even variable-level, would suffice. Will parquet and other physical formats be supported?

DDI-SDMX: presentation at the DDI Scientific meeting. Submission to the SDMX Global Conference is being prepared.

Next meeting: Wednesday June 11^th

In attendance: Deirdre Lungley, Noemi Betancort, Benjamin Beuster, Dan Gillman, John Kunze, Flavio Rizzolo

Agenda and minutes

Admin items - Frequency of the meetings

Different options were discussed, e.g. shorter meetings every other week, monthly, etc. The consensus was that once a month, with the option of adding another meeting when necessary, best fits the way sub-groups are currently working.

Decision: try the monthly option for a few months and see how it goes. Due to conflicts the next meeting will be in three weeks (May 28th).

Update from sub-groups

Tools: No meetings. Next meeting in person in Bergen next week. Deirdre will be working with Pascal, who wants to make his DDI toolkit available (he is currently off for a few weeks). The Tools sub-group wants to meet with the documentation sub-group to coordinate how documentation about tools is produced.

Syntax: will start migration from Acceleo 3 to 4.

Qualitative: keep meeting twice a month.

Documentation: initial meeting. Discussion on whether changes need to be made. First documents to tackle are the implementation guide and the variable cascade. The Documentation sub-group will meet with the Tools sub-group, as requested.

DDI-SDMX: no meeting and nothing to report. Brief summary of the group activity so far was discussed as a recap.

Template discussion

Noemi provided an overview of the https://docs.google.com/document/d/1q1nCUvDTTm_aBjb37Vl4nCfUEuPxYD-_n--pOb8jdgc .

The template was put together based on templates used by RDA WGs, FAIR mappings WG, and other groups working with repositories. No standard, but many commonalities among them.

The main goal is to describe data for implementation purposes, i.e. what the implementation is about and how CDI can help.

It contains a description of what data looks like (sample), characteristics of the data, and requirements (disclosure limitations, terms of use, linkage, metadata requirements)

It includes an output section covering the benefits of this implementation (provenance, transparency, reproducibility, etc.)

Next steps would be to test it by the sub-groups to determine how to adapt/improve

It might too much information to fill upfront. However, it’s a tool to clearly communicate requirements and as such many details are necessary in some cases to properly implement a solution. It all depends on who is the audience and who is filling out the template.

Where do we go from here? It aligns with the SB strategic goals, we need to follow up with the TC.

In attendance: Hilde Orten, Achim Wackerow, Noemi Betancort, Dan Gillman, Wendy Thomas, Flavio Rizzolo, Deirdre Lungley, John Kunze

Agenda and minutes

WG planning and reporting

(Noemi and Flavio - doc at https://docs.google.com/document/d/1RFOvs7ciHQAS0P_EG-NF3lSJFWTu_-eKeBvLKPNwyN8/edit?usp=sharing
spreadsheet: https://docs.google.com/spreadsheets/d/1qIAw6zK6KIDBNSUQTFJfIjqRdkyMkj9oFTyQnNdttpI/edit?gid=6601827#gid=6601827
Work is ongoing.

Funding request opportunities for the FY 2026

(See the email from Jon/Jared regarding funding opportunities below). There seems this year to be two options: 2000 US Dollars for each WG, + open call for 10 000 USD. Deadline May 7th.
SB clarifies with EB on next Friday how the situation is with the funding for the working groups.
Some money for improving the tooling for the generation of the field-level documentation and encodings would be good.

Reporting from last year’s funded activities

Deadline May 1st.
Two reports will be done, tooling, and Chur meeting. Hilde and Achim take care for the reports. An interim vice-chair (see below) should send the reports in.

Input from the sub-groups

Syntax rep. group: CDI-98 (Deirdre)
The issue is in the current issue tracker at github, see: Missing default values · Issue #10 · ddi-cdi/ddi-cdi
It is re-opened. Additional information will be added.

AOB

o   Libby is not available as vice-chair. There is a need for a vice-chair at least for an interim period.

o   Two issue trackers for CDI: Jira https://ddi-alliance.atlassian.net/jira/software/c/projects/CDI/issues/ vs. GitHub https://github.com/ddi-cdi/ddi-cdi/issues
JIRA write access will be closed

In attendance: Deirdre Lungley, Joachim Wackerow, Noemi Betancort, Bejamin Beuster, Hilde Orten, Dan Gillman, Flavio Rizzolo, John Kunze

Agenda and minutes

Admin

ISO Draft

WG members review of ISO draft (Wendy and Dan)
see DDI ISO Standard 2025-03-01.docx, https://groups.google.com/group/ddi-cdi/attach/a0a136ad202b9/DDI%20ISO%20Standard%202025-03-01.docx?part=0.1
The comments should be done accordingly the ISO template, see: https://share.ansi.org/ISOT/ISOT%20Voting%20Resources/ISO%20Commenting%20Template.doc
Hints from Dan:
The general, editorial, and technical classification of comments can be defined this way:

• Technical – comments addressing requirements expressed in the document

  • Example – if I have described value domain incorrectly, then that is a technical issue

• Editorial – comments about wording that is not about requirements

  • Misspelling of a word

  • Grammatical errors

• General – comments pertaining to the document in its entirety

  • Use of the wrong font or style

  • The same error cropping up throughout

WG planning and reporting

(Noemi and Flavio are working on it), see: https://docs.google.com/document/d/1RFOvs7ciHQAS0P_EG-NF3lSJFWTu_-eKeBvLKPNwyN8/edit?usp=sharing

Input from the sub-groups

Syntax representation group: work is planned regarding Python Pydantic classes (data validation and manipulation)

AOB

Noemi mentioned a funding option for software development in the German National Research Data Infrastructure (NFDI), https://www.konsortswd.de/en/flexfunds/

The production framework for generating the field-level documentation and encodings can now be run in batch mode. A related Git repository is provided to the TC, see: https://bitbucket.org/wackerow/ddi-cdi_production/ . TC plans to integrate this into Github automation.

In attendance: Deirdre Lungley, Joachim Wackerow, Noemi Betancort, Bejamin Beuster, Hilde Orten, Dan Gillman, Flavio Rizzolo

Agenda and minutes

1. Admin

• CDI Webinar
  parked

• Review and publication of CDI article – status
  The paper “DDI-CDI and Other Standards” is published in the DDI Working Paper Series, see: https://doi.org/10.5281/zenodo.11223221

• Production tool – status
  Good progress is made
  Annual meeting of the Scientific Community (May 22) prep

• Plan and CDI WG

2. The Scientific Board has asked all WG’s to provide a two year plan (from summer 20204 through December 2026) in line with the Scientific Work Plan, before the Annual meeting of the Scientific Community on May 22nd. The CDI plan is, however, missing. It would be really good if the CDI group can get a plan for 2025-2026 in place before the annual meeting. Plans from the Working Groups are available here. Scientific Work Plan summer 2024 through December 2026.

• CDI reporting (group will be contacted by SB before Easter)

• CDI presentation for the Annual meeting of the SC (group will be contacted by SB before Easter).

We need somebody to help with the CDI WG plan and to collect items from the CDI sub-groups. It will be good if other people than the SB chairs do this. Flavio and Noemi have been asked by email today. Let’s see if they would be willing/have time for this. Otherwise somebody else?

Noemi and Flavio are willing to put together the report and plan for the CD WG. The subgroups should send related material.

 Input from the sub-groups
Benjamin (Examples and Tools [ET]) reported on a meeting with Deirdre and Pascal Heus. A further meeting is planned with Oliver and Olof.

3. Qualitative data [QD] has interest in a documentation subset for their purpose.

4. AOB

In attendance: Deirdre Lungley, Wendy Thomas, Joachim Wackerow, Noemi Betancort, Bejamin Beuster, Hilde Orten, Filipi Miranda Soares

Agenda and minutes

1. Admin

   1. Google folder structure
      TC is preparing a proposal for a generic structure. It will be sent to EB because of funding.

2. CDI Webinar
   Postponed.

3. Review and publication of CDI article
   Noemi reviewed it, Wendy and Filipi will look at it.

4. Production tool
   Work is going on. It is complicated because Acceleo is designed as an interactive tool

5. 2 year plan and reporting CDI WG

   The Scientific Board has asked all WG’s to provide a two year plan in line with the Scientific Work Plan before the Annual meeting of the Scientific Community on May 22nd. The CDI plan is, however, missing. It would be really good if the CDI group can get a plan for 2025-2026 in place before the annual meeting. Also, we will be asked to do some reporting before meeting and should be prepared for that.
   Hilde will send SB work plan and expectations how a CDI work plan could relate to the SB work plan. Subgroups might have input into this.

6. Input from the sub-groups
   Tools subgroup: see report from Benjamin.

7. AOB

In attendance: Darren Bell, Deirdre Lungley, Wendy Thomas, Joachim Wackerow, Noemi Betancort, Flavio Rizzolo, Bejamin Beuster

Agenda and minutes

1. Admin

   • Feedback on CDI after the release

   • Continuation with subgroups and main group (only reminder)

   • Email list, subject prefixes, email archive (public) (only reminder)

   • Confluence pages: purpose, updates (only reminder)

   • Possible use of Google docs

     • Who could create this?

     • Folders per subgroup should be then located below a main folder, (relevant info linked from the Confluence site).
       Google docs structure for DDI working groups also for DDI-CDI subgroups. Flavio will file an issue. TC will look into it. A generic solution would be great.

2. CDI Webinar
   Darren will set up a Google document where ideas can be collected. The topic will be again discussed in two weeks.

3. Review and publication of CDI article
   Paper on “DDI-CDI and other Standards” can be reviewed by the group until Friday, March 7, 2025. It can be published as DDI Alliance paper (where it will get a DOI). It should be listed in the related page and linked from the DDI-CDI page.

4. Questions from the sub-WGs

5. AOB
   Consistency of associations names in RDF and other encodings should be discussed. This will be addressed by the syntax representations subgroup. Information on the issue will be sent to the group.

DDI-CDI WG Meeting – 12 February 2025

In attendance: Darren Bell, Deirdre Lungley, Hilde Orten, Wendy Thomas, Joachim Wackerow, Arofan Gregory, John Kunze, Flavio Rizzolo

Agenda:

(1) Admin, if any 

(2) Finalisation for the public release of 1.0

(3) Organising sub-groups and meetings

(4) AOB

Discussion Points

1. Deirdre to meet with Benjamin regarding joint meeting between Implementation and Tools groups, will e-mail if further action needed (joint meeting, issues etc.)

2. Achim proposes to have a dedicated list for DDI-CDI, with subgroup prefixes. Use e-mail as first step, then escalate issues to the generic group, then meet if needed.

From an e-mail exchange (Achim):

With the background that subgroups are starting now, it would be really great if we can use soon the CDI Google group email list for the communication. The advantage would be that an email group archive develops then. All subgroups should use this email list. Each subgroup should have an acronym which can be the prefix in the email subject (like: [mod] subject). This way the subgroup can be identified easily and everybody is informed what is going on. Suggested acronyms:

·       nq  Quali

·       mod Modelling

·       doc Documentation/Community Implementation Guide

·       map SDMX-DDI Mapping

·       sr  Syntax Representation

·       et  Example and Tools

·       w3c W3C Alignment

• Will need public access to the e-mail archive. Link from Confluence. Only members can post to it - access would be read only.

3. The DDI-CDI 1.0 release is just waiting on the announcement in the newsletter. (Jared says there will be both a general announcement and the newsletter, released later today.) Should we do a webinar? We could do a written announcement for e-mail lists, and then do a webinar of it can be organised. Darren will pursue the webinar.

4. Will rely on Hilde/Achim/Libby to organise meetings during Arofan's medical leave. Next meeting will be in two weeks. Hillde will send e-mail announci9ng the next meeting.

5. Final open questions from release discussions. These are minor points in e-mails between Darren, Achim, Wendy and Arofan. Address at next meeting. Darren will follow up with Achim.

DDI-CDI WG Meeting – 5 February 2025

In attendance: Darren Bell, Deirdre Lungley, Hilde Orten, Benjamin Beuster, Dan Gillman, Wendy Thomas, Joachim Wackerow, Arofan Gregory, John Kunze, Flavio Rizzolo

Agenda:

(1)   Admin

Arofan to go on Medical leave as of February 16. Achim, Hilde, and Libby to fill in chair temporarily.

(2) Finalisation for the public release of 1.0 - Achim's questions

·       HTML request for RDF namespace needs a new page, Darren to create

·       Add links to field-level documentation (without “RDF” in the path) – not a replacement for the RDF links. This does not need content negotiation, as it is essentially a link to the model.

·       Remove RDF XML version until we follow up with Pierre Antoine (Fuseki auto-conversion)

·       Redirects needed to support relative links in field-level doc will be added

·       We will distribute the “unique names” version of the model, and add a comment that additional versions are available in the download package

All changes to be made by this coming Friday.

(3) Hilde asked some additional questions:

·       Testing for/model additions for new data structures new (e.g. NetCDF)? (Could be important of CLIMATE-ADAPT)

Dan Gillman and Flavio Rizzolo are both interested in this issue, which we should discuss with the CDIF effort covering the same thing. This may not end up in CDI beyond the logical description, but we should have one solution.

·       Proposals/model snippets for changes to or new things for CDI, processes.

Raise specific issue in the CDI WG and we can deal with them.

·       Status of SHACL/ ShEx – are they sharable (even if not published)?

CLIMATE-ADAPT ontologist wanted access to this. Deirdre has decent SHACL, but the ShEx is not working as well. We could share the SHACL as a work-in-progress. Not very time-urgent. Do in the next couple of weeks. Achim, Hilde, and Deirdre to sort out as they work on this., Also share with Doug Fils for CDIF – he could use the CDI SHACL.

(4) Organisation and schedule moving forward

We will meet next week, and then shift to meeting every other week. We will try to get Libby to join. There will be further e-mail communications.

(5) AOB

[Hilde is in Athens with free ice cream. Darren says “Beware of Greeks bearing gifts…”]

None.

2025-01-29

DDI-CDI WG Meeting – 29 January 2025

In attendance: Darren Bell, Deirdre Lungley, Hilde Orten, Benjamin Beuster, Dan Gillman, Wendy Thomas, Joachim Wackerow, Arofan Gregory, John Kunze

Agenda

1. Admin, if any 

·       Report to SB still TBD

·       Wendy to send Arofan minutes in collapsable Minutes on Confluence

2. Finalisation for the public release of 1.0

Everything is now in the repository and is correct.

Process: we send TC an e-mail with final locations. Need to establish a full download package location (with everything in the release). Currently the full download package is in GitHub. Wendy will ask people in TC (Olof, Dan Smith) and get an answer as to how to produce the needed ZIP from GitHub.

Achim will transmit the download package to TC once he knows how to do it. There may also be a partial download package just for the field-level documentation.

We now have a product page on the new Alliance website, as well as a page per version for each spec. Once done, we can review (links are not yet final.)

3. Hilde's credit issue

From Hilde:

The list is here: Cross Domain Integration (CDI) Working Group

In the short version of credits at the field level doc. These are mentioned:

Contributors to DDI-CDI Development

Members of the Cross Domain Integration (CDI) Working Group shepherded the standard into its final form and produced the final documentation. Listed in alphabetical order they are:

• Arofan Gregory (chair)

• Dan Gillman

• Flavio Rizzolo

• Hilde Orten

• Jay Greenfield

• Joachim Wackerow

• Larry Hoyle

• Oliver Hopt

• Wendy Lee Thomas (Technical Committee contact)

I would suggest to add the following members to this short list (alphabetical):

• Benjamin Beuster

• Darren Bell

• Deirdre Lungley

• John Kunze

Proposed fix:

Add heading before Spreadsheet paragraph on ddi-cdi/CREDITS.md at main · ddi-cdi/ddi-cdi

“Members of the Cross Domain Integration (CDI) Working Group since 2023”

• Benjamin Beuster

• Darren Bell

• Deirdre Lungley

• John Kunze

Achim will make this change. John’s affiliation is Drexel University Metadata Research Center.

4. Testing the field-level doc

Arofan and Deirdre have played with the current version and it seems to be working as intended.

5. AOB

Subgroups:

These need to start – people should respond to Dan (etc.)

We will meet next Wednesday, and then shift to meeting every other week

Achim raised the issue of issue-tracking the high-level and field-level doc. We could use the old bug-tracker? Or we could just add a new label to Github? Consensus is to stick w/Githun with a new label (or a label for each).

2025-01-22

DDI-CDI WG Meeting – 22 January 2025

In attendance: Darren Bell, Deirdre Lungley, Hilde Orten, Benjamin Beuster, Dan Gillman, Wendy Thomas, Joachim Wackerow, Arofan Gregory

Agenda

1. Admin, if any 

·       Report to SC still TBD

2. Finalisation for the public release of 1.0

·       Changes needed for finalization – Achim looked at updated model file, to send Word doc, but changes needed in documentary part of the model too. We will give changes to Flavio.

·       Link to current version currently not active, but will be on release. This will go into the doc as sent by TC. Achim to check.

·       Website for DDI officially goes live by the 31^st.

·       Should be finished by this Friday. The one thing may be changes to the JSON-LD files – we need one large one, and Achim needs to make sure it is integrated.

3. Organising the sub-groups (convenors in bold)

·       Quali Subgroup – Noemi, Dan, Hilde, Darren, and others

·       Modelling Subgroup – Flavio, Achim, Arofan

·       Documentation/Community Implementation Guide Subgroup – Dan, Arofan, Darren, Hilde

·       SDMX-DDI Mapping Subgroup – Dan, Arofan, Flavio, Wendy (for DDI Codebook/Lifecycle)

·       Syntax Representation Subgroup – Achim, Deirdre, Pierre-Antoine as advisor

·       Example and Tools Subgroup (?) – [what is relationship to Pascal] – Benjamin, Deirdre

·       W3C Alignment – Darren, Achim, Arofan, Hilde

Kick-off date would be start of February. Main meetings become status meetings of subgroups.

(4) Review of bugs

[Not today with Flavio’s absence]

Minutes Virtual CDI meeting 2022-02-16

Attendees 

Achim, Arofan, Flavio, Hilde, Larry, Jay 

Apologies 

Dan, Wendy 

 1. Changes to the model resulting from the XML schema work by Achim/Larry 

Some model issues were detected during the XML schema work by Larry and Achim 

List of classes in DDICDILibrary:

• Agent

• ConceptualDomain

• ComponentPosition

• PhysicalSegmentLayout

• PhysicalSegmentLocation

• EnumerationDomain

• ValueDomain

The identifier attribute should be added to these classes. Dependent on the implementation, these classes could be instantiated. Then it makes sense that they have an identifier.

Action: Flavio to implement 

Reference: 

Attributes on Reference: What are the “required” and “semantic” attributes on Reference? They are undocumented. 

Decision: Remove “required” and document “semantic”. 

Action: Flavio to remove “required”. Arofan and Hilde to document “semantic” as the type of reference that may or may not come from a Controlled Vocabulary. 

Cardinality change: Multiplicity of attribute Reference::ddiReference should be 0..1 instead of 1..1. 

Decision: Agreed to change the cardinality of reference to 0..1. 

Action: Flavio to implement. 

NB: New file from Flavio available that includes the agreed changes provided post meeting on 2022-02-16. 

ControlledVocabularyEntry: 

entryReference and vocabulary lacks documentation. 

Action: Arofan and Hilde to complete this during the field level documentation upgrade. 

2. Other issues 

It may not be time to provide an XML schema before the release. Larry proposed to provide a snippet for the release, containing Concept, Variable, Codelist. 

Action:

Larry to continue with the XML and the example. 

Arofan and Hilde to continue with the field level documentation upgrade. 

Check in with the group next week as needed if more issues may be detected. 

Minutes Virtual CDI meeting 2022-01-26

Attendees

Achim, Arofan, Flavio, Hilde, Dan, Larry, Wendy

Apologies

Jay

1. Admin 

- SciDataCon panel plan

Arofan will prepare a draft proposal for a CDI panel for SciDataCon for the group to look at. The CDI as part of an interoperability framework together with other standards like DCAT, http://schema.org , PROV etc.  

2. Release Issues:

- Enumeration property questions

Arofan is working on reviewing definitions for Enumerations and had some questions to some of them.

StructureTypology

• Graph

• Lattice

• Network

• Partition

• Tree

Action: Flavio to look at the definitions for these, and check if changes are needed to the list of items and their definitions.

TemporalOperator:

• AndJoin

• AndSplit

• XorJoin

• XorSplit

Action: Flavio to find definitions for these, look at DDI-L (3.3) /possibly Process model in DDI4

Enumerations with no connections:

Action: Flavio will look for enumerations with no connections in the model. This task has been compled.

- Updating the XML and field-level online doc (for in-progress work)

Action: Achim will provide new clickable documentation and new XMI files, based on the EA file from Flavio of 2021-12-21.  This task has been completed.

- Plan for incorporating field-level doc

Arofan will continue to revise field level documentation and will send to Hilde for discussion and entry when he has something in hand.

4.      Further discussion of moving forward  topics/SC doc from this week

Delivery of model to the TC:

Wendy asked Arofan to provide a tentative date for this in the near future.

Document for the Scientific Board Contact:

Arofan has created a document for Simon, the Scientific Board Contact of the CDI group, about the next step priorities of the group.

Action: Hilde to publish this on the wiki in Confluence Cross Domain Integration (CDI) Working Group . This task has been completed.

Minutes virtual CDI meeting 2022-01-19

Attendees

Achim, Arofan, Flavio, Hilde, Jay, Larry, Wendy

Apologies

Dan

1. Admin (if any)

• Arofan reported that CODATA and RDA’s WorldFAIR EU grant proposal has been accepted.

• Deadline for abstracts to SciDataCon 2022 is February 14th 2022. Arofan will prepare a proposal for a session on DDI.

2. Status on release

The first step is for Arofan and Hilde will continue the preparation of the field level documentation. The upgrade of the spec is the next step.

3. Further discussion of moving forward topics

-Production set-up

Achim is currently working on tools for model to text transformations using Eclipse Acceleo for transform the EA model to canonical xmi. Bitbucket is used an environment for this. A goal is to automate the process as much as possible, however, some manual steps related to the export from EA and the check of output from the transformation are needed.

Wendy pointed out that production flows and tools may vary between the DDI products and that an overview regarding what we have, where things are, how processes are realised etc. would be useful to document for each product.

-RDF representation

Achim is currently working to improve the production tool, and will then integrate

the RDF code of Pierre Antoine. He will get back to Pierre Antoine in February regarding this.

-Other focus areas

• How other domains look at the CDI model: Flavio will forward a paper he is writing together with colleagues that addresses this.

• Implementation guidelines work from Dagstuhl: Arofan will send a draft of the Dagstuhl work to the group for input. Flavio and Wendy are interested to look at this.

• Standards mapping: Achim presented a matrix for standards mapping at Dagstuhl. This could form basis for a regular way to document mappings between standards. To have mappings representations in SKOS would allow machine actionability. Wendy pointed out that mappings should preferably be documented at several levels for different purposes, starting from conceptual and going into more detail. Flavio pointed out that we should maintain CDI related mappings.

-Priorities

After the work on the first version of the CDI model and the spec has been finished, the RDF representation would be the next thing on the priorities list, and after that implementation guides and mappings. The current XML representation also needs a review.

Additional syntaxes was also a topic at Dagstuhl. Larry mentioned that we need to think about a method for the mapping of the model to object oriented languages, and not only put focus on the objects. Arofan pointed out that Eclipse based tools can bind to object oriented programming languages (Java, Phyton, C++ etc.). This needs to be further explored and perhaps discussed with modelling experts. Achim pointed out that EA can do this as well, but that it has its own mapping understanding. StatCan also has an approach for general libraries that adress a family of object oriented languages. Like the EA approach this also has some limitations. Wendy pointed out that it would be useful to discuss this topic in a broader group as well. Transformation rules in COGS could for example be explored.

It was agreed that Arofan will organise an effort to write a position paper on the topic later on.

Minutes Virtual CDI meeting 2021-12-15

Attendees

Achim, Arofan, Dan, Flavio, Hilde, Jay, Larry, Wendy

1.  Admin (if any)

    - Liaison w/ SB (Simon)

Simon Hodson will be the CDI contact from the Scientific Board. The first point of contact will be that Arofan drafts a document describing goals achieved and future plans of the group.

2. Updates on documentation issues

Arofan and Hilde are working on the field level documentation. All elements have been gone through, as to whether their definitions and other documentation like explanations or examples need to be added or changed. Properties have mostly been edited and is available in a temporary EA file that the group has access to – updates with edits and additions of other components like classes, associations, datatypes and enumerations are forthcoming.

3. Updates on model freeze and generation

Achim has created a new canonical xmi file based on Flavio’s draft frozen file of 2021-11-23, with some minor edits.

Flavio will implement the changes proposed by Achim to the temporary EA file that Hilde is working on and, will produce a new file on which she can continue to edit the field level documentation.

Work on release candidates for xsd is ongoing.

Minutes Virtual CDI meeting 2021-11-10

Attendees:

Achim, Arofan, Dan, Hilde, Jay, Larry

 Apologies:

Flavio

Agenda: 

1.      Admin

Hilde reported from the meeting of the Scientific Board.

Arofan reported about the tutorials planned for the EDDI Training FAIR. 

2.      Recommended model freeze and forward game plan (from Friday meeting last week)

It was discussed whether the model is ready to freeze at this point. The topic of whether to keep the patterns in the model was then discussed. It has been agreed earlier not to have the patterns in the model. At this meeting it was agreed to keep the patterns in the model with the reasoning that they can be useful for developers, and that it would not make sense to have one version of the model with patterns and another one without them.

Actions related to the inclusion of patterns:

In relation to the model: Achim to ask Flavio to make pattern classes abstract again. A new version of the model to be provided.

In relation to the documentation:      

• Arofan/Hilde will review field level documentation for the patterns.

• Achim will find out how to make patterns part of the generated documentation.

3.      Status and updates

Documentation:

Arofan and Hilde will start to review the filed level documentation. A question that came up at the meeting is how to deal with examples in the documentation. Wendy suggested to have an example file at the product page that could be referenced. Possibilities need to be further explored.

Production process/storage/publication:

Achim will take care of the XMI production for the release. The production process includes some manual steps. The content is currently stored in Bitbucket.

Achim will liaise with Wendy/TC regarding what the TC needs to make home for in connection with the release (types of material etc.).

Minutes Virtual CDI meeting 2021-10-27

Attendees:

Achim, Arofan, Dan, Flavio, Hilde, Jay,

Apologies:

Wendy

Agenda:

1. Admin (if any)

• DDI-CDI and related usecases, the role of CDI in a core interoperability framework etc. was presented at a SciDataCon, see https://www.scidatacon.org/virtual-2021/sessions/370/ Arofan, Flavio and Hilde presented in the session. Great interest in the topic was shown from participants, of which some potentially could be new and useful contacts for the CDI group.

• DDI-CDI will be presented by Arofan and Dan at the forthcoming EDDI Training Fair late november.

2. Model - status - Frozen???

Achim thanked Flavio for his great work on the model. Hilde suggested that the three Signification pattern classes to again become pattern abstractions. This was agreed and fixed by Flavio during the meeting.

3. Organization/timing of field-level doc, diagrams, and updates

A group consisting of Arofan, Flavio, Hilde and Jay will check the latest changes to the model. They will meet on November 5th in order to coordinate.

4. Production flows/tools

Achim will work on the documentation delivery tool this week, so that documentation from the tool can be used to evaluate the model. Production flow/tools topics will be discussed further after the release.

5. RDF binding work?

It was agreed that a sub-group consisting of Achim will focus on the RDF representation work (OWL, JSON-LD).

6. Other looking forward (based on Dagstuhl outcomes)

Not discussed

Minutes Virtual CDI meeting 2021-10-20 

Attendees:

Arofan, Dan, Flavio, Hilde, Jay, Wendy

Apologies:

Achim, Larry

Agenda:  

1. Admin (if any)

Arofan informed about a proposal to establish an informal liaison between W3C and the DDI Alliance regarding RDF/JSON-LD. This will be brought up with on the Scientific Board. Arofan suggested Hilde to act as a contact point from the side of the Alliance.

2. Model - status 

Flavio has implemented suggestions from Dagstuhl in the model.

He will now look into solutions for requirements from the Unit of Measures group as well as to implement solutions for DMT-273 (Instance Variable’s relationship to a source).

A new version of the model covering the above has been provided post meeting (the frozen one?)

3. Organization/timing of field-level doc, diagrams, and updates

The planning of this will start when a frozen version of the model is available.

4. Looking forward (based on Dagstuhl outcomes) 

A set of deliverables is planned to be made available post-release:

RDF syntax representation (using the UML subset), description of use-cases, alignment with other standards etc.. 

Arofan suggested that the CDI core group work continues to meet every second week, and that small temporary groups are formed, focusing on specific deliverables and bringing in external experts. Model maintenance also needs to be addressed.

Flavio proposed that new ideas, collaborations and standards alignments should be addressed through an open and exploratory process, and that relevance for other DDI products should be brought into the picture.

Wendy suggested post release use cases and deliverables to be discussed with the TC. Arofan is open to discussions between the CDI group and the TC.

Arofan pointed at four goals for the further CDI work.

• Exploratory work, get people involved.

• Leverage CODATA.

• New deliverables should be supportive of the product.

• Have real use-cases.

Jay expressed support of this, and pointed at model maintenance, use-cases as basis for deliverables, implementation guides, and promoting of the standard as important aspects of focus.

All agreed that activities should be within the frames of the Scientific Plan.

This topic requires further discussion.