Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Expand | ||
---|---|---|
| ||
ATTENDING: Wendy, Oliver, Jon, Guillaume, Jeremy, Dan S. DDILIFE-3524 need examples see issue Documentation: Jon needs and hour with Jeremy next week to sort out final issues. Wendy needs to do a content dump for Jon. Short Sprint prior to NADDI. This is at the pass-off point between documentation and TC review. This is being looked at as a chance to do the following: Wrap up any documentation issues Oliver - remotely Announcement of sprints and ask people to participate Should this be a TC meeting? in which case we have 3.3 work that could be done even if it is out for review. Implementation issues, software development issues. We used to have annual face-to-face meeting and these have always been very productive we need to reinstitute support for this. If we want a TC meeting do we do this as part of a review of 4 or do we want more 3.3 line. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Jeremy, Oliver, Guillaume, Larry DDILIFE-3524 The conditional text type inserts a block of text IfStatement condition and text if true - should probably go through Else to provide a default insert at minimum Resolve to add an IfThenElse to choice in ConditionalText. WT will draft IfElse for dynamic text. How to indicate the position. Write documentation and examples of usage. Reviewed DDI_L_3 entries and pulled into Master |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Oliver, Johan, Jeremy, Larry DDILIFE 3581 - OK to remove DDILIFE 3582 all approved with following not#4. Make sure it stays in the same order as previous when it was in in AbstraceVersionable. If not just add to each (non Abstract) to retain order #7-9 move to reusable DDILIFE 3524 - Check with Guilaume and others about using computation and logical expression, separating "true" and "false" responses into separate conditinal texts. How to specify which text. Definately good to be able to express specific text insert in a consistent way. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jeremy, Larry DDILIFE-2935 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Oliver, Jon, Larry, Johan, Kelly Reviewed commits and pushed to master |
title | 20171109 |
---|
ATTENDEES: Wendy, Oliver, Dan S., Jeremy, Jon, Jay
- DDI 3.3 - get structural content done by EDDI complete documentation by EOY This will allow implementers to download schema if they want an early look
- Recommendation to Kelly as Project Manager to include an open call for participation in future sprints
- Request to settle on a 10:00 US Central / 17:00 CET start time for TC all year
- Development of an activity list for moving https://docs.google.com/a/umn.edu/spreadsheets/d/1ODRYBd6luuctdPKxnxg2azOJ4o59D9wwxUQbJ2vI1ak/edit?usp=drive_web
- Determined member availability for meetings during remainder of year
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Larry, Dan S., Jay Production Framework - decision is in TC
Discussion points: cannoical XMI (as opposed to EA version), XMI in the production line (source vs. another product) Gather up all the issues regarding EA XMI problems Prototype timeline:
Modeling Team does the Functional Views to review content Implications for Lifecycle and Documentation
Finishing up 3.3 content We are almost there - hoping we can finish by EDDI check on 2 .6 development status in terms of resolution and entry |
title | 20171005 |
---|
ATTENDEES: Wendy, Jon, Dan S., Dan G., Larry, Jeremy
Approved this list for Dagstuhl 2017:
Define model-based approach -clarify documentation on:
what kind of a model this is and what that implies (logical model falling between a conceptual model such as GSIM and an implementation model such as the XML or RDF binding)
how is this different and what does it support
goals of a model-based approach
how does it fit with design rules in DDI overall
what tooling should provide to support this
DDI4 model itself -
Implementation review
can it be implemented?
how to resolve any implementation issues (process, modeling rules, specific changes)
Clarification on Views -
what are we trying to solve
what are options for solving it
what are the criteria for evaluating whether the solution solves the problem
What exactly is a prototype - out for review but phrased in a way that lowers expectations - this is not clear in the communications because these sound like DDI 4 is coming out in June
Clarify just what is going out and communicate clearly
What the product description should be for the outputs are in terms of set of products
What is the product description of what prototype includes
In addition to 3.2 coverage
Use cases supported
Clear work plan for DDI products over for the coming year
Priorities
What needs to get done to meet those
DDILIFE 3.3
Reviewed final issues - on track for later October
Generic Grid inclusion dependent upon ability to review in implement first
Codebook View
Ready for MT/TC preparation for review - can go forward with the set of elements identified
Some issues for LogicalDataDescription but should not hold up review
Where to Publish the web docs for 3.2 and 3.3
Where should the docs go after they are generated especially for developers so they can see what their change result in
For in development or in individual branchs during development and testing
Could we ask the alliance to pay for another cloud instance?
Github pages? - not a dynamic site
Use ReadTheDocs
Not sure that the clickable website should be the "specification" if there are typographical errors you want to be able to change without versioning. So the web site can be the dynamic version.
As the Technical Committee it would be great to be able to see the current state of all parts of the output - submission forks
Official is static, but development would show corrections, changes, etc. Could set up as repository in Github that can serve web pages.
Suggest we have a brief discussion at Dagstuhl about a longer term solution
Short term solution would be the Github and ReadTheDocs pages
Dan S. will set up DDI-COGS repository containing CSV etc. and another repository to support generated outputs to support web pages
May need some programming to make the website easy to use and explore
title | 20170928 |
---|
ATTENDEES: Wendy, Jon, Dan S., Jeremy, Jay, Larry, Guillaume
Dagstuhl goals discussion
What exactly is a prototype - out for review but phrased in a way that lowers expectations - this is not clear in the communications because these sound like DDI 4 is coming out in JuneClarify just what is going out and communicate clearly
What the product description should be for the outputs are in terms of set of products
What is the product description of what prototype includes
In addition to 3.2 coverage
Use cases supported
Clear work plan for DDI products over for the coming year
Priorities
What needs to get done to meet those
DDILIFE 3.3
What needs to get done to get this out the door
3534 is almost entered
3519 Copenhagen mapping in process of being in
COGS 3.2 to COGS model
3.3 documentation - go through for any added references that are not strongly typed
Is there something that Jon could do now to will get him going. The 3.2 documentation could only take a few days and used for a base of 3.3
Move release date to November unless ready sooner. But before EDDI
Codebook View release for review:
Expect that there would be some additional documentation with examples where it would be helpful. Some of the examples and classes are still being worked out.
By end of next week (Oct 7) to TC.
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Jeremy, Larry Follow-up from last week 3573 assigned to future DDILIFE-3530 Assign everyone to look at above points and comment on JIRA 3530 Reviewed draft document of TC review of DDI4 materials for review. Specific comments were made on document and will be incorporated with a new draft. Some specific future work: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Jon, Dan, Larry DDILIFE-3573 The best place to locate documentation would be in computation item, it is possible a 'light weight' structure could do the job here, but would likely need to be fairly generic (as is computation item) to support a wide range of possible use cases. DDILIFE-3530 Some tasks for the next meeting on 21 September a. Review allowable content in the cells to make sure they make sense |
title | 20170907 |
---|
ATTENDEES: Wendy, Jon, Johan
Initial focus on documentation. workplan covering content and work assignments entered on DDILIFE-139
Johan has been doing training on DDI 2.5 and noted some display errors in html documentation. He is entering in DDICODE as found and Wendy is making corrections in Bitbucket DDITC development area. These will need to be reviewed .
Proceeding for Codebook View review release:
Package sections used:
Review it for modeling rules
Views:
Make sure the parts hold together - no orphan elements
To get out by 6 October TC needs to review:
Check for modeling rule compliance by 15th and give a list of needed corrections to CB View group and Data Description group.
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan G., Jeremy, Larry, Jon DDI 3.3- what needs to be done Generic grid issue, proposal posted and discussed. Noted that Wendy has done work on entering 2.5 issues |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Jeremy, Johan, Larry Remaining 3.3 is waiting on Jon Reviewed 11 outstanding DDICodebook issues resolved, determined action, or put on hold |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jeremy, Dan S Reviewed remaining issues for 3.3 discussing just what is needed for generic grids. Wendy will complete another proposal by next meeting Dan verified status of Copenhagen mapping and clarified some issues regarding schemes and groups Update on COGS: Will be making a release next week. The following links provide information on recent workflow and progress https://github.com/Colectica/cogs/graphs/punch-card Will be able to show features at Dagstuhl We seem on track for 3.3 review and Jon and Wendy will turn attention to high level documentation Update of 2.5 seems workable in the near future and we discussed using COGS to produce documentation as well as showing a uniform look and feel for DDI documentation 3.2 documentation will be created with COGS. Wendy will investigate the reviewing options for this update |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jeremy, Jon, Dan S, Guillaume, Larry ACTION: Dan S will create an issue and assign it to Wendy for investigation |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Jeremy, Jay, Jon reviewed items entered for 3.3 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Jeremy, Jay, Larry, Dan G. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Jeremy, Johan, Jay, Guillaume |
title | 20170518 |
---|
ATTENDEES: Wendy, Jon, Dan S., Jeremy, Larry
Presentation at Member Meetings
Questions that might be raised:
- Why are you even working on 3?
- supporting existing users
- creating a transition path
support new users of existing products
Development Review not a release - Codebook Functional View
Large number of elements so its how they are presented especially in the documentation
- Flattening documentation, grouping by use
Improvements coming to Drupal - discussion of how certain things were done in
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Larry, Jay, Dan G. Reviewed draft content for TC report and presentation sessions at Members and Scientific Board meetings Reviewed and accepted Dan S. document on Implementer's Guide Best practices (fixed consistent usage of XHTML, XML) Post meeting: document has been posted on DDI Alliance site on current specification and the 3.2 page. There will be an announcement in the news letter prior to IASSIST |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Jeremy, Dan S., Johan, Larry
NEXT WEEK TC presentations at Members Meeting and Scientific Board |
title | 20170427 |
---|
ATTENDEES: Wendy, Jon, Jeremy, Dan S., Larry, Johan, Barry
NOTED: No security certificate for ddialliance.org. Have notified the group and will follow up.
(post meeting: Jared has contacted Michael at ICPSR about handling this)
CESSDA: will work on that and get it out to TC later today for approval and sending over weekend
DDILIFE Issues resolved:
DDILIFE-3545
DDILIFE-3532
DDILIFE-3533
For each area:
- Issue being addressed
- Enablers of the solution
- How to implement
There were still some ambiguities about best practices for identification which will be distributed for discussion next week.
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Jeremy, Dan S., Dan G., Larry, Jay, Johan
CESSDA Metadata Model
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Jeremy, Jon DDILIFE-2933 Reviewed and require more information from filers before action - wlt will contact regarding this and related issues raised in the related papers which was based on 3.1 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Larry, Jay, Dan G., Dan S., Jeremy, Johan
DDI Lifecycle issues: |
title | 20170323 |
---|
Work plan
Approved with some minor changes in legend and use of color. Legend now identifies Critical (red), Priority (green), Oversight (light blue), and External dependencies (gray)
Oversight only: work that is being done by groups other than TC that the TC has responsibility for ensuring completion
External dependencies: TC has responsibilities following the work of an external group but is dependent upon the group completing work before taking on those responsibilities. TC will check in on progress periodically and adjust TC workplan when required.
DDILIFE issues for 3.3
DDILIFE-3510 (cannot progress until schema changes for 3.3 are all entered)
DDILIFE-3540 resolved (documentation)
DDILIFE-3541 closed (use avaialbe attribute)
DDILIFE-3534 resolved
ACTION ITEM:
create an online dynamic listing of added documentation (inline and highlevel) between publications.
PRODUCTION RULE:
The addition of inline documentation alone should not drive a version change
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Jeremy, Larry, Dan S. |
Expand | ||
---|---|---|
| ||
Meeting canceled due to meeting conflicts and technical issues of members |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Larry, Jeremy, Dan S., Dan G., Johan |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Jeremy, Johan, Larry |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Larry, Dan S., Jeremy, Johan Worked on 2934 to clarify exactly what was being addressed and how to make this machine actionable information that could be used by statistical packages |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Jeremy, Larry |
title | 20170202 |
---|
ATTENDEES: Wendy, Jon, Dan S., Larry
Q2 review wrap up:What needs to be completed prior to report
Do we do a preliminary report (by end of February) with a follow up at annual meeting (some issues may not be resolved easily)
Working with other teams where issues were assigned
What should be included in report?
Discussion
- We can say at the end of Feb/March that this is the current status
- There are generic issues that are still being worked on
- If people are particularly interested in particular things they can follow up on issue tracker
- GSIM and RDF broader issues
- They would be resolved by next release???
- Respond to individual reporters
- Evaluation of the review system in TC
- Follow-up with other groups:
- We had 85 issues raised and were shoved off to various places
- Describe how we're going to manage over the next few months
- Follow up with each group getting a short paragraph from each group about status of these issues: Codebook requirements, things dependent upon other things, etc.
Reviewed for inclusion in 3.3 and basic comments
*=DDI3.3 priority, F=Future
*3532 - Measurement Unit
*3533 - Measure Definition
*3534 - Include documentation on DDI - CV availability
*3535 - INSEE use of Conditional text uses this as a means of dealing with language variations
F3536 - Incorporation of DDI-Views Process Pattern
F3537 - Rest Protocol
*3538 - Field for unavailability remarks /reason for data not being available
*R3539 - Controlled Vocabulary for Data Access
*3540 - Detailed Information about Individuals
Got to this point: members asked to review and identify any that should not be DDI3.3 Priority
3541 - Variable Quality
3542 - Detailed Information about Literature
3543 - Field for Products
3544 - Field for File Size
3545 - Add Measurement and Measurement Construct to Instruments
3548 - Would like to capture relationship "isReplicateOf" and opposite
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Larry, Jon Note: XKOS review extended through 2017-02-15 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Johan, Larry, Jeremy, Jon, Guillaume, Dan S. Q2: Reviewed triage decisions, approving approaches Lifecycle issues 3533 and up |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Dan S., Larry, Jeremy AGENDA:
Reinstatement of DNS work:
3.3 work
Next: new issues in DDI-LIFE, Q2 triage/results |
title | 20161222 |
---|
AGENDA
- Reinstatement of DNS work - Yes
- RDF Vocabulary Public Review (XKOS, DISCO) - XKOS by EOY and DISCO when Achim says its ready
- Extension of Q2 review period (through Jan 15) - YES
- 3.3 work - delay until next meeting
Joachim Wacker reported that he had been working on the issue of resolving DDI URNs, which involves communicationwith the Domain Name System (DNS), a hierarchical distriubted naming system for computers, serices, or an resource connected to the Internet or a private newwork. The Alliance needs to interface with DNS to resolve DDI URNs now that 3.2 has been published and the identification mechanism is stable. Achim will be developing a Request for Comment document for the Internet Assigned Numbers Authority (IANA) and then will apply for the DDI URN and DNS entry, which will help to resolve DDI URNs int he future. URNs will be resolved in a two-stage process: the DDI agency ID gets resolved by DNS and the requesting software receives an answer as to what kinds of DDI services are available; then the local system is queried and URNs are resolved.
Open issues are here: https://github.com/linked-statistics/disco-spec/issues?q=is%3Aopen+is%3Aissue
Some issues regarding the model should be probably closed before the review, like 220-228. I can try to get this resolved with Thomas and Ben by email in mid of January. All others I can try to resolve in January or they will be open while the review. They are not critical. Some cleanup work has to be done on the website as well. I can take care for this. I’ll be in office again starting from Jan 16.
We have to deal with some time restrictions. Thomas is available only on the weekends for calls. Ben is busy until end of January with lectures. I assume both would be available in February for answering possible questions by email regarding new issues coming up while the review.
This could result in a plan of finalizing Disco for review in January and starting the review for example on Jan 30 or Feb 6 (more relaxed).
Re DDI URN:
See also my email from Monday.
I see following main questions:
- Do want to go for a DDI URN? I’m still convinced that this is the right approach.
- If yes, which versions of DDI should be addressed by the RFC for the DDI URN and which not. I assume 3.2 (and 3.* >3.2), 2.5 (and 2.* >2.5), and DDI-Views (no maintainable anymore). Can DDI 3.1 be omitted?
- Should we plan a REST protocol? I think this is the next appropriate step to provide a basis for distribute DDI resources (identified by the DDI URN, resolved by DNS and local services, and queried by DDI REST).
Currently we just should express a strong interest in this; then we can go ahead with making a plan.
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Larry, Dan S., Jeremy, Chantal, Flavio, Jon New member: Chantal Ripp From StatsCan working with Data Liberation Initiative using DDI-Codebook with some transition work to DDI-L and DDI4 Next meetings: 11-24 Thanksgiving Day US (no meeting); 12-1 WT not available (Jon); No meeting on 12-8 EDDI; No meeting 12-15 Sprint |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jeremy, Johan, Dan S., Larry D4Q2: D4Q2-35, 34, 33, 15 verified completion and closed filed DMT 107 regarding consistency in usage of URN, URL, and uri in conjunction with xs:anyURI DDI 3.3: Set prioritites for meeting through December
Technical tasks from Mantis
|
title | 20161103 |
---|
ATTENDEES: Wendy, Jon, Dan S., Jeremy, Johan
AGENDA:
- Review process update
- TC assigned issues
Review process update
- Went over the general process and Triage results
- Reviewed report Dashboards created by Jon
- Discussed means of tracking issues assigned to other groups
- completion
- action taken
- review of handling - was it really dealt with or just tabled
- ACTION: Jon and Wendy will look at options for better tracking of group actions
TC Assigned Issues
- Resolved the following issues in D4Q2: 5, 12, 15, 33, 34, 35, 44
- Fixes were made and once reviewed will be closed
title | 20160929 |
---|
ATTENDEES: Wendy, Jon, Jeremy, Dan S., Larry
- Couple of other things different in Lion from diagram
- Workflow realizes process and page 7 Using Process Pattern. Add in.
- Workflow sequence contains WorkflowSteps
- Process contains ProcessStep - make note difference.
TC review of Q2 release contents
- Look at scorecard and design rules to see if there is something we need to add
- We should be able to follow post passing on to another working group so track within other groups and if they have been resolved.
- Link to issues as filed in other group
- Track / review linked use tags or labels as to which group it went to
- How does MT follow what other groups are doing? We could put in an issue in DMT with all the links
- If TC assigns an issue to a group we should be looking at how they are following up if only for reporting purposes and compliance with design rules
- Wendy will look at JIRA for possibilities, revise and/or provide implementation of Jon's workflow draft
ACTIONS
- watch for materials for comment over the next week
Dan and Jeremy unavailable next 2 weeks for calls
title | 20160922 |
---|
ATTENDEES: Larry, Dan S, Jeremy, Jon
Apologies: Johan, Wendy
AGENDA
JIRA Workflow
Jon didnt do - will do so for next week
DDILIFE-3511
Function and documentation of in/out parameters - for NEXT week
DDILIFE-3533
Need Wendy's views on implications on this. As it appears that it would mean connecting the NCube structures / references into the variable cascade.
It was though that the NCube structures were thought about solely to manage instance variables and this could mean extending in, 3.3. was not meant to be leading to major changes, so a judgement is needed here.
DDILIFE-3532
Adding MeasurementUnit to RepresentedVariable makes sense for ValueRepresentation (not for CategoryScheme - though Larry raised whether this might be a use case).
Agreed to look at other elements in RepresentedVariable to make sure that other elements should not also be included
Other elements on VariableRepresentation are:
VariableRole?,
r:WeightVariableReference*,
StandardWeightReference?,
ImputationReference?,
ConcatenatedValue?,
r:ProcessingInstructionReference?,
(r:ValueRepresentation | r:ValueRepresentationReference)?,
MissingValuesReference?,
r:ContentDateOffset?,
r:AggregationMethod?
Also, whether there is any interaction as a consequence of DDILIFE-3512 and 3503
DDILIFE-3529
For discussion next week
Style |
---|
#theme-header {display: none;} |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Olof, Larry, Jon, Johan, Jeremy, Dan S. AGENDA: For Q2 release:
Recommendations for Dagstuhl Week 2 Agenda:
To Do Items:
FOR NEXT WEEK: Scheme for review JIRA tracker Binding and IN/OUT parameters Review of any unagreed LIFECYCLE issues Hold time in your schedule to review package from MT during the week of 24-30 September. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Dan G., Jeremy, Larry, Guillaume Agenda:
DDI Management Document: Approved for sending to Director's Advisory Group DDILIFE 3529 - table for additional material on implications DDILIFE 3530 - Generic grids is tabled to post-3.3; other related issues need comment and updates - will happen over the next two weeks DDILIFE 3531 - Resolved to move isPublished to AbstractVersionable - additional information regarding additional publication levels was determined to be out of scope. See comment on issue. Update provided on Q2 2016 Review - anticipated receipt of package 2016-09-23, we will need to move quickly to get review out in one week |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Dan G., Jeremy, Larry, Guillaume Agenda:
3529
3530
3531
Data Management document
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Jeremy, Dan S., Larry Reviewed process for managing the Q2 review process. No changes or additions. Will revise during process as needed. Discusses overall work flows and work activities of the DDI Alliance in terms of interface with TC activities and responsibilities. Discussion based on conversations with individual members over the past month. Summary of discussion will be written up and distributed to TC members for editing and further action. Topics covered:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Jeremy, Guillaume, Flavio 3.3 QuestionGrids examples have been placed on 353
After next two meeting: take a view of what can we get into 3.3 Review process in Q2: Alter basic approach to:
Role of TC:
ACTION: Draft up a definition of group roles and specific activities of TC in review (wlt) |
Expand | ||
---|---|---|
| ||
ATTENDEES: Achim, Dan S., Wendy, Jon, Hilde O, Guillame D, Larry, Jeremy 3518 - Question item linked to Represented variable Concept and universe incorrectly placed in represented variable Not a universe, it a Unit Type. this was corrected in Issue 3512 When a question is reused, the instance variable will be linked to the represented variable and hence 'self harmonised'. DECSION: a) add the link to Question Item 0..n these also may need to be linked to different Represented variables (structured mixed response domain) b) review how to add to Question Grid given that it collects multiple responses and need a clear link between a subset of responses and a specific RepresentedVariable Build a structure that clarifies the path between response set/subset and specific RepresentedVariable 3122 - 497(Mantis): Need a means of indicating if question translation was done for data collection or not Translations need to be maintained independently of the source. Use a controlled vocabulary in TypeofQuestionGroup 3526 - Other, please specify" in QuestionGrid a. In progress b. Look at examples - requirements and based on that explore additional grid like formats that have a more open use. Create new issue to draw up a 'Demand for a Generic Grid structure' |
Expand | ||
---|---|---|
| ||
ATTENDEES: Questions in 3.3
TO DO:
|
title | 20160630 |
---|
ATTENDEES: Wendy, Jon, Achim, Dan S., Jeremy, Dan G., Flavio
Update on RDF Vocabularies
- Reviewed list of information needed to get RDF vocabularies out for review
- Links will be to DDI Alliance site pages www.ddialliance.org/Sepcification/RDF/Discovery ../XKOS
- Get current XKOS version from Franck as well as link to implementation
- DISCO - Missy is an implementation
- Verify Franck availability during review period. Franck and Dan G. will do XKOS follow-up
- Thomas Hartmann and Benjamin Zapilko will do DISCO follow-up
- Review will be for 8 weeks with reminder at mid-point to get comments in
- Double check to see who the announcement comes from (TC and/or Director)
Update on Q2 work
- Patterns issues:
- if we go back to the previous way should not cause a major problem
- How we use the pattern and how its realized - we need to be minimally happy with it
- Statistical Classification needs to be redone, Data Description, Format is more preliminary (put out with caveat of only CSV and Fixed), Agent
- Could take 3 weeks instead of 2 - Can we get some of this through as a flow for the purposes of documentation?
- List of documents that need review for accuracy - make a google doc to work on with sections
- A thing we could call out is whether the approach to patterns make sense
Preparation for discussion on Questions in 3.3
- How question grids are currently used
- The user defined grids (generic grids) - arrange questions and structures that they want to (people want to use it for everything)
- Describing more complex grids - how is this contrary to multi-mode
- Separation of reusable question / its use; ties up with the clarification of the process pattern (3.3 vs 4)
- Separation of display and content
- goal is to get 3.3 decision with a mind to 4
- July 7 - RDF update if needed
- Other meetings will take place only if we have topics - Q2 work primarily
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Larry, Flavio, Jeremy, Jon Reviewed documents on Cardinality Rules and revisions to Identifiable and Annotated Identifiable Finalized documents and sent to MT |
title | 20160616 |
---|
versionDate
...
title
creator
...
versionDate
...
annotation
title
creator
...
Discussion:
- Use of Annotation as other than annotation of the metadata class; i.e. citationOfDataFile Datatype=Annotation
- Probably would like to retain Annotated as a ComplexDataType
BibliographicCitation returned to Annotation to support a means of providing a string for a published citation by the provider
- Things that have intellectual content and need to be discoverable in their own right should be AnnotatedIdentifiable
- Example: A CodeList would need annotation as would the categories that are being coded are concepts with intellectual content, however the "Code" attached to it only intellectual meaning within the context of the CodeList and if it needs identification should just be Identifiable.
title | 20160609 |
---|
ATTENDEES: Wendy, Jon, Dan S., Jeremy, Dan G., Johan, Achim
AGENDA:
- Summer schedule
- DDILIFE-3527 Ornulf's paper
- Update from Sprint and IASSIST
SCHEDULE:
Vacations:
- Jon - July 2-24
- Johan - all of July
- Dan S - June 23
- Achim - August
- Jeremy - Sept 29
- Dan G - August sometime
Activities and due dates:
- June 9 - 15 Finalize RDF for review
- June 16 - 22 RDF Vocabulary page set up
- June 23 - 29 RDF Vocabulary public review
- June 30 - July 6 Q2 set up pages/JIRA; Q2 request issues
- July 7 - 13 3.3 question structure resolution; Q2 pre-announce
- July 14 - 20
- July 21 - 27 Q2 development release
- July 28 - Aug 3
- Aug 4 - 10 Codebook request issues
- Aug 11 - 17 3.3 schemas
- Aug 18 - 24 3.2 documentation; 3.3 documentation
- Aug 25 - 31 3.3 review
- Sep 1 - 7
- Sep 8 - 14 Codebook set up pages/JIRA;
- Sep 15 - 21 Codebook pre-announce
- Sep 22 - 27
- Sep 28 - Oct 5 Codebook development release
DDILIFE-3527
- Ornulf paper - read for next week
- Most of his concerns are now met - how things are brought into codebook
- DDI 4 identification
- Point for instructional material
- When people are modeling they use the annotated identifiable as a base when they could be either a ComplexDataType or even just an Annotated base or add a relation to Annotated
- Can TC come up with guidelines for when something is a ComplexDataType, Identifiable, AnnotatedIdentifiable, or independent use of has Annotation
- We may also want to enhance the identification paper to include the guidelines
UPDATE:
http://cessda.net/About-us/2015-Work-Plan#eztoc6619_0_3
https://www.ukdataservice.ac.uk/about-us/our-rd/cessda-metadata-management
title | 20160519 |
---|
ATTENDEES: Wendy, Larry, Dan S., Jeremy, Jon
DDILIFE 3525/3526:
Discussion centered on both the specific issues and a more general review of Questions and Question Grids in 3.3. In particular we are trying to limit backward incompatible changes, but at the same time want these to work at least for the known/general use cases. Dan S. is doing a review of how and where particularly grids are used so we can define a set of use cases we need to meet. These will drive our review of the Question and Question Grid structures.
We are clear about the problems presented and will include these in the general review needs.
ANNUAL REPORT:
Identified items to be included in annual report. Wendy will draft and send around for final comments or additions. Included were items focused on last year and those that would be focused on next year.
Noted meeting with Sanda and Taina in Bergen. Any Controlled Vocabulary issues that others would like raised should be sent to Wendy before 31 May.
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Larry, Dan S., Jeremy DDILIFE 3525 tabled until next week TC review of MT materials for review Since that review we come up with the idea of platform specific ADD TO list on Status Report:
Added to Capability Metrics:
These should be commented on in the status report REVIEW PAGE:
TC 2 week turnaround once delivered from MT to do the Status Report If anything is frozen we need to be explicit about that - need decision from MT about Freezing/period for Freezing part or all of Drupal TO DO List:
|
title | 20160505 |
---|
ATTENDEES: Wendy, Larry, Dan S., Jeremy, Jon
DDILIFE-3525
General comment: we may want to do a users survey and see what kinds of grids are supported then either create a one-grid to rule them all or a set of grids that address simple standards cases and then more specified complex types. This would be good prep for DDI4 discussion. Dan will survey what's being supported.
DDI has always tried to the logical form of the questionnaire to be multi-model and some of this seems to be large screen and paper. A separation of the logical and display when we choose to go into display.
ACTION: Dan will do the survey and Wendy will review the specific issue for next week
Review and update of Task List on TC page
- Adjusted dates for development reviews (DDI4), RDF vocabularies and 3.3
- WLT - review Design Principles document against original MF principles list for completeness, bring any outstanding issues to TC next week
- Set process to transfer an Agency ID - Talk to Jared on writing up a procedure on this
- Jon will have draft of 3.2 high level document update ready for TC review soon - Once reviewed this can be an expedited sub-minor version change; follow-up would be to work with Training Group on developing content for Use Cases/User Guide
Next weeks agenda:
- DDILIFE-3525
- Any work resulting from review work above
- Process for reviewing material from Modelling Team for publication
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Achim, Jeremy, Dan S., Jon, Johan, Larry Design Principles:
Documentation:
Design:
Capability:
ACTIONS:
Functional Views documents - See DMT-59, DMT-34 PHDD comparison and Public Review: discussion
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Johan, Larry, Jeremy AGENDA:
|
title | 20163031 |
---|
ATTENDEES: Wendy, Michael Iannaccone, Achim, Jon, Dan G., Dan S., Larry, Flavio, Jeremy, Kelly
AGENDA: URL issues; DDILIFE 3511, 3516, 3513, 3521; RDF review
URL issues (with Michael Iannaccone from ICPSR)
Michael: Two things need to be resolved Is the current server compatible or be made compatible If the URL's can be made compatible with Druple
Michael will investigate Needs a set of all files we need to serve so we can ignore all of these paths He needs to test
Achim and Dan will provide URL for current files to Michael
The service they are on right now is $50/year and has been a reliable plateform, but it may not provide a lot of support An option at $32 a month would provide the support needed Possibly hosting on ICPSR server rather than U of Michigan - needs to look into
RDF Review:
XKOS is ready to go some delays with DISCO Achim will let us know when there is a firm date
DDILIFE Issues
3521 - ask Johan to respond
3511 - need response from Guillaume, Hilda, and Achim
3516 - only for PhysicalInstance
3513 - Time looks good people need to look at Geography
3524 - Dan and Jeremy need to report
Larry added comment to DMT-21 regarding duplication of Unit in Population as noted in today's discussion.
NOTE: Getting response on 3521, 3513, and background report on 3524 should wrap up issues work on 3.3. Jon and Wendy making major advancements on the documentation so we are making steady progress.
Who's going to be at NADDI?
Dan S., Jeremy, Wendy, Dan G., Larry, Arofan
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Achim, Dan S., Jeremy, Larry, Jon, Guillaume AGENDA: Q1-2015 Review Summary
URL Naming Scheme
DDI 3.3 issues
Remaining status:
NEXT WEEK:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Larry, Johan, Achim, Dan S., Jeremy, Jon Final Review of DDI RDF Vocabularies: (summary document)
TC deadlines:
Controlled Vocabularies - Technical structures:
Proposal:
Discussion:
ACTIONS:
|
title | 20160225 |
---|
ATTENDEES: Wendy, Larry, Jon, Achim, Jeremy, Dan S., Johan
AGENDA:
Last set of DMFQA issues - Structure of ComplexDataType Name, Definition and Description usage, movement of Definition from Member to Concept, Inheritance of ConceptualVariable from Concept
Multiple names 0..n
Each name needs a context (optional)name
content = xs:string
context = EnumeratedValue whatever
- This is much clearer than using LocalID
- Place name on Concept and then where it is needed.
ACTION:
- A group of people are concerned with having a definition and/or description
- Put definition on Concept and make sure that the others that need it actually get it.
- DMT-56 has to really think about what it really means to have all these things being concepts as well as linking to concept (expand on this in the final report summary). Where in the Variable cascade it is more meaningful that it Measures a concept. See DMFQA-50, 25, 7 Breaking the inheritance chain between ConceptualVariable and Concept.
- Review all of them
- Distinction between definition and description. There are the people filling in the metadata and those who do the searches.
One way to test if this is acceptable is to go with what has been proposed in the table as agreeable and highlight it in the next review. This is the best solution we have and is it workable or unworkable and then go from there. Make sure this get clear in the review instructions. Especially from the search direction. Issue 41 suggested that only one or the other which was rejected and that there needed to be clear documentation and more disciplined use. Write up the two parts clearly.
When a description is used without a definition is the description documentation still appropriate?
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Larry, Dan S., Jeremy, Flavio, Achim DMFQA-66,71 (attachments on 71) Closed and sent to MT as DMT-59. General information provided for instructions to Business Modelers and users. Issues of common content PARKED in the MT. DMFQA-28,41,53, 38 (attachments on 41 Resolved for recommendation 1 in renaming of Label and more clearly defined role of Name, definition, and description. ACTION:
|
title | 20160211 |
---|
ATTENDEES: Wendy, Jon, Larry, Johan, Jeremy, Dan S., Achim
DMFQA-71, 66:
Walked through and edited document Functional Views.docx on DMFQA-71
ACTION: review lion content in Utility and edit to reflect changes
SPRINTS
IASSIST: Marcel and Michelle will both be available to act as SprintMeister for IASSIST Sprint.
NADDI: Wendy and Jon are organizing. Please send any TC specific requirements for discussion or outputs to the list.
Q1 Review document:
Send comments to list and/or edits to document. Still need to resolve 2 sets of items before releasing (71,66 and Name/Label/Description, etc. issue)
NEXT WEEKS AGENDA: Please add to calendar
title | 20160204 |
---|
ATTENDEES: Wendy, Achim, Larry, Jay, Jon
AGENDA
- DDI-LIFE 3522, 3523, 3525
- NADDI Sprint
DDI-LIFECYCLE 3522
Agreed proposal from Wendy
addition of the following object to DateTimeRepresentationBase and ManagagedDateTimeRepresentation:
DateRangeLimits (0..1) type="Range"
Enter the Minimum and Maximum values of the valid date range in the format provided in DateFieldFormat.
DDI-LIFECYCLE 3523
Deferred discussion, as verbal input from Wendy required
DDI-LIFECYCLE 3524
Deferred discussion, general view was that this is possibly only needs documentation / examples, Seek views of Jeremy / Dan to see if this is a real world problem elsewhere.
Discussion on NADDI Sprint
There are enough people to make the Sprint work, focusing on a review of content and preparation for Q2 Release
Wendy and Jon will work on setup etc
Likely attendance is: Wendy, Arofan, Larry, Jon, Dan G (and possibly Jay)
Remote attendees: Barry, Oliver, Achim (possibly Olof)
Items for Next Week
a. Deferred items from last week
b. DMFQA – 71 Views: should they have a basic set of classes?
c. DMFQA – 66 Functional Views: Usefulness of Functional Views
d. IAssist Sprint Content
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Achim, Jon, Dan S., Jeremy, Larry AGENDA: Remaining Q1 Issues: Views and content 71 - Views: should they have a basic set of classes? 66 - Views: Usefulness of Functional Views
ClassificationItem, Code and CodeList 52 - Unclear difference between ClassificationItem and Code 48 - So many ways to create a CodeList
Ability to provide a relationship to a Concept 50 - Review all classes that extend Concept for appropriateness
Name/Label, Definition/Description Issue 53 - Insufficient documentation for Designation 38 - Chapter 10, Designation, Relationhsip, P147 43 - InstanceVariable, RepresentedVariable, and ConceptualVariable should have semantic "name" property 41 - Redundant properties: definition and description
Next week:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Achim, Guillaume, Jeremy, Jon, Larry AGENDA:
DDILIFE-3511
ACTION:
ADDITONAL comments:
Summary of TC Q1 review
Add minutes from 1/14 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Larry, Jon, Johan DDILIFE 3620, 3504 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Johan, Larry, Jeremy, Dan S., Dan G., Flavio Reviewed DDI Lifecyle issues 3504-3519 all but 3511 are now in process. 3520 will be addressed next week. 3521 was added based on discussions of 3511. Members asked to review list of recommended changes from xs:integer to xs:noneNegativeInteger by next week DDILIFE-3504 Try to wrap up outstanding issues next week. |
Agenda Topic Index Key
Pre-2016 Minutes Page
20160908
20160901
20160818
20150611
20150212
20150129
20150122
20160915
20160303
20150423
20170504
20170427
20170420
20160428
20170907
20170810
20170803
20140821
20170202
20140619
20170914
20170907
20170831
20170803
20170706
20170629
20170615
20170608
20170427
20170413
20170330
20170323
20170316
20170302
20170223
20170216
20170209
20170112
20161117
20161110
20160922
20160908
20160901
20160811
20160804
20160721
20160630
20160519
20160505
20160421
20160331
20160310
20160204
20160121
20160114
20160107
20151217
20150618
20150507
20150326
20150305
20140619
20141120
20141113
20150514
20150423
20150416
20150219
20150129
20150122
20150115
20141113
20150611
20150514
20150416
20150326
20150305
20150212
20150205
20150129
20150122
20150115
20141218
20170316
20170202
20170119
20170112
20161222
20161110
20161103
20160225
20160218
20160211
20160128
20151217
20151119
20151112
20151001
20150924
20150917
20150910
20150903
20150827
20150820
20150813
20150806
20150723
20150716
20150709
20150702
20150325
20150618
20160623
20160616
20150514
20150430
20150212
20150115
20141002
20150521
20150430
20150423
20150416
20150402
20150319
20160929
20160811
20160630
20160512
20150521
20150430
20150305
20150226
20150219
20150212
20150205
20141120
20141113
20141002
20140821
20140417
20160915
20150430
20141120
20140522
20140515
20140417
20130801
20140918
20140717
20140703
20140626
20140612
20140626
20140612
20140515
20140417
20140703
20140612
20140612
20140515
20140417
20160331
20150219
20150205
20150129
20160303
20150122
20161222
20160630
20160428
20160331
20150212
20150115
20140515
20140417
20140821
20140515
20150319
20150205
20170323
20160609
20151210
20140619
20140410
Agenda Topic Index Key
Pre-2016 Minutes Page
AGENDA TOPIC | DATE |
---|---|
DDI 3.3 | 20180118 20180111 20180104 |
DDI 4 Prototype | 20180118 |