[kepler-dev] [Bug 1750] New: - development of a (remote) Kepler repository
bugzilla-daemon at ecoinformatics.org
Wed Oct 27 06:42:28 PDT 2004
Summary: development of a (remote) Kepler repository
AssignedTo: berkley at nceas.ucsb.edu
ReportedBy: ludaesch at sdsc.edu
QAContact: kepler-dev at ecoinformatics.org
The issue of a remote Kepler actor (and workflow) repository has come up every
now and then. It would serve multiple purposes:
- as an actor and service registry for discovery, similar to a UDDI registry for
web services (only better ;-)
- to avoid loading each and every actor when installing Kepler: actors could be
discovered dynamically (with an expanded actor search function), their
interfaces could be loaded into the local users view (so actor signatures become
visible); eventually for "local actors" their code would be loaded from the
remote repository and plugged into the user's local installation.
Note that some actors will require jars from the repository to be downloaded and
plugged-in, while others, most notably WS actors only required to download and
plug-in the interface or a thin "interpreter layer"
- as a community repository for common tasks (semantic annotations for actor and
workflow classification become very important)
A related issue is that of a browsable and searchable data repository.
More information about the Kepler-dev