| Priority | Issue | Started | Prep | Discuss | Decide | Doc | Impl | Table | Done for Sprint |
|---|
| A1 | DMT-10 Agree on versioning/evolution framework | | | | | 4/11 | Added proposal to JIRA/ our work is done needs broader review | Tuesday | x | x | | | x |
| A1 | DMT-40 Prepare Data Capture View for use as initial formal test case of build process | | | | | | 4/11 | Review of Process Model prior to discussion | Wed | x | x | x | | x |
| A1 | DMT-45 Determine how to handle external references in XML and RDF bindings | | 4/12 | determined this has been resolved | | | x | | | x |
| A1 | DMT-56 A number of classes should have a relationship to Concept | | 4/12 | in drupal | | | x | x | | x |
| A1 | DMT-61 Use of Name, Label, Definition, Description - TC actions and recommentation | | 4/11 | in Drupal, document drafted | | | x | x | | x |
| A1 | DMT-63 Review of Data Description for Q2 2016 review | | | | | | | | 4/11 | Initial review completed, discussions held, decision on way forward made, some outstanding issues | Wed | x | x | x | | x |
| A1 | DMT-64 Property that provides a highlevel overview/description | 4/11 | | | | | | | x |
| A2 | DMT-18 Adoption of GSIM terminology | 4/13 | | Wed | x | | | | x |
| A2 | DMT-20 Intent and coverage of DDI 4 | 4/12 | | | | | | | x |
| A2 | DMT-21 Review for consistent use of Abstract Classes | 4/12 | | | | | | | x |
| A2 | DMT-22 Clarify references to GSIM, DDI versions, RDF | 4/13 | | | x | | | | x |
| A2 | DMT-23 Describe modeling conventions in high level documentation | | 4/12 | in progress; parts written needs to be pulled together reviewed and published | | x | x | | | |
| A2 | DMT-36 Some packages contain classes which duplicate the purpose of other classes | | 4/14 | packages for publication are OK | | | | | | x |
| A2 | DMT-47 Design and determine effective use of design decision document | | deemed out of scope for sprint. Not critical to Q2 but still on MT agenda | | | | | x | |
| A2 | DMT-49 Usage Guide for Lion | | 4/12 | part of DMT-23 | | | x | | | |
| A2 | DMT-51 Binding specific documentation | | 4/11 | Oliver is updating current changes in XML binding | | x | x | | | x |
| A2 | DMT-65 Inheritance issue with AnalyticMetadatum - related to use of Codes and Categories | 4/15 | | | x | | | | x |
| B1 | DMT-34 Rules for adding classes to Views - review for consistancy | | 4/12 | Decisions made documents need to be pulled together | | x | x | | | |
| B1 | DMT-60 Relationship between Sign and Designation requires clarification | 4/14 | | | | x | x | | x |
| B2 | DMT-12 Review the use of URN as opposed to URI | 4/13 | | | x | | | | x |
| B2 | DMT-19 Naming rules regarding use of verb or noun | 4/19 | | | x | x | x | | x |
| B2 | DMT-26 Reg Exp serialization in model should support multiple bindings | 4/14 | | | x | | | | x |
| B2 | DMT-28 Instructions for entering RDF mappings | 4/14 | | | x | | | | x |
| B2 | DMT-30 XML Centric expression of regular expressions | 4/14 | | | x | | | | x |
| B2 | DMT-46 Determine structure and implement an internal "code review" of the outputs | | | | | | | x | |
| B2 | DMT-59 Functional Views: structure, creation and content | | | 4/11 | documentation drafted | Tuesday | | x | | | |
| C1 | DMT-48 Review Relations and Correspondences | 4/15 | | | | | x | | x |
| C1 | DMT-54 Provide TC with contents of Q2 2016 release | | | | | | | x | |
| C1 | DMT-58 ValueDomain for RepresentedVariable | 4/14 | | | | | | | x |
| C2 | DMT-15 Can a Datum be Versioned? | 4/14 | | | | | | | x |
| C2 | DMT-17 Documentation for OrderRelation, Relationships, properties needs improvement | 4/14 | | | | | | | x |
| C2 | DMT-32 Review the use of patterns in DDI to leverage RDF and provide design consistency | | 4/13 | linked to patterns discussion (53) | | | | | | |
| C2 | DMT-53 Review use of design patterns | 4/11 | | | | | | | |
| C2 | DMT-57 Review documentation and intent for ClassificationItem and Code | 4/14 | | | | | | | x |