Bled Meeting Minutes
WP5 sessions (13 and 14 January 2009)
(Some conclusions and action points)
From M10 towards M14 release
- Deliver D5.2.1 (M10) – Waiting for updated version from Michael Witbrock.
- Finalize Baby LarKC release (ORDI, Description Language) –
- Vassil plan to finalize it in 2 weeks (27 Jan. 2009). He is in contact with Mick to integrate it in Baby LarKC. Vassil will present the results most probably in the next telco, 27.01.2009. AP: Vassil to organize small telco with the relevant people to discuss it.
- AP: Barry is in charge to include the description language in the current API - It will probably be a separate piece of documentation. He is currently tasked with creating a sample plug-in descriptions (WSMO-Lite) for WP1, that we can use in WP5 for integration with the baby larkc. In a later stage this will need to be integrated in the intelligent decider from Cyc (or any other intelligent decider). The API would not change, just the information in the plug in dscription and the reasoner within the decider plugin.
AP: Blaz (CycEur) integrate the plug-in description language in the current Cyc platform decider
Set-up new development environment (hosting LarKC code + LarKC Plug-ins + early adopters Plug-ins) & Procedure for Issue tracking – AP: HLRS to evaluate options proposed by Eyal and perform migration and establish issue tracking procedure. End Feb., latest. (28.02.2009)
Coding practices from Hamish => AP HLRS to consider it for the new infrastructure
Early Adopters Documentation (installation guidelines, user manual, …) – AP: CycEur. End Feb., latest (28.02.2009)
Testing the LarKC Early Adopters Tutorial, Milano: for internal adopters <= get feedback for the ESWC09 Workshop – 18.05.2009, morning.
Public Release, M14 (end May 09)
- LarKC Early Adopters Workshop (collocated with ESWC09) (June 09)
Hosting the prototype for public release and demos: discussion during STRB meeting. Buy a machine + Mainteinance (always alive!). Future solution: easy scalable, Amazon Cloud. Naso volunteer to buy a new machine. AP: HLRS check about the possibility to do it + maintain. Naso volunteered to buy machine in the STRB meeting.
Release Manager
Release manager=> Decide 1 person (in HLRS?) AP Georgina to check who in hlrs can be the release manager for managing the M14 release (platform + plugins + app data + …)
Demo for EC Review: integration with WP6 use case => support to WP6 use case. AP: Georgina in contact with Emanuele. Support in plug-ins wrapping, plug-ins identification and search. Telco Fri 23.01, 10 am. AP: Georgina send preliminary list of necessary steps to Emanuele (based on the discussion in Bled)
D5.3.1 Req analysis:
AP: CycEur send ToC + first content (based on Barry´s doc) by 27.01.2009 – Deliverable due M12 (end Feb/end March)
- Include Marvin lessons learned in this doc
D5.5.2 Validation Goals: AP: Ontotext send first draft by 27.01.2009
LarKC Architecture Definition, towards:
Distribution & Parallelization
Scalability
- AP: HLRS integrate the content presented (+feedback received) in Bled in the written document and circulate to the WP5 list. Include some initial thoughts about Marvin. Take some lessons from Marvin, applicable to the architecture in order to solve scalability issues.
- AP: HLRS organize a meeting for Architecture discussion, before end Feb. We should discuss there deliverable D5.3.1 + relevant architectural decisions towards distribution, scalability,… (AP: Georgina to propose date or setup a doodle with other possible dates)
- Marvin: Presentation from Eyal on Marvin architecture. Preliminary identification of LarKC components with Marvin components. It seems to be a good approach to start thinking on a scalable and distributed architecture. We need to analyse it more in detail and take the lessons learned for the definition of the LarKC architecture.
AP ID |
Description |
Responsible |
Date |
Status |
AP1 |
Integrate ORDI in Baby LarKC. Small telco with the relevant people to discuss it. |
Vassil (Ontotext) |
before 27 Jan. 2009 |
|
AP2 |
Include description language in the API definition / Baby LarKC (at least preliminary hints) |
Barry (UIBK) |
27 Jan. 2009 |
|
AP3 |
Set-up new development environment (hosting LarKC code + LarKC Plug-ins + early adopters Plug-ins) & Procedure for Issue tracking |
HLRS |
28.02.2009 |
|
AP4 |
Evaluate options proposed by Eyal wrt development environment (svn,...) |
HLRS |
28.02.2009 |
|
AP5 |
Early Adopters Documentation (installation guidelines, user manual, …) |
?CycEurope |
28.02.2009 |
|
AP6 |
Hosting the prototype for public release and demos. Check possibility to buy machine and have 1 person for mainteinance |
In parallel HLRS, Ontotext |
28.02.2009 |
|
AP7 |
check who whether somebody in hlrs can be the release manager for managing the M14 release (platform + plugins + app data + …) |
Georgina (HLRS) |
asap |
|
AP8 |
support demo wp6 use case for review. 1st support contact in Bled and telco with Emanuele |
Georgina (HLRS) |
23.01.2009 |
|
AP9 |
D5.3.1 Req analysis, first draft (ToC, initial content) |
27.01.2009 |
|
|
AP10 |
D5.5.2 Validation Goals (ToC, initial content) |
Ontotext |
27.01.2009 |
|
AP11 |
LarKC Architecture, integrate content presented + feedback from Bled in a document |
Georgina(HLRS) |
asap |
|
AP12 |
organize a meeting for Architecture discussion |
HLRS |
asap |
|
AP13 |
integrate the plug-in description language in the current Cyc platform decider |
Blaz (CycEur) |
mid. Feb. |
|
