| Line 24 was replaced by line 24 |
| - *** Bertram brought up that a design tool might also be nice (DBDesigner4) |
| + *** Bertram brought up that a design tool might also be nice ([DBDesigner4|http://www.fabforce.net/dbdesigner4/screenshots.php]) |
| At line 35 added 1 line. |
| + **** Matt will contact Deana about environmental data |
| Lines 38-39 were replaced by lines 39-45 |
| - ** Java API to sparrow status |
| - ** Design and implementation in Kepler status |
| + ** Chad implemented search interface for the actors, pluggable to accomodate new ontology search interface |
| + ** Chad will contact Shawn about further development on this, in particular |
| + *** need mechanism for semantic registration for MoML |
| + *** need access to sparrow API via Java |
| + *** Chad still working on trimming the result tree to exclude all non-matched items and categories |
| + **** Wants to implement the double-window view to compare effectiveness |
| + ** Chad estimates that Oct 15 delivery date is possible (he's going on vacation for a week though) |
| At line 42 added 13 lines. |
| + ** Matt: need ability to archive data products with their structural and provenance metadata |
| + *** Bertram: do we have one systematic way to store metadata about execution (execution trace) that includes parameter settings, versions of services, etc. |
| + **** Assumes notion of global ID's for services and data objects |
| + ** Matt: also need ability to save workflows themselves in Grid environment, for sharing and collaboration |
| + *** Then users can search and find components others create, including web services and other services that are Grid-available |
| + ** Ilkay: 'Blue-box' recorder (parallel to director) that decides what needs to be recorded and archived |
| + ** Bertram: maybe short-term is to get actor to write back to EcoGrid nodes and can be incorporated into workflow |
| + *** Ilkay says the web service harvester may be incorporated by Oct 15 to allow finding remote services -- possibly with help from Bing and/or Efrat |
| + *** Ilkay also says we should trim the tree for the release to only include stable stuff |
| + |
| + 5. Kepler hackathon -- should we have another |
| + ** Ilkay says it was useful. Would like another. But we had a hard time finding an available time. The week of Oct 11-15 might be possible, but it is right between 4 other weeks of meetings, and is probably too close to our intended Oct 15 release date. We also have the SEEK meeting as a possible planning meeting in the first week of November. Maybe we could ask more Kepler people to come to at least a portion of that? |
| + ** Matt and Bertram will follow through on whether the SEEK meeting is the right place for the next Kepler planning meeting |
