[kepler-dev] RE: [seek-dev] scope, design of the Ecogrid registry vs Kepler registry
bzhu at sdsc.edu
Wed Oct 13 16:17:57 PDT 2004
Here is the link for Matt's design document for Ecogrid registry.
which has links to our original design docs in Ecogrid meeting in Seattle.
The current Ecogrid registry schema is
From: seek-dev-admin at ecoinformatics.org
[mailto:seek-dev-admin at ecoinformatics.org]On Behalf Of Bertram Ludaescher
Sent: Wednesday, October 13, 2004 3:55 PM
To: Matt Jones; Bing Zhu; Jing Tao; Rod Spears
Cc: seek-dev at ecoinformatics.org; kepler-dev at ecoinformatics.org
Subject: [seek-dev] scope, design of the Ecogrid registry vs Kepler registry
Matt et al:
Another topic that came up in todays meeting was the EcoGrid
registry. Bing is working on an XML Schema for the registry schema.
I also found some other documentation, e.g. here:
Here are my questions:
1. Are additional design docs available?
2. What is the planned functionality, scope, and schema of this
registry, and last not least
3. How does it relate to the planned Kepler actor repository that we
have been talking about recently? (aka load an actor from a remote
repository kind of stuff...)
It seems that a Kepler actor repository might very well subsume the
Ecogrid registry, since instantiated web service actors would have all
the info that the Ecogrid service registry has and probably more
(e.g., semantic annotations)
Overall it seems that at least the following issues need to be addressed:
(a) schema definition f the repository (e.g., need to store WSDLs,
Kepler actor jars, semantic annotations etc. in the case of the Kepler
(b) repository access functions: how to register stuff into the
repository, how to update and delete from the repository, and how to
query and get it out?
Part (a) sounds like a SMODD (simple matter of database design ;-) ...
Are there any repository standards that we could use?
seek-dev mailing list
seek-dev at ecoinformatics.org
More information about the Kepler-dev