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 28 Next »

Daily Agenda - Thursday

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
MDMT-40Gall30 MINUTES
MDMT-63Gall60 Minutes
     
     
     
     
     
     
     

CURRENT ASSIGNMENTS:

NameIssueActivityDate
ArofanDMT-20high level docWed
Dan G review document 
Jon   
Larry review documentWed
Wendy

 DMT-49

  Wed
Achim*   
Barry   
Flavio*   
Jared   
OliverDMT-10, 59impl in XMLWed
John HuckDMT-53paper reviewTuesday on
WendyDMT-23 Wed
    

 *limited availability primarily for task assignments

   

Table of Issues and View of Progress (Note: Done means done in the sense of this sprint)

PriorityIssueStartedPrepDiscussDecideDocImplTableDone
 A1DMT-10 Agree on versioning/evolution framework4/11Added proposal to JIRATuesdayxx   
 A1DMT-40 Prepare Data Capture View for use as initial formal test case of build process4/11Review of Process Model prior to discussionWed     
 A1DMT-45 Determine how to handle external references in XML and RDF bindings4/12determined this has been resolved  x  x
 A1DMT-56 A number of classes should have a relationship to Concept4/12in drupal  xx  
 A1DMT-61 Use of Name, Label, Definition, Description - TC actions and recommentation4/11in Drupal, document drafted  xx  
 A1DMT-63 Review of Data Description for Q2 2016 review4/1190% in DrupalWed  x  
 A1DMT-64 Property that provides a highlevel overview/description4/11       
 A2DMT-18 Adoption of GSIM terminology4/13 Wedx   x
 A2DMT-20 Intent and coverage of DDI 44/12       
 A2DMT-21 Review for consistent use of Abstract Classes4/12       
 A2DMT-22 Clarify references to GSIM, DDI versions, RDF4/13  x   x
 A2DMT-23 Describe modeling conventions in high level documentation4/12       
 A2DMT-36 Some packages contain classes which duplicate the purpose of other classes packages for publication are OK      
 A2DMT-47 Design and determine effective use of design decision document        
 A2DMT-49 Usage Guide for Lion4/12part of DMT-23  x   
 A2DMT-51 Binding specific documentation4/11Oliver is updating current changes in XML binding xx   
 A2DMT-65 Inheritance issue with AnalyticMetadatum - related to use of Codes and Categories        
B1 DMT-34 Rules for adding classes to Views - review for consistancy4/12   x   
 B1DMT-60 Relationship between Sign and Designation requires clarification        
 B2DMT-12 Review the use of URN as opposed to URI4/13       
 B2DMT-19 Naming rules regarding use of verb or noun4/19       
 B2DMT-26 Reg Exp serialization in model should support multiple bindings        
 B2DMT-28 Instructions for entering RDF mappings   x   x
 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 content4/11 Tuesday     
 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?       x
 C2DMT-17 Documentation for OrderRelation, Relationships, properties needs improvement        
 C2DMT-32 Review the use of patterns in DDI to leverage RDF and provide design consistency4/13linked to patterns discussion (53)      
 C2DMT-53 Review use of design patterns4/11       
 C2DMT-57 Review documentation and intent for ClassificationItem and Code        

 

 

 

  • No labels