Jul 08 2009
Last week we had for the second time our KiWi meeting in Prague at the Sun Microsystems offices – almost a tradition by now.:-) The main goals of the meeting were to kick off the implementation of the enabling technologies and the integration and implementation in the use cases. Also, for the first time, we organized the meeting as an “open space” without long Powerpoint presentation but instead with long and lively discussions.
KiWi Core System and Collaboration with INSEMTIVES
On Thursday morning, we started with a general presentation of the current state of the KiWi system, mainly showing the demonstration given in Heraklion at ESWC09 (which won us the ESWC Best Demo Award) and in Luxemburg at the KiWi Review. Furthermore, Marek showed the prototype for information extraction and annotation, and Klara a prototypical visual editor for her rule-based query language.
Besides the KiWi core system, Tobias Bürger from STI Innsbruck presented the ideas behind the FP7 INSEMTIVES project to the KiWi consortium as a first step towards collaboration between INSEMTIVES and KiWi (he also blogged about it). We see possibilities for collaboration at several levels: dissemination (i.e. joint organisation of events, joint publications), research (INSEMTIVES results could improve Community Equity) and technology (KiWi platform could be used in INSEMTIVES). We will further investigate a possible collaboration at the INSEMTIVES meeting in Innsbruck next week, where we are invited to present KiWi in turn.
On Thursday afternoon, we took a look at the four KiWi enabling technologies and how they integrate with the rest of the KiWi system. Jakub started with presenting ideas for a rule-based language capable of reasoning over tags and RDF structures (after Klara already presented her work in the morning). We had a lively discussion on the different aspects of the rule languages, how they might be unified and fit together, and how they might serve the other parts of the KiWi system. We decided that what we would need as a first step would be a simple rule-language with forward chaining based on RDF, on top of which more complex ideas would be evaluated.
Next came a discussion on information extraction, based on what Marek presented in the morning. It was agreed that information extraction would be used (1) in the editor to support the user in semi-automatic annotation, and (2) in the importing functionality to automatically extract metadata and perform annotations. The information extraction component works by incremental training with positive and negative examples.
We concluded the afternoon session with a discussion on personalisation. Personalisation in KiWi means primarily recommendations, and secondarily user interface customisation. Peter introduced us into the multifactor recommendation algorithm the group in Aalboarg has been working on in the last year, and we discussed the different factors that might be used, including Sun’s Community Equity. We also discussed where recommendations might be useful.
Logica Use Case
Friday morning started with a presentation of the current state of the Logica use case by Karsten. Karsten introduced into a “formalisation cycle” that moved from collaboratively created unstructured text in the KiWi system to structured data in the Logica Risk Management system and from there back to unstructured text in KiWi. What is currently already implemented is the export from the Logica system to KiWi using a custom templating mechanism. We discussed that we should try to replace this templating mechanism by RDFa only and that we should also investigate RDFa for forms (e.g. RDForms). The connection between unstructured text and forms will then be realised using the RDFa annotation mechanism implemented by Marek.
SunSpace Use Case
The second half of Friday was dedicated to discussing the Sun Use Case, and the technologies and services we would need to integrate there to support the already existing SunSpace intranet. We agreed that it was unreasonable and unrealistic to expect that Sun would replace the existing Confluence installation in favor of KiWi, because the aim of KiWi cannot be to create yet another Wiki engine that competes with what is already there. Instead, in the SunSpace use case, the KiWi system will be more like an intelligent index that integrates content and data from already existing sources and offers additional value in the form of advanced services (e.g. search, tagging, …) and widgets that can be included on the user interface level (e.g. recommendations, tagging, metadata, …). The data integration will make use of existing technologies like Linked (Open) Data. We decided that we would contribute particularly to the update mechanism of Linked Data since this seems to be an issue that is yet not resolved.
A second major point of discussion was the integration of Sun’s Community Equity (CE) with KiWi. We decided that we would head for a rather tight integration at the EJB level rather than at the Web Service level, because then we will be able to use CE more easily for e.g. recommendation and search. This integration will take place until end of August.
Finally, we briefly discussed single sign on for KiWi and correspondingly, Henry‘s suggestion for FOAF+SSL, which Steffi has already mostly implemented in KiWi. Also, an issue still to be solved for the SunSpace Use Case is how to handle permission management in KiWi.
We closed the meeting on Friday afternoon. Most said it was the most productive KiWi meeting we had yet and that we have moved much forward. I just hope that we can also hold the pace.:-)
Note: I will upload figures and pictures as soon as I have them.
One response so far