| At line 91 added 8 lines. |
| + * Nico on Taxon / SMS |
| + ** partial overlaps |
| + ** give me the ants of south america ... give all concepts of ants (may be thousands) ... |
| + ** Deana: in biodiversity use case; want to group by function, which is similar to form |
| + *** Several international ones that are comprehensive in traits and functions |
| + *** Weren't sure the relevance to north america plants |
| + *** in KNB now, can do exactly the same search (via ITIS) ... through markup via EML |
| + ** rich: given two identifiers how are they similar |
| Line 95 was replaced by lines 103-116 |
| - ** |
| + ** schema mapping language ... what is taxon doing versus what is sms doing (for annotations) and how can each be informed by each other |
| + *** for taxon, mapping into exchange schema ... trying to determine how concepts are represented within a database |
| + *** for sms, mapping into ontology |
| + ** more examples for annotation |
| + *** deana possible small kr/sms working group to identify useful items to annotation (workflow and data) and map to Rich's ontologies |
| + ** interface for annotation ... filtering Rich's ontology ... to form-style interface for annotation (Laura, Jessie, and Deana) |
| + ** graph-based ontology queries for filtering and selecting ontology (Serguei, GrOWL) |
| + ** SMS/Taxon link-up points |
| + *** compare mapping languages |
| + *** data discovery queries w/ taxon |
| + *** similarity between ids |
| + *** operations that sms needs ... taxon ops that sms needs |
| + *** how does sms know when to call a taxon service? e.g., via which concepts in the rich's ontology? |
| + ** sparrow to owl; owl to sparrow |
| At line 96 added 1 line. |
| + * Next steps (...) |
