2020-2021 Minutes Page, 2018-2019 Minutes Page, 2016-2017 Minutes Page, Pre-2016 Minutes Page
ATTENDEES: Wendy, 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 |
ATTENDEES: Wendy, Jon, Dan S., Flavio, Darren --ID and Reference for COGS --Publication process for CDI - new date is mid-July --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 |
ATTENDEES: Wendy, Oliver, Dan S Updated on CDI status, Codebook review status, COGS input corrections, and LOD work at UKDA
|
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
|
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 |
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
|
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:
|
ATTENDEES: Wendy, Flavio, Darren Funding requests
Codebook 2.6
TC priorities for next year:
|
No meeting |
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
|
ATTENDEES: Wendy, Jon, Dan S., Flavio, Oliver, Johan, Daren Agenda Items:
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.
|
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:
|
No meeting |
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 |
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? |
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:
|
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
|
ATTENDEES: Wendy, Oliver, Larry, Flavio, Dan S., Barry Codebook -
LOD Infrastructure
Virtual Meeting
XKOS Best Practice Review
Scientific Board WG on URN -
|
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 |
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 |
ATTENDEES: Wendy, Jon, Dan S., Oliver, Larry, Barry Review of Work Plan: XKOS:
COGS Virtual meeting
Mapping Work:
Additional Notes:
|