Work Plan in Detail - IKS

Interactive Knowledge Stack for small 

to medium CMS/KMS providers 

By Trenz Pruca 

Malesuada quis, egestas quis, 

wisi. Donec ac sapien. Ut orci. 

Duis ultricies, metus a feugiat 

porttitor, dolor mauris convallis 

est, quis mattis lacus ligula eu 

augue. Sed facilisis. Morbi lorem 

mi, tristique vitae, sodales eget, 

hendrerit sed, erat lorem ipsum. 

Vestibulum eget purus vitae 

eros ornare adipiscing. Vivamus 

nec quam. Integer vestibulum 

malesuada libero. Sed vehicula 

fermentum leo. In condimentum. 

Nullam wisi arcu, suscipit consectetuer. 

Vestibulum imperdiet 

nonummy sem. Vivamus sit amet 

erat nec turpis tempus consequat. 

Praesent malesuada. Donec 

vitae dolor. Donec at lacus ac mi 

vehicula bibendum. Donec 

feugiat tempor libero Aenean ut 

erat ut nibh commodo suscipit. 

Nam uut, massa. Maecenas vitae 

ante et lacus aliquam hendrerit. 

Curabitur nunc eros, euismod 

in, convallis at, vehicula sed 

consectetuer posuere, eros 

mauris dignissim diam, pretium 

sed pede suscipit: Adiam condimentum 

purus, in consectetuer 

Proin in sapien. 

Fusce urna magna,neque 

eget lacus. Maecenas felis nunc, 

aliquam ac, consequat vitae, 

feugiat at, blandit vitae, euismod 

vel, nunc. Aenean ut erat ut nibh 

commodo suscipit. Maecenas 

metus non quam. 

Cras erat. Aliquam pede. 

vulputate eu, estmorbi tristique 

senectus et netus et male. Aliquam 

pede. Proin neque est, 

sagittis at, semper vitae, tincidunt 

quis Malesuada quis, egestas 

quis, wisi. Donec ac sapien. 

Ut orci. Duis ultricies, metus a 

feugiat porttitor, dolor mauris 

ligula eu augue. Sed facilisis. 

Morbi lorem mi, tristique vitae, 

sodales eget, hendrerit sed, 

erat.. 

Vestibulum usce urna magna,neque 

eget lacus. Maecenas 

felis nunc, aliquam ac, consequat 

vitae, feugiat at, blandit vitae, 

euismod vel, nunc. Aenean ut 


Maecenas metus non quam. 

Nam uut, massa. Maecenas 

vitae ante et lacus aliquam 

hendrerit. Aenean ut erat ut 

nibh commodo suscipit. Curabitur 

nunc eros, euismod in, convallis 

at, vehicula sed consectetuer 

posuere. 


wisi. Donec ac sapien. Ut orci. 

Duis ultricies, metus a feugiat 




mi, tristique vitae, sodales eget, 


Step up to the Challenge 

Join IKS, an open source project to 

bring semantic technologies to 

CMS platforms convallis est, quis mattis lacus 

1 

The IKS Thesis & Approach 

Contents 

Executive Summary 

Interactive Knowledge (IKS) is 

an integrating project whose 

target are the hundreds of 

SMEs in Europe providing 

technology platforms for 

content and knowledge management 

to thousands of end 

user organisations... 

2 

Main Innovations 

In order to support the transition 

to a truly knowledge 

based economy, we must 

move our current support 

technology from a contentbased 

technology to a 

semantics-capable 

technology... 

4 

Success Indicators 

We describe the following 

five critical success factors 

and give success and failure 

conditions: IKS Technology 

Stack, Interaction with 

knowledge at the user level. 

Raising the technological 

capabilities of CMS CMS provid- provid- provid- 

6 

ers. Raising the value of 

interactive knowledge in in the 

perception of the user... 

Implementation Plan 

Interactive Knowledge has a 

duration of 48 months; and a 

budget of 8,5 M€ with 5,6 M€ 

requested funding. The project 

is organised in 10 Work 

Packages and uses an effort 

of 750 person months. It 

expects to leverage leverage another 

9 

200 person-months in 

open source development... 

development...9 

development...

Executive Summary 

Interactive Knowledge (IKS) is an integrating project whose target 

are the hundreds of SMEs in Europe providing technology 

platforms for content and knowledge management to thousands 

of end user organisations. 

Downstream, hundred-thousands of corporate end users and 

millions of content consumers are affected by the quality of 

service provided through these platforms. The majority of these 

platforms is built under the "Linux/Apache/mySQL/php" paradigm 

known as the LAMP stack. More advanced CMS platforms 

are provided by firms with a software engineering background 

using frameworks such as .NET and JEE5. All of these frame- 

works lack the capability for semantic web enabled, intelligent content, and therefore lack the capacity 

for users to interact with the content at the user's knowledge level 

Interactive Knowledge will close the ... 

• … engineering gap for CMS architectures: the Interactive Knowledge Technology Stack 

will enable many open source CMS frameworks to become semantically enabled 

• … research gap on user interaction with knowledge objects: the use of semantics to 

support direct user interaction with knowledge content will be a focus of Interactive 

Knowledge 

• … research gap on empirical validation: we involve a group of six technology providers 

and further 50 smaller CMS/KMS providers for controlled engineering experiments to ensure 

quantitative analysis of requirements and of subsequent technology validation for 

semantically enabled, interactive knowledge and content management systems. 

• ... impact gap for industrial take-up: starting with six industrial partners in the consortium, 

we will recruit 50 more European CMS/KMS providers and activate a dozen relevant 

open source communities to embrace IKS specifications, and be present in standards bodies 

(W3C,OASIS, etc). 

INTERACTIVE KNOWLEDGE invites all stakeholders to work towards bringing European CMS/KMS providers 

to the leading edge of innovation in knowledge technologies, for the benefit of all users. 

...and the winners are Zemanta 

...the community at work 

2 

...IKS leaders emerge

Main Concepts 

aoreet nec interdum 


The Problem - poor Malesuada technology quis, egestas breeds quis, poor solutions felis nunc, aliquam - poor ac, solutions consequat breed poor productivity. 

wisi. Donec ac sapien. Ut orci. vitae, feugiat at, blandit vitae, 

There are several hundred CMS and KMS provider SMEs in Europe, and most of them are currently not 

Duis ultricies, metus a feugiat euismod vel, nunc. Aenean ut 

able to leverage semantics-based porttitor, dolor mauris technology convallis for erat use ut in nibh their commodo systems. suscipit. This has negative impact 

downstream, on thousands est, quis mattis of end lacus user ligula organisations eu Maecenas which metus are non served quam. by these providers, and ultimately, 

tens or hundreds augue. Sed of facilisis. thousands Morbi of lorem knowledge Nam workers uut, massa. in the Maecenas downstream organisations are 

prevented from leveraging 

mi, tristique 

their 

vitae, 

skills. 

sodales 

The 

eget, 

poor 

vitae 

technology 

ante et lacus 

base 

aliquam 

of CMS/KMS providers is a major in- 

hendrerit sed, erat lorem ipsum. hendrerit. Aenean ut erat ut 

hibitor of progress and innovation, world-wide. 

Vestibulum eget purus vitae nibh commodo suscipit. Curabi- 

Interactive Knowledge eros is ornare an integrating adipiscing. Vivamus project with tur nunc impact eros, on euismod content in, con- and knowledge management 

technology providers nec in quam. Europe. Integer In vestibulum the area of intelligent vallis at, vehicula content sed we consecte- identified four fundamental gaps 

malesuada libero. Sed vehicula tuer posuere. 

that so far, appear to have been neglected by stakeholders and which lie at the heart of the above 


productivity problem: Nullam wisi arcu, suscipit con- Malesuada quis, egestas quis, 

• the engineering sectetuer. gap w.r.t. Vestibulum architectures: imperdiet Semantic wisi. Donec Web research ac sapien. has Ut been orci. moving into academic speciali- 

nonummy sem. Vivamus sit amet Duis ultricies, metus a feugiat 

sation and the research community has been neglecting that industry needs coherent architectures to fit 

erat nec turpis tempus conse- porttitor, dolor mauris convallis 

into existing technology landscapes, and that it needs development and migration paths from "traditional" 

quat. Praesent malesuada. Donec est, quis mattis lacus ligula eu 

to semantics-enabled technologies - Interactive Knowledge addresses this problem by its "Semantic CMS 

vitae dolor. Donec at lacus ac mi augue. Sed facilisis. Morbi lorem 

Technology Stack", which will demonstrate migration paths from the current "Linux/Apache/mySQL/php" 

vehicula bibendum. Donec mi, tristique vitae, sodales eget, 

paradigm (known feugiat as the tempor LAMP libero stack) Aenean to a framework ut hendrerit which sed, is erat compatible lorem ipsum. with developments in the semantic 

web research erat communities. ut nibh commodo There suscipit. are significant research challenges in understanding "The Stack" and 

its layers. Nam uut, massa. Maecenas vitae 






• the research gap sed pede w.r.t. suscipit: user interaction Adiam condi- with knowledge objects: Semantic Web research has several important 

strands mentum of investigation: purus, in consectetuer 

ontology languages such as OWL; the representation of processes; the use 

of rules in ontologies; Proin in sapien. semantic web services; reasoning engines; large-scale knowledge bases, and ad- 


vanced query languages such as SPARQL. Recently, a lot of interest has shifted to social computing and 


semantic technologies. What remains poorly understood, however, is the adequate representation of se- 


mantics in the user interface, so that the user can interact with the "knowledge" directly! This is where In- 


teractive Knowledge 

vel, nunc. 

is 

Aenean 

addressing 

ut erat 

a 

ut 

major 

nibh 

gap which requires also a thorough understanding of the existing 

work in semantic commodo technologies. 

suscipit. Maecenas 

• the research gap metus w.r.t. non to quam. empirical validation: Interactive Knowledge involves a core group of six tech- 


nology providers and an extended group of up to 50 smaller CMS/KMS providers and engages them in 


controlled engineering experiments to understand which semantics-based approaches will work and what 

senectus et netus et male. Ali- 

will not work, and on what time-scales. This way, we ensure valid substantiations of our claims. 

quam pede. Proin neque est, 

• the impact gap sagittis w.r.t. at, industrial semper vitae, take-up: tin- Knowledge technologies have simply not arrived yet, in mainstream 

content cidunt and knowledge quis Malesuada management quis, eges- - Many European technology providers are SMEs and even the 

advanced media tas management quis, wisi. Donec providers ac sapien. have not yet, even understood the potential of relatively simple 

semantic web technology, Ut orci. Duis such ultricies, as the metus use a of RDF! Interactive Knowledge will involve up to 50 European 


CMS and KMS providers bringing knowledge technologies to them. It will activate a dozen open source 

convallis est, quis mattis lacus 

communities which have stakes in related fields such as intelligent lay-outing and semantics-enabled stor- 


age solutions for content. Interactive Knowledge will also be present in standards bodies such as W3C and 

Morbi lorem mi, tristique vitae, 

OASIS to ensure 

sodales 

a balance 

eget, 

between 

hendrerit 

industrial 

sed, 

effectiveness and conceptual soundness of CMS and KMS related 

standardisation. 

erat.. 



3


In order to support the transition to a 

truly knowledge based economy, we 

must move our current support technology 

from a content-based technology 

to a semantics-capable technology, 

and we must do so not just for the big 

players, but we must convince European 

SMEs that this is a worthwhile journey 

to take. This is expressed in the mission 

statement: 

Interactive Knowledge creates a 

technology platform for semantically 

enabled content and knowledge 

management, targeted at small to 

medium CMS technology providers. 

This overall mission entails a number of 

necessary innovations which do not 

seem to have been in the focus of research 

on Intelligent Content and Semantics, 

so far: 

• There are very advanced technology 

platforms such as semantic 

web services and there are even 

combinations of these advanced 

service architectures with GRID 

architectures, but there has not 

been much research into what 

stops current CMS technology 

providers from buying into semantic 

technologies. Interactive 

Knowledge will provide a seman- 

“A-B-C People” 

Doug Engelbart's far-sighted vision about technologies 

for knowledge workers that enable users 

“downstream” to be more productive stands at the 

beginning of this project. 

tically enabled 

layered CMS/ 

KMS architecture, 

its specification 

and a 

reference implementation - the 

Interactive Knowledge Stack. 

• There has been excellent research 

work into foundations of ontological 

representations, and there 

are large scale workbenches for 

ontological engineering, but there 

have not been many attempts to 

make foundational ontologies usable 

by commercial software developers 

and there has been even 

less research into developing user 

interfaces which let end users interact 

with knowledge structures 

in an intuitive 

fashion. InteractiveKnowledge 

will provide 

a layered, 

semantically 

enabled user interface framework 

which can be customised by software 

developers of CMS applications 

so that end users can interact 

with knowledge-rich content 

in an intuitive way. 

4 

What stops current CMS 

technology providers from 

buying into semantic 

technologies? 

How can end users interact 

with knowledge-rich 

content in an intuitive 

way?

• There have been three waves of 

research into interoperation between 

heterogeneous information 

systems, starting with database 

interoperation in the 1980s, doing 

semantics-based interoperation 

in the 1990s (e.g. the US I3 

programme - Intelligent Information 

Integration) and being reinvented 

at present, by the Semantic 

Web community, albeit 

with a new set of implementation 

technologies. 

Very few of the 

known in- 

teroperationsolutions have ever made it into 

mainstream systems because they 

tended to be too complex to use. 

Interactive Knowledge will analyse 

the most useful semanticwrapper 

innovations and make 

them mature enough to be used 

in the Stack. We will combine this 

pragmatic approach with the latest 

expertise in interoperation 

technology, combining work from 

networked enterprises with the 

research done in intelligent content 

and semantics. 

• With RDF and OWL, the Semantic 

Web community has developed 

two new but not necessarily compatible 

storage 

Is a mismatch in database paradigms, next to 

technologies impending the existing rela- 

semantic technology take tional, hierarchical 

up? 

and object-oriented 

data bases. This 

makes it nearly impossible 

- even for research projects 

- to find a coherent system 

architecture for data storage, rule 

representation and reasoning 

over instances and schemas. Interactive 

Knowledge will do engi- 

5 


Is interactive and intuitive 

content a reality? 

neering research into practical, 

yet sound persistence architectures 

which do not exhibit the 

current, frequently encountered 

problem of duplication of information 

in reasoning and database 

systems. 

• By developing a coherent CMS 

framework, Interactive Knowledge 

will be better able to hide complexities 

of computer-based 

knowledge representa- 

tion from the user. The 

user must always be 

confronted with a rep- 

resentation of his/her 

knowledge space, which is adequate 

and fits the mental model 

of the user's understanding of the 

knowledge domain. Interactive 

Knowledge will develop conceptual 

metaphors which can act as 

hidden ontological patterns, thus 

moving user interface design 

closer to natural language (albeit 

controlled natural language).

Expected Market Impact 



Malesuada quis, egestas quis, felis nunc, aliquam ac, consequat 

wisi. Donec ac sapien. Ut orci. vitae, feugiat at, blandit vitae, 

Duis ultricies, metus a feugiat euismod vel, nunc. Aenean ut 

porttitor, dolor mauris convallis erat ut nibh commodo suscipit. 

est, quis mattis lacus ligula eu Maecenas metus non quam. 

augue. Sed facilisis. Morbi lorem Nam uut, massa. Maecenas 

mi, tristique vitae, sodales eget, vitae ante et lacus aliquam 

hendrerit sed, erat lorem ipsum. hendrerit. Aenean ut erat ut 

Vestibulum eget purus vitae nibh commodo suscipit. Curabi- 

eros ornare adipiscing. Vivamus tur nunc eros, euismod in, con- 

nec quam. Integer vestibulum vallis at, vehicula sed consecte- 

malesuada libero. Sed vehicula tuer posuere. 


Nullam wisi arcu, suscipit con- Malesuada quis, egestas quis, 

sectetuer. Vestibulum imperdiet wisi. Donec ac sapien. Ut orci. 

nonummy sem. Vivamus sit amet Duis ultricies, metus a feugiat 

erat nec turpis tempus conse- porttitor, dolor mauris convallis 

quat. Praesent malesuada. Donec est, quis mattis lacus ligula eu 

vitae dolor. Donec at lacus ac mi augue. Sed facilisis. Morbi lorem 

vehicula bibendum. Donec mi, tristique vitae, sodales eget, 

feugiat organisations. 

tempor libero Aenean ut hendrerit sed, erat lorem ipsum. 


Nam uut, massa. Maecenas vitae 






sed pede suscipit: Adiam condimentum 

purus, in consectetuer 













sagittis at, semper vitae, tincidunt 

quis Malesuada quis, egestas 

quis, wisi. Donec ac sapien. 

Ut orci. Duis ultricies, metus a 


convallis est, quis mattis lacus 


Morbi lorem entertainment. 

mi, tristique vitae, 

sodales eget, hendrerit sed, 

erat.. 



What are we aiming at? It would be a great improvement over current 

practice if Interactive Knowledge could develop CMS components 

that are suitable for the top 50% of CMS software 

developers to build adequate solutions for the top 50% of customers. 

This means that we would expect 50% of the firms who get exposed to 

Interactive Knowledge to actually take up the technology and methodology 

beyond the project's life time and we expect the solutions 

developed to be considered successful in 50% of the customer 

cases. This figure would be considerably higher than current 

estimates concerning the success of traditional IT solutions in end user 

It would be a further great improvement if we moved from the current 

support technologies for content management, to a support technology 

for Ambient Intelligence which is where the "content" technologies will 

have to move, eventually. Such a move would enable: 

• Rapid development of content-supported ambient environments, 

i.e., adaptive, web-based and flexible support of heterogeneous 

contents delivered by semantic CMS allow faster integration 

into ambient environments 

• The main innovation potential within the context of ambient environments 

is by far the potential for new product designs. Contents 

can be more rapidly integrated into smart products that 

deliver new means for interaction, collaboration, and 

6

IKS developed a working 

hypothesis which we call 

the Interactive Knowledgeedge 

Stack. We We are trying 

to start a dialogue 

in the the developer community, 

about the 

need for for a a conceptual 

layering. As a start, 

we we developed the folfollowing concepts, 

visualised in this 

diagramm. 

IKS layers: behavioural/ 

interface, description/ 

middleware, distribution 

& storage/repository 

Join the dialogue 

7 

The IKS Hypothesis 

We invite people who have an interest in future, advanced forms of 

interaction with “intelligent” content on the web and how such future 

forms of content can be managed. 

In short we want to show practical pathways for current CMS technology 

provider to such advanced platforms piece by piece, in manageable 

steps! That’s why we need the practitioners amongst you, too!


Interactive Knowledge is a unique attempt to achieve impact 

through industrial uptake of semantic web technologies in an 

important sector of the European economy: supporting business 

related semantic content and knowledge management. 

We describe the following five critical 

success factors and give success and 

failure conditions: 

• CSF-1 IKS Technology Stack 

• CSF-2 Interaction with knowledge 

at the user level 

• CSF-3 Raising the technological 

capabilities of CMS providers 

• CSF-4 Raising the value of interactive 

knowledge in the perception 

of the user 

• CSF-5 Providing a useful methodology 

for developing and managing 

semantic CMS 

CSF-1 IKS Technology Stack 

There are three sub-criteria that need to 

be achieved: 

• Specifications - it would be a success 

if IKS contributed significantly 

to standards of OASIS and 

W3C. It would be a failure if there 

were no specifications beyond to- 

Objectives Tree 

day's state of the art, after the 

project has ended. 

• Software - it would be a success if 

several non-trivial applications 

were developed and if these applications 

exhibit a widely acknowledged, 

significant integration of 

semantic models with current CMS 

technology. It would be a failure if 

more than half the developers 

would report the IKS framework to 

be unusable for their purposes. 

• Demo Applications - it would be a 

resounding success if 80% of IKS 

based applications received favourable 

reviews from their respective 

end users. It would be a 

failure if no significant applications 

have been built by month 

36. 

CSF-2 Interaction with knowledge at 

the user level 

There are five sub-criteria that need to 

be achieved: 

8

• Development of the Intelligent 

Project Controlling Tool as an 

early use case - it would be a success 

if the majority of end users 

regarded the tool as "helpful", "intelligent" 

and if the tool itself was 

proof of the IKS specifications. It 

would be a failure if the majority 

of the users do not see any difference 

to similar tools or achieves 

its success without use in any of 

the IKS specifications. 

• Useful interaction at applications 

level - it would be a success if the 

majority of applications were able 

to use the IKS interaction model 

for building their semantic CMS 

applications. It would be a failure 

if none of the applications make 

use of the generic model specification. 

• Useful basic knowledge models 

for use in applications - it would 

be a success if the majority of applications 

were able to use the IKS 

knowledge model for building 

their semantic CMS applications. It 

would be a failure if neither the 

models can be used directly or 

can be mapped to domain knowledge 

models. 

• IKS user model is adopted by 

many semantic CMS providers - it 

would be a success if the majority 

of applications were able to use 

the IKS user model for building 

their semantic CMS applications. It 

would be a failure if the model is 

neither used nor has defined relations 

to existing popular user 

models. 

• IKS Discourse Model is used by 

many semantic CMS providers - it 

would be a success if the majority 

of applications were able to use 

9 


the IKS discourse model for building 

their semantic CMS applications. 

It would be a failure if the 

IKS discourse models are not accepted 

by relevant communities 

as an innovative and useful approach. 

CSF-3 Raising the technological capabilities 

of CMS providers 

There are four sub-criteria that need to 

be achieved: 

• Horizontal use case applications 

- it would be a success if CMS 

providers which previously had a 

strong specialisation for a specific 

sector, would report significant 

new business opportunities in new 

application domains, afforded by 

the increased capabilities of the 

IKS framework. It would be a failure 

if none of the CMS providers 

report efficiency gains. 

• Vertical use case applications - 

the success criteria for vertical 

integration are dependent on the 

actual structure of the IKS Stack. 

The semantic benchmarks in WP1 

will lead to our first set of success 

criteria. The final set will be decided 

together with the release 

version of the IKS framework, in 

M36. It would be a failure if neither 

the methodology nor the IKS 

software framework would lead to 

tangible industrial uptake. 

• 40+ CMS firms are participating in 

IKS - it would be a success if the 

target of 50 CMS providers taking 

part in validation experiments, 

was achieved. It would be a failure 

if less than 20 CMS providers were 

taking part by month 36. 

• Benchmarks for semantic capability 

- it would be a resounding 

success if the IKS benchmarks


were adopted by several international 

bodies, as lead reference 

for measures of CMS quality. It 

would be failure if little significant 

external reference was made to 

IKS by month 36. 

CSF-4 Raising the value of interactive 

knowledge in the perception of the 

user 

There are three sub-criteria that need 

to be achieved: 

• Demonstration of a use case for 

advanced CMS in an Ambient Environment 

- it would be a success 

if the ambient intelligence community 

realised the importance of 

semantic CMS as part of the 

AmISpace infrastructure and if at 

the same time, CMS providers understood 

the commercial potential 

of AmISpace. This will be achieved 

through high-quality papers for 

interdisciplinary journals, workshops 

and conferences. It would 

be a failure if no significant interdisciplinary 

results were produced. 

• Demonstration of an actual end 

user system in a consumer show 

room - it would be a success if 

one or more IKS use cases raised 

significant interest with the intended 

end user audiences and 

the attendant press and media 

coverage over a sustained period 

of time, or repeatedly. This should 

lead to a market perception of IKS 

being a "disruptive" technology 

with high leverage. It would be a 

failure if neither the technology 

itself nor the perception of it 

would lead to measurable change 

of customers' purchase behaviour 

with respect to advanced content 

management. 

• Achieving the "Semantic Wave 

Europe" - it would be a success if 

at the end of the project there 

were in the region of 100 CMS 

providers acknowledging the use 

of IKS related specifications, 

methods and/or components in 

their products, and if there were 

in the region of 500 individuals 

from different communities acknowledging 

the use of IKS related 

specifications, methods and/ 

or components in their knowledge 

and content related work. It would 

be a failure if less than 30% of a 

representative sample (firms or 

individuals) were aware of IKS and 

its technological framework. 

CSF-5 Providing a useful methodology 

for developing and managing 

semantic CMS 

There are three sub-criteria that need 

to be achieved: 

• Academic Training - it would be a 

success if three universities adopt 

significant parts of the IKS training 

materials for graduate or undergraduate 

studies. It would be a 

failure if the IKS design family will 

not be adopted in academic discourse. 

• Industrial Training - it will be a 

success if there is a high demand 

for IKS industrial training and the 

training is offered and subscribed 

to, at commercial conditions. It 

would be a failure if there is no 

external interest in IKS-related 

trainings. 

• IKS Books - it would be a success 

if the book gets published receives 

favourable feedback.. It 

would be a failure if the book was 

not published by external publishers. 

10

Implementation Plan 



Overall strategy 


Interactive Knowledge wisi. has Donec a duration ac sapien. Ut of orci. 48 months; and a budget of 8,5 M€ with 5,6 M€ requested 

funding. The project Duis is organised ultricies, metus in 10 a feugiat Work Packages and uses an effort of 750 person months. It 


expects to leverage another 200 PM in open source development outside the project, as well as a fur- 


ther 100-200 PM in augue. external Sed facilisis. validations Morbi lorem of the project results. 

These leveraging activities mi, tristique and vitae, their sodales financing eget, are described in WP8 ("Semantic Wave Europe") and in 


the financial resource planning section. The work packages are briefly introduced below: 

Work Package Title Brief Overview of WP 

WP1 - Benchmarking industrial 

semantic software capabilities 

WP2 - IKS Requirements Capture 

through Use Cases 

WP3 - Research into Requirements 

of the Interactive 

Knowledge Stack 

WP4 - Design and Implementation 

of the Use Cases 

WP5 - Design and Implementation 



WP6 - Validation of the Interactive 


We will devise a benchmarking scheme and the six IND-partners will attempt to build a small system 

with distinct semantic challenges. The results feed into requirements capture for the Interactive Knowledge 

Stack. 

While the benchmark provides a "laboratory" type situation, we use four distinct use cases for practical 

requirements capture for the Interactive Knowledge Stack. This feeds into WP3, WP4 (Design) and WP7 

(Methodology) 

We will conduct research at four levels: knowledge-based interaction and presentation; knowledge 

representation and reasoning; semantic lifting and wrapping of legacy resources; semantics based data 

access and reasoning (backend support) 

The four use cases are developed in parallel with the implementation of the Interactive Knowledge Stack 

(WP5) and the two work packages will inform each other, in a similar way as WP2 and WP3 do for 

requirements. 

We build an Alpha, Beta and final release of a reference implementation of the envisaged Interactive 

Knowledge Stack. The Alpha and Beta releases are validated internally, in the use cases. The final release 

is used to build the Road Show Demonstrators (WP9) and it is given to the external early adopters 

for use and validation by firms outside the consortium (Task 6.3) 

It is important to explain the difference between Task 6.2 (47 PM) and Task 6.3 (5 PM!) here: Task 6.2. 

is the validation by the IND-partners of the consortium in specific validation projects whereas Task 6.3 

is our contribution to conducting and managing of the external validation which has no effort charged 

to the project! The external validation partners receive a training grant as the project's contribution to 

their acting as early adopters. 

WP7 - Methodology By year two we publish a report on the state of semantic capabilities of European CMS providers; by year 

three we provide industrial training to be disseminated by regional transfer offices and at the end of the 

project a full methodology handbook will be published. The university partners will introduce the 

knowledge generated in the project into their academic teaching programmes. 

WP8 - "Semantic Wave Europe" The term "Semantic Wave" is borrowed from Mills Davis, a US Evangelist for Semantic Web. Here it 

stands for the work we envisage to activate open source communities and European CMS providers (and 

their customers!) to embrace the specifications and benefits of the Interactive Knowledge Stack. 

WP9 - Industrial Application & 

Demo 

We demonstrate the use of the final Interactive Knowledge Stack for building industrial applications and 

we make the show cases stand out from the crowd. 

WP10 - Project Management We manage the project through co-ordination, QA controlling and financial controlling, through the use 

of semantic Wikis and via a "visiting manager"! 

11

Work Plan in Detail 

WP 1 - Benchmarking industrial semantic 

software capability 

IKS will invite organisations which conduct or use CMS 

benchmarks, to act as stakeholders in defining success criteria 

for advanced knowledge and content management. 

In Task 1.1 we design the benchmarking 

experiment to be conducted. Each 

of the IND partners will be given the 

same task of building a semantically 

enhanced web-based content management 

system within a tight time-frame. 

We envisage a sophisticated benchmarking 

model which factors out standard 

software engineering capabilities 

and strengths in user interface building, 

from actual semantics- or knowledgebased 

capabilities. The benchmarks will 

start with a three level distinction of capability 

and will later be refined to five 

levels, if possible. 

In Task 1.2 the six IND partners will be 

doing the benchmark exercise which 

will most likely be staggered - we let 

them develop one level of achievement, 

validate it and then go on to the next 

step in the exercise. This is why we envisage 

a nine-months period in which 

these benchmark-and-validate cycles 

(Tasks 1.2 and 1.3) will be done. 

In Task 1.3 we validate the results of 

the benchmarking exercise and use the 

results (e.g. interviews with designers/ 

developers about their experiences, 

challenges faced) as input to the requirements 

capture phase of WP3 (Requirements 

of the Interactive Knowledge 

Stack). 

Formal assessment of IKS components 

to ensure progress over conventional 

CMS applications: There are several 

widely accepted CMS benchmark procedures 

available at present. The BNP 

benchmark uses 15 criteria under three 

headings: Technical (e.g. architecture 

and functionality), Usability (e.g. personalisation 

or workflow support), Business 

(e.g. technology partners and support 

for open standards). 

Benchmarks used by CMSWatch use a 

more sophisticated structure distinguishing 

functionality along the content 

life cycle (e.g. production and delivery). 

Academic work on "semantic benchmarking" 

is still focused on technology 

without regard for business contexts. 

IKS will map industrial CMS benchmarks 

to the layers layers of the Interactive Knowledge 

Stack. Industrial success criteria 

will be attributed to components of the 

stack. Next, "best of breed" achievements 

for each of the criteria will be 

noted. Finally, the "semanticity" of the 

CMS solution will be assessed. This 

measure has several dimensions: 

• how declarative is the implementation? 

The opposite would be implicitness. 

• how generative is the approach? 

The opposite would be programmatic 

enumeration of cases. 

• how recombinant is the software 

function in question? The opposite 

would be a function whose output 

cannot be recombined with the 

output of other software funcfunc-functions. 12

WP2 serves the purpose of providing 

real-world requirements as witnessed 

by industrial partners. We have four use 

cases in which the scope is defined upfront, 

and case has a distinct bias: 

Task 2.1 is the visionary use case 

where we demonstrate how the field of 

CMS may be influenced (and changed!) 

through the vision of Ambient Intelligence. 

The challenge of this case is to 

"route" content and interactive knowledge 

objects according to the needs of 

the user and according to the environment 

of the user. The simple example 

is: You are taking a bath, watching 

some sports in the background (football, 

car racing), but actually listen to 

some music while the sports is on mute. 

Suddenly, you have a good idea about 

your new project and you want to 

quickly make a note of the idea, as a 

comment to the multimedia presentation 

you have been putting together 

with your team. You need to transfer 

your computer desktop to one of the 

bathroom displays (while still listening 

to the music and watching the sports) 

and you want to use speech recording 

and speech-to-text to add the comment 

to your presentation and mail it to 

some colleagues. The game goes into 

overtime and you want to go into the 

Sauna - so you now want to follow the 

same sports event as a radio transmission. 

Your whole house is managed by 

you using a "mixing desk" on which you 

call up "tracks" and you mix them to 

whatever you feel is right for you. This 

includes re-setting the heating from 

winter-mode to summer-mode, while 

sitting in the bath - if you believe this is 

possible today: try it out now - you will 

13 


WP 2 - Understanding and Requirements 

Capture through Use Cases 

not even understand the manual and 

the device that needs to be programmed! 

This is what Interactive 

Knowledge is all about: intelligent digital 

convergence of (currently dumb) 

content. And this is what future CMS/ 

KMS will be dealing with! 

Task 2.2 by contrast, looks at a horizontal 

use case from NUXEO, a CMS 

provider with a "horizontally placed" 

CMS framework. We have not fixed the 

actual target application, but it will be 

one where a broad range of functionality 

is needed and therefore, a use case 

where we can study the set of generic 

functions needed in the Interactive 

Knowledge Stack, at each of the layers. 

We will also look at cases from Day 

Software who are similarly placed. 

Task 2.3 looks at requirements from 

a vertical use case provided by Pisano/ 

CIC who are active in the portal market 

for travel agencies and who are interested 

in combining their CMS with recommender 

systems - another example 

for a CMS provider moving towards 

added value through "intelligent content". 

Task 2.4 looks at the requirements in 

an area where a very rich knowledge 

domain is combined with CMS of arbitrary 

richness in media. The application 

domain is project controlling, and as a 

demonstration of this, we will analyse, 

design and build a knowledge-based 

"Project-controlling system". This 

means content management connected 

with previous plans, and the monitoring 

of efforts against knowledge workers 

output (e.g. software or documents). A 

version of this system will be made ac-


cessible as freeware. There are two 

good reasons for this application case: 

all stakeholders (EC, researchers, industry, 

reviewers, etc.) understand the domain 

in question, understand the challenges 

of managing knowledge based 

content in this domain, and are therefore 

in a position to assess the quality 

of our work, without any need for 

judgmental support from outside. This 

is an additional challenge and motivation 

for the research group, apart from 

the second good reason: we are confident 

that such a system has a serious 

business case and some of the partners 

will jointly develop it into a business 

venture, possibly in collaboration with 

one of the industrial partners in the 

project. The exploitation plans of the 

partners will be developed in WP8 - 

"Semantic Wave Europe" and WP9 - "Industrial 

Application and Demo". 

WP3 looks at the scientific foundations 

needed to create an industry-strength 

Interactive Knowledge Stack which has 

real impact on the solutions provided by 

CMS-SMEs in Europe. Note that the 

software engineering perspective across 

the whole stack is provided in WP2 - 

Task 2.2 (horizontal industrial use case) 

where the "Stack-experts" from University 

of Paderborn are working closely 

with industry and with the researchers 

in WP3! 

Task 3.1 looks at the requirements 

for the user interaction with knowledge 

and at the attendant presentational 

aspects. The real challenge is to 

make the plethora of current and past 

research results - which are at different 

levels of maturity and using different 

implementation technologies - operational 

in a stack of current, reasonably 

future-proof technologies that start at 

the interface and end in either a relational 

database or a dedicated knowledge 

base with a reasoner, at the backend. 

Task 3.1 focused on the top-end 

of this information flow. 

Task 3.2 needs to provide the foundations 

for both, the user interaction 

as well as the data schemas or ontologies, 

and for the rule-based machinery 

envisaged to support complex 

business logics. This is where foundational 

ontologies and ontology design 

patterns from foundational ontologies 

expected to provide the "semantic bus" 

for the whole system, and this is where 

most of the conceptual complexity 

needs be hidden from the developer 

and subsequently, the end user. 

WP 3 - Research into requirements of the 

Interactive Knowledge Stack 

Task 3.3 is dedicated to the general 

problem of accessing legacy information 

sources, for which IKS wants to 

provide a set of useful answers. We 

want to focus on those semantic lifting 

components that have a high utility for 

business applications. Therefore, we will 

provide a general "adapter architecture" 

for connecting information resources to 

the models of the Interactive Knowledge 

Stack, and we will populate that architecture 

with actual semantic lifting 

components for "Web 2.0 content" (e.g. 

mash-ups), multi-media repositories 

and traditional structured and semistructured 

information sources. 

Task 3.4 addresses the issues of the 

database backend and in particular, 

the dilemma of "duplication and syn- 

14

chronisation" between traditional database 

technology on the one hand and 

knowledge basis which support inferencing, 

on the other: the underlying 

problem is that different programming 

and system design paradigms are at 

work, here. This is not unusual in industry 

and we will need to research 

practical approaches to solving the dilemma 

depending on the needs of the 

user. 

WP 4 - Design and Implementation 

of the Use Cases 

A look at the Gantt chart will show that 

the use cases will be designed and implemented 

alongside the design and 

implementation of the Interactive 

Knowledge Stack (WP5). The logic of this 

apparent parallelism needs to be explained: 

We envisage the Interactive 

Knowledge Stack to be implemented in 

three iterations (Alpha, Beta, Final) and 

there will be close collaboration between 

the developers of the Use Cases 

and the developers of the Stack. This 

"exploring the benefits and 

limitations of the the Stack" in 

close collaboration is deliberate: 

only by trying to build 

actual use cases can we be 

sure to address real semantic 

modelling modelling problems 

when designing the Stack. 

This means that the use 

cases will be exposed to 

Alpha and Beta versions 

of Stack-components 

and in some areas, will 

actually have to use ex- 

isting technologies to be developed 

in time. Note that this is part and 

parcel of our research method. We need 

to experience as developers, what it 

means to create an application which 

15 


has semantic capabilities injected into 

the design and implementation. 

WP 5 - Design and 

Implementation of the 

“Interactive Knowledge 

Stack” 

Our working hypothesis - to be validated 

or falsified in the project - is the 

Semantic CMS Technology Stack which 

we refer to as the "Interactive Knowledge 

Stack". We assume that a clean 

architecture with well-designed layers 

of abstraction and well thought-out 

technological perspectives (cf. Zachman 

- framework, ARIS-model, etc.) will help 

immensely in bringing semantic CMS 

applications from a "black art" to a well 

understood software process. The current 

assumption for this Stack is an 

eight-layer model. 

Our research focus is on the top-four 

layers where we identified a massive 

research gap with respect to cognitively 

and linguistically (!) sound semantic interaction 

models. 

For the fourth layer from the top, our 

research is on finding a suitable set of 

technologies that integrate Business 

Rules with the envisaged interactive 

knowledge front end (layers 1-3) as well 

as with the workflow (5) and distribution 

services layers (6). 

At the back end (services/distribution 

layer (6) and persistence layer (7)) our 

research is more geared towards working 

out which of the available technology 

options offer stability, easy of integration 

and reasonable performance for 

industrial application. We do not envisage 

"ground-breaking" work in new 

query languages and storage paradigms, 

but in validating the existing


work for usability in knowledgebased 

content management 

(SPARQL, RDQL, Excerpt-based XML 

and RDF querying, RDF-Triple 

stores). 

We will maintain a list of external 

open source software components 

and specifications and their relationship 

with the Interactive Knowledge 

Stack, because it is likely that 

the Stack may offer alternative implementation 

options. This list will 

be organized along the following 

criteria: Availability (IPR, licensing 

scheme), Dependencies (Modularity, 

Implementation languages), and 

Maturity (Industrial strength vs. 

research prototypes). 

The problem of developing an 

industry-strength technology platform 

for a semantic CMS stack requires 

significant understanding of 

user interfaces, cognitively and linguistically 

valid user modelling, 

semantic web, software engineering, 

and content management. The 

consortium was designed to cover 

this range of capabilities including the 

definition of advanced CMS development 

methodologies that can be used 

under realistic economic conditions. 

WP 6 - Validating the Interactive 


WP6 is devoted to the validation of the 

Interactive Knowledge Stack by conducting 

four tests: firstly an internal 

validation by the developers of the two 

RTD use cases (AmI-Case and Project 

Planning Case); secondly also a validation 

internally, by the developers of the 

horizontal and vertical use cases which 

are led by the industrial partners; 

thirdly a validation externally, by a 

group of up to 40 40 registered CMS providers 

acting as "early "early adopters"; and 

finally another validation externally, by 

conducting empirical studies with the 

"downstream users" of 

the above applications. 

It is important important to to explain 

the difference between between 

task 6.2. and task 6.3. 

Task 6.2 includes the 

development of a system under "laboratory 

conditions" within the project, by 

the six industrial partners, and the 

monitoring of the development by the 

research partners. Task 6.3 on the other 

hand, has all the validating development 

happening outside the project and 

only the monitoring being done from 

within the project. 

16

WP 7 - Methodology for developing 

Interactive Knowledge Stack 

applications 

There are four elements that make up 

our methodological contribution: 

• A report on semantic technologies 

in CMS, based on researching 

current content management 

systems (open source and proprietary) 

and assessing their semantic 

capabilities, and also 

based on experiences with the 

benchmarking exercise and requirements 

capture in year one 

and two 

• Handbook for developing semantic 

CMS applications to support 

application designers and 

developers with a method for 

building semantic 

CMS 

applications 

step-by-step. 

Additionally 

this handbook 

will 

contain reports 

on applications 

that 

were developed 

within 

these descriptions 

are 

related to the 

overall 

method in 

order to give 

developers a "feel" for the approach 

taken by Interactive 

Knowledge. 

• Curriculum and training training material 

for university teaching. We 

will develop a prototype set of 

17 


materials which should be 

adapted and refined by lecturers, 

depending on the actual curricula 

of the target institutions and academic 

programmes. The materials 

will be openly accessible. 

• Curriculum and training material 

for industrial training - we 

will develop a basic set of materials 

which can be adapted and extended 

depending on the actual 

needs of specific industrial training 

programmes. The materials 

will be openly accessible. 

WP 8 - Community and 

Stakeholder activation 

WP8 includes all tasks concerned with 

the activation stakeholders. These include 

inviting open 

source developer 

communities to 

take part in discussion 


Knowledge 

Stack, recruiting 

further industrial 

CMS providers as 

"early adopters" of 

the technology, and 

an awareness programme 

for academia. 

It is also necessary 

for Interactive 

Knowledge to 

take part in any 

awareness activities 

where potential 

customer communities (e.g. e- 

Government) are made aware of requirements 

which are likely to occur in 

the near future and which they need to 

understand in order to procure futurefutureproof systems.


WP 9 - DEMO Activities - Showcase 

Applications of Interactive Knowledge 

In WP9 we develop and demonstrate the 

use of semantically enhanced CMS 

which allow new forms of interaction 

with knowledge rich content. Two lead 

use cases have been predefined, two 

more are outlined, and several others 

will be chosen in the later stages of the 

project. The two defined lead cases are 

described below. 

Ambient Contents on semanticallyenabled 

CMS 

This will be our most advanced and 

"daring" show case: This showcase is 

motivated by the Ambient Intelligence 

and Pervasive Computing visions of 

ISTAG and others. The case is justified if 

one accepts that future, ambient applications 

will put immense semantic 

strains on traditional content management. 

In order for the content management 

system to present the right information 

it will have to be sensitive to 

contextual information. Furthermore, it 

will have to ensure that a multitude of 

guidelines, rules and regulations are at 

all times followed and that the system 

must be as supportive as possible to the 

user. This will require much tighter synchronisation 

between content presentation 

and underlying "world model". 

With Ambient Content, the IP IKS extends 

the traditional, desktop-bound 

view on digital contents towards future 

forms of content usage scenarios and 

evaluates whether „semantic CMS“ will 

be sustainable enough for future applications. 

AC is content that adapts to any kind of 

physical environment and leverages 

available technology infrastructures for 

interaction with users. A user (or user 

group) might intend to access weather 

information in a room. His request is 

captured and routed to a control unit 

which translates this natural language 

request intro retrieval sequences over a 

set of CMS services. Results sets a re 

processes and routed to a presentation 

planning service which determines 

which devices or device sets optimally 

support this particular content according 

to user and situational requirements. 

For instance, 

weather 

information 

is sent to 

his mobile 

phone together with the mesmessage that additional contents have been 

sent to his email account which also includes 

a weather forecast animation. 

18

This viewpoint requires to place content 

in the center of a product design takes 

while perceiving CMS and presentation 

and interaction technologies (e.g., mobile 

phones, TV, radio etc.) as supporting 

technologies that can be used by 

contents according to situational needs. 

Therefore AC is far more adaptive and 

requires intelligent processing support 

on various levels and seman- 

tic descriptions 

of 

contents, 

CMS 

services, 

devices 

and task 

environments. 

19 

The 

use 

case 

in IP 

IKS 

“Ambient 

Bath and Infotainment” 

targets a home situation in 

a particular physical environment, i.e., a 

bathroom. Bath rooms increasingly become 

central locations that have to fulfill 

increasing user demands. For ininstance, in the morning you might become 

informed about current news, 

stock market information but also entertaining 

content such as the best 


jokes of preferred late night shows. 

During a bath you might want to talk to 

your spouse who is currently in a hotel 

or to thin trough your holiday plans for 

which some pictures, videos or 3D projections 

of possible locations and 

apartments would be helpful. Our approach 

for this use case is: 

• Determine requirements for ambient 

bath rooms together with industrial 

partners parallel to a literature 

analysis on ambient intelligent 

environments with a focus 

on dynamic contents. 

• Develop an AC design framework 

for embedding ambient contents 

in physical environments 

• Develop rapid prototypes and ambient 

contents 

• Assess and evaluate resulting 

prototypes with the help of user 

studies 

• Conduct an impact analysis on 

products enhanced by ambient 

content; assess market potentials 

• Revise the design methodology 

for products enhanced by ambient 

content and refine the AC design 

framework in workshops with 

project partners and selected external 

industrial partners 

The Semantic Project Controlling 

Assistant 

This is an advanced knowledge-rich application 

which will support the process 

of quality control for research and technology 

projects. At first sight, this is 

clearly an "inward-looking" application 

of semantic content and knowledge 

management, because its user group 

are researchers and technologists working 

on larger scale projects At second 

sight, however, there are very good reasons 

to tackle this application:


• it is scientifically challenging because 

it has a mix of hard knowledge 

based constraints (e.g. effort 

figures must match) and soft constraints 

(tasks which are dependent 

on each other, may sometimes 

overlap) and it may combine different 

media (diagrams, charts, 

tables, animations, audio/video) 

• it is technically challenging, because 

the current mode of operation 

is to use different heterogeneous 

tools whose inputs and 

outputs do not match at a semantic 

level! 

• it can be extended to all domains 

where project management plays 

an important role 

• in this application, our technical 

research results can be validated 

by all stakeholders: The independent 

industrial reviewers will 

know the domain, the EU officials 

(e.g. project officers) know it, and 

the researchers as users also 

know it well. 

• it has a significant potential value: 

if it works well then it should indeed 

make the managing and 

controlling of projects faster and 

less error-prone, thus allowing 

the creative spirits to concentrate 

on good and innovative ideas. 

We are trying to build a convincing interactive 

knowledge based tool for 

managing knowledge-level dependencies, 

e.g. if we remove contractor X 

from the consortium, which tasks and 

deliverables will be affected and what 

expertise is lost? Which paths in the 

PERT will have to be redesigned? Which 

parts of the consortium agreement and 

the contract need to be revised? 

Interactive semantic CM/KM applications 

in traditional markets 

The Ambient Intelligence application 

and the Intelligent Work Plan Description 

application are purposefully chosen 

as very advanced usage scenarios which 

take into account the four-year schedule 

of the project. However, the industrial 

partners often have more traditional 

markets with much shorter product 

cycles and Interactive Knowledge 

must be able to add significant value to 

those applications, as well, otherwise 

there is no incentive for industry to 

adopt the technology and the processes 

needed to handle the technology. 

Therefore, the project is set up to 

monitor and contribute to, the adoption 

of the semantic CMS Technology Stack 

in "live" (i.e. real-world) projects of the 

industrial partners. We envisage three 

types of such applications: 

• one with a focus on horizontal 

aspects of the "IKS Stack" (i.e. 

without any domain specifics) 

• one with a focus on vertical aspects 

of "IKS Stack" (i.e. providing 

a sector-specific solution) 

• two with a focus on user specific 

domain representations (i.e. focussing 

on interactive knowledge 

user interfaces with specific representational 

demands, such as 

aggregation of large data sets, or 

representation of semantically 

complex object-configurations) 

We will also look at a mix of media richness, 

from highly structured objects 

(e.g. CAD) to multimedia and to illstructured 

information. The objective is 

to get exposed to diverse, but realistic 

requirements as faced by developers of 

real-world CMS/KMS solutions. 

20

21 


Each of the industrial CMS partners will bring one specific showcase to Interactive 

Knowledge and will be able to address it in the course of the project. These will later 

be developed into demonstration cases for the Interactive Knowledge Road Show 

taking place in the last 6 months of the project. These cases will be used to ensure a 

wide range of possible and likely requirements. This is important to avoid a semantic 

bias in the envisaged Semantic CMS technology stack. 

The following table gives an overview on nature of the use cases, which defines the 

applications to be demonstrated within the show case activities. 

Type to en- ter text 

Use Case 1 

Project Controllling 

Problem Owner Researchers, peers, 

technology project 

managers. 

Primary solution 

developer 

community 

Research purpose 

of the use 

case 

Which layers of 

the stack are 

validated in 

particular? 

Specific aspects 

of the use case 

Use Case 2 

“Vertical Application” 

A down-stream endcustomer 

organisation, 

e.g. a travel agency 

IKS researchers CMS developers from 

the industrial partners 

Make it possible for any 

of our peers to understand 

where IKS is 

making progress 

Addresses all layers, 

shows the flow of information 

through the 

Stack 

This use case is needed 

for the researchers 

themselves to understand 

both the application 

domain and the 

research questions that 

the domain poses to us. 

Description of Use Cases 

Showing that the Stack 

is capable of delivering 

semantic CM at all 

layers 


shows the flow of information 

through the 

Stack 

There is likely to be one 

application in the tourism 

domain (travel 

portals with semantics 

based content management) 

Use Case 3 

“Horizontal 

Application” 

The industrial CMS 

solution partners 

CMS developers from 

the industrial partners 

Showing that the stack 

is generic enough to be 

used in more than one 

solution context, with 

little adaption. 


shows that the flow of 

information through the 

Stack is independent of 

the application domain. 

We need to show how 

other semantic web 

technologies (semantic 

web services, business 

processes and semantic 

wrapper technologies) 

can add value to the 

Stack (or vice versa) 

Use Case 4 

“Ami-Case” 

Duravit as an external, 

downstream end customer 

organisation 

IKS researchers jointly 

with one or two industrial 

partners 

Demonstrating the 

potential of IKS as a key 

enabling technology for 

AmI-Space 

There will be one focus 

on convincing, flexibel 

multi-modal user interfaces 

and another on 

managing distribution 

in highly mobile environments. 

Demonstrating the use 

of IKS in mobile, ambient 

scenarios.

Team Team Welcomes Welcomes YOU YOU to to 

get involved! 

involved! 

IKS Team Welcomes YOU to 

22


Malesuada quis, egestas quis, sagittis at, semper vitae, tin- 

wisi. Donec ac sapien. Ut orci. cidunt quis Malesuada quis, eges- 

Duis ultricies, metus a feugiat tas quis, wisi. Donec ac sapien. 

porttitor, dolor mauris convallis Ut orci. Duis ultricies, metus a 

est, quis mattis lacus ligula eu feugiat porttitor, dolor mauris 

augue. Sed facilisis. Morbi lorem convallis est, quis mattis lacus 

mi, tristique vitae, sodales eget, ligula eu augue. Sed facilisis. 

hendrerit sed, erat lorem ipsum. Morbi lorem mi, tristique vitae, 

Vestibulum eget purus vitae sodales eget, hendrerit sed, 

eros ornare adipiscing. Vivamus erat.. 

nec quam. Integer vestibulum Vestibulum usce urna mag- 

malesuada libero. Sed vehicula na,neque eget lacus. Maecenas 

fermentum Contact leo. In condimentum. Us: felis nunc, aliquam ac, consequat 

Nullam wisi arcu, suscipit con- vitae, feugiat at, blandit vitae, 

sectetuer. Vestibulum imperdiet euismod vel, nunc. Aenean ut 

nonummy sem. Vivamus Wernher sit amet Behrendt erat ut nibh commodo suscipit. 

erat nec turpis tempus conse- Maecenas metus non quam. 

quat. Praesent malesuada. 

Project 

Donec 

Manager 

Nam uut, massa. Maecenas 

vitae dolor. Donec at Salzburg lacus ac mi Research vitae ante et lacus aliquam 

vehicula bibendum. Donec Jakob Haringer hendrerit. Straße Aenean 5/3 ut erat ut 

feugiat tempor libero Aenean ut nibh commodo suscipit. Curabi- 

erat ut nibh commodo 5020, suscipit. Salzburg, tur nunc Austria eros, euismod in, con- 

Nam uut, massa. Maecenas +43 662 vitae 2288 vallis at, 409 vehicula sed consecte- 

ante et lacus aliquam hendrerit. tuer posuere. 

wernher.behrendt@salzburgresearch.at 


in, convallis at, vehicula sed Malesuada quis, egestas quis, 

consectetuer posuere, eros wisi. Donec ac sapien. Ut orci. 

mauris dignissim diam, pretium Duis ultricies, metus a feugiat 

sed pede suscipit: Adiam condi- porttitor, dolor mauris convallis 

mentum purus, in consectetuer est, quis mattis lacus ligula eu 



Fusce urna magna,neque mi, tristique vitae, sodales eget, 

About IKS 


IKS - Interactive Knowledge Stack is an Integrating Project part-funded by 

the European Commission. It started in January 2009 and will provide an 

open source technology platform for semantically enhanced content management 

systems. 

The project partners are Salzburg Research (coordinator), Deutsches Forschungsinstitut 

für Künstliche Intelligenz,University of St. Gallen, Consiglio 

Nazionale delle Ricerche, Software Quality Lab, University of Paderborn, 

Software Research and Development and Consultancy Ltd, NUXEO, Alkacon 

Software GmbH, TXT Polymedia, Pisano Holding GmbH, Nemein Oy, Day 

Software AG, Hochschule Furtwagen University. 

Visit us at www.iks-project.eu for more information. 


aliquam ac, consequat Copyright vitae, 2010 Interactive Knowledge Stack 









23

www.iks-project.eu 

24

Work Plan in Detail - IKS

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?