Earlier Meeting Minutes:
2020-2021 Minutes Page, 2018-2019 Minutes Page, 2016-2017 Minutes Page, Pre-2016 Minutes Page
Expand | ||
---|---|---|
| ||
Expand | ||
| ||
ATTENDEES: Wendy, Jon, Dan, JeremyOlof, Flavio, Jeremy 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
| ||
Expand | ||
| ||
https://ddialliance.org/Specification/DDI-Lifecycle/BETA Jon and Dan are checking it out in EA by entering and then exporting a single instrument Announcement content: Add UML output Maybe for high level documentation we can pull background information together as well as address questions raised Final steps Dan will merge UML updates in shortly and tag a package for release Change to Beta version in documentation Jon will get it out on social media Updates of ddialliance site pages Get Wendy the appropriate links for updating pages DDI-Lifecycle | Data Documentation Initiative Olof Olsson 9:23 AM Next meeting: 4 Jan 2024 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan, Olof, Oliver, Flavio
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan, Jeremy, Olof, Oliver, Flavio, Christophe
Content: create a draft release on Github and create notes Email draft: email content and draft of any additional information not in content documentation
Jon will speak to Jared and make sure we have domain names for documentation
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan, Jeremy, Oliver, Flavio Roadmap document TC Organization paper RDF common set working group IASSIST |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan, Jeremy, Flavio, Darren, Christophe, Oliver Review of CDI processing
PROPOSAL replace green box with section: File an issue on this product 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 New working group on RDF (Dan) Codebook
CV releasing a new version resolving SKOS issues COSMOS - Admin Data workshop - has it been set? NEXT MEETING: No meeting in November after 16th; no meeting on December 28th |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan, Jeremy, Oliver, Christophe Alternate 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. How to describe multiple storage formats of a single study description/variable description. Add to Guide/Best Practices content. DDICODE-534 DDICODE-537 Funding request to support IT infrastructure for development tools - maintenance, upgrade etc. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Flavio, George discussed DDICODE-536 and DDICODE-537 see comments in issues Items for a process derivative products canonical UML model Derivative of the process we use "canonical UML" Set up the review and publication process for these process derivative products |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan, Olof, Jeremy, Flavio Published Agenda
CDI Syntax Representations
Question regarding use of other RDF vocabularies
Codebook update
Tool developed at Dagstuhl
Issues · ddialliance/ddi-cdi-sample-generator FUTURE AGENDA ITEMS
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Oliver, Christophe, Flavio, Jeremy, Dan Detailed agenda and outcomes of TC meeting in Ljubljana
Update from Scientific Board Meeting
Update on CV stuff
Production of CDI
Tool from Dagstuhl
ACTION: Firm up the draft road-map so that it clearer and makes prerequisites clear. Add to Face-to-Face TC meeting agenda |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan, Christophe Scientific Board agenda Has CV been contacted Training Group Working group proposal on Data Capture (Questions and Questionnare work from Paris EDDI, Codebook interest in expressing questionnaire, provenance of data, etc.) Roadmap Next meeting agenda 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. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan, Jeremy CDI update XKOS Best Practices comprehension review 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 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan, Flavio, Darren, Oliver, Jeremy Roadmap development Additional materials were added and a listing of practical steps added prior to meeting Regarding Practical Steps:
ACTION: After completing changes noted above, send links to Darren and Hilde for SB CV resolution system -
|
Expand | ||
---|---|---|
| ||
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 Comprehension review:
Audience for review: NSI group, EUROSTAT working group, general DDI Users as a broad pass A few questions were raised based on a quick skim the document
ACTION: Have TC members read through and note any issues Capturing comments:
EDDI session proposal Roadmap
Concept/ConceptualText/Controlled Vocabularies used |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Oliver EDDI 2023 session proposal Codebook: Concept/ConceptualText 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. ADDITIONAL INFORMATION:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan, Jeremy, Flavio, Oliver RDF Union Model Working Group:
General comments on working groups and coordination:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan, George, Oliver, Jeremy, Flavio, Christophe Dan's email regarding RDF union model Issues:
ACTION:
Overall goals for DDI Suite integration/interplay:
Principals - clarify
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Jeremy, Oliver, Flavio, Dan Lifecycle 4.0 preparation Start with the Bugs and move to the improvements Presentations for EDDI
TC meeting
Future meetings Codebook work primary topic for August |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan, Jeremy, Oliver AGENDA
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
ACTION: Activities from Aug-Nov:
ACTION: |
Expand | ||
---|---|---|
| ||
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan, Jeremy, Oliver, Darren DDI Codebook 93, 95, 97 - reviewed (see JIRA issues for comments) Lifecycle 4.0 ISI World Statistical Conference |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan, Flavio, Christophe CDI New XML examples List of consistent items requiring comment:
First impression:
Codebook Status Lifecycle |
Expand | ||
---|---|---|
| ||
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Oliver, Christophe Focused Technical Review for CDI representations Reviewer Suggestions: Olof Olson JSON-LD (all is the request) 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 Christophe raised a question: Current options:
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 |
Expand | ||
---|---|---|
| ||
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
Types of questions to consider:
Review interests
Directions for commenting
Limited availability over summer: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan, Jeremy, Flavio Issues from CDI group - this could be changed prior to publication for vote Topic piece for TC meeting Probably at EDDI Slovenia 27-29 Nov (M-W, add a Th-F) Two to three day Review of specification:
Areas of review focus by members: Additional items of note
ACTION ITEMS:
|
Expand | ||
---|---|---|
| ||
Due to individual conflicts on 05-25 and IASSIST 06-01 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan 1 Membership updates 4 Administrative Cancel next 2 weeks meeting (May 25 and June 1) |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Oliver, Flavio, Dan CV update DDI Annual Meeting Future focus:
Jira issue
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Oliver, Dan, Flavio Exec Meeting (from Jon) CDI update Follow-up on discussion with Daryl last week TC report at the annual meeting |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Oliver, Flavio Developers Group relationship with TC
Alliance web pages - current changes and future options
Guest at half past the hour Daryl Hepting - Disco interest ACTION:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Flavio, Dan, Oliver, Christophe, Jon Controlled Vocabulary
Activity updates
2024-25 work priorities (google doc version for future work 2024-25 work priorities )
COGS I need actions here. This was a priority for this year and we seem to be stalled. How do we fix this?
Other issues? See DDILIFE-3713
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Jon, Oliver, Darren
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Flavio, Darren, Genevieve, Christophe, Dan Introduction of new memberChristophe Dziowski (Insee)
CV resolution update
Postman collection for test RDF system: Funding
ACTION: Wendy will complete and send out for any additional comments and then turn in on April 10 Face-to-face
Administrative data Need to clarify a couple of points in cost estimate with Jon Approved within group Does not address infrastructure development work. Focuses on maintenance/bug issues. Any long term needs for standard maintenance or infrastructure (cloud space for example) should eventually become a standard budget item not a yearly request DDILIFE-3512Dan will provide example of how to handle use of UserAttributePair of identifiable parent object with multiple CodeValueTypes. Add to a future agenda for review |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Flavio, Jon, Darren, Oliver Location of updated SKOS output for CVs (Wendy will add object structures to database of DDI products) Funding Discussion: DISCO discussion: CESSDA and CV update: URI's in CESSDA output have been updated (not totally right - still human readable - but not a problem for us CESSDA is migrating from bitbucket to GitHub which will cause some issues During meetings in CESSDA after 28th April we can move on this then (based on Darren's availability) The URI's generated on our side will remain constant over time |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Genevieve, Oliver, Dan REGRETS: Flavio, Jon, Darren Scientific Board Issues TC reviewed the issues from the Scientific Board 2023 extension of their workplan. The goals was to identify what materials we needed to pull together to support further work by the Scientific Board. We also considered the timelines for these issues so that we can add them to our 2023 workplan. See the Google Doc in the TC Drafts folder: Scientific Board Goals Requiring TC Input DDICODE-101 We reviewed the additional comments from Taina and Sanda on this issue. See the Jira issue for additional discussion. We have proposed a solution which will be fleshed out in the next few days for review. Note that this solution attempts to balance the intent of concept and conceptualText, the needs noted by the filers, and the need for consistency over the versions of Codebook. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Oliver, Dan, Darren Update on CDI work schedule - shared draft from CDI DDICODEBOOK see issues for discussion, comment, and resolutions where decided |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Darren, Dan, Genevieve, Flavio Codebook issues - some specific questions and also how you want to deal with non-response to questions we've asked filers LIFECYCLE Controlled Vocabulary alignment with Codebook Status of CV system - further discussions with CESSDA and our next steps in terms of reporting status and any action we want from SB New issues with DDI Alliance web pages and future changes in Drupal and page options |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Genevieve, Dan REGRETS: Jon, Flavio Discussed Marketing Group role per request from Jared. Notes located at |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Oliver, Flavio Clarification of TC check list for product review prior to publication
ACTION:
SB-12
Recommended:
ACTION: Darren will work on wording based on this discussion Codebook issues needing comment from Katja and Sanda have gone out (5 issues) Postman promotion of DDI Controlled Vocabularies and other content
TO DO:
ACTION: Darren will prepare something for the next SB CV work:
ACTION:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan, Darren, Oliver, Genevieve DDI Alliance web pages (Products section) Ideally we should be able to generate a landing page for CVs Don't understand where we currently are on the Drupal GOALS:
How does DDI manages old content? Is there a process? ACTION: Create a set of redirects that we want ACTION: Darren will send suggestion for product page structures ACTION: Oliver will look into Drupal capabilities DDICODE-101
ACTION: Get back to filers and find out exactly what they want to express and review solutions DDICODE-95 DDICODE-90/91 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan, Jon, Oliver, Genevieve, Darren DDICODE-101 Notes are on the issue. We discussed both the request, the desired usability based on the request, and software issues. Darren and Dan will go through carefully. This will probably need a meeting with Katja and Taina to resolve. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Oliver, Genevieve Went through SB draft of 2023 workplan and added comments in time for SB meeting on 2023-01-17 Reviewed number of Codebook issues that were outstanding. Resolving or identifying where more information was needed see Jira with filter Codebook-Outstanding |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Flavio, Dan, Genevieve, Oliver Reviewed document of SB work plan making notes regarding updates and requests for more clarity Jon will draft the report form so we can respond and get in by due date to SB COGS still has a couple tickets left In JSON we are treating this as a property Could be done after conversion so we are not doing a lot of editing. Dan will look at what needs to be done and when they can fit it in CODEBOOK |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Flavio, Dan, Oliver Reviewed the notes from the Integration Languages workshop ACTIONS:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Flavio, Oliver, Dan, Darren NOTE: No meeting until December 8 due to US holiday and EDDI AGENDA: Carry over from last week ACTION: Darren will make the changes noted and contact Achim and Pierre-Antoine Recommended sub-agencies: initials are consistent with past identification as DDI-L, DDI-C, and DDI-CDI
ACTION: Wendy will write up and contact Jared and Darren about getting these filed. Product maintenance groups will be informed of the name of the sub-agency as filed. Update of 2021-2022 TC work plan to cover 2023 See comments on document |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Oliver Test RDF-vocabulary: Controlled Vocabularies - Overview Table of Latest Versions | Data Documentation Initiative Scientific Board extsion of 2021-2022 plan to cover 2023 Draft of URI construction
use of rdf.ddialliance.org/[product]/[version]/ DDI Sub-agencies for products in DDI Agency Registry: Should each product have a sub-agencies to file Draft a list and verify the names to match the CV Lifecycle: int.ddi.life or int.ddi.l Codebook: int.ddi.code or int.ddi.c XKOS: int.ddi.xkos SDTL: int.ddi.sdtl Controlled Vocabularies: int.ddi.cv CDI: int.ddi.cdi |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Flavio, Oliver, Geneviève, Johan Codebook issues from review [comments and notes are listed in Jira issue] |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan, Oliver, Flavio Guidelines for contributions to Lifecycle - how that work with new COGS system and new available options for contribution Current status of validation rules: validate — COGS 1.0 documentation Validation checks are made. The rules are there due to multiple bindings this checks to make model is valid for each implementation BACKGROUND: There are rules for adding modify/adding things in COGS. These are process rules and incorporate the rules defined in the validation system. The guidelines under discussion are not COGS specific but contributor guidelines specifically for Lifecycle. Audience would be not only COGS but also consider audience of content working groups. This could be a framework for contribution guidelines for other products, even those not using COGS. They would be useful for content working groups who are defining new content areas which may be incorporated into multiple products. Guidelines should be provided for all products TOPIC AREAS: Identification: What needs to be identified and what doesn't (easier to integrate across products and retain consistency) Patterns:
Use of common structures:
Documentation:
IMPLEMENTATION LANGUAGE SUPPORT:
WORK PLAN:
Workplan for RDF registry system (CV and XKOS): [submitted via email - Darren]
Next Week:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Dan, Oliver, Flavio, Genevieve, George Presentation on registry for Controlled Vocabularies and RDF Implementations Controlled Vocabularies
ADD to HTML page content:
Postman CV production process:
Test Group: Carsten Inclusion of Disco in registry: URL namespaces
Next steps:
Coming soon from Scientific Board
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Flavio, Oliver, Dan, Genevieve, Implementation Language Meeting Process:
FUTURE AGENDAS: COGS was discussed last week
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Oliver, Flavio, Darren, Dan Implementation Language meeting in December 2022
Preparations for Lifecycle 4.0 Beta
Codebook
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Oliver, Dan, Flavio, Genevieve AGENDA and notes: Welcome to new memberGenevieve Michaud from SciencesPo has jointed the Technical Committee as of this meeting Bitbucket access issues
Working Group Relationships
Process PapersTechnical paper review Product process Plan for completion:
FUTURE AGENDA ITEMS:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Darren, Oliver Codebook version 2.6 public review
Task list from August meetingACTION: Wendy
Scientific Board meeting
ACTION ITEM: (Darren) What we currently do: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Flavio DDI-CDI Bitbucket proposal Reviewed and have no problems with this. Resulted in a review of current Bitbucket layout and the need to clean up and clarify repository of published packages. meta project landing page Clean up bitbucket space DDI Atlassian Member Management Reviewed draft and confirmed goal of encouraging use of primary tools and management areas for capturing the work of the Alliance. We added a few points on follow-up work, particularly in working with the workshop coordinators to meet current and future needs within licensing constraints TC meeting follow-up Discussed set up of a full meeting page with links to workplan, notes, and meeting report. Will contain executive summary and list of tasks generated in meeting. |
Expand | ||
---|---|---|
| ||
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Jeremy, Darren, Flavio 1-Notified TC on the content of the ISI IPS proposal 2-Implementation Meeting (around EDDI) 3-Codebook: update on preparations 4-Review of workplan for TC August meeting Workplan for August 2022 TC Meeting |
Expand | ||
---|---|---|
| ||
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 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Flavio, Darren --ID and Reference for COGS DDILIFE-3703: Review of properties from ReferenceType for use in 4.0OPEN --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 SSHOC DDI Codebook Metadata Crosswalk |
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
|
Expand | ||
---|---|---|
| ||
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.
|
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
Technical Design Specification | Metadata Profile (CVS<>RDF<>DDI L) 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:
|