SIMILE Research Drivers

(AKA Use case document - The title of the document and the title of the web
page are different.)

--------

3.4 Distributed Resources

It would be useful to add the distribution issues between client and a
federation of SIMILE systems.  The way a client interacts (i.e. use cases)
with SIMILE can be different from how one SIMILE system interacts with
another, whether they use the same technical mechanisms or not.  I can think
of three modes:

1/ Interactions from client to SIMILE system
2/ Interactions with "the system" of the form SIMILE installation at one
institution with a SIMILE installation at one institution
3/ Interactions between machines making the SIMILE installation at one
institution.

On the semantic web, the client is programmatically accessing SIMILE, or by
web page, so issues of client-side caching, change notification arise, as do
security, and, potentially, charging and SLAs.

--------

SIMILE and the Semantic Web

The Semantic Web isn't a number of closed worlds so information from SIMILE
will be reused by other systems, whether portals, client-end applications or
something else.  The current document covers this.  The other way round is
also interesting - how does SIMILE use semantic web information from
elsewhere?  Library information can be ingested but what about dynamic
information?

Examples: schedules related to course material. Other papers in the same
track or same session at a conference.

This could be considered the role of the SIMILE client to do such
integration or it could be made possible as part of the service architcture
within SIMILE.

SIMILE could choose just to be a "leaf node" in the semantic web - providing
information but not consuming it from other semantic web sources.  This
would still be valueable and should be the focus of initial demonstrators
but in the long term it limits the ability to evolve as the way we use
infromation changes.


	Andy

Received on Friday, 4 April 2003 08:53:20 UTC