| Line 5 was replaced by line 5 |
| - ! Misc Thoughts |
| + !Misc Thoughts/Facts |
| Lines 7-8 were replaced by lines 7-9 |
| - ** Possible collaboration point: reasoning over functional attribute database |
| - * Semantic mediator will call TOS |
| + ** Associate with GUIDs, names, other concept attributes? or associate dynamically? |
| + ** __Possible collaboration point: reasoning over functional attribute database__ |
| + * Semantic mediator will call TOS (Taxonomic Object Service) |
| At line 10 added 5 lines. |
| + * Current TOS demo/SOAP service is not working because it is being upgraded. This should be up again soon. Even simple service will help identify issues to be addressed. |
| + * Split or lump to common resolution |
| + ** must define resolutions |
| + ** rank vs set operations |
| + ** original concepts vs third party relationship assertions |
| Line 12 was replaced by line 18 |
| - ! SMS focusing on following scenario: |
| + !SMS focusing on following scenario: |
| Lines 25-26 were replaced by lines 31-33 |
| - EML |
| - * Maintain GUIDs in metadata or resolve dynamically? |
| + !Relation with EML Taxonomic coverage |
| + * how capture results, esp if these required human intervention |
| + * is TCS resolution going to be associated with EML as semantic annotation or resolve dynamically? |
| Line 31 was replaced by line 38 |
| - Additions/Modifications to TOS: |
| + !Additions/Modifications to TOS: |
| Removed line 46 |
| - * Relation with EML Taxonomic coverage: if binomial, and launch TCS search, how capture results, especially if these required human intervention; is TCS resolution going to be associated with EML as semantic annotation. |
| Line 48 was replaced by line 54 |
| - SMS tasks: |
| + !SMS tasks: |
