TC Meeting Minutes

Earlier Meeting Minutes:

2022-2023 Minutes Page, 2020-2021 Minutes Page, 2018-2019 Minutes Page, 2016-2017 Minutes Page, Pre-2016 Minutes Page

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

1-Codebook pull request
ok and merged

2-Funding requests (Deadline is 26 of April)

  • Face-to-Face again

  • Infrastructure costs - flag and could suggest it should be a regular budget line; software contingency budget as well as on-going costs

  • 10K last year was infrastructure contingency from which a couple of months of AWS

  • Alliance pays Colectica and this will move to AWS at some point
    As part of the move to AWS a bit of work needs to be done to convert from zone file to AWS (route 53) - Dan will write up

  • Admin data meeting - talk to Flavio about meeting next year; funding request

3-Strategic Plan
Looks good - no questions or specific concerns from TC members at meeting

4-Administrative documents
Not ready for discussion

5-CDI submission to TC and production process review
Darren talked with Arofan about RDF URLs and everything is in line

Other:

FUTURE:
No Oliver until April 18
No meeting on 11th due to COSMOS conflict

ATTENDEES: Wendy, Dan, Oliver, Darren, Christophe

AGENDA

Resolution system

CV system

  • Access to https://github.com/ddialliance/ddi-cv-platform (am hoping that Oliver will be at TC tomorrow).
    All is in hand

  • Misalignment of version numbers in https://github.com/ddialliance/ddi-cv - logged at

  • This has been resolved, however there is a problem with the resolving the old version numbers x.x rather than x.x.x

  • They will check with CESSDA after talking to Sanda identify where the problem is in terms of inaccurate extensions

RDF hosting/resolution

  • RDF hosting/resolution for CDI (upcoming) is not a dependent on the CESSDA CV version issue being fixed.

  • DB will contact Arofan to clarify CDI RDF serialization’s readiness and double-check required URI patterns for CDI

  • All CVs have unique URIs based on version numbers and are stored in Fuseki default graph.  For non-CV products e.g. CDI or DDI4 (that don’t necessarily have versioned URIs) we will create individual graphs for each product.

Codebook pull request review

OK and merged

4.0 BETA issues - Comments also added to issue discussion in GitHub

Item 8

  • Changing from internal CV to external could be a Lifecycle 4.1 task

  • Identify those that could be CV

  • Add enumeration documentation to the item type

  • Group ones should probably be taken over by CV group

  • Dan will look through to make sure enumerations are coming through correctly - OWL specs may require URIs for enumerations (this would be an issue for next round of review - how referenced

  • Wendy will look at CV options now. Darren can look at later. This is not urgent.

  • Adding documentation on lists that are currently there. Create notes of what should be added to each README file.

Item 23
Not critical in short term. Good to get multiple eyes on this.

Item 36

  • Should be addressed in 4.0 BETA 2

  • Add additional notes on previous discussions

  • Group instances to see what could be managed in the same way

FUTURE
Administrative documents (Jon) as available (Jon not on call)

ATTENDEES: Wendy, Dan, Flavio
POST-MEETING WRAPUP (due to forgetting US change to DST): Jon, Darren, Oliver, Christophe

Review of approach to issues 8, 23, and 32:

  • Issue 8: (spreadsheet has been added to issue)

    • Identify good canditates for conrolled vocabulary

    • Group itesm need either documentation of definitions of types or use a controlled vocabulary. This is true of internal enumerations currently containing documentation.

  • Issue 23: (spreadsheet has been added to issue)

    • When versionables reference other versionables looking for order needs - assigning of contents is required or used

    • DISCUSSION: How explicit order gets injected - clearly needed in some serializations but XML has two camps (order implied, order not implied)
      First step is identifying where order is needed

Additional Topics:
ISI presentation:

ISI do we want to propose something on DDI like last year in Ottawa?

Does TC want to send something - IPS

We have 3 weeks - kick around an idea for a topic

Something beyond use cases

Parts of DDI - multiple serializations

How content fits together and can move between products

3-4 people with or without discussant

XKOS:
Best Practice ready to go so look for email on that

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

Codebook

  • Pull request has been amended and content is now correct

  • Looking forward, the concept/conceptualText will be posted immediately following the resolution of the current pull request

  • This will be followed by the remaining issues which are more targeted

ACTION ITEM:
Dan will note items that are NOT documentation change so they can be reviewed next week

 

DDI-L 4.0 Beta 1 Issues

  • Another beta the middle or end of April after gathering COSMOS feedback

  • An issue on representing sentinel variable values in Represented Variable

  • All new content issues should go into GitHub. They will be tagged for releases.

  • This will also allow broader discussion of content issues in clearer way than we have been able to do before.

 

ACTION ITEMS:
Wendy:
#36 - go back and pull together the earlier discussion of dealing with extended reference and review current need for continued use of this content
#8 - review enumerations as converted to CSV and conversion to outputs
#23 - locations of ordered attributes
Jon:
Administrative documents - add content on #16, #17, #30, #31, #32, #33, #34

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

Webinar review

  • A lot of people who we seldom or never seen

  • Good suggestion:

    • Guidance on pull requests

    • We can set up templates

    • Contributors guidance document

  • Missing documents

    • What is the model

    • Master?

    • Development version

  • In terms of code the past published specifications can be compared

  • Between 3.2 and 3.3 we could do a dif but we can't track between 3.3 and 4.0 because each generation is structurally different (dependent on mapping and change documentation)

  • The ability to track individual changes

  • How do we want to do this? If we publish 4.0 as a package

    • Track each time only model changes not differences in different serializations

    • We could do this locally [there will be so many structural changes a dif won’t work]

  • At the moment published versions are in Bitbucket so we need a separate repository to hold published versions in GitHub to replace this

  • Jon has started adding files (citation, license, contribution guidance, form for contributions

  • One issue about having a missing license file we use cc-by [Note that the Alliance has determined that this is the license to be used by all products. We will need to check license on production programs (cc-by was not on the list of options]

  • Document how things move through approval and that people can build on their own branch

  • There is a GitHub project called DDI-CDI and DDI-CDI-resources

  • Needs to be on DDI Alliance set of repositories

  • There is no governance on the Alliance site

ACTION: Jon will start drafting governance documents

Status on CV and pipeline

Codebook

  • Pull request for ddi-c_2

    Note that the first ff3481b is bogus. It is the second commit 0cce353 that contains the documentation changes to codebook.xsd

  • How to process through these?

    • People could put in comments in before next meeting for the documentation

    • The documentation content and the next (Concept/ConceptualText) are large. Some review should take place outside of meeting and then deal with questionable areas with group. Future edits should be more localized.

    • Oliver will check to see if there is a clear way to correct and entry error (alt is to reject pull request, kill this Fork and start over)

NEXT WEEK:
Codebook - Documentation review

FUTURE AGENDA ITEMS (as ready):

GitHub administration and guidance

Publication repository on Bitbucket - options/plan