Talisman can potentially interact with other myGrid components. Some of the interactions are as follows (roughly ordered with the simplest / most likely to be implemented first, and the more speculative or longer term at the end).

1. Interaction with repository - Talisman should be able to store and access data in the repository, both in the sense of having a new field resolution type and resource in Talisman that would allow this access, and in the sense of storing provenance trails generated as Talisman applications run into the repository
2. Dynamic service lookup - it would be good if I didn't have to hard code service endpoints into my applications, so some interaction with a service (whether gateway or UDDI-foo) that allows this lookup to be done at runtime would be a good thing
3. Ontology and text minining services - Talisman can act as a client for these services, in exactly the same way as it currently does with our analysis services, databases etc
4. Notification - Talisman can potentially generate and accept notification events, this is likely to be particularly important in conjunction with ...
5. ...workflow enactment. Although Talisman contains a workflow engine itself, there are possibly reasons to use an external enactment service, should this be implemented the notification services will be required to provide the communications glue between the server side Talisman data structure and the workflow enactment service.
   Apparently the workflow people have already done this, woo More details to follow....
6. Talisman as a service itself - this is very much speculative, but it is in theory possible to expose Talisman's core engine as a web service, effectively allowing some level of web service access to every system with an appropriate Talisman bridge layer, currently this includes the ensembl data and arbitrary relational databases (amongst others).

-- TomOinn - 23 Jan 2003

• myGridInteractionscomplete.pdf: Diagram of possible Talisman - myGrid interactions