Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jeremy, Larry DDILIFE-2935 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Oliver, Jon, Larry, Johan, Kelly Reviewed commits and pushed to master |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Oliver, Dan S., Jeremy, Jon, Jay
|
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 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Dan G., Larry, Jeremy Approved this list for Dagstuhl 2017: Define model-based approach - Reviewed final issues - on track for later October Codebook View Ready for MT/TC preparation for review - can go forward with the set of elements identified Where to Publish the web docs for 3.2 and 3.3
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. Dan S. will set up DDI-COGS repository containing CSV etc. and another repository to support generated outputs to support web pages |
Expand | ||
---|---|---|
| ||
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 June 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 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 |
Expand | ||
---|---|---|
| ||
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: 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 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Jeremy, Larry
support new users of existing products
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 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Jeremy, Dan S., Larry, Johan, Barry NOTED: No security certificate for ddialliance.org. Have notified the group and will follow up. CESSDA: will work on that and get it out to TC later today for approval and sending over weekend DDILIFE Issues resolved:
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: |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Larry, Jeremy |
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 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Larry
Discussion
|
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 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Larry AGENDA
I spoke with Achim at EDDI and apparently the work he was doing regarding filing for a DNS. This will be the basis of getting approval for the DDI URN and having a related DNS entry for arpa.urn.ddi (for the DNS-based resolution of DDI agency ids). Here is the statement from the 2014-06-02 DDI Alliance Meeting of the Scientific Board: 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. Funds have already been allocated for this filing. The most recent document I seem to have is from 2009 and is attached. However, I may have something more recent on my home computer. The point of the agenda item is that Achim would like a formal go-ahead before he picks up work on this again. As you see this document is from 2009 and would require updating to support all versions of the DDI URN. Here is the latest version: The required work would comprehend the adaption to the current DDI URN format and to some underlying RFCs which changed in the meantime changed. The formal definition of a DDI URN is required if we want to use them broadly. This RFC draft (see above) defines the DDI URN before the great identifier discussion. Furthermore it defines a distributed way - based on DNS - to resolve DDI URNs in a two step process to local services and to physical locations. This work and the definition of a DDI REST protocol could build the basis of a distributed DDI-based infrastructure. One question is which versions of DDI URNs should be described by this document? I assume 3.2 (and 3.* >3.2), 2.5 (and 2.* >2.5), and DDI-Views (no maintainable anymore). Re Disco: 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 Issues remaining possible for 3.3 (see spreadsheet) 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
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Jeremy, Johan AGENDA:
Review process update
TC Assigned Issues
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Jeremy, Dan S., Larry Q2 Prep Workflow is missing from Lion
TC review of Q2 release contents
New workflow for Q2 JIRA
ACTIONS
Dan and Jeremy unavailable next 2 weeks for calls |
Expand | ||
---|---|---|
| ||
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: Achim, Dan S., Jeremy, Wendy (Hilde paper) Questions in 3.3
TO DO:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Achim, Dan S., Jeremy, Dan G., Flavio Update on RDF Vocabularies
Update on Q2 work
Preparation for discussion on Questions in 3.3
Meetings in July
|
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 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Achim, Dan S., Jon, Larry, Jeremy Recommendation: change Annotation to ComplexDataType When you are annotating there are two options ONE: all content as first order properties versionResponsibility versionDate ... title creator ... TWO: retain Annotation as a ComplexDataType versionResponsibility versionDate ... annotation title creator ... Discussion:
Discussed (no real decision): BibliographicCitation returned to Annotation to support a means of providing a string for a published citation by the provider Recommendation that properties from current AnnotatedIdentifiable be part of Identifiable What should be AnnotatedIdentifiable?
Looked at the questions Why should a class be identifiable? Why should a class NOT be identifiable? Took notes on original document. Will reframe with recommendations for changes to model and decision model for making a class identifiable or annotatedIdentifiable. |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Jon, Dan S., Jeremy, Dan G., Johan, Achim AGENDA:
SCHEDULE: Vacations:
Activities and due dates:
DDILIFE-3527
UPDATE: Reviewed Larry's spreadsheet and made a detailed assessment of mapping into model Jay and Dan did work on Methodology with a scheme on how to relate the designs at various levels of specificity to describe study level (high) to detailed level Glossary need - particularly in terms of use of the class (can we harvest off terminology from documentation of the use of a class in a view to create a cross-user-base terminology) DDI-R from Poster Session not currently in repository of R so now we have a number of them but they are all in development stage; which approaches people are taking and what are the limitations IPython preceded by a tool Jupyter (presentation session) - how could this fit into our idea of documenting code with general/generation instruction CESSDA projects with lots of presentations with work in progress - There is a group developing some more abstract rules on the technical framework (Johan) and categorization of tools (ranking software regarding usability, maturity, etc.) (Hossein Abroshan hossein.abroshan@cessda.net) https://wiki.earthdata.nasa.gov/pages/viewpage.action?pageId=49446977 CESSDA Metadata Management Project is working on a DDI profile for CESSDA purposes. Contact Mari. http://cessda.net/About-us/2015-Work-Plan#eztoc6619_0_3 https://www.ukdataservice.ac.uk/about-us/our-rd/cessda-metadata-management Would it be useful to have a page where we could track things we'd like to keep track of; there is work on a more comprehensive listing of papers, presentations, etc. that we may want to link into. Bring this idea into the group working on this (Achim) ACTION: Achim will draft points for a note to Mari from TC regarding CESSDA DDI profile work and Wendy will send from TC. |
Expand | ||
---|---|---|
| ||
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:
|
Expand | ||
---|---|---|
| ||
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
Next weeks agenda:
|
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:
|
Expand | ||
---|---|---|
| ||
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:
|
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Larry, Jon, Achim, Jeremy, Dan S., Johan AGENDA:
ACTION:
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:
|
Expand | ||
---|---|---|
| ||
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 |
Expand | ||
---|---|---|
| ||
ATTENDEES: Wendy, Achim, Larry, Jay, Jon AGENDA
DDI-LIFECYCLE 3522 Agreed proposal from Wendy addition of the following object to DateTimeRepresentationBase and ManagagedDateTimeRepresentation: DateRangeLimits (0..1) type="Range" 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
2018 Minutes Page
Pre-2016 Minutes Page
Agenda Topic | Meeting Date |
---|---|
Alliance Roles/Activities | 20160908 20160901 20160818 |
Atlassian Tool User Access | 20150611 20150212 20150129 20150122 |
Bitbucket Repository | 20151105 |
Controlled Vocabularies | 20160915 20160303 |
CSPA LIM | 20150423 |
Design Principles/Best Practices | 20170504 20170427 20170420 20160428 |
DDI 2.x | 20170907 20170810 |
DDI 3.2 and GSIM | 20140522 |
DDI 3.2 Documentation | 20170803 20140821 20170202 20140619 |
DDI 3.3 | 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 |
DDI examples for users | 20140417 |
DDI Licensing & copyright | 20150514 20150423 20150416 |
DDI4 Comment Page | 20150219 20150129 20150122 20150115 20141113 |
DDI4 Documentation | 20150611 20150514 20150416 20150326 20150305 20150212 20150205 20150129 20150122 20150115 20141218 |
DDI4 Issue Review Q2 | 20170316 20170202 20170119 20170112 20161222 20161110 20161103 |
DDI4 Issue Review | 20160225 20160218 20160211 20160128 20151217 20151119 20151112 20151001 20150924 20150917 20150910 20150903 20150827 20150820 20150813 20150806 20150723 20150716 20150709 20150702 20150325 20150618 |
DDI4 Modeling Guidelines | 20160623 20160616 |
DDI4 Presentation - Town Hall | 20150423 |
DDI4 Production Process | 20150514 20150430 20150212 20150115 20141002 |
DDI4 Q1 2015 release issues | 20150521 20150430 20150423 20150416 20150402 20150319 |
DDI4 Q2 2016 release issues | 20160929 20160811 20160630 20160512 |
DDI4 Versioning and Binding | 20150521 20150430 20150305 20150226 20150219 20150212 20150205 |
DDI4: TC issues list | 20141211 |
DDI4: TC role in review | 20141120 20141113 20141002 20140821 20140417 |
Expression language | 20130801 |
IASSIST Sprint | 20140522 |
JIRA implementation | 20160915 20150430 20141120 20140522 20140515 20140417 20130801 |
Modeler Issues: Collections / Classification | 20140918 20140717 |
Modeler Issues: Core content | 20141522 |
Modeler Issues: Identifiers | 20140703 20140626 20140612 |
Modeler Issues: Name, Label, Description | 20140626 20140612 20140515 20140417 |
Modeler Issues: Q1 Content | 20141211 |
Modeler Issues: Reference | 20140703 20140612 20140612 20140515 20140417 |
Product URLs | 20160331 20150219 20150205 20150129 20160303 20150122 |
RDF Vocabularies | 20161222 20160630 20160428 20160331 20150212 20150115 20140515 20140417 |
SDI (Weighting, Sampling, Questionnaire Development) | 20140821 20140515 |
TC confluence site | 20150319 20150205 |
TC Priorities/Activities Scheduling | 20170323 20160609 20151210 20140619 20140410 |
Town Hall - informational | 20150423 |