| Priority | Issue | Started | Prep | Discuss | Decide | Doc | Impl | Table | Done |
|---|
| A1 | DMT-10 Agree on versioning/evolution framework | 4/11 | Added proposal to JIRA | Tuesday | | | | | |
| 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 | Tuesday | | | | | |
| A1 | DMT-45 Determine how to handle external references in XML and RDF bindings | | | | | | | | |
| A1 | DMT-56 A number of classes should have a relationship to Concept | | | | | | | | |
| A1 | DMT-61 Use of Name, Label, Definition, Description - TC actions and recommentation | 4/11 | 75% in Drupal | | | | | | |
| A1 | DMT-63 Review of Data Description for Q2 2016 review | 4/11 | 90% in Drupal | | | | | | |
| A1 | DMT-64 Property that provides a highlevel overview/description | 4/11 | | | | | | | |
| A2 | DMT-18 Adoption of GSIM terminology | | | | | | | | |
| A2 | DMT-20 Intent and coverage of DDI 4 | | | | | | | | |
| A2 | DMT-21 Review for consistent use of Abstract Classes | | | | | | | | |
| A2 | DMT-22 Clarify references to GSIM, DDI versions, RDF | | | | | | | | |
| A2 | DMT-23 Describe modeling conventions in high level documentation | | | | | | | | |
| A2 | DMT-36 Some packages contain classes which duplicate the purpose of other classes | | | | | | | | |
| A2 | DMT-47 Design and determine effective use of design decision document | | | | | | | | |
| A2 | DMT-49 Usage Guide for Lion | | | | | | | | |
| A2 | DMT-51 Binding specific documentation | 4/11 | | | | | | | |
| A2 | DMT-65 Inheritance issue with AnalyticMetadatum - related to use of Codes and Categories | | | | | | | | |
| B1 | DMT-34 Rules for adding classes to Views - review for consistancy | | | | | | | | |
| B1 | DMT-60 Relationship between Sign and Designation requires clarification | | | | | | | | |
| B2 | DMT-12 Review the use of URN as opposed to URI | | | | | | | | |
| B2 | DMT-19 Naming rules regarding use of verb or noun | | | | | | | | |
| B2 | DMT-26 Reg Exp serialization in model should support multiple bindings | | | | | | | | |
| B2 | DMT-28 Instructions for entering RDF mappings | | | | | | | | |
| B2 | DMT-30 XML Centric expression of regular expressions | | | | | | | | |
| B2 | DMT-46 Determine structure and implement an internal "code review" of the outputs | | | | | | | | |
| B2 | DMT-59 Functional Views: structure, creation and content | 4/11 | | Tuesday | | | | | |
| C1 | DMT-48 Review Relations and Correspondences | | | | | | | | |
| C1 | DMT-54 Provide TC with contents of Q2 2016 release | | | | | | | | |
| C1 | DMT-58 ValueDomain for RepresentedVariable | | | | | | | | |
| C2 | DMT-15 Can a Datum be Versioned? | | | | | | | | |
| C2 | DMT-17 Documentation for OrderRelation, Relationships, properties needs improvement | | | | | | | | |
| C2 | DMT-32 Review the use of patterns in DDI to leverage RDF and provide design consistency | | | | | | | | |
| C2 | DMT-53 Review use of design patterns | 4/11 | | | | | | | |
| C2 | DMT-57 Review documentation and intent for ClassificationItem and Code | | | | | | | | |