Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Jeremy, Dan S., Flavio, Larry, Ingo Ingo contact from Scientific Board
In-person meeting update
Virtual Work Event on COGS in spring
ACTION: Clear statement of what needs to be done and when DOI follow-up ACTION:
Mailman follow-up ACTION:
Quick discussion of upcoming Scientific Community meeting
Extra Action Item:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Jeremy, Dan S., Flavio, Darren, Oliver, Larry, Johan
Collectica registry enhancement
DOIs for high-level documentation
ACTION:
Repository organization for standards and product generation tooling
Timeline for DDI-CDI - estimated to be provided to TC Jan 19 Face-to-Face meeting planning
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Oliver, Dan S., Larry, Flavio, Johan, Jeremy Mappings:
TASK:
CV versioning of URI in CV manager
Clarifying points:
ADMINISTRATIVE: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Johan, Larry, Oliver, Dan S., Darren, Jon, Barry, Flavio Resolution work update:
HTTP based work is planned to be completed by EDDI Mailman lists
CODEBOOK work
NO Meeting on 25th November Topic for next week:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Oliver, Darren, Flavio, Johan, George (first topic only), Barry AGENDA:
Codebook-
DECISION: Review of content that is product independent - do this first and then put in a future version of Codebook; it would be good to look at this from the perspective of Lifecycle which is not just descriptive of past actions https://docs.google.com/document/d/1wIBolHEKTi5_JujKBkdr2s92PVpQKp_z8tyPbTqQV1E/edit?usp=sharing Review of use in Codebook as a separate process - beta version 2.6 and then official release ACTION: create JIRA issue for separate review of weighting content to track who is being asked to look at this (TC-225) CDI Update:
RDF Resolution:
Added content areas from MFP work:
XKOS Controlled Vocabularies (note that Controlled vocabularies has its own subagency which is actually "int.ddi.cv" Note that the current URI's are in error and do not/will not resolve |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Flavio, Jon, Dan S., Jeremy, Johan, Larry CDI update:
Broader coordination of implementation formats across the DDI suite: RDF and JSON representations:
UML modeling:
Discussion:
Management of requirements and integrated framework: https://docs.google.com/document/d/1TEy2zdxfARDgkOABb6kzuAmHK2oBJ0f5CmxL9F9pEbQ/edit?usp=sharing Issue presented:
Discussion:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Flavio, Johan, George, Jon, Darren Question regarding handling default values by validators
DDICODE-52 and related weighting and sampling issues
ACTION: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jeremy, Dan S., Barry, Jon Technical Work Updates:
Codebook:
Resolution Document
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Oliver, Darren, Larry, Flavio LOD document:
ACTIONS:
Agency Registry Review Criteria:
ACTIONS:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Oliver, Dan S., Larry, George
ACTTION:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Barry, Oliver, Larry, George, Jon Discussion of document specifying work needed to implement a DDI resolution system for CVs and RDF vocabularies https://docs.google.com/document/d/1rPcg44jV2xmqGTxTMKZsFgFgUhxtGeSpUt9DiE7pX7k/edit?usp=sharing
CV maintenance:
RDF vocabularies:
General questions/comments: If the docker container get moved to a different host? This is just the infrastructure. Within the restart we need to ensure that a fixed address of that infrastructure would be kept. We would need to bring this into the namespace of the DDI Alliance A triple store with sparkle end point and puddy will provide a wide range of formats. ACTION: Darren needs to go over it, add on cost items, if no substancial changes we can then finalize and contact Jared |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Oliver, Dan S., Flavio, Darren Resolution work: Upcoming:
Work tasks starting in October/November:
Things to think about for 3.4 work:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Oliver, Larry, Barry, Dan S., Darren, Flavio Resolution System:
EDDI update: CDI vote: Thinking ahead: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Larry, Flavio, Barry CDI:
Are there additional features of UML being used?
Webinar for DDI voting members should focus on:
Approach of Codebook alignment with Lifecycle: Codebook is descriptive in nature while Lifecycle takes that descriptive content and adds machine-actionable content to better support searching, management, access, and metadata driven processing. Therefore Codebooks descriptive content should move cleanly into Lifecycle and any actionable content (controlled vocabularies, specific content, etc.) should also be easily transferable.
FUTURE MEETINGS: Resolution documents will be scheduled for August 19 when Oliver is available |
Expand | ||
---|---|---|
| ||
No meeting |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Jeremy, Oliver, Darren, Larry, Barry DDI Alliance agency level resolution: CVs
DECISION
ACTTION: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Larry, Oliver, Darren, Flavio AGENDA:
DNS Resolution: https://docs.google.com/document/d/143tERbtM8Eze-z28jCZMxTm8bHaGfKh6/edit Comments have been added to the page including additional areas that need to be covered and clarifications. We will work on this over the next month. Target audience is the Scientific Board but content should be usable for informing ddi agencies and end users. Preparation for meeting with Jared on 22nd |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Larry, Oliver, Barry, Flavio Follow up on last week's action item
Discussion of next week's Scientific Board agenda XKOS and Paradata
DDI URN resolution - Status update - goals and policies to be formed
UPCOMING MEETING: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Oliver, Darren, Larry, Dan S., Flavio, Jeremy, Michael, Sanda, Taina, Barry AGENDA: Clarification of steps needed to finalize the publication of DDI Controlled Vocabularies on the DDI web site at the level of access currently available. (NOTE: this does not include content resolution of items in vocabularies which is being addressed separately) STEP 1: getting SKOS output correct from CESSDA Step 1 Notes:There are identified issues with the CESSDA SKOS content which have been noted by Achim and passed to the TC. Franck Cotton reviewed the SKOS example and validation report, identifying specific problems that required fixing, best practices that should be followed, and other related comments. This information has been passed to Darren and Oliver. While these issues involve the CESSDA system, TC will address the issues in the transformation of the CESSDA output into the DDI published content. Darren will provide this feedback to CESSDA. TC will alter its transformation scripts over time as changes are made in the CESSDA system. Step 2 Notes:Tool: is a command line tool that pulls content (SKOS multilingual file from CESSDA); transform to SKOS, CodeList, HTML; prepares package of content to be uploaded to the Alliance site Options for timing:
DECISION: Tool will be run on a monthly basis. This has been agreed upon by Sanda and Taina. The CV group should review during the year to determine if the timing is correct. Periodicity can be adjusted in the future based on this review. SKOS content:
ACTION: Oliver needs to determine if we have enough information to make these additions, do we need to retrieve separately ACTION: Wendy obtain and verify versioning of CVs in DDI as stated by group and clarify what will be expressed in DDI Step 3 Notes:ACTION: Need to agree on the actual URI pattern we want to use. They are currently wrong and this needs to get this corrected in the CESSDA tool Considerations --
QUESTION: could DDI site run automatically. What is currently being implemented in JAVA. TC needs to find a location to run that pull. DESCISION: Run the JAVA within bitbucket. When we are displaying multilingual. Use a bitbucket repository for that retaining all copies. Michael could just run a clone of the repository. ACTION: Michael and Oliver need to coordinate so that what comes out of transformation is what Michael needs for updating the site ACTION: Wendy and Barry need to discuss options for informing public of new CV publications and updates. CV group should then work with Barry and TC to ensure that updates are appropriately publicized. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Darren, Larry, Oliver, Dan S., Barry AGENDA: FROM Jared - How about I attend a TC meeting in July to discuss next steps (I should be available the weeks of 12 and 19 July)? We'll want to identify any DDI member organizations that could provide the services you are seeking. Additionally, we should consider preparing for a competitive bid with outside vendors.
ACTION ITEM: Work with Michael to ensure that content is transformed into page content ACTION ITEMS:
Work on additions to the product pages for Codebook (past development, change logs for published versions, etc.) Issue with URL resolution resolved Best Practice issues to addressed remove page of topics
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Larry, Barry, Dan S., Oliver, Flavio Some notes regarding specific activities: For the CVs is a very simple approach. Implementation is about a day if ICPSR is supporting. High Priority get this out in the next few months HTTP agency resolution service: Should occur Aug/Sept; grid updated Product mapping ACTION https://ddialliance.org/Version2-0.xsd Have emailed Michael for a listing of all URLs for Codebook schema and dtd instances. FOLLOW-UP ON VALIDATING URLS: When I later tried the xml file in oxygen it did validate. 1) having a working URL in the schema location is helpful for files distributed by an archive. That makes it completely clear which schema is correct. In the example below, the namespace URI (http://www.icpsr.umich.edu/DDI) is not specific to DDI Codebook, being the DDI home page. The version 1.2.2 may no longer be adequate now that version number is no longer tied to product line (Codebook, Lifecycle, etc.). A better practice might be to use https://ddialliance.org/Specification/DDI-Codebook/ for Codebook. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Darren, Dan S., Oliver, Larry, Barry, Flavio CDI review package - update
Canonical URLs for DDI XSD files - Darren
Example that bounces Note that later check using http://www.icpsr.umich.edu/DDI/Version1-2-2.xsd resolved to https://www.icpsr.umich.edu/DDI/Version1-2-2.xsd on DDI site Tried this header using XMLSpy and it validated. ACTION: Is there a need for an Apache configuration change? Can Michael send the host definition for the DDI Alliance site. Set up meeting with Michael, Oliver, Wendy, Darren, plus whoever wants. ACTION REQUEST: Good to have a record of decisions and approach to provide guidance to community - Darren will supply when work is done
Codebook: what is meant by "compatible content" within the definition of what Codebook is intended to relate
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Jeremy, Flavio, Larry, Oliver, Darren, Barry 1) Budget requests finalized - cost estimate
2) Update on XKOS activity
8375 added "and Metadata Access" to documentation of "var" check issue for comment that the code for category should cover the catStat. #### |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Flavio, Jeremy, Dan S., Larry, Darren, Jon Presentation to Members meeting - base on SB presentation for next year and add past year work including: Notes on clarifications for work plan and any document to groups outside of TC |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Oliver, Dan S., Barry Response from DDI-CDI Resource Pages ACTION: (Wendy) As more work is done on resources pages I will create a page on the wiki to present and discuss approaches UML modeling in CDI NEXT WEEK: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Oliver, Darren, George, Dan, Flavio, Flavio Preliminary discussion of DDICODE-52 please read the proposed solution George getting in touch with Stas regarding SDTL work Use of Slack in DDI
Tools page update - ideas for content and maintenance
Implementation of maintenance - Note to DDI-CDI group
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S. Darren Oliver, Barry, Flavio https://docs.google.com/document/d/1DuYMk2n8GSfbxjlEjweDuw42Y29Ork2npt6Oq-jQOyQ/edit?usp=sharing
57 has nothing to do with SDTL but with the SDI work. Notify George. CDI vs MRT Jon will draft up some notes on this so we can get it to CDI as soon as possible for them to respond to so we go into pubiction with an idea of where this goes. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Darren, Larry, Jon, Michael, Oliver, Flavio, Dan G, Barry Discussion of providing a means of resolving DDI RDF vocabularies (currently CVs and XKOS) down to the vocabulary instance level. Darren and Oliver will both be available. Goals of this meeting are to clarify exactly what is needed and a process for achieving this in the near future. Controlled Vocabulary Issues: Currently, notional URIs exported as RDF (SKOS) content from CESSDA Vocabulary Manager do not resolve anywhere e.g. https://ddialliance.org/Specification/DDI-CV/AggregationMethod_1.1.html#Sum . Secondly, these are HTML URLs rather than URIs functioning as resolvable persistent identifiers. Thirdly, there is currently no RDF endpoint infrastructure at ddialliance.org to support URI resolution. DDI system currently does not provide a means of resolving to an vocabulary instance endpoint. We also have minimal clarity on what should be provided as an endpoint to an RDF vocabulary (html product https://rdf-vocabulary.ddialliance.org/xkos.html) or a .rdf expression such as Terse RDF Triple language (Turtle) RDF Endpoint: Goal is to get a snippet of RDF data, whether by direct query or as embedded RDF in HTML pages. 2 things to be solved: 2-What do we need to do to publish the DDI vocabularies We need to port everything out from CESSDA Vocabulary Service as a SKOS or SKOS-XL file. DDI uses the CESSDA CV manager as a means to edit and manage versions of DDI CVs. DDI is responsible for the publication and resolution of the DDI CVs. CESSDA CV manager needs to be fixed The standard export of SKOS has some internal issues Would ICPSR be willing to set up an RDF container The web site publishing could work in the same way to static files - SKOS to update into HTML and other formats The whole point of DDI using the CESSDA tool was for editing and version management support which in the past was a fully manual process. We need to create a native environment that supports resolution of RDF endpoints; separate RDF store able to resolve DDI Alliance URL/URI We need to talk separately about editing and publishing. Editing will continue on CESSDA tool for now as it meets our needs. Changes in the system, particularly output changes, would need to continue to meet the needs of the DDI CV group Suggestion for approaching this:
RESOLUTION: ACTIONS:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Oliver, Flavio Reviewed the entries in Codebook bitbucket related to CV and text consistency work. Dan will do a more detailed review and validate. The next areas of Codebook work are some specific issues for extended content. Went through first draft of document commenting on workplans submitted to SB. Added some points. Wendy will update and post for additional review and comments. Sending to SB next week. ACTION: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Darren Discussed the Codebook changes for CVs and added notes on conclusions Controlled Vocabulary issues - DDI - Confluence (atlassian.net) Looked at CESSDA SKOS extracts at https://vocabularies.cessda.eu/vocabulary/ModeOfCollection Information will be transferred to specific DDICODE issues as relevant |
Expand | ||
---|---|---|
| ||
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Flavio, Larry, Oliver Update from SB meeting 2021/22 activities - provide some more detail in terms of things that need to get done; set some priorities Additional information on web page work including content model for DDI overall
NEXT MEETING |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Jeremy, Oliver Getting Started Page discussion:
How might this page be used?
Conclusions: This page is intended for the a person with zero knowledge (new potential users), so what do they need and how might this be presented?
Information needed to describe task work:
This cannot just be refreshed and needs to be reimagined in the context of the current site. Need to look at what are we trying to do here - get a clearer idea of what this is trying to accomplish - how does it tie to the overview with the application perspective ACTION: write up an approach to reorganizing |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Larry, Oliver, Flavio Codebook content review: language code attribute provide source code - will this change Follow-up note (email to members) simpleTextType mixed="true" abstractTextType mixed="true" baseElementType abstract="true" Workplan to SB: areas of emphasis Integration across models emphasizing CV work update: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Larry, Flavio Review of document outlining Codebook development rules Clarification for document clarifying work rules for Codebook: add "When the instance is changed to reference new schema" Action: update, post on wiki and inform Codebook group for additional comments Discussion of next fiscal year and 2-3 year work plan for Scientific Board due 2 March DDI-CDI review, vote for publication, and publication if approved. This has been shifted from the last quarter of the current fiscal year due to shifts in the DDI-CDI workplan following feedback from presentations/review. Clarifying statement regarding use of COGS and the implications i.e. supporting a more approach to modeling supporting various expressions Comparison and mapping work Include sentence or two about HTTP based resolution process in our workplan for next year (see agenda from meeting in Minneapolis for additional points) Roadmap document: Long view 2-3 years out: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Jon, Jeremey, Oliver, Flavio COGS:
Discussion: Decision: How to handle minOccurs="1"
Physical Structure sections need full review: Check Best Practices to see if these can be clearer Options for retaining Provenance between 3.3 content and COGS (capturing specific changes) Moving Forward Project outcomes: NEXT WEEK |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Larry, Dan S., Flavio, Barry, Darren Codebook Best Practices - ACTION: Darren will work on draft, Wendy will provide background material to date Identification Text
Controlled Vocabularies
Review of Codebook changes
Updates: --Statistical Classification - almost done Examples --Darren will look at URI resolution on CVs - Darren will draft this up for some future meeting Resolving API endpoints for agencies - well-known endpoint |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Oliver, Dan S. Codebook Best Practices Technical aspects to support interoperability on tools and versions. Specific points noted for coverage:
We can definitely say things are deprecated (xml-lang example) xs:appInfo maybe use this for deprecation for the assistance of implementers and processing tools. We could use our own notation for it. Do we need to individually nudge some people: IHSN (World Bank)? Let's wait to see what we get as those we noted were all on existing lists ACTION ITEM: Background information: Best Practices Lifecycle example A technical Best Practices in the area of identification, language, and places where there are multiple ways to handle content, to provide a best practice to ensure interoperability on tools and versions. Also of concern is consistency within the community. Feedback needed: ACTION ITEMS: Notice on TC agenda sent to group: TC, yesterday the Codebook group discussed the value of a Best Practices document and what it should contain. We also discussed the process for obtaining feedback on what should go into it and where there are specific problems that need to be addressed. Dan S. was on the call and provided a clear description of the overall focus of such a document. The approach that was proposed was for TC to draft a document for the purpose of getting feedback from Codebook community. This should include a clear definition of focus and what type of information is needed from the community in terms of specific fields and problem points that affect interoperability and consistency within the community. While the focus of this Best Practices is technical rather than application based, we need to ensure that any feedback that is outside of the coverage of this document will not be lost but will inform the content of new high level documentation that is also being planned for Codebook. At our meeting tomorrow I would like to draft out the coverage of a Best Practices document as we see it now and a draft of request for feedback/content gathering that can be sent to the community. This request should go out to the Codebook group as well as to the DDI-Users list and the IASSIST list (the original groups from whom the Codebook group were solicited). |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., George, Jon, Larry, Oliver AGENDA Background info: SDTL experience: Purpose of Markup Examples: 2) Strengths of different work products 3) Use of examples Related issues/questions: Best Practices needs to be propagated for products especially Codebook - help to steer with migration problems ACTION: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Larry, George, Oliver, Barry, Dan S., Jon Check-up on current work plans identifying status, action during January, and specific actions needed.
|
Expand | ||
---|---|---|
| ||
ATTENDESS: Wendy, George, Larry, Barry, Dan S. Pages under Learn: Tools page:
DDI Profile page
Relationship to Other Standards
Implantation Guide page for Products
Additional comment: Larry raised use of different browsers which display dropdown content differently - he will file with the website issue tracker |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Oliver, Dan S., Larry, Barry, George, Flavio
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Jeremy, George, Barry Publication of SDTL and new product pages
COGS - how will we manage versioning in COGS? Is it a matter of publication
AGENDA: Year end announcement press release - next 2 meetings
PR news flier:
TO DO: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Oliver, George, Jeremy, Dan S., Larry, Johan SDTL Publication: 1. What are the next steps to publishing the SDTL standard? The package that went out in the same form 2. Since we published the standard for review, we have made a number of small changes to SDTL. There are a few more small changes that are pending discussion at the SDTL WG tomorrow. All of the changes are listed on this page: https://ddi-alliance.atlassian.net/wiki/spaces/DDI4/pages/1207926786/Pending+SDTL+Changes Mostly minor changes for example split a single property into 2 Prep for publication: Announcement content: provide to Barry NSF grant information add to page ARPA filing Once verified Dan will check and once finalized will be filed. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jeremy, Dan S., Jon, Larry, Oliver, George Webinar at the beginning of a voting period.
Resolution issues:
Announcement: Over 200 signed up for EDDI |
Expand | ||
---|---|---|
| ||
ATTENDEES - Wendy, Jon, Larry, Dan, Jeremy, Oliver, George, Flavio DDI Codebook 2.6 citation, CV, access
DDI Suite - coverage work
Mapping within DDI with others
COGS input / output
DDI Lifecycle expanded documentation
DDI Alliance pages
URN resolution issues
ACTION:
ACTION: Priorities:
ACTION ALL:
Interesting sidebar: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, George, Jeremy, Dan S., Larry, Oliver, Barry Preparation for SDTL Vote: Include links to X'd items Important Links:
ACTION:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Oliver, Flavio sounds like they want an http resolution system Dan is correct in terms of the needs of the CV group. A place to provide a URN for a CV Add this feature to the registry site - URL pattern based redirection Is there a set of information that we can provide Answer to CV group: There needs to be a couple of different entries in the pattern (SKOS, DDI-Codelist XML, web page, etc.) Daylights Saving change: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Oliver, George, Larry, Flavio, Johan, Dan S. Reviewed pages in product section
ACTION ITEMS FOR WENDY:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Olof, Oliver, Johan, Dan S., Flavio, George Alter, Jeremy RDF Pages SDTL PRODUCT Pages The only place with a list of all the products on the drop down DDI Registry Page - should this be DDI Agency ID Registry Add text to indicate you can look up agencies as well Product development page Looking forward to other pages Overall Coverage Model |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Jeremy, Larry, Johan, Oliver Target Date: Scheduling vote mid-to-late October Support material: In terms of documentation an SDTL user guide has been created and set up so that the User Guide is the entry into COGS. 2 articles have been written (the C2metadata project and an instruction on SDTL) Working on publication of first, SDTL paper has been submitted to IASSIST Quarterly, a third paper on Use Cases is being written. Including:
Webinar:
Coverage:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Jeremy, Larry Updates on the following topics: DDI pages - content and layout, timeline
Codebook - current work status, TC review of work/changes
CDI - update on webinars, publication work
COGS work - where are we? are there things we are waiting on?
SDTL
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S. Clean-up:
Issues raised in Codebook:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Larry, Oliver, Jeremy, Dan S., Flavio, Jared, Barry Review of DDI Alliance pages assigned to TC About:
Product tab: Menu Items:
Content:
Layout:
ACTION ITEMS:
|
Expand | ||
---|---|---|
| ||
MEETING CANCELLED |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Larry, Flavio TOPIC: DDI Alliance web pages under Specification drop-down GENERAL THOUGHTS:
THINGS TO KEEP IN MIND:
PAGES we can look at that are well organized:
ACTION ITEMS:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Larry, Jeremy Work plan for COGS work:
Additional bindings and a different XML binding is a separate topic:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Jeremy, Dan S., Larry, Flavio, Achim (guest) URN document
ACTION Corrections will be made and then document redistributed for comment period and then discussion will begin with ABNF
Location of all cardinalities Known problem modeling areas: Discussion points: Reference - if we want additional content we need to hand write those - check on what comes out as reference (see settings folder) Choice - one way to solve choice issue if they were derived from a common base class we can have a single choice pointing to the base - where should we add base classes Corrections - currently just used for documentation so we can publish any corrections we can rerun and get it up on the site As we make fixes we can reiterate all the sets ACTION Have concrete examples of each - prepare full spreadsheet of issues and post. Also post initial comparison spreadsheet |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Jeremy, Larry, Oliver, Achim (guest) CV toolprogress waiting on completion of API update to finalize URN work:see document FinalQuestions.txt and emailDiscussions-week20200702.txt as background Decisions appear in BOLD 1: Included characters - ; general URI syntax rules (RFC3986) alphanum = ALPHA / DIGIT ; obsolete, usage is deprecated COGS ReviewWendy went over XML to CSV validations she's doing covering:
Some issues have been found which will be explored and described more fully and presented for next meeting. Flavio also has found some issues in the UML (XMI) renditions. Next Week:COGS review with specific issues identified for discussion prior to meeting. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Larry, Flavio, Jeremy, Achim (guest) URN namespace for DDI (this links to document also found on TC-4)
Implications -
AGREEMENT on the following: SUGGESTED solution: ACTION NEEDED: Circulate this suggested solution for comments and agreement among TC prior to next weeks meeting (preferably by Tuesday so that Achim can incorporate this solution into the document) Internationalization issue raised by Achim: Discussion:
DECISION: Limit to ASCII Issue #4 Version is required for identification
ACTION: Resolve whether version should be optional in namespace document ACTION:
Extensions mechanism:
UML Documentation -
Procedure: Next Weeks Agenda Future Agenda Item: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Jeremy, Larry, Oliver, George SDTL
Codebook - set up list Description of DDI Suite of products (general verbiage)
TC responsibility for DDI Alliance web pages
Update on URN namespace work
NEXT WEEKS AGENDA:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Larry, Oliver, Jeremy, Barry, George, Dan S. Trademark Barry Reviewed contents of SDTL Review Page SDTL role in the DDI Suite Benefits section is clear statement of role of DDI Went through checklist provided earlier to George IP regarding CC BY 4 Added note: FROM CHAT: Link to gitlab location - link for tools CLICK to file a comment Please provide your name and email in the body of your comment |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S, Larry Updates: CDI webinar (Larry) - about 18 some technical problems but they got through; another next week Will relate these points to Marketing and Training Groups Dan S. will join the DDI-C group monitoring solutions SDTL meeting soon COGS: Flavio, Wendy, and Jon are testing the UML, XML, CSV for transformation errors Will pass on to Jon and Flavio |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Larry, Oliver, Flavio, Jon Just touching base with each other Status/Update CV waiting on some technical work from CESSDA prior to DDI publication - Oliver will confirm what the plans to address identified issues Review Codebook group approach One of the objectives is to get Codebook into a not manually created situation COGS output evaluation of XMI and documentation: Need to track down where the problem occurs - Flavio will provide Jon with examples Flavio will also add TC issues regarding the use of and requirements for the XMI produced by COGS |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Jeremy, Larry, Dan G., Dan S., Oliver, George Alter (guest) AGENDA: SDTL Review Preparation Discussion regarding preparation of SDTL for publication by DDI Alliance: Web presence- where it will be
What is going to be the package of information:
Status : mature version of SDTL covering data transformation commands found in statistical packages (main library) 3 parts: Documentation of these three parts Link to Tools such as
Some background information:
Are there any implications of where the COGS instance resides
DDI Alliance GIT installation it would be good to mirror this early. Use GitLab as development space and then mirror accepted content in Github. Then when C2M project closes down then it would just be in Github (Jeremy and George will work with this) What questions will be proposed on the review page. This will be discussed during the next month to reflect the needs of the SDTL group and any TC concerns. |
Expand | ||
---|---|---|
| ||
NO Meeting due to virtual meetings of Scientific Board and Members Meeting of DDI |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S, Flavio, Jeremy, Larry, Oliver Presentation reviewed and finalized SDTL - plan to put out for Public Review July 1 review
Technical feedback on bindings -
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jeremy, Oliver, Larry, Dan S. Membership drive:
Members meeting:
SB meeting:
Announcement for tech info: comments on the generation of a binding in COGS repository (https://github.com/ddialliance/ddimodel/issues) Comment on model work presented last call: These were a the basic starter content providing a basic framework - getting started on different common sets of metadata for specific purposes |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Flavio, Dan S. Codebook: Announcement Version 6 of Colectica will go out next week supporting 3.3 Roadmap work: DDI Suite of Products - overall model Metadata Roadmap - StatsCan (GSIM) Data Platform Metadata repositories Mapping between DDI Lifecycle and GSIM High level view of DDI Suite Review old work on GSIM TO DO: Agenda for next week: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Flavio, Oliver, Larry, Jeremy AGENDA: Wendy sent out email to all members asking interest in continuing to serve and area of focus. Due back by end of month when search for new members will take place. This allows us to see areas where we are weak in terms of focus areas. Continue to seek members who are willing to be active in specific focus areas and retain interest and oversight with the broader work. Attendance at meetings is driven by agendas Specific tasks for the next 3-4 months identified 3.3 high level documentation - continuing work task (Jon, Wendy) Wendy will organize identified tasks and use as basis of future agendas Annual Report: Highlight - major version FINALLY got out Presentation part: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Jeremy, Dan S., Larry, Oliver, Flavio Update on publication and review status
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S. Work Products Looked at Work Products page: Should be published work products Talking about what is coming is not productive for the products page as it causes people to wait and has caused people to wait
Under drop down box Specifications: DDI Codebook Under About: Describe the DDI Suite description New entry for Developing Products Lifecycle 3.3 publication
Wendy will pull together the announcement information and send to Jared |
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Jeremy, Larry, Oliver, Flavio DDI-CDI:
DDI-L 3.3 vote
DDI-C
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Jeremy, Larry, Oliver Agenda:
Codebook review approach - setting up content for an announcement
Other topics Membership - contact current members about continued interest and solicit new members |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Jeremy, Dan S., Oliver, Flavio DDI Lifecycle 3.3 Vote:
DDI-CDI
The DDI Alliance (http://www.ddialliance.org/) is pleased to announce the public release of XKOS version 1.2, a free and open specification that facilitates sharing and management of statistical classifications. XKOS is a simple and elegant model to represent complex classifications via their structural and textual properties, as well as the relations between classifications. By leveraging the widely-used Simple Knowledge Organization System (SKOS), XKOS extensions allow linkages to a wealth of existing thesauri and taxonomies to better support statistical classifications and concept management systems. XKOS also refines SKOS semantic properties to allow the use of more specific relations between statistical concepts, classifications, or any other case where SKOS is employed. XKOS is currently used at a number of national statistical agencies and has been available as a draft since 2013. Since undergoing a final review in 2017, all issues have been addressed and corrected in preparation for the publication of version 1.2. Links to the specification and instructions for comment are found at: http://www.ddialliance.org/Specification/RDF/XKOS NOTE: The above was the public release notice. The following is the text of the public review: The DDI Alliance is pleased to announce the Public Review of XKOS, an RDF Vocabulary which extends the Simple Knowledge Organization System (SKOS) for the needs of statistical classifications. It does so in two main directions. First, it defines a number of terms that enable the representation of statistical classifications with their structure and textual properties, as well as the relations between classifications. Second, it refines SKOS semantic properties to allow the use of more specific relations between concepts. Those specific relations can be used for the representation of classifications or for any other case where SKOS is employed. XKOS adds the extensions that are desirable to meet the requirements of the statistical community. Links to the specification and instructions for comment are found at http://www.ddialliance.org/Specification/RDF/XKOS. We are eager to obtain feedback from the DDI and RDF communities on this vocabulary. The comment period is open until January 31, 2017, and we hope to hear from you.
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Flavio, Larry, Oliver, Dan S., Jeremy Lifecycle 3.3 vote Have something by next Thursday - fighting with Sphinx CDI Review TC review of CDI should address: Things to finish before face-to-face meeting Review of binding output Jon can start looking at what Lifecycle 3.4 is or could be in early April NEXT WEEK AGENDA: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Flavio, Oliver AGENDA:
Summarized status of mapping Face-to-Face meeting proposal
Jon not available in September CDI -
Contact Arofan to see if there are background documents that are ready and available that would be useful to list similar to earlier reviews (done) Codebook Have made progress on specific issues and am preparing a statement for soliciting input from Codebook users. Get moving in the next few weeks. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Jeremy, Larry Codebook:
Lifecycle:
Face-to-Face meeting: Pick up where we left on the face-to-face meeting --In terms of timeline as we were thinking last year...Septemberish? Financing: similar to last year - justify the higher amount by need to get the right people in the meeting Timing: September planning gives us a deadline for background information aquisition (post-Labor Day) - need to check about space availability Location: Minneapolis Topic:
Send out a general interest request for participation with a clear agenda, background information, etc. (specific names mentioned included) Need to get discussion of the future structure of codebook going sooner rather than later. Identify who is using it and what they use in terms of specific objects and sub-features (mixed content with specific fields like concept) are being used. Contacting users regarding Codebook: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Jeremy, Larry, Oliver Lifecycle Documentation - checklist for vote
Vote announcement:
Modeling work: -
Codebook:
NEXT WEEK AGENDA: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Jeremy, Dan S., Oliver, Larry TC-213 Workplan - General
Distribution of member effort at least in short term (through June)
CDI Codebook Roadmap work - note that this is not a TC activity alone but involves Marketing and the broader Scientific Board community 3.4 3.2 high documentation |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Jeremy, Larry, Oliver, Flavio APOLOGIES: Jon AGENDA: Work plan for 2020 DDI Core review - provideded update
DDI Codebook
DDI 3.4 would be just a serialization of the COGS system DDI 3.2 high level documentation |
Expand | ||
---|---|---|
| ||
Present: Jeremy, Flavio, Dan, Oliver, Larry, Jon |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Larry, Oliver, Jeremy TO DO List: 3.2 documentation has also been updated and is available - announce the model documentation when we release updated 3.2 documentation Do we want a note that additional examples completed after publication may be found in the High Level docs (link to) Quick review of Schema docs looks good (Larry, Jeremy) Should the set of examples be outside the package? would need change the reference to the schemas in each. REMOVE the schema reference completely because most systems use locally assigned. Usage is to see how something is done. Move up FieldLevelDocumentation Folder on level with XMLSchema folder (only thing now left in Documentation folder) 3.2 review email Add new content from last 3.3 public review page Decided on review period Jan 24-Feb 21 (4wks) Package will contain License, Change Log, Readme, XML Schema folder, Field Level Documentation Folder Note that these links should be moved to the DDI website with publication ACTIONS: |
Expand | ||
---|---|---|
| ||
ATTENDING: Wendy, Jon, Larry, Oliver, Dan S. Current status of documents Main issues: Specific topic listed in above Jon is currently moving things around and so all should look at and provide comments to Jon regarding improvements Next Thursday should be the target Reviewed DDILIFE-3662 added Lifecycle to title (merged) and closed issue |
Agenda Topic Index Key
2018-2019 Minutes Page
2016-2017 Minutes Page
Pre-2016 Minutes Page
AGENDA TOPIC | DATE |
---|---|
Resolution System - work done by TC | 20211111 20210923 20210916 20210909 20210902 20210819 20210722 |
Agenda for TC face-to-face | 20211209 20200227 20200220 |
Mapping of products | 20211111 |
Controlled Vocabulary Publication | 20210701 |
DDI Site Pages | 20200304 20201217 20201210 20201203 20201112 20200924 20200917 20200827 20200813 |
Lifecycle 3.3 | 20200409 20200312 20200305 20200220 20200213 20200123 20200116 20200109 |
Codebook update | 20211104 20211028 20211021 20210408 20210401 20210225 20210128 20200312 20200220 20200213 20200206 |
Roadmap - COGS | 20200723 20200716 20200625 20200206 |
CDI review | 20200409 20200326 |
SDTL Review | 20201119 20201029 20200903 20200618 20200528 |
2020 Workplan | 20200305 20200206 20200130 |
URN filing | 20201112 20200716 20200709 20200702 |
...