Plans for WP5 in the M6-M10 period
(this is after the Stuttgart plenary meeting, and leading up to the internal release of the platform).
Note on M12 release: According to the DoW the Rapid prototype deliverable (D5.2.1) is due M10 (end Jan.09). We must have this in mind when doing the planning.
Cyc: remove proprietary code, work on thread-safety, migrate current DECIDEr to V0.2 API
Innsbruck:
- complete current API
- integrate ORDI as data-layer API
- test previous item by moving to another demo-scenario,
- using a larger dataset (to be provided by Amsterdam)
Stuttgart: set up issue tracking system, and fill with current issues (from earlier WP5 meetings and from the Stuttgart-consultation sessions)
Later: write a number of example "stub"-plugins that enable remote invocation (as web-service, as HTTP, other?). This is probably our quickest-win scenario to get remote execution going before the M12-M14 release
Later: design declarative representation for pipeline configurations
Later: start a "discussion thread" on the general LarKC architecture (besides the early prototype architecture), considering the remote issues and others that we plan to have in a longer term. Currently we are finalizing our "remote issues" contribution to the D1.2.1, that can be a starting point for that discussion.