| Lines 43-45 were replaced by lines 43-45 |
| - *** Extracting concepts from online and monographic sources, just mammals?, (Susan, Aravind) |
| - **** Currently: 1600 PDF documents obtained, 100 are bat taxonomy papers, extracting data next |
| - **** Desired: extract parent-child hierarchies, descriptions, synonyms, |
| + * Extracting concepts from online and monographic sources, just mammals?, (Susan, Aravind) |
| + ** Currently: 1600 PDF documents obtained, 100 are bat taxonomy papers, extracting data next |
| + ** Desired: extract parent-child hierarchies, descriptions, synonyms, |
| Line 47 was replaced by line 47 |
| - *** TOS Data acquisition roadblocks, process, role of software tools, getting data into TOS with an import tool for usability testers. |
| + * TOS Data acquisition roadblocks, process, role of software tools, getting data into TOS with an import tool for usability testers. |
| Line 49 was replaced by line 49 |
| - **** Currently: ITIS ("relational" concepts), Bats from MSW 2005 (MSW concepts from original pubs and synonyms without bib references), MSW 1993, FNA in TCS, German Mosses (concepts with concept maps), |
| + ** Currently: ITIS ("relational" concepts), Bats from MSW 2005 (MSW concepts from original pubs and synonyms without bib references), MSW 1993, FNA in TCS, German Mosses (concepts with concept maps), |
| Line 51 was replaced by line 51 |
| - **** Requirements: TOS Actor could be tested with plant data, |
| + ** Requirements: TOS Actor could be tested with plant data, |
| Line 53 was replaced by line 53 |
| - **** Possible: Use Bob Peet's plant concept data (44,000 with relationships?)with PLANTS county level distribution data as a supplement to bat use case scenario, Ranunculus data set, 8 classifications, NA & Mexico. |
| + ** Possible: Use Bob Peet's plant concept data (44,000 with relationships?)with PLANTS county level distribution data as a supplement to bat use case scenario, Ranunculus data set, 8 classifications, NA & Mexico. |
| Line 55 was replaced by line 55 |
| - **** Action: Stinger Guala to identify in 2 weeks the number of versions of PLANTS, send to KU to DiGIRize, Bob will send rich treatement of plant concepts the US Southeast. Available now: Ranunculus data, it needs to be upgraded to latest TCS, Xianhua will do that in 1 week. Jan or Feb: All USDA Plants in version 4, mapped against all plants in FNA, and also all of the Alan Weekly collaboration, his version mapped against 8 different classifications of plants. |
| + ** Action: Stinger Guala to identify in 2 weeks the number of versions of PLANTS, send to KU to DiGIRize, Bob will send rich treatement of plant concepts the US Southeast. Available now: Ranunculus data, it needs to be upgraded to latest TCS, Xianhua will do that in 1 week. Jan or Feb: All USDA Plants in version 4, mapped against all plants in FNA, and also all of the Alan Weekly collaboration, his version mapped against 8 different classifications of plants. |
| Line 57 was replaced by line 57 |
| - *** 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 |
| + * 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 |
| Lines 59-64 were replaced by lines 59-64 |
| - **** S-T TOS/TCS External Roles/Personas |
| - ***** S-T might be a concept provider for other people to test their concept applications, |
| - ***** S-T might be a concept repository for projects looking for a place to store them, might need a batch import process if requested. |
| - ***** S-T *must* use GUIDs because there will be multiple concept object servers |
| - ***** S-T if TOS is a global reference implementation, then we need to implement the whole TCS schema in TOS, we could not implement just some TCS fields, we would need to input and output 100% standard TCS documents. |
| - ***** Schema changes over time, do we need to maintain records in each version forever? |
| + ** S-T TOS/TCS External Roles/Personas |
| + *** S-T might be a concept provider for other people to test their concept applications, |
| + *** S-T might be a concept repository for projects looking for a place to store them, might need a batch import process if requested. |
| + *** S-T *must* use GUIDs because there will be multiple concept object servers |
| + *** S-T if TOS is a global reference implementation, then we need to implement the whole TCS schema in TOS, we could not implement just some TCS fields, we would need to input and output 100% standard TCS documents. |
| + *** Schema changes over time, do we need to maintain records in each version forever? |
| Lines 67-68 were replaced by lines 67-68 |
| - **** S-T TOS/TCS Internal Roles/Personas |
| - ***** See SEEK use cases 1 & 2 and other related logic |
| + *** S-T TOS/TCS Internal Roles/Personas |
| + *** See SEEK use cases 1 & 2 and other related logic |
| Line 72 was replaced by line 72 |
| - *** Status and review of Usability process:(Laura Downey with status powrpoint slides) |
| + * Status and review of Usability process:(Laura Downey with status powerpoint slides) |
| Line 76 was replaced by line 76 |
| - *** 4:00 May Tutorial Workshop Planning, Pennington for Romanello-Katz, Beach |
| + * May 2006 EOT Workshop Planning (Pennington, Beach) |
| At line 83 added 2 lines. |
| + |
| + |
