Earlier Meeting Minutes:
2022-2023 Minutes Page, 2020-2021 Minutes Page, 2018-2019 Minutes Page, 2016-2017 Minutes Page, Pre-2016 Minutes Page
Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
ATTENDEES: Wendy, Jon, Oliver, Dan, Jon, Darren, Flavio Implementation Language meeting around EDDI Funding for Fall meeting on Implementation Languages has been approved. We need to develop a more fully developed outline for this meeting to discuss with CDI later in July.
Codebook 2.6 review
COGS No Jon next two weeks - no actions on COGS until then August meeting of TC in Minneapolis Funding has been approved Specific goals and outputs from August meeting: --Document changes in structure CANCEL Next two meetings - June 30, July 7 | ||||||
Expand | ||||||
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
The model definition itself doesn't need any knowledge so perhaps in the settings area rather than just in the code. Clearly shouldn't be in the model
This would be useful for documentation at the serialization level.
See issue Number DDILIFE 3703
--Publication process for CDI - new date is mid-July
--submission
--parts delivered
--difference on contents to determine if additional review is needed
--clear statement of what members are voting on as this is a new product for the DDI suite
Place on future agenda - Please think about this so we can move through the process expeditiously
--DDI Codebook comparison to other products - work done by SND - how to integrate this into DDI work on comparison https://zenodo.org/record/6505238#.YqyJwnZBz-g
Place on future agenda
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Oliver, Dan S Updated on CDI status, Codebook review status, COGS input corrections, and LOD work at UKDA
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Flavio, Darren In person meeting If funded by Exec Committee the TC In person meeting in Minneapolis at ISDRI has been approved for August 1-5, 2022. A note has been sent to TC members confirming the dates. Presentation at Members Meeting and Scientific Board The Members meeting presentation is only 3-5 minutes in length. Focus will be on funded activities and Codebook work. Will get a short statement from Darren so that this work presented accurately. Next year focus of coordinating multiple implementations of products and progressing on the production platform. COGS decisions regarding Identification and Representation properties, use of citation
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Oliver, Dan S. Annual Report No additional comments, will leave available through Sunday and then send in Codebook
COGS work Reference:
Identifiers:
CHOICE issues are being sorted PhysicalDataProduct
Representations
CV and RDF resolver: https://rdf-vocabulary.ddialliance.org/cv |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Oliver CV work
DDItoCogs issues from Virtual Meeting
Standing on the Agenda
Report for the Scientific Board Meeting
Date for F2F Technical Meeting
Codebook Review
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Dan S. Update on CDI Virtual Meeting:
Topics to discuss:
Substitution Groups:
Reference
Rational to document:
Organization:Monday
Tuesday
Thursday
Actions:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Flavio, Darren Funding requests
Codebook 2.6
TC priorities for next year:
|
Expand | ||
---|---|---|
| ||
No meeting |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Oliver, Darren, Flavio DDI Agency Registry publication/announcement
Identifying technical contacts in DDI Notes from Jared's email
Preparing for May Virtual meeting - what we need to complete in April Items below were noted today and are on the page
DDI Alliance resolution system for CVs and RDF vocabularies
|
...
title | 2022-03-24 |
---|
ATTENDEES: Wendy, Jon, Dan S., Flavio, Oliver, Johan, Daren
Agenda Items:
Worked on Funding requests preparing them one for discussion with CDI (this was recorded as changes in the draft documents found in TC Draft shared google folder.
Did a final review of the recommendations for technical document review. This can be sent to Ingo and Hilde for discussion in SB
Members were asked to look at DDICODE-85 regarding a new Codebook Tree document and add comments as needed.
Discussion of the Recommendation for Review of Technical Documents brought up some broader issues noted below. Some of these are broader than the purview of TC so they will be raised in SB or EB as appropriate.
...
Discussion of types of documentation, technical interoperability, semantic comparability, use case focus
...
Organizing information can be difficult to meet the needs of different people
...
Need to be clearer about what can be found where
...
Technical interoperability
...
Semantic interoperability
...
Clearer publication of what is covered and perspective - on product page
...
How to describe the decision making approach in using different features (CVs, Variable Cascade, etc.)
...
What is the line between "official" publications of a product and what are supplementary materials (like the training materials)
...
Guidance documents by users of DDI
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Flavio, Oliver Reviewed current work plan through December 2022
May virtual meeting on COGS work: Outstanding issues:
What can we do pre-meeting
Documents recently discussed in TC draft google folder:
|
Expand | ||
---|---|---|
| ||
No meeting |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Larry, Oliver, Dan S., Darren, Johan CV documentation in codebook DOI's for Best Practices and High Level Documentation Citing a standard you reference the specific home page URL Step this back to the question of what is the need for a separate DOI for these official publications related to a product. We need a clearer sense of the use case for this as well as the broader need. Doing DOIs requires that we managing versioning more than an internal log of update changes within the document. If we can't cite a document without a DOI then we need a DOI. File and management persistent identifier versioning situation ACTION: Nail down what needs to be done for the documentation of the changes to the DDI Agency Registry both on the site and on the DDI Alliance page, then the announcement. CANCEL Meeting on 10th March |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Larry, Oliver, Dan S., Darren, Johan, Carsten (2nd half for URN discussion) Codebook: Reviewed changes to agent types, conceptualTextTypes and concepts - spreadsheet should be implemented as listed Enter these as a set for review, then enter documentation changes to 68 items. Note that 5 items need examples. Mapping: Johan - Project Shoc (social sciences and humanities open cloud) to create mapping to other standards and policies for conversion. There is a month and a half to the end of the project. Present to work to TC next week. Contact Flavio who will not be able to attend. Recommendations part:
Carsten: Diagram of URN resolution works (diagram in the SB WG paper) If there is an established resolver used by agency You'd have to know the common name for the web/URN/verbatim service record and could use the DNS records to look up where those resolves are How to come from DDI to the actual object This can do "N to T" General Discussion
Background Information: Carsten's email: From Dan's slides from EDDI (https://doi.org/10.5281/zenodo.5747652) I understood as follows: Did I understand this correctly and where can I find a full documentation of steps two and three to follow end to end? |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Larry, Dan S., Oliver, Flavio, Darren XKOS best practices:
Codebook: DDICODE-83 and general policy for use of conceptTextType
The cutoff for deciding if an element should change from a simpleTextType to a conceptualtextType:
DDI Agency Registry:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Oliver, Flavio, Larry, Darren, Dan S. Update on Codebook activities:
Follow-up on TC review of URN Working Group paper:
CV LOD system
COGS After the virtual meeting regarding COGS input we will be focusing on COGS output with a goal of identifying where similarity in formats for XML, RDF, JSON-LD, other formats is useful between products and where differences are needed to support specific applications. Planning needs to start for funding and scientific plan in conjunction with the groups developing products. For example, Pierre Antoin has a relationship with Scientific Board in terms of development of RDF JSON-LD for DDI-CDI and RDF in general. This discussion is broader than TC and work has been done in each of the products with one or more formats that needs to be considered:
Google groups and role of SRG list
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Oliver, Larry, Flavio, Dan S., Barry Codebook -
LOD Infrastructure
Virtual Meeting
XKOS Best Practice Review
Scientific Board WG on URN -
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Larry, Johan, Darren, Flavio CV work CODEBOOK
CDI is still finalizing documentation and will get to use dependent upon peoples work availability. ADDITIONAL ISSUES we need to organize for discussion:
Discuss when work plans need to be in for SB and how this coordinates with the financial requests. NEXT WEEK NO TC due to Scientific Community Meeting |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Larry, Oliver, Dan S., Darren, Flavio, Johan Requirements and Process Management - Integrated production framework and platform
Codebook CV work
Requirements and Implementation Management DDI Agency Registry update work |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Oliver, Larry, Barry Review of Work Plan: XKOS:
COGS Virtual meeting
Mapping Work:
Additional Notes: EDDI videos will be coming out in the next few weeks as they come in - Jon will talk to Jared and probably post by track Jeremy, Flavio, Christophe, Olof Scientific Board Strategic Plan [note Flavio and Dan are elected members on the SB. Wendy is ex-officio] 1.4 W3C and explore - RDF representation preparation in 2024 - why would we want to give away the variable cascade to another organization 1.6 no date so when is this supposed to be worked on? non-open source like Colectica - what does it mean? The notion that we are working with commercial vendors and make no mention of those we currently work with. What exactly are we trying to develop? Work with related software (analysis tools) regarding input/output support? 2.2 we don't have an activity defined as such, what is in 2024? Clarify what this is mean here? architecture of content or of repository. Starting when? 2.3 addition of SDMX and HLG to this group specifically or as part of whole DDI interoperability. What do we mean by this in terms of organizational level? 2.4 The example is about domains not geographies but domain areas. Awkward, examples do not relate to geographies. 2.5 Progress toward ISO certification (we started, why is this 2025? What is meant by progress. More details - contact continuation, paperwork, GENERAL: of strategic plan to prioritize and focus work on specific areas. Concern there is too much for too many. Who is going to do this. 3.1 TC is working on in terms of organizing documents and publication 3.2 difference between 3.2 and 3.4? GENERAL: Verbiage is abstract making it difficult to differentiate and make sure that different aspects are identified as sub-bullets Omitted support of DDI Codebook 2.6 3.8 don't understand what this means (modularity within a product), but between products? Why is the example is a provenance model. Discussion on user mailing list (conceptual, and reference variable) was the actual issue we would face with 3.8. things differ between products and there are different implementations in various products. Need for metamodel to understand what is found in multiple products, but varying implementation. Example of metamodels (Groups). Need both metamodel to understand differences, and in some areas a single mullti-use content. Suggestions in the scientific model that haven't been discussed. They seem to be arising from a minimum number of sources "Let's do a provenance model" opens up a can of worms. No background discussion. There is a process raising topical rears and pursuing their development across products in one way or another. HOLES?: Lack of content regarding how to use DDI suite together. (maybe related to 2.6) maybe expand to include 2024? ACTION:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Dan, Christophe, Jeremy Newsletter submission TC report to Scientific Board Glossary Group document publication DDI Lifecycle github issue Rather than think of the specific item raised here ACTION: Wendy enter this discussion on #38 (DONE); others should add comments on role of RepresentedVariable or other points as needed NEWS: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Flavio, Dan, Oliver, Christophe, Jared, Jeremy
--Is it possible to move everything to AWS? How complex might this be to maintain and supervise Current view of what goes to AWS: --Clean up even before vendor --Splitting may have unintended consiquenses such as loss of database functions (publications, examples, etc.) --Would the options we are looking support these --Issue about having to shadow the brand and sync it between 2 sites and with a 3rd party vendor --What potential costs there would be with backup etc. - there is still need for web support (not completely volunteer) --It seems to me that we are missing a written target sitemap (whether we have one or two platforms) that would guide the specifics of the migration. --Could we take a few weeks out to design what we want the site to look like https://docs.google.com/spreadsheets/d/1y54OKTmJeSV3YwxR6RBa7yJyHvD8P1drjPmG4C2vZoM/edit#gid=517461823
|
Expand | ||
---|---|---|
| ||
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Flavio, Christophe, Dan Pages from Alliance site
Specific questions: docs.ddialliance.org - what is this intended to provide
Resources:
Agency registry:
ACTION ITEMS:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Oliver, Darren, Dan 1-Codebook pull request 2-Funding requests (Deadline is 26 of April)
3-Strategic Plan 4-Administrative documents 5-CDI submission to TC and production process review Other:
FUTURE: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan, Oliver, Darren, Christophe AGENDA Resolution system CV system
RDF hosting/resolution
Codebook pull request review OK and merged 4.0 BETA issues - Comments also added to issue discussion in GitHub Item 8
Item 23 Item 36
FUTURE |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan, Flavio Review of approach to issues 8, 23, and 32:
Additional Topics: 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: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Oliver, Dan, Jeremy, Darren, Flavio, Christophe Codebook
ACTION ITEM: DDI-L 4.0 Beta 1 Issues
ACTION ITEMS: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Oliver, Darren, Christophe Webinar review
ACTION: Jon will start drafting governance documents Status on CV and pipeline
Codebook
NEXT WEEK: FUTURE AGENDA ITEMS (as ready): GitHub administration and guidance Publication repository on Bitbucket - options/plan |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Flavio, Christophe, Jared (guest) GitHub:
ACTIONS:
Clarification of document repository approach
ACTIONS:
DDI-L 4.0 BETA review of webinar
Questions regarding spreadsheet
ACTIONS:
XKOS update:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Dan, Oliver, Jeremy Infrastructure: AWS issue: Webinar FUTURE AGENDA: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan, Jeremy, Flavio, Oliver DDI-L 4.0 BETA webinar As of last Friday, we had 35 sign-ups. Draft of short presentation contents AWS set up TC budget for AWS has been approved, so we need to get moving on setting up an account, presumably we need to get Jared to put the Alliance down to pay that. Talk to Darren and/or Olof about taking this on to get set up. Product Page Implications for how the content is made available on the download and doc site for each product A revised example will be made based on comments. Follow with examples of transfer of all product pages. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan, Oliver, Christophe DDI Lifecycle 4.0 BETA webinar
DDI infrastructure proposal
Atlassian
NEXT WEEK:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan, Oliver, Flavio Discuss page change drafts for products (TC-242, TC-243, TC-244)
Organization and ongoing management of GitHub content TC pages under Learn dropdown on Alliance site NEXT WEEK: |
Expand | ||
---|---|---|
| ||
No meeting was held. The following is the information sent out to the group for their attention and action: TC issue tracker Use filter TC-outstanding to filter out completed issues Notes from DDI-CDI meeting on 2024-01-17 Comments about Git repository raised during CDI meeting on 2024-01-17 - note that Achim was not present so there will be more Organizing BETA access, support repository, policy, pull requests Each product needs to provide a canonical expression of the product |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan, Jeremy, Flavio, Oliver Update on CDI work
Topics for future webinars
DDI-L 4.0 BETA review
EDDI session on priorities
Follow-up on - web pages and webinar with Jared
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan, Jeremy, Flavio DDI-Lifecycle version 4.0 beta follow-upWebinar of some description
ACTIVITY: (Wendy review and create list) pull discussion pieces together, clean up, post, and send links Product pages on Alliance Site Overview of products page can be updated but is in good shape overall
|