|
Difference between
version 66
and
version 65:
| Removed lines 91-93 |
| - *** 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? |
| - |
| - |
| Removed line 95 |
| - *** 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 101 was replaced by lines 97-98 |
| - **** Kepler work flow scenario: |
| + **** Kepler work flow scenario: Kepler has Actors that can actually merge the data, need some user interaction with TOS to decide which level of lumping the user wants, include synonyms, concept overlaps, go up a level, etc. |
| + |
| At line 102 added 1 line. |
| + |
| Line 105 was replaced by line 103 |
| - ***** if concepts match in TOS |
| + ***** if concepts match in TOS (other TOS operations) |
| At line 140 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 142 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. |
| + |
Back to All Hands Meeting 2005,
or to the Page History.
|
