- Nov 27, 2008
Content Versatility in the KiWi Core System
It’s been five months since the last Joint Work Package (WP) meeting in the KiWi – Knowledge in a Wiki – project. This morning, we gathered in Vienna for the next round – focus this time around will be on the core system (architecture developed by the WP3 team, handing over and paving the way for WP 4 team) and the use cases (Logica, Sun Microsystems) where it is of particular importance that everyone involved in the project understands the requirements of the use cases.
Using a different skin and interface, KiWi can take various forms and shapes – even shapes where you might not spot the wiki in it at first glance. TagIT is such an example of an adaptation of the KiWi core system: a geotagging platform targeting youth in Salzburg who can locate, tag and comment on places that matter to them.
Vice versa, KiWi in its wiki incarnation displays a little map, provided a content item is enhanced with geoinformation; technically, the map on the wiki page is an interpretation of a georelated tag (learn more about complex, structured tags proposed by the KiWi Enabling Technologies Work Package in this article: Usage Data Model Day in the KiWi Project).
Take a look at the screenshots below:
It is the same article that is being displayed, in the first example using the classic KiWi interface, in the second example using the TagIT interface with the article appearing as an info page.
This afternoon, we expect to see another configuration of the system, in a presentation about how the system is specifically tailored to the needs of Logica’s “Knowledge Management for Project Management” usecase.
N.B. The system is not yet publicly available, if you have questions, please contact Sebastian Schaffert.