TC Meeting Minutes 2022-2023

ATTENDEES: Wendy, Jon, Dan, Olof, Flavio, Jeremy
Excused: Oliver

DDI Lifecycle version 4.0 BETA

Jon and Dan are checking it out in EA by entering and then exporting a single instrument

Announcement content:

Add UML output
Change to 4.0
Info on free account on github
Link ML is included in the full download package but these are ones that are the official ones
There are 2 different owl publishers (closed generated by by owl publisher) others generated by Linked ML toolkit

Maybe for high level documentation we can pull background information together as well as address questions raised
Implementation of serializations was focus of former high level - need to determine what is model level

Final steps

Dan will merge UML updates in shortly and tag a package for release
Dan will inform Wendy to send out and copy to pages in Confluence
Plan in some web presentations/ Q&A sessions/ - Jon will come up with a schedule of promotional/informational events (first meeting in Jan)
Make comment period through end of March

Change to Beta version in documentation
Check out ability to put preview status
Name of the release will include Beta (1,2,3)

Jon will get it out on social media

Updates of ddialliance site pages

Get Wendy the appropriate links for updating pages
Update problems related to these links from Google - should go to current page

​DDI-Lifecycle | Data Documentation Initiative

Olof Olsson 9:23 AM
​DDI-Codebook | Data Documentation Initiative still have "DDI Codebook 2.5 (under review)"

Next meeting: 4 Jan 2024

ATTENDEES: Wendy, Dan, Olof, Oliver, Flavio

• CDI till mid January

• Olov moved rest of materials to GitHub

• Beta review of DDI-L version 4 out next week

• Merged Olof's work on LinkML and will test that out

• File copied of documents on Beta review on Confluence site so they are easily aviable.

• Get this out next week for Beta review

• Send to: DDI-User List, Developers groups, DDI-SRG

• Oliver will catch up with Darren again when he is back from vacation (no issues, just follow-up)

ATTENDEES: Wendy, Jon, Dan, Jeremy, Olof, Oliver, Flavio, Christophe

• Review pull request for issues #12 and #19
  ​Language tagged strings and documentation, referencing subtypes of versionable by DanSmith · Pull Request #20 · ddialliance/ddimodel
  Walked through pull request process; validation, build outputs, see what exactly changed
  When pull request is added we can set required reviewers prior to merge
  ​Merge pull request #20 from DanSmith/master · ddialliance/ddimodel@486b43e

• Draft of DDI 4 beta release announcement
  Timing: Already working in Olof's repository (no restrictions) so need to find out when this can move. Two versions of OWL, straightforward, and with restrictions on domains
  restricted model says hasConcept can only be used on items variable and category (only place predicate can be use)
  Get feedback on both approaches in OWL (simple OWL - Olof; add in and put in build output)
  If we get done before the holidays we can get a release out.

Content: create a draft release on Github and create notes

Email draft: email content and draft of any additional information not in content documentation
Complete draft by next week and add to meeting agenda.

• Plan timing of DDI 4 beta release (next week?)
  Complete draft by next week and add to meeting agenda.
  Want full history on Bitbucket and clone to Git
  One repository per product
  CDI directly to github and remove bit bucket
  Production is not already pipeline on CV so that can be moved
  Oliver will double check with Darren if there are any transfer issues

• does anyone have any work that is not pushed
  Wendy will push to dditc

• If there is time I'd also like to review the infrastructure plan including, process for implementing, and timeline issues
  What does this mean for the timing of support of documents ion serving
  Neat to have this when the beta release went out
  Serving line documentation and high level documentation
  How is lifecycle updated (in terms of builds) - what are the options in terms of published documentation and documentation of new builds (need to provide access to both)
  <https://doc.ddialliance/<product>>/<version>where we always have:<https://doc.ddialliance/<product>>/masterto reflect the current state of master?

Jon will speak to Jared and make sure we have domain names for documentation
docs.ddialliance.org to point to the documentation server (DNS change handled by ICPSR/UMICH)

• Newsletter article
  Others will review. Jon will add info from today ad

ATTENDEES: Wendy, Jon, Dan, Jeremy, Oliver, Flavio

Roadmap document
-- get this done WENDY
EDDI TC meeting agenda
-- overall
Lifecycle get to the point where we can get something out to look at
--Schema changes, COGS stuff, and specific issues about objects
Codebook handfull of issues
CDI - what needs to get done
Controlled Vocabulary - what's left
Infrastructure needs piece

TC Organization paper
Two basic models
-- Bit of a problem with the product working groups reporting directly to the Scientific Board due to the workflow of product releases through the TC
-- The important thing is that the TC has a responsibility for the infrastructure
-- Autonomy of the working groups retained but clearer relationships [rationalize relationships]

RDF common set working group
Those who expressed interest have received draft of announcement. Please review so Dan can send out

IASSIST
No DDI meetings at IASSIST this year
No TC members have submitted presentations - please notify us if you do

ATTENDEES: Wendy, Jon, Dan, Jeremy, Flavio, Darren, Christophe, Oliver

Review of CDI processing

• Have a list people to contact - recheck with Arofan for any additions

• Time period is decided

• Need text for email

• Get issue filing information updated on site

• Updates from Flavio this week

• Generate packages and get to TC

• So still possible within November

• May be able to get out by EDDI with a 6 week review period

• OK on the approach for issue filing (Jon still needs to verify that general Atlassian login filing works - don't anticipate a problem)

PROPOSAL
On product page:

replace green box with section:

File an issue on this product
If you have an Atlassian account you can CLICK HERE to file an issue.
If you do not have an Atlassian account you can create a new account and then file an issue or use the DDI submission form HERE [link to the File and issue page]

File and issue page:

If you have an account with Atlassian click on the product below to file an issue.

If you do not have an account with Atlassian you can {create an account with Atlassian} [link to Atlassian site] then return to this page and file your issue.

Don't want to create an account? Use this Google Form to provide information on your issue and we will file it for you. You will be provided with the Jira issue number once it is filed so you can view comments and decisions on your issue as work progresses.

If you are not sure which product your issue relates to, file it on the Technical Committee issue tracker. We'll make sure it gets to the right project or projects.

DDI Codebook
DDI Lifecycle
DDI Cross Domain Integration (CDI)
Controlled Vocabularies
XKOS
SDTL
Technical Committee

New working group on RDF (Dan)
Working on announcement on new working group
Look for that in the next day or two

Codebook

• 3 Codebook items - send Darren a reminder of numbers

• Review process for Codebook entries - do remotely maybe hopefully PLEASE

CV releasing a new version resolving SKOS issues
Plan to get our system going on the 23 Nov
Oliver would be able to rerun at any time
Coordinating with them about any static information that needs to move over from DDI site

COSMOS - Admin Data workshop - has it been set?
Been difficult to nail down the meeting coordination
Flavio is in group that is coordinating meeting
Mon/Tues before is a time that CDI group would like to have meeting
Could be Mon/Tues after COSMOS

NEXT MEETING:
Roadmap document
Draft agenda for EDDI meeting/TC
Paper about ways in which working group could operate

No meeting in November after 16th; no meeting on December 28th

ATTENDEES: Wendy, Dan, Jeremy, Oliver, Christophe

Alternate Issue Submission form

​DDI ISSUE SUBMISSION FORM

Use as a back up as option for subject matter persons. This should be prominent on the pages. The zen desk at Colectica is also a good solution (internal user support). It is possible to bring this more to the foreground. Review ability to non DDI Jira members to file ASAP.

[Added noted 2023-11-08: Changed permissions to allow any Atlassian account holder to create issues. Identified page for information on creating an Atlassian account. ​Create an Atlassian account | Atlassian Support }

Codebook.
DDICODE-535
Item Adrian-4 #48
Would be difficult to define which format went with which file. If we want to provide multiple file descriptions. Everyone would have to add in the logic to figure out the relationship between the file format and the specific file description. The PDF codebook might contain more than one format but would always reference which of the file was being described (link between varFormat and physical file). These issues were why we created lifecycle. Need to be clear about purpose of codebook (1 datafile/dataset in a single format). varFormat provides additional information on the formating of the variable within a specific file.

How to describe multiple storage formats of a single study description/variable description. Add to Guide/Best Practices content.

DDICODE-534
see issue

DDICODE-537
see issue

Funding request to support IT infrastructure for development tools - maintenance, upgrade etc.
Does the RDF server fall under that? yes
Better description on what types of things would be covered, how tapping in or approval of funds would work. Opportunities for paying for some CI stuff for running serializations. For instance CI builds are running on Dan's personal account, but this should be moved to DDI github account.
Add to agenda for discussion at EDDI meeting.

ATTENDEES: Wendy, Flavio, George

discussed DDICODE-536 and DDICODE-537 see comments in issues

Items for a process derivative products

canonical UML model
go to ​Library domain model UML class diagram example describes main library classes and relationships.

Derivative of the process we use "canonical UML"

Set up the review and publication process for these process derivative products
Cross DDI product toolkit for working with primary products:
DDI profiles
canonical UML
UCMIS
Transformation tools between products

ATTENDEES: Wendy, Dan, Olof, Jeremy, Flavio
Excused: Oliver, Christophe, Jon

Published Agenda

• Production pipeline (Oliver's pptx has been added to TC drafts folder (​PipelinesInDDIProduction.pptx

• I sent out the CDI Syntax representation document separately - we need to look at this and prepare for the syntax review (I believe there may have been some done at Dagstuhl and we need to take that into account

• Tool discussed at last weeks meeting (dependent upon Olof's availability)

CDI Syntax Representations

• The document provides the content needed for a technical review of the bindings

• Pretty clear on each of the steps

• UCMIS purpose and usage explained

• Updated package with small changes (cardinality, directionality, etc.) with updated change log

• Documentation update and model update - we should get this sometime in early November

• 2 months may be a reasonable to get back by mid-January

• Be ready when we receive it and can extend 2 weeks if needed

Question regarding use of other RDF vocabularies

• If we want to incorporate DC vocabulary etc that need to be moved back into the model

• For example we moved some data types back into the UML model

• The different syntaxes can have rules for how to pull these in (external namespace or DDI namespace)

• It's easier to annotate at the model level

• This question is the purpose of the new working group

• At least needs to be denoted in the model and manage the representation usages and relationships

• There were discussions regarding the acceptance or problems with use of external vocabularies

• The idea of a platform specific model comes back for individual syntaxes like OWL or JSON-LD (only for those that needed them)

• Has been under debate for some time and RDF group will discuss this. In the mean time this is how it is being done.

Codebook update

• Requirements for publication

• Process and tooling

• Oliver's production process slide

• Schema changes are being entered followed by documentation updates

• Adrian Dusa’s comments have been very helpful in identifying specific issues

Tool developed at Dagstuhl
​GitHub - ddialliance/ddi-cdi-sample-generator: JavaScript example application to generate ddi-cdi (json-ld)

• JSON-LD sample generator from CSV file using a view application

• Provides an interactive production of CDI

• Thought is that this should be expanded to Codebook and Lifecycle

• Work should be done in the Developers Group

• Aim for this is to show implementors how to implement

• Olof has written a proposal for a new tool for multiple products

• The NextDoor Publisher (Codebook, Lifecycle, CDI - export only)

• Hope to have an early version out in a few months

• What is needed for the sample generator and variable descriptions

• Ask to file documentation issues in product or TC JIRA

• Example implementation of CV in products

• How to use Codebook - will have a best practices so this can be used to capture this content

• ADD TO PAGES: Point at tool from each products. Would be a good tool when deciding

• This is great. It is something we have been missing for years

• For import Colectica basically does what NESSTAR supported plus whatever has been asked for

• There is a mapping on the Colectica page - it is a listed task for Colectica to get a complete mapping and this would be useful in NextDoor development

• There is an open issue tracker of things Olof and Oliver think need to be done. Add if needed with details.

​Issues · ddialliance/ddi-cdi-sample-generator
​NCCSV

FUTURE AGENDA ITEMS

• Including data in DDI - interesting question regarding a disconnect between data and metadata

  • Dan has submission of paper for COSMOS (not DDI specific)

  • Dataset in Lifecycle is not really used because it requires understanding of DDI to unlock the data

  • Using front matter on CSV with commented out JAMAL etc.

  • A good topic to discuss over drinks at EDDI

• Double check with Jon regarding TC presentation at EDDI - put on December agenda

• Next week no Dan or Jeremy

• Codebook updates next week

ATTENDEES: Wendy, Jon, Darren, Oliver, Christophe, Flavio, Jeremy, Dan

Detailed agenda and outcomes of TC meeting in Ljubljana

• Discuss options paper around work group organization - Focused discussion.

  • Where we are with Lifecycle - get it back on track

  • We have to still make the decision about embedding xhtml imbedded in schema

  • Update the converted lifecycle model to support extensions from privative types (value on class) - either not extend and make properties or change the tooling

  • FUTURE agenda item: change tooling or adjust model - this is a one time import

  • FUTURE agenda item: Dublin Core and XTML embedding in the specification - needs to be in consideration of multiple serializations (RDF, JSON, etc.)

  • Review of RDF specification - Pierre Antoine was going to add tickets (before or at meeting)

    • Property (source variable can only be used on a certain class)

• Goal is to get something that is ready to move in a level review for those outside of TC

• RDF group is getting started in the next few months so not much for the TC meeting

• Participants: Wendy, Jon, Dan, Jeremy, Darren, Olof, Christophe(?)

Update from Scientific Board Meeting

• sub-groups vs working groups for product development (when they should be sub-group or working group)

• Make this a future agenda item regarding this - between now and the TC meeting we get options and implications written down and then presented to SB

Update on CV stuff

• There has been some improvement by developers in Slovenia

• They changed something on the identification of concepts that now gives persistent non-language identifiers which means we no longer need to tweek the RDF and can just port it over. Leaving the transformation to codelist and html page

• Can probably wrap up in November (still a few bugs)

• Quite a lot of issues flagged in CV group itself - Darren should look at this to see if there is anything that we need to worry about

• From technical point of view, we should be able to put this up in 4-5 weeks

Production of CDI

• Talked to Achim about getting information about pipeline

• Diagrams of the workflow of different products (Lifecycle, Moving Forward, SDTL, CDI)

• CDI is manually moved through via Achim

• Can make possible upgrades by adding multiple access to EA and all should be able to extract the XMI and create a pipeline of the steps following that.

• Canonical XMI should be easy to pipeline. Acceleo requires a java library which would need editing at any changes. Sphinx could be pipelined

• Could pipeline some of this - main thing is to get this in a check-in check-out github approach

• Very few people usually editing in EA and they have to coordinate

• EA is not manageable through GIT

• Dif the XMI is technically possible but its a pain

• Has to be forbidden to check in different models of EA and XMI. Never a commit of just one of these files. They HAVE TO BE IN SYNC

• Diagrams are missing from this model - go into documentation

• ​CV Group Meeting Minutes

• Oliver can make these available for a discussion - including future pipeline and getting Achim to correct where needed

• Acceleo - main idea is that it is an eclipse plugin that can use a transformation description to create RDF, XSD, etc.

• To make this into a pipeline you need to surround transformation scripts with something that is possible to run headless

Tool from Dagstuhl

• Future agenda coordinate with Olof

ACTION: Firm up the draft road-map so that it clearer and makes prerequisites clear. Add to Face-to-Face TC meeting agenda

ATTENDEES: Wendy, Jon, Dan, Christophe

Scientific Board agenda

Has CV been contacted
​Scientific Board Working Group Contacts
Darren is contact

Training Group
Who needs to review what? TC does the technical review, what does the SB review or need to review? Structure of the training group and various sub-groups within the Training Group and how that should work.

Working group proposal on Data Capture (Questions and Questionnare work from Paris EDDI, Codebook interest in expressing questionnaire, provenance of data, etc.)
World Bank has expressed interest in a descriptive entry for questionnaire
Insee has a strong interest in this area - expressing specific technical features
Data capture in general

Roadmap
Indication of Lifecycle 4.0 would look like
Codebook change is it a possibility? Is it something that is really a profile of Lifecycle?
Boarder discussion of identification and versioning when it's required and what that means. Multiple serializations raise the question of what is a reference what is a structural relationship, versioning.

Next meeting agenda
Get a sense of what we are going to be doing in Lubjiana
Dan and Jeremy (?)
Wendy
Jon

ACTION: Common concepts and RDF - Dan will be submitting a plan for the working group and can include Christophe and Flavio as an initial member.

ATTENDEES: Wendy, Jon, Dan, Jeremy

CDI update
Production information is being finalized by CDI group and should be delivered to TC in the next few weeks
TC needs to prepare for the review of the implementation formats for accurate rendition from UML XMI
Prior to vote CDI needs to prepare a presentation for voting members

XKOS Best Practices comprehension review
Still seems to be a problem with google to icpsr routing for DDI-SRG
Check out and inform Jared
Have Christophe resend
All TC members should review this document and comment as needed

CV resolution

Progress in URL production from CESSDA tool

Once all points resolved and verified, we can move forward on live resolution system

Keep moving on Codebook

ATTENDEES: Wendy, Dan, Flavio, Darren, Oliver, Jeremy
Excused: Jon

Roadmap development

Additional materials were added and a listing of practical steps added prior to meeting

​Roadmap Work Page

Regarding Practical Steps:

• Production tools - Codebook is there something we can do to support better automation of the process

• Make some notes on what documents contribute (StatsCan - example of what someone else is doing)

  • roadmap is kind of a GSIM view

  • Data Platform - remove

  • Metadata repositories (StatsCan)

ACTION: After completing changes noted above, send links to Darren and Hilde for SB

CV resolution system -

• In reading the GitHub issue dealing with URI correction - not clear if this will resolve the issue

• Oliver and Darren are looking at this (both will be in Dagstuhl to discuss)

• There are still issues, particularly in terms of language management which is different from the DDI approach

• Its a complex pipeline and much of our transformations address changing output from CESSDA - this could be a lot cleaner

• Continuing issue of internal communication and changes occurring without consideration of issues that it causes DDI

• It may be easier to pull out of the CESSDA CV manager

• TC needs to pull together a proposal concerning long-term support of CV manager

• It would be good to have the lifecycle codelist version (these are current products of our pipeline

• Oliver will send Dan example of codelist output to review - the following link provides access to all outputs of the pipeline that transforms CESSDA output

​ddi-alliance/ddi-cv

ATTENDEES: Wendy, Jon, Darren, Dan, Flavio, Christophe, Jeremy

XKOS Best Practice paper comprehension review

Note that XKOS is the first document to go through the technical document review process and is being used to sort out the details
Document is located at:
link-statitics.github.io/skos/skos-best-practices.htl#bp-labels

Comprehension review:

• Intended audience - the question raised in a comprehension review is whether the intended audience understands what is being covered and the intended guidance

• Review process - need to identify intended audience, length of review period, how comments are collected (these will vary with the document)

• Announcement of publication

  • WHO: DDI and others known user groups

  • WHAT: Description of coverage should be in the announcement
    [notes interrupted due to technical difficulty. connection reestablished during a discussion of some questions the TC members had regarding use of time stamp vs. version number]

  • Date stamp only for Best Practice, no version

  • The Technical review was done earlier

  • The comprehension review should address the following

  • Clear what is covered and what is not

  • Are the options and recommendations clear

Audience for review: NSI group, EUROSTAT working group, general DDI Users as a broad pass
Some stats can people will be interested

A few questions were raised based on a quick skim the document

• major revisions of classification

• major versions with new URIs

• proposed URI patterns - a proposal or recommendation (we recommend because...)

• more text around why

• Primarily it was an issue of making sure that users would understand why an approach was recommended as well as what was recommended

ACTION: Have TC members read through and note any issues

Capturing comments:

• How to respond - filing in github is the best way to respond

• Will have a meeting in a few weeks with the European working group for suggestions and ask for some feedback on how short/long it should be

EDDI session proposal
Turn into a presentation - Wendy

Roadmap
The Scientific Board has asked for a draft or whatever the current stage of this work is prior to the in-person Scientific Board Meeting in early October
Steps:

• Last road-map document

• What we captured last August 2022

• Go through past minutes

• Draft - pull it together

• Chur - document

• Put on agenda for next week

Concept/ConceptualText/Controlled Vocabularies used
next week

ATTENDEES: Wendy, Jon, Darren, Oliver
REGRETS: Dan, Flavio

EDDI 2023 session proposal
Need to add specific presenters/titles/short statement
See document: ​EDDI 2023 Proposals

Codebook: Concept/ConceptualText
Suggestion to keep these separate where concept adds all of the specific URL/URN links and a place for the "code". This way the label can go in the textual content of concept (all locations need to be repeatable) and the text portion of the conceptual text retains it role of containing general text related to the parent tag. This was original a means of being able to add specific concepts to large textual pieces rather than use of the text portion to provide labels or description of a concept.

Need a guidence document on this that also pulls in CESSDA discussions and SKOS provisions. Focus on backward compatibility, ease of identifying labels (as opposed to broader descriptive text), and clear transfer of information between Codebook, Lifecycle, CDI, XKOS, CVs, etc.
https://github.com/cessda/cessda.metadata.profiles/blob/main/CDC_2.5_PROFILE/cdc25_profile.xml line 980 for example
ACTION: Wendy will write up and Darren will review and edit

ADDITIONAL INFORMATION:

• Jon submitted the proposal for a TC side meeting at EDDI (number 28)

• Darren will let TC know if there is any material they need to prepare for the in-person Scientific Board meeting in early October (following next week’s SB meeting)

•  

ATTENDEES: Wendy, Jon, Dan, Jeremy, Flavio, Oliver

RDF Union Model Working Group:

• Dan will be sending out an email to user list asking about interest for new proposed working group on RDF

• Do we need a separate official work group for this or just a sub-set of the TC

• Easier to bring other people into from the outside

• Does it have more of a life if its a formal committee

• Relatively informal thing and if it gets legs then think about setting up a group

• Dan will write up and we'll start with it informally

General comments on working groups and coordination:

• TC's role is clear but needs to be clearly publicized

• Is it helpful to have all these working groups (product and topical) if we can't keep them coordinated

• Topical groups in terms of new coverage

• Silo's of products

• New content coming out of product groups can cause issues when coordinating across groups

• Groups need to have a roadmap for what they are doing and where they are going

• New areas need to be exposed to others

ATTENDEES: Wendy, Jon, Dan, George, Oliver, Jeremy, Flavio, Christophe

Dan's email regarding RDF union model

Issues:

• Is there enough commonality between -yes by intent and at a higher level Concept-->Specialized Concept-->Specific content

• A more finite set then what Flavio and Wendy are looking at

• Common representation at at least a specific level

• How atomic objects are put together (similarity/differences)

• What content is transferable what is specific to a product due to its use

• Is there a role for Disco in this - implications in terms of Disco as a published product

• Really requires a separate working group - need to refine the focus

  • RDF (initial but not sole outcome)

  • Harmonization/higher level model for DDI

  • It makes sense to have a dedicated group - task group but could continue as an ongoing support product

  • Define ties to TC as the product coordination group

  • Need people who are familiar with all of the different products - Codebook, Lifecycle, CDI, etc.

ACTION:

• Draft new working group description - Dan will write a draft (Wendy will point to documents describing what is needed)

• Can we do a combination so that there is some short term payoffs and then look with more time - how much is TC still doing and feed this into this group

• Charge should focus on finding commonalities and objects that are and can be shared among the products
  Group shouldn't start out looking at ontologies but at commonalities

• How the group is populated

Overall goals for DDI Suite integration/interplay:

• Move for products to have more common ontology/common objects

• This could be a new core to align products

• Facilitate the movement of content between products (working group would support) - product specific content

• More consistency in future

Principals - clarify

• Coping and handling various content problems (ICPSR, CESSDA, WorldBank, etc.)

• Extending or surrounding - what gets covered by which parts of the suite

• Need for tooling for: decision support, content transformation (to consume content and transfer), other?

• What working groups would support (new group) - comparability from top to bottom

• Jon's experience in Codebook to Lifecycle transfer - what are the problems, how do we develop the products in a way that ease this problem

• For the last decade DDI has lived in this dualistic universe which had a tense relationship and now are becoming trinitarians with CDI. Need a credo that states there is a DDI reality underlying this and needs to be viewed as part of a broader whole.

• This session should probably be written up as an article for IQ

• Post meeting discussion between chair and vice-chair regarding implications for TC role in DDI:

• Roadmaps for each product - what we want to do, how does it align with other products?, should it be in more products?

ATTENDEES: Wendy, Jon, Jeremy, Oliver, Flavio, Dan

Lifecycle 4.0 preparation

Start with the Bugs and move to the improvements
Add column E information comments to Jira issues. Jon will start looking at the bugs.

Presentations for EDDI

• Update from TC - slot which can cover what we need it to

• Could do something on (training or session) Codebook 2.6 or CDI

• Common ground of products - Flavio and Wendy / presentation preparation - session rather than presentation

  • granularity

  • applications needed to support

  • implication for movement between others

  • Referencing from DDI and other products

  • Classification areas

TC meeting

• We need to have very specific outcomes.

• The people we need are the people around the technical committee

• Olof should be invited

• Flavio reviewing the UMI (XMI output)

• RDF tasks - making the URIs for types of items across products (non-product specific) not planned for a time so we need to look at when this can go on the schedule (main item types only). Flavio/Wendy model work can feed into this in terms of identifying common elements. We can get clearer on this as we go along.

• Are there validation implications between different syntaxes (XML, RDF, Json, UML/XMI, etc.). Implications for use, provide shape to various scenarios.

• Check back in during September to see where we are and make we keep tightening this up.

Future meetings

Codebook work primary topic for August
Cancel next week due to attendance

ATTENDEES: Wendy, Jon, Dan, Jeremy, Oliver

AGENDA

• Update on CDI work and technical review work

• TC meeting - in context of EDDI

• Codebook work - remaining few issues, comments from Darren if available

• August/September/October work schedule

CDI

CDI draft of materials they have pulled together regarding process looks like it is covering everything we've asked for

End of August is the earliest we will get this due to vacations etc. This works well for setting up technical review. We should be ready to go with this soon after we receive information from CDI.

ACTION:

Email Arofan with one added item for common approaches (use of External Controlled Vocabularies) as well as the goal to outline parameters of technical review before we receive final materials.

EDDI - TC meeting

• TC Meeting - agenda

• Pick up areas where there were issues where remodeling

• Were the decisions we made workable

ACTION:
Jon and Wendy will start drafting the agenda for the meeting and we can refine as we go along

Activities from Aug-Nov:

• Dan COGS stuff in August/September

• Go over outstanding LIFECYCLE issues for inclusion in 4.0 and getting that work done
  ​4.0 and 4.1 applicable issues

• Codebook - Schedule time ASAP August/September

• Getting schema changes done in August - September finalizing documentation and process info

• Flavio and Wendy - models

• Drafting out when and how to roll out separate lifecycle and codebook groups and then what TC looks like after

• RDF work that came out of EDDI last year - look at this after next weeks review of 4.0 issues

ACTION:
Send Jon content for Codebook high level documentation

ATTENDEES: Wendy, Dan, Jeremy, Oliver, Darren

DDI Codebook 93, 95, 97 - reviewed (see JIRA issues for comments)
All issues were agreed on in general and only specific need to be determined (exactly how changes will be entered)
Darren will look at details and provide comments on how to enter

Lifecycle 4.0
Review of issues to identify which could/should be made it 4.0 especially due to required structural changes
Review of subsitution groups and other obscure XML structures
Test for round tripping between 3.6 and 4.0

ISI World Statistical Conference
ISP session on DDI 20 year cooperation with Statistical Agencies
When presentations published I'll provide links to DDI world

ATTENDEES: Wendy, Dan, Flavio, Christophe

CDI

New XML examples
Cardinality issues for wide (having to have at least one data point)
review to see if there are

List of consistent items requiring comment:

• Identification

• Referencing

• Sequencing

• External Controlled Vocabulary usage

• Ability to run the script (UCmss)

• Templates included in a repository link

• Run in Eclipse add-in (open source tool)

• Mapping of serializations -

• Why the ontology's were selected (other RDF languages)

First impression:

• All properties are unique per class but can make querying the model is more difficult. (why was this decision made)

• The domains of each property are unique

• No mention of cardinalities in the OWL (this is available in OWL)

• Not putting cardinality in but putting in a SHAQL or SHECKL

• Question about cardinality of identifiers

• ACTION: Dan will write up a list of comments or questions regarding sparql query language is pretty powerful. Serialization is written in such a way that makes this difficult to use.

• Consistent property names in past version

Codebook Status
ACTION: Review for change to resolved status

Lifecycle
Milestones - 4.0 (structural change)
Milestone - 4.1 (content updates)
ACTION: Review open issues (fixes that can to in 4.0; what needs to wait; what requires long-term discussion)

ATTENDEES: Wendy, Jon, Oliver, Christophe

Focused Technical Review for CDI representations

Reviewer Suggestions:

Olof Olson JSON-LD (all is the request)
Franck Cotton (turtle)
Oliver Hopt
Benjamin Zepilko
FORS guys nudge specifically (from developers group)
Deirdra Lungley
Sam Spencer
[Christophe and Jon will check with a few within their organizations]

Label to use for issues filed in DDICDI: TC_review_v1.0_rc1

Codebook 2.6 - need to get this moving again and finished up; there is immediate demand for this work to be completed
ACTION: Wendy will go through and create a list of exactly what needs to be completed and provide to Jon and others that can help with completing this

Christophe raised a question:
How do we create a mapping between concepts using Lifecycle, CDI others

Current options:

• Correspondence table - simple mapping, makes use of controlled vocabularies

• Array concept - create a concept broader/narrower exact/similar, subclass or reference

• XKOS - probably best equipped area

• Statistical Classification - check that out

ACTION: Christophe will look at current options and then file a TC issue that can be looked at across products in terms of further development

ATTENDEES: Wendy, Jon, Dan, Christophe, Oliver, Flavio, Jeremy

Scientific Board - please provide Jared with any recommendations for the open position in the Scientific Board. Please verify that the person you identify is insterested.

CDI review

The materials to be included in the review are all in the DDI-CDI repository:  ​ddi-alliance/ddi-cdi

Assumption: CDI will fix known bugs prior to publication vote, requires a new package version. The time involved with having the technical review of the production process provides time for fixing known bugs and any reported during review.

Timeline

• June-July get out for technical review of production process

• Provide 2-3 weeks plus taking us probably through August

• CDI needs to provide a revised packaged based on bug ccorrection and review

Types of questions to consider:

• Use of propriatary file structures. (md, spss.sav, EA, docx, xlsx, etc.) Should these be changed to non-proprietary or instructions provided for general access)

• Diagrams are in EA - folder of diagrams (many in documentation so people don't have to go into EA

• SPSS.sav could this be a set-up file with database if required

• Which documents should be in the package and which should be treated as separately versioned support documents

Review interests

• XML Schema and XMI - Oliver, Wendy

• Production process - Jeremy, Wendy, Oliver, et al

• json-ld ontology - Dan, Christophe, Flavio (ask Ben Z.)

• field-level - Jon, Oliver, Wendy

• High-level - Jon, Wendy, Flavio
  second half may be weaker than first half

Directions for commenting

• Where should we make notes issues and questions?

• Specific issues in JIRA tracker - Use existing CDI tracker with labels TCReview, other one for public review

• List of questions/comments we can go over - google sheet within our folder
  ​CDI Review by TC

Limited availability over summer:
Oliver - July 1 - 18
Flavio/Wendy - ISI July 16-20
Jon July 1-24
Christophe 2 week in July and one in August
Dan won't be at TC Septemberr 28

ATTENDEES: Wendy, Dan, Jeremy, Flavio

Issues from CDI group - this could be changed prior to publication for vote
--Relaxing cardinalities in the areas of dataPoints
--Key contents
--system requirements (will be in data files but not during process)
--Understanding XML examples regarding documentation
--what put out immediately to support spec - explaining the examples more fully
--Examples still need to be passed over to TC

Topic piece for TC meeting

Probably at EDDI Slovenia 27-29 Nov (M-W, add a Th-F)
Space at MPC - as an option (talk to Cathy)

Two to three day
Flavio not sure but would need funding - Minneapolis is easier

Review of specification:

• Complete except UCMIS component tooling - reinforce that this needs to be passed on
  Documentation references this document so this implies this needs to be released at the same time
  Need for additional review - there are now 2 RDF syntaxes are completely new and XML is created with a new tool
  --serializations are now changed or are new
  --specific technical review for alignments and model representation, style of generated OWL etc
  --we don't know the amount of review of this - ask Arofan who has reviewed these outside of CDI that have reviewed
  Would also allow them to change cardinalities prior to vote
  Check documentation for explaination of role of CDI

• What has been changed more recently is the process part and should be looked at by the TC more closely, this has not been used as much as the rest

• If there is a review period for serialization, it would be good to have notes available prior to that
  --UML-normalized
  --Normalized to OWL etc
  Documentation of why and how - completing whats mentioned in the notes
  There is more to review in auto-serialization process (consistency, coverage, etc.)
  Track how we set this up for future reviews
  --suggest specific people
  --future reviews for this or other products (first serialization situations, second serializations)

Areas of review focus by members:
Jeremy in the next 2 week - XML serialization and production
Flavio - production process, whole stack to see everything is in place

Additional items of note

• Reminder of Dagstuhl invitation for interest in attending
  Interoperability workshop more open initiation

• Once new version of Lifecycle is out we want to look at the physical description for simplification and broader coverage, NCubes, dataset reference metadata can be easily transferred back and forth. First stuff after production. Good topic for content meeting in next fiscal year requests

ACTION ITEMS:

• Send request to TC members regarding review of French language versions of training slides

• Inform Arofan of interest in a techncial review of serializations and auto-generation processes. Who has reviewed these to date? When will the UCMIS be available?

• Send request to TC members regarding internal review of DDI-CDI package: initial questions, aspects they would individually like to look at.

• Reminder of the Dagstuhl invitation for interest

Due to individual conflicts on 05-25 and IASSIST 06-01

ATTENDEES: Wendy, Jon, Dan
REGRETS: Flavio

1 Membership updates
Genevieve will be leaving TC due to change in position
Ask members to each suggest one person
2 Presentation at Annual Meeting
focus is on future focuses (see ppt) reviewed approach of stating goals followed by specific areas of work
3 Schedule of expected activities through mid-September
CDI
Codebook
SDTL - Talk to George in June about version 2
Lifecycle - COGS (Dan will be working on remaining issues)
Any on-going individual work (web pages, broad modeling)

4 Administrative
Summer scheduling availability:
Jon - gone most of June
Wendy/Flavio - out July 16-20 for ISI

Cancel next 2 weeks meeting (May 25 and June 1)
Members will be notified when CDI hands over package materials so they can start looking at them independently

ATTENDEES: Wendy, Jon, Darren, Oliver, Flavio, Dan

CV update
Several issues have been resolved at CESSDARemaning should be resolved at meeting ERlang (Erikson created)Concept URIs is all that is left to fixThis should allow for test system roll-out right after Annual meetingMay 24th meeting - roll out test and work out production run