Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Daily Agenda

M=Morning, A=Afternoon
Activity: G=Group discussion, S=Small group discussion, P=Prep work, D=Documentation work, I=Implementation work 
M/ATopicActivityAssignees Est. Time Allotted
A61/64SDanG, JJ60 minutes
M56GEveryone60 minutes
A56GLH,AG,WT60 minutes
A63SLH,DanG,JJ120 minutes
     
     
     
     
     

CURRENT ASSIGNMENTS:

NameIssueActivityDate
Arofan   
Dan G   
Jon   
Larry DMT-10 pre-sprint 
Wendy DMT-49, 47  pre-sprint
Achim*   
Barry   
Flavio*   
Jared   
Oliver DMT-51  pre-sprint
    
    
    

 *limited availability primarily for task assignments

   

Table of Issues and View of Progress

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

 

 

 

  • No labels