|
Difference between
version 67
and
version 66:
| At line 130 added 2 lines. |
| + *** Uber-discussion: next two year vision, deliverables, roadmap, engineering dependencies, end-user tasks to be supported, data acquisition for the prototypes, decomposing Kepler engineering steps to accomplish usage scenarios. How do all the SEEK-Taxon components fit together now? |
| + |
| At line 132 added 2 lines. |
| + *** Broader TDWG and community issues for TCS and TOS. What are their expectations? Our responsibilities? Can SEEK demonstrate the utility of TCS and TOS within the next year? What tools do we need to complete and harden for the community to buy into TCS and TOS? What can we expect from the GBIF community? Short term versus ultimate objectives. |
| + |
| Line 137 was replaced by line 141 |
| - *** May Tutorial Workshop Planning, Pennington for Romanello-Katz, Beach |
| + |
| Line 139 was replaced by line 143 |
| - *** Uber-discussion: next two year vision, deliverables, roadmap, engineering dependencies, end-user tasks to be supported, data acquisition for the prototypes, decomposing Kepler engineering steps to accomplish usage scenarios. How do all the SEEK-Taxon components fit together now? |
| + *** 4:00 May Tutorial Workshop Planning, Pennington for Romanello-Katz, Beach |
| At line 140 added 1 line. |
| + |
| Line 143 was replaced by lines 148-149 |
| - *** Broader TDWG and community issues for TCS and TOS. What are their expectations? Our responsibilities? Can SEEK demonstrate the utility of TCS and TOS within the next year? What tools do we need to complete and harden for the community to buy into TCS and TOS? What can we expect from the GBIF community? Short term versus ultimate objectives. |
| + |
| + |
Back to All Hands Meeting 2005,
or to the Page History.
|
