| Line 5 was replaced by lines 5-10 |
| - Possible collaboration point: reasoning over functional attribute database |
| + ! Misc Thoughts |
| + * How associate growing body of functional/trait attributes with taxonomic information? |
| + ** Possible collaboration point: reasoning over functional attribute database |
| + * Semantic mediator will call TOS |
| + * For a more automated workflow approach - maybe associate taxonType[] as output port for dataset actor and input port for analysis actor |
| + * Weighted output from TCS is an issue—how use in Kepler? |
| Line 7 was replaced by lines 12-13 |
| - Semantic mediator will call TOS |
| + ! SMS focusing on following scenario: |
| + SMS WILL construct for a given (number of) dataset(s) the best set of information (limited/query concepts; as “complete a filled-in concept as possible”)) to feed to the TCS (binomial, year, location, e.g.)—and a specification of the grain to which you want these resolved (default to finest grain?). TCS then returns (a potentially integrated or presentation of possible integration options) of these two lists of concepts. Aimee says that Taxon is aware of this, but hasn't gotten to it yet, as it is the hardest/most complex function (and builds on the others). |
| Removed lines 9-17 |
| - EML |
| - * Maintain GUIDs in metadata or resolve dynamically |
| - ** Could bind resolution if done by original data collector/author |
| - ** Third party resolution results could improve over time until TOS cache is somewhat stable. |
| - ** Who is responsible for the association if not maintained in EML? |
| - |
| - SMS focusing on following scenario: |
| - SMS WILL construct for a given (number of) dataset(s) the best set of information (limited/query concepts; as “complete a filled-in concept as possible”)) to feed to the TCS (binomial, year, location, e.g.)—and a specification of the grain to which you want these resolved (default to finest grain?). TCS then returns (a potentially integrated or presentation of possible integration options) of these two lists of concepts. Aimee says that Taxon is aware of this, but hasn't gotten to it yet, as it is the hardest/most complex function (and builds on the others). |
| - |
| Line 20 was replaced by line 17 |
| - * Resolve names for each list |
| + * Resolve names for each li* st |
| Lines 28-30 were replaced by lines 25-29 |
| - |
| - |
| - For a more automated workflow approach - maybe associate taxonType[] as output port for dataset actor and input port for analysis actor |
| + EML |
| + * Maintain GUIDs in metadata or resolve dynamically? |
| + ** Could bind resolution if done by original data collector/author |
| + ** Third party resolution results could improve over time until TOS cache is somewhat stable. |
| + ** Who is responsible for the association if not maintained in EML? |
