Science Environment for Ecological Knowledge
Ecoinformatics site parent site of Partnership for Biodiversity Informatics site parent site of SEEK - Home
Science Environment for Ecological Knowledge









 

 

 



All Hands Meeting 2005

Difference between version 89 and version 49:

Line 20 was replaced by line 20
- *** Taxon (Kennedy (TCS), Peet (ConceptMapper), Stewart (TOS))
+ *** Taxon (Kennedy)
Lines 33-34 were replaced by lines 33-34
- * 10:45 - 11:15 Synthesis Center demo at SDSC
- * 11:15 to 12:00 Data Integration as 2006 goal
+
+ * 10:45 - 12:00 Data Integration as 2006 goal
At line 39 added 3 lines.
+ ** Synthesis Center demo at SDSC, 30 minutes (see [http://syncenter.org])
+
+ * 1:00 pm - 5:30pm
Lines 48-50 were replaced by lines 51-54
- ** Taxon Breakout (Beach)
- *** Concept data discussion with NESCENT and CIPRES reps
- *** Any remaining sub-project updates
+ ** Taxon Breakout (Beach) [Taxon Breakout| AllHandsMeeting2005TaxonAgendaAndNotes]
+ *** Laura Downey, Going Forward Presentation from Estes Park
+ *** Xianhua Liu, Concept Mapping and authoring tool: review of prototype
+ *** Martin Graham, Collections visualization tool: review of prototype
Line 52 was replaced by lines 56-57
- * 7:00pm __Group Dinner__, Location TBD
+
+ * 7:00pm __Group Dinner__, Location: Rock Bottom
Lines 56-58 were replaced by lines 61-67
- ** [Kepler breakout| AllHandsMeeting2005KeplerAgenda]
- ** Taxon Breakout
- *** Kepler complete work flow discussion (see Franz, Liu, Peet, 29 Sept. doc)
+ * 8:30 am - 12:00 pm
+ ** 8:30 Joint Session
+ ** 9:30 [Kepler breakout| AllHandsMeeting2005KeplerAgenda]
+ ** 9:30 [Taxon Breakout| AllHandsMeeting2005TaxonAgendaAndNotes]
+ *** Taxon-Kepler Interaction Design and Engineering Discussion with Dan Higgins
+ **** Use case 1: GARP
+ **** Use case 2: Biodiversity
At line 60 added 2 lines.
+ ** SEEK-Taxon/CIPRES Project Lunch, Franz, Stewart, Gales with Miller, Jin, Lucie): Common ground
+ * 1:00 pm - 5:30 pm
Removed lines 62-64
- ** Taxon Breakout
- *** Extracting concepts from online sources (Susan, Aravind)
- *** Usability thread: bat project (Laura)
At line 65 added 6 lines.
+ ** [Taxon Breakout| AllHandsMeeting2005TaxonAgendaAndNotes]
+ *** Extracting taxonomic concepts from online taxonomic literature update (Susan Gauch, Aravind)
+ *** TOS Concept Data batch acquisition: roadblocks and options (All)
+ *** Status and review of Usability process:(Laura Downey powerpoint presentation)
+ *** Proposed May 2006 EOT Hands-On Workshop, Discussion, Deanna Pennington, Jim Beach
+
At line 67 added 1 line.
+ * 8:30 am - 12:00 pm
At line 91 added 4 lines.
+ **** Improving the Annotation Tool
+ ***** Filling in Annotations via ontology constraints
+ ***** Defining what makes a "good" annotation, and how to guide users towards these
+ ***** Improvements to the UI, including selecting ontologies and "templated" annotations
Line 97 was replaced by line 116
- ** Taxon Breakout
+ ** Taxon Breakout [Taxon Breakout| AllHandsMeeting2005TaxonAgendaAndNotes]
Lines 99-100 were replaced by line 118
- *** May 2006 Taxon-oriented SEEK workshop, NM (with Deana)
- *** Future Plans: events, objectives, deliverables
+ *** Uber-discussion: 2006-2007 Vision, objectives, deliverables, roadmap, events
At line 102 added 1 line.
+ * 1:00 pm - 5:30 pm
Lines 106-113 were replaced by lines 125-142
- * 10:30 - 10:45 __Break__
- ** Working exercise: data integration approaches
- *** Case study requirements for integration
- *** Simple "smart" concatenation
- *** Extending to more complex (and realistic) examples
- *** Adequacy of annotations and ontologies for integration
- *** Scalability of 'knowledge reasoning' approaches to data integration (e.g., incorporating instance data)
- **** Discuss possibility of the reasoner (e.g., Jena) developing an 'integration plan' that is implemented in another system (e.g., R) to avoid having to load instance data from multiple voluminous data sets (e.g., 3 100MB data files) into the reasoner itself (e.g., Jena)
+ *** Working exercise: data integration approaches
+ **** Case study requirements for integration
+ **** Simple "smart" concatenation
+ **** Extending to more complex (and realistic) examples
+ **** Adequacy of annotations and ontologies for integration
+ *** Data Management support for sms
+ **** The EML actor as entry point for data integration
+ **** How do we deal with multiple output formats from EML?
+ **** How do we deal with null values?
+ **** How do we carry out integration specifications given by sms?
+ ***** For example, using "R" to load instance data from multiple voluminous data sets (e.g., 3 100MB data files) and executing data integration "recipes"
+ ***** A database-style approach? (e.g., SQL)
+ *** What approach do we use for representing data conversions?
+ **** Examples: unit conversions, count/area = density, rescaling/projection
+ **** Represent conversions within ontology?
+ **** Represent conversions as actors (searched via annotations, e.g.)
+ **** Define a new or leverage an existing representation for conversions (Prolog, SWRL, XML syntax a la STMML, MoML attributes)
+ **** Use potpourri approach (i.e., try to accomodate multiple mechanisms)
Lines 115-116 were replaced by lines 144-145
- ** Taxon Breakout
- *** Bob Peet leaves; Less critical items
+ ** Taxon Breakout [Taxon Breakout| AllHandsMeeting2005TaxonAgendaAndNotes]
+ *** 1:00 PM Taxon meets SMS and KR 1 Hr. Bertram, Mark, et al.

Back to All Hands Meeting 2005, or to the Page History.