Semantic CMS Community - IKS

bolivialodgeInternet και Εφαρμογές Web

14 Δεκ 2013 (πριν από 3 χρόνια και 5 μήνες)

86 εμφανίσεις
















Deliverable:



7.4.
Report on Material for
Industrial Training for IKS

Deliver
y

Date:



2012/12/08

Author(s):


Wernher Behrendt

(Editor)
,

Salzburg

R
e
search

Filename:



iks_d74_Industrial_Training_Overview.docx

Publication

Level:


Public

Semantic CMS Community

D7
.
4

Report on Material for


Industrial Training for IKS

©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





2

/

23

Table

of

co
n
tents
Table

of

contents

................................
................................
................................
................................
....

2
 
History

................................
................................
................................
................................
.....................

3
 
Copyright Notice

................................
................................
................................
................................
....

3
 
IKS

in

a

Nutshell

................................
................................
................................
................................
....

3
 
1
 
Executive

Summary

................................
................................
................................
.........................

4
 
2
 
Overview of Industrial Training

................................
................................
................................
....

5
 
2.1
 
The Front
-
End: create.js

................................
................................
................................
......

5
 
2.2
 
Semantic Interaction: vie.js

................................
................................
................................
.

5
 
2.2.1
 
VIE integration in nutshell

................................
................................
.....................

6
 
2.2.2
 
Common representation of content on HTML level

................................
..............

6
 
2.2.3
 
Common representation of content on JavaScript level

................................
.........

6
 
2.2.4
 
Example

................................
................................
................................
..................

7
 
2.2.5
 
I/O operations

................................
................................
................................
.........

7
 
2.2.6
 
Dependencies

................................
................................
................................
..........

7
 
2.2.7
 
Integrations

................................
................................
................................
.............

7
 
2.2.8
 
Using VIE on Node.js

................................
................................
.............................

8
 
2.2.9
 
Development

................................
................................
................................
...........

8
 
2.2.10
 
Code organization

................................
................................
................................
...

8
 
Building VIE

................................
................................
................................
................................
..

9
 
Running Unit Tests

................................
................................
................................
........................

9
 
Unit tests on Node.js

................................
................................
................................
......................

9
 
Continuous integration

................................
................................
................................
...................

9
 
2.3
 
Semantic Enhancement Engines: Apache Stanbol

................................
............................

10
 
2.4
 
Methodology


IKS Reference Architecture

................................
................................
.....

12
 
2.5
 
IKS Components and their Integration into CMS Stacks

................................
..................

14
 
2.5.1
 
Apache Stanbol

................................
................................
................................
.....

14
 
2.5.2
 
VIE Framework

................................
................................
................................
....

14
 
2.5.3
 
Creat
ejs

................................
................................
................................
.................

14
 
2.5.4
 
Hallo editor

................................
................................
................................
...........

15
 
2.5.5
 
ViePalsu

................................
................................
................................
................

15
 
2.5.6
 
Terkait

................................
................................
................................
...................

16
 
2.5.7
 
Aemoo

................................
................................
................................
..................

17
 
2.5.8
 
Polymedia Multimedia Showcase

................................
................................
........

18
 
2.5.9
 
Pisano eTourism Showcase

................................
................................
..................

19
 
2.5.10
 
The "Intelligent Bathroom"

................................
................................
..................

20
 
2.5.11
 
Nuxeo (Horizontal application of IKS)

................................
................................

21
 
2.5.12
 
Semantic Indexing and Search with Apache Stanbol

................................
...........

22
 
3
 
Background Notes

................................
................................
................................
..........................

23
 

©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





3

/

23

History

Version

Name

Date

Remark

V1.0

Wernher Be
h
rendt

December
2012

Overview of Materials for Industrial Training

V0.1

Wernher Behrendt

March 2012

Report on state
of play at
M36,

in
Y3 Review

Copyright Notice

This document contains material, which is the copyright of certain IKS consortium parties, and may
not be r
e
produced or copied without permission. The commercial use of any information contained in
this document

may require a license from the proprietor of that information. Neither the IKS consort
i-
um as a whole, nor a certain party of the IKS consortium warrant that the information contained in this
document is capable of use, nor that use of the information is f
ree from risk, and accepts no liability
for loss or damage suffered by any person using this information.


Neither the European Commission, nor any person acting on behalf of the Commission, is responsible
for any use which might be made of the information

in this document.


The views expressed in this document are those of the authors and do not necessarily reflect the pol
i-
cies of the European Commission.

IKS

in

a

Nutshell

Interactive

Knowledge

(IKS)

is

an

integrating

project

targeting

small

to

medium

CM
S

providers

in

Europe

providing

technology

platforms

for

content

and

knowledge

management

to

thousands

of

end

user

organisations.

Current

CMS

technology

platforms

lack

the

capability

for

semantic

web

enabled,

intelligent

content,

and

therefore

lack

the

cap
acity

for

users

to

i
n
teract

with

the

content

at

the

user

s

knowledge

level.

The

objective

of

IKS

therefore,

is

to

bring

semantic

capabilities

to

current

CMS

frameworks.

IKS

puts

forward

the


Sema
n
tic

CMS

Technology

Stack

which

merges

the

advances

in

seman
tic

web

infrastru
c
ture

and

services

with

CMS

industry

needs

of

coherent

architectures

that

fit

into

existing

technology

lan
d
scapes.

IKS

will

provide

the

specifications

and

at

least

one

Open

Source

Reference

Implementation

of

the

full

IKS

Stack.

To

validate

the

IKS

Stack

prot
o
type

solutions

for

industrial

use

cases

ranging

from

ambient

intelligence

infotainment,

project

management

and

contro
l-
ling

to

an

online

holiday

booking

system

will

be

developed.


©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





4

/

23

1

Executive

Summary

We give an overview of the IKS materia
l that can be found on
-
line, to be used for industrial training.
In the third and fourth year, IKS has moved from a hybrid approach (closed and open access/source) to
a completely open process. This is witnessed by the graduation of Apache Stanbol to a fu
ll ASF pr
o-
ject in September 2012 and by the adoption of the front
-
end technologies VIE and
create.js, in several
large content management systems, among them Typo3 and Drupal release 8.


In contrast to the original plan, practically all of IKS
-
related deve
lopment and community su
p
port is
now happening
in open access fashion, on the W
eb. We have adopted

heavily
, the methods, tools and
the mindset of Web 2.0, making use of public repositories and mailing lists, twi
t
ter and the like.


In order to keep a manage
rial overview of these diverse developments, this deliverable can be seen as
a collection of relevant links to follow. The document can be used by practitioners and researchers
alike, as a printer
-
friendly yellow pages to the main strands of development, t
raining and di
scourse, on
the “IKS Web”.


The

main
strands are:



The
IKS Wiki
http://wiki.iks
-
project.eu/index.php/Main_Page

as general starting point.



The semantic CMS framework Apache Stanbol

starts at:
http://stanbol.apache.org/



The front
-
end support for semantically enhanced CMS comes from
http://createjs.org/guide/



The semantic interaction framework VIE (V
ienna IKS Editables) is on
http://viejs.org/


All dedicated t
raining materials for IKS can be found on

http://wiki.iks
-
project.eu/index.php/Acade
micTraining#Topics


For industrial users to get started immediately, the following tutorial is recommended:

http://stanbol.apache.org/docs/trunk/tutorial.html





©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





5

/

23

2

Overview of Industrial Tr
aining

We ordered this section in increasing complexity. The front end create.js brings HTML5 based edit
a-
ble content to CMSs. The semantic interaction framework VIE allows users to connect the edit
-
enabled framework
with semantic services. Finally, the Apa
che Stanbol engines offer via RESTful
API, a number of semantic enhancement services
that can be triggered via the semantic interaction
framework.

2.1

The Front
-
End: create.js

Source:
http://createjs.org/


Create.js

is a co
mprehensive web editing interface for Content Management Systems. It is designed to provide a
modern, fully browser
-
based HTML5 environment for managing content. Create can be adapted to work on a
l-
most any content management backend.


The
user interface ph
ilosophy

behind Create is simple: all content that you are allowed to change becomes
editable, right there on the page you’re reading. Any modifications you make are retained in your browser and
can be sent back to the CMS with a push of a button.


Edit in

place
:
With Create.js you’re always editing your content right where it is shown, exactly the way it is
shown.

No need to fuss around with admin interfaces or to second
-
guess how your finalized content will look
like on a page.


Create.js has been written

in JavaScript so that it can be integrated as the web editing interface on top of any
Content Management System.

CMSs like OpenCms, Symfony CMF, and Midgard have already integrated Cre
a-
te.
Create.js

is
free software

developed by
Henri Bergius

and the
Midgard Project

in collaboration with
IKS

and
co
-
funded by the Europ
ean Union


2.2

Semantic Interaction: vie.js

Source:
http://viejs.org


VIE.js
(“Vienna IKS Editables”)

is a JavaScript library for implementing
decoupled C
ontent Management S
y-
stems

and semantic interaction in web applications. In short, VIE provides a bridge between
Backbone.js

and the
semantic web.


With VIE you can easily interact with RDFa
-
annotated content on your

pages, as well as connect with v
a
rious
semantic services like
Apache Stanbol

and
DBpedia
.


All entities you deal with are managed in a centralized collection,
and VIE provides ways to deal with nam
e-
spaces, relations between entities, and if needed, your content type system.


VIE is used as the basis for a wide variety of tools ranging from
content annotators

to full
front
-
end editing inte
r-
faces

and
semantic browser extensions
. You can find many of these from the
Widgets

section of
this s
i
te.


Download 2.1.0 (minified)

Download 2.1.0 (debug)


©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





6

/

23

2.2.1

VIE integration in nutshell

Adding VIE to your system is as easy as:

1.

Mark up your pages
with RDFa annotations

2.

Include
vie.js

into the pages

3.

Implement
Backbone.sync

2.2.2

Common representation of content on HTML level

A web editing tool has to understand the contents of the page. I
t has to understand what parts of the page should
be editable, and how they connect together. If there is a list of news for instance, the tool needs to understand it
enough to enable users to add new news items. The easy way of accomplishing this is to ad
d some semantic a
n-
notations to the HTML pages. These annotations could be handled via Microformats, HTML5 microdata, but the
most power lies with RDFa.

RDFa is a way to describe the meaning of particular HTML elements using simple attributes. For example:

<div id="myarticle" typeof=
http://rdfs.org/sioc/ns#Post

about="http://example.net/blog/news_item">


<h1 property="dcterms:title">News item title</h1>


<div prope
r
ty="sioc:content">News item contents</div
>

</div>

Here we get all the necessary information for making a blog entry editable:



typeof tells us the type of the editable object. On typical CMSs this would map to a content
model or a database table



about gives us the identifier of a particular obje
ct. On typical CMSs this would be the object
identifier or database row primary key



property ties a particular HTML element to a property of the content object. On a CMS this
could be a database column

As a side effect, this also makes pages more understan
dable to search engines and other semantic tools. So the
annotations are not just needed for UI, but also for SEO.

2.2.3

Common representation of content on JavaScript level

Having contents of a page described via RDFa makes it very easy to extract the content m
odel into JavaScript.
We can have a common utility library for doing this, but we also should have a common way of keeping track of
these content objects. Enter
Backbone.js
:

Backbone supplies struc
ture to JavaScript
-
heavy applications by providing models with key
-
value binding and
custom events, collections with a rich API of enumerable functions, views with declarative event handling, and
connects it all to your existing application over a RESTful
JSON interface.

With Backbone, the content extracted from the RDFa
-
annotated HTML page is easily manageable via J
a-
vaScript. Consider for example:

v = new VIE();

v.use(new v.RdfaService());

v.load({element: jQuery('#myarticle')}).from('rdfa').execute()

.s
uccess(function(entities) {


_.forEach(entities, function(entity) {


entity.set({'dcterms:title': 'Hello, world'});


entity.save(null, {



success: function(savedMod
el, response) {




alert("Your article '
" +

©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





7

/

23

savedM
o
del.get('dcterms:title') + "' was saved to server"); }
}); }) console.log("We got " + entities.length + " edit
a
ble objects
from the page"); });


The classic VIE API will also work:

var v = new VIE({classic: true});
var objectInstance =
v.RDFaEntities.getInstance(jQuery('#myarticle')); objectI
n-
stance.set({'dcterms:title': 'Hello, world'}); objectInstance.save(null, {
success: function(savedModel, response) { alert("Your article '" +
savedModel.get('dcterms
:title') + "' was saved to server"); } });


This JS would work across all the different CMS implementations. Backbone.js provides a quite nice RESTful
implementation of communicating with the server with JSON, but it can be easily overridden with CMS
-
specific
implementation by just implementing a new
Backbone.sync method
.

2.2.4

Example

There is a full static HTML example of VIE at work. Saving outputs the edited contents as JSON into the J
a-
vaScript console:



Example with Hallo

Be sure to read the
annotated VIE source code

for API documentation.

2.2.5

I/O operations

All Input/Output operations of VIE ar
e based on the
jQuery Deferred

object, which means that you can attach
callbacks to them either before they run, or also after they've been run.

The operations may either succeed, in which ca
se the
then

callbacks will fire, or be rejected, in which case the
fail

callbacks will fire. Any
then

callbacks will fire in either case.

2.2.6

Dependencies

VIE uses the following JavaScript libraries:



jQuery

for DOM manipulat
ion and
Deferreds



Backbone.js

for entities (models) and collections



Unde
rscore.js

for various JavaScript utilities

Some functionality in VIE additionally uses:



RdfQuery

as a triplestore and for reasoning over rules

2.2.7

Integrations



Create



Google Web Toolkit



Symfony2



Palsu

©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





8

/

23

2.2.8

Using VIE on Node.js

VIE is a CommonJS library that w
orks on both browser and the server. On
Node.js

you can install it with:

npm install vie


Here is a simple Node.js script that uses VIE for parsing RDFa:

var jQuery = require('jquery'); var vie = require('vie');

// In
stantiate VIE

var VIE = new vie.VIE();


// Enable the RDFa service

VIE.use(new VIE.RdfaService());


var html = jQuery('<p xmlns:dc="http://purl.org/dc/elements/1.1/"
about="http://www.example.com/books/wikinomics">In his latest book <cite
property="d
c:title">Wikinomics</cite>,

<span property="dc:creator">Don Tapscott</span>

explains deep changes in technology, demographics and bus
i
ness.</p>');


//

VIE.load({element: html}).from('rdfa').execute().done(function() {


var objectInstance =
VIE.en
tities.get('http://www.example.com/books/wikinomics');


cons
o
le.log(objectInstance.get('dc:title'));

});

2.2.9

Development

VIE development is coordinated using Git.
VIE@IKS

is the canonical "blessed repository",

with actual dev
e-
lopment happening at
VIE@bergie
. Feel free to
report issues

or send
pull requests

i
f you have ideas for pushing
VIE forward. Contributions that i
n
clude their own unit tests appreciated!

Development discussions happen on the
VIE mailing list

and the
#iks

channel on Freenode. See also
VIE on
Ohloh
.

2.2.10

Code organization

VIE source code is inside the
src

directory. Each separate unit of functionality should be handled in its own
file, with the
src/VIE.js

being the entry point to the system.

©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





9

/

23


Build
ing VIE

The VIE library consists of many individual pieces that we merge together in the build process. You'll need
Apache Ant
. Then just run:

$ ant

The built VIE library will appear in the
dist

folder.

Running Unit

Tests

Direct your browser to the
test/index.html

file to run VIE's
QUnit

tests.

Unit tests on Node.js

You need Node.js and
NPM
. Then just run:

$ npm install
--
dev $ npm test

Continuous integration

VIE uses
Travis

for continuous integration. Simply add your fork there and every time you push you'll get the
tests run.





©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





10

/

23

2.3

Semantic Enhancement Engines:
Apache Sta
n
bol

Source:
http://stanbol.apache.org/docs/trunk/components/



Figure 1: The Apache Stanbol Components



Enhancer

and
Enhancement Engines



Entityhub



Contenthub



Ontology Manager



Rules



Reasoners



CMS Adapter



FactStore

Apache Stanbol is built as a modular set of components. Each component is access
ible via its own RESTful web
interface. From this viewpoint, all Apache Stanbol features can be used via RESTful service calls.

Components do not depend on each other. However they can be easily combined if needed as shown by the di
f-
ferent
usage scenarios
. This ensures that the list of used components depend on the specific usage scenario and
not on the Apache Stanbol architecture.

All components are implemented as
OSGi

bundles, components and services. By default Apache Stanbol uses
the
Apache Felix

OSGi environment. However generally we try to avoid the use of Felix specific f
eatures. If you
need to run Stanbol in an other OSGi environment an encounter problems tell us by opening a
JIRA issue

and/or
asking about it on the Stanbol Developer
mailing list
.

For deployment Stanbol uses the
Apache Sling

launcher. While the Stanbol Community maintains different
launcher options including run
-
able JARs
and WAR files we expect users to configure their custom launchers
optimized for their usage scenario. However it os also possible to us Stanbol with other launchers (such as
Apache Karaf
) or to add its bundles to a
ny existing OSGi environment.

Figure 2 depicts the main Apache Stanbol components and their arrangement within the Apache Stanbol arch
i-
tecture.

©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





11

/

23


Figure 2: Apache Stanbol Architecture



The
Enhancer

component together with its
Enhancement Engines

provides you with the ability
to post content to Apache Stanbol and get suggestions for possible ent
ity annotation in return.
The enhancements are provided via natural language processing, metadata extraction and lin
k-
ing named entities to public or private entity repositories. Furthermore, Apache Stanbol pr
o-
vides a machinery to further process this data
and add additional knowledge and links via a
p-
plying rules and reasoning. Technically, the enhancements are stored in a triple
-
graph that is
maintained by
Apache Clerezza
.



The 'Sparql endpoint' gives acc
ess to RDF graphs of Apache Stanbol. This especially includes
the graph with all enhancement results managed by the Apache Stanbol
Contenthub
.



The 'EnhancerVIE' is a stateful inte
rface to submit content to analyze and store the results on
the server. It is then possible to browse the resulting enhanced content items.



The
Rules

component provides you with the me
ans to refactor knowledge graphs, e.g. for
supporting the schema.org vocabulary for search engine optimization.



The
Reasoner

can be used to automatically infer additional knowledge
. It is used to obtain
new facts in the knowledge base, e.g. if your enhanced content tells you about a shop located
in "Montparnasse", you can infer via a "located
-
in" relation that the same shop is located in
"Paris", in the "Île
-
de
-
France" and in "Franc
e".



The
Ontology Manager

is the facility that manages your ontologies. Ontologies are used to d
e-
fine the knowledge models that describe the metadata of content. Additionally,

the semantics
of your metadata can be defined through an ontology.



The
CMS Adapter

CMS Adapter component acts as a bridge between JCR/CMIS compliant
content management systems an
d Apache Stanbol. It can be used to map existing node stru
c-
tures from JCR/CMIS content repositories to RDF models or vica versa. It also provides se
r-
vices for the management of content repository items called
content items

within the
Conte
n-
thub
.



The
Entityhub

is the c
omponent, which lets you cache and manage local indexes of reposit
o-
ries such as DBPedia but also custom data (e.g. product descriptions, contact data, specialized
topic thesauri).



The
Contenthub

is the component which provides persistent document store whose back
-
end
is Apache Solr. On top of the store, it enables semantic indexing facilities during text based
document submission and semantic search together with faceted search cap
ability on the do
c-
uments.



The
FactStore

is a component that let's use store relations between entities identified by their
URIs. This relation between two entities is called a
fact
.


©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





12

/

23

2.4

Methodology



IKS Reference Architecture

Source:
http://www.slideshare.net/fabchrist/introduction
-
to
-
the
-
iks
-
70
-
technology
-
stack


In the Interactive Knowledg
e Stack (IKS) project various software components and services are developed that
are loosely coupled in an open and flexible technology platform for semantic CMS.

In addition to the provision of "software pieces", the project also provides methodical sup
port for building
semantic CMS. In order to adress this topic, we developed a reference architecture for building semantic CMS.

This reference architecture can be used in two different ways. On the one hand, the reference model can be used
to develop a se
mantic CMS from scratch. This can be useful, when a new product is developed or an existing
product is redesigned. The Stanbol software is a reference implementation of our architecture and shows how
this model can used to build software. The following dia
gram shows the comparation between the reference
model and the concrete instantiation.




On the other hand, the architecture provides valuable support for enhancing a "traditional" CMS with semantic
capabilities. In an SCMS the content is stored in a tr
aditional Content Repository and the knowledge about that
content is additionally stored in a Knowledge Repository. Our proposal of an SCMS reference architecture, as
shown in figure below, is designed in such a way that any existing CMS, that has an archi
tecture similar to the
one depicted, can be extended to become an SCMS. This ensures that a CMS can be semantified without any
major changes to the existing CMS. To create an SCMS out of a CMS the traditional CMS content column is
extended by a second know
ledge column for the semantic features in parallel.


©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





13

/

23



To interact with each other both columns are connected at the level of Content Access and Knowledge Access.
The content of an SCMS is stored in the content column. Traditional content repositories ar
e best prepared for
this task. The content is transported from the content column to the knowledge column at the
Content/Knowledge Access layer. For a loosely coupled solution, this could be done via some service
implementation, e.g. RESTful Web Services.
The delivered content can be analyzed by the components of the
knowledge column. The obtained knowledge is stored in the knowledge column. Once the content column needs
additional knowledge regarding some content it can query the content column. On the oth
er hand the knowledge
column can search for new or changed content in the content column.


Slides

from the presentation of the reference architecture at the EMISA Workshop 2011:


File:IKS Ref Architecture.pdf
.


Reference

Fabian Christ, Benjamin Nagel: A Reference Architecture for Semantic Content Management Systems. In M.
Nüttgens, O. Thomas, B. Weber (eds.): Proceeding of the Enterprise

Modelling and Information Systems
Architectures Workshop 2011 (EMISA'11), Hamburg (Germany). GI, LNI, vol. P
-
190, pp. 135
-
148 (2011)




©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





14

/

23

2.5

IKS
Components and their Integration into

CMS Stacks


Source:
http://ww
w.iks
-
project.eu/Demos



2.5.1

Apache Stanbol

Apache Stanbol Online Test Ve
r
sion

Apache Stanbol is an Open Source HTTP
service to help Content M
a
nagement System
developers semi
-
automatically enhance u
n-
structure
d content (text, image, ...) with r
e-
lated ent
i
ties and links.


2.5.2

VIE Framework

VIE

is a JavaScript library for i
m
plementing
semantic interaction in web applic
a
tions

Annotate.js

-

provides in
-
text editing support

Bookmarklet

for live annotation of webco
n-
tent

VIE autocompl
ete widget

for easy entity
lookup defin
i
tion for form fields

2.5.3

Createjs



Createjs from the Midgard Project is a co
m
prehensive web editing interface for Content Management Systems. It
is des
i
gned to provide a modern, f
ully browser
-
based HTML5 environment for managing content. Create can be
adapted to work on content management ba
c
kends.

©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





15

/

23

2.5.4

Hallo editor



A d
i
straction
-
free writing for the web. Hallo is the simplest web editor imaginab
le. Instead of cluttered forms or
toolbars, you edit your web content as it is. Just you, your web design, and your content. Actually, this text
you're reading has Hallo loaded. To try it out, just click here and start writing. If you want to make more co
m-
prehensive modifications, just select some text.

2.5.5

ViePalsu



Palsu is an online collaborative meeting tool. Instead of each participant keeping their own meeting notes, we
transform the meeting to a conversatio
n where everybody can add their remarks as the meeting progresses. Me
e-
ting notes can be used to add tasks and mention people related to the meeting.

©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





16

/

23

2.5.6

Terkait


terk
ait analyzes semantic objects on a webpage and presents related content.



terkait uses semantic services to analyze the content on your webpage in order to present related co
n-
tent, e.g., images, videos or news articles to you. By default, the top 5 releva
nt entities that have been
extracted are shown and filtered for persons and places which can be configured through the options
pane.






©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





17

/

23

2.5.7

Aemoo

Aemoo supports exploratory search over the Web. Throu
gh a simple keyword
-
based search interface, users can
query Aemoo about the linking network of any entity, which is collected by aggregating knowledge from diverse
sources such as linked data, Wikipedia, Twitter, and Google New




©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





18

/

23

2.5.8

Polymedia Multimedia Showcase



During 2011 Polymedia was acquired by KIT digital.


This demonstrator has been designed and developed as part of the industrial showcase work in IKS. The use case
workflow foresees

two actors: the publisher, using the Polymedia/KIT Cloud Video Editor in order to prepare
the chosen video by adding semantic tags


and the user, consuming the considered video thanks to a semantic
player capable of re
-
producing the multimedia content whi
le interpreting the tags in real
-
time. The combination
of both these features will be used to present pictures or articles linked to the current scene. This demonstrator
currently leverages on the following components developed in IKS: Semantic Video Annot
ation Services (Editor
+ Player), VIE Image widget (Player)
















©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





19

/

23

2.5.9

Pisano eTourism Showcase



This website shows the integration of semantic technologies into the packagemaster system, in terms of a tourist
use
-
case scenario.

The new semantic funtions should help product managers to analyse hotel informations and tour descriptions,
and from this retrieve the information automatically.

The objective is to generate additional information simply and to save tour att
ributes. An important goal is to
reduce the time spent on data management by product managers and to improve the quality of tour content. The
Demonstrator is a prototype packagemaster system with IKS Components.. It shows the capabilities of semantic
text
enhancements with the Apache Stanbol software and new onsite editing functionality with the VIE Widget.










©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





20

/

23

2.5.10

The "Intelligent Bathroom"

Within the scope of the project IKS
an "intelligent bathroom" has been developed at chair ISS in cooperation
with several partners. The bathroom, which has been developed as Ubiquitous Information System (
UIS
), stands
for the vision of interactive knowledge. The following videos, slide shows and posters present the prototype and
provide an insight into the technical backgrounds.

The intelligent bathroom merges enhanced content
-

and knowledge
-
management
-
tec
hnologies with dev
e-
lopments from coming of the field of "ambient intelligence" and the internet of things. Therefore a new des
i-
gning method (SiDIS) for interactive, knowledge based environments has been developed. Thus, an intelligent
environment was creat
ed, which is supported by interactive knowledge resting upon previously defined requir
e-
ments.

German Version:
http://iss.uni
-
saarland.de/de/projects/intelligent
-
bathroom/












©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





21

/

23

2.5.11

Nuxeo (Horizontal application of IKS)


Nuxeo has been integrated to leverage Apache Stanbol services for entity indexing, detection and automated
linking in the context of the News and Media Industry. Thi
s work is demonstrated online with content provided
by the Agence France Press and integrated with tools from our Partner Temis:

Try It!
http://temis.demo.nuxeo.com

Access codes: (demo / demo)

This demo is in pa
rticular leveraging most of the Stanbol Enhancer and EntityHub infrastructure.




















©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





22

/

23

2.5.12

Semantic Indexing and Search with Apache Stanbol



In this demo, we will introduce our semant
ic indexing and search demonstration that we have built in the scope
of IKS project. In very general terms, this demonstration shows semantically enhancement of already existing
documents contained within a content management system(CMS); semantic indexing

of those documents cons
i-
dering characteristics of a particular domain which the CMS documents belongs to and search over the indexed
documents. Before going into the details of the demonstration, we would like to give a brief overview about the
IKS and Ap
ache Stanbol projects. After that we will give detailed steps of the demonstration.




©

IKS

Consortium


2012


Del iverabl e

7.4

IKS


Overview of Material for Indu
stri al Trai ning December
2012





23

/

23

3

Background Notes

At the time of writing the IKS proposal (in early 2008), we envisaged that industrial take
-
up of IKS
technology would have to be based on “spreading th
e word” from some

center of IKS
related
knowledge


and we were primarily thinking of the applied research institutes within the consort
i
um to
form that core group. Accordingly, we split the task of developing training material along the line of
academic v
s. industrial training. Furthermore,
we assumed then, that recruiting early adopters would
also require the early provision of such material. Therefore, we planned industrial training to develop
before
academic training
. Things developed differently:


Firs
tly, with the help of industrial partners Day Software (later Adobe), we went on a path that led us
to incubating the main developments of IKS under the name of “Stanbol” at the Apache Software
Foundation. Secondly, it turned out that academic partners dev
eloped a great deal of training materials
e.g. for lectures and summer schools so that the originally planned, lead by provision of industrial m
a-
terial was actually reversed. Thirdly,
with the move to Apache,
the industrial aspect of
IKS developed
a much l
arger,
community driven dynamic th
an we
had
anticipated. This made developing industrial
training materials both more dif
ficult and less useful, with open source development in full flow.


At the third year review, the reviewers made the following recommen
dation concerning WP7:

The main deliverable in this period for this work package has been the D7.1 Book publication on

S
e-
mantic Technologies in CMS. Significant work was also evident in development of teaching

materials
in order to assist with the promotio
n of IKS and indeed Semantic CMS into the

curriculum of univers
i-
ty and research organisations across the world. The material is of a high

quality and includes slides,
exercises and some tutorials. The reviewers felt that the inclusion of

more online demons
trations
would round off the material well. Teaching material looks very

complete and professional and the
developers are to be commended. However, perhaps the level

of the material could be explored in o
r-
der to present different flavours for undergraduate

versus

postgraduate course provision.

The indu
s-
trial material has not been d
e
veloped to any extent at present. The reviewers feel that

the purpose of
industrial training m
a
terial is not clear and that the consortium should re
-
validate

the purpose of this
material. It would be better, perhaps, to develop use case information for

prospective Semantic CMS
adopters. This could be an e
-
book or multimedia web resource
.


In order t
o keep the momentum that has been gathered in the development of Apache Stanbol and

the
front
-
end libraries

vie.js and create.js

on github,
during the second half of 2012 we

shifted surplus e
f-
fort from developing material
for Industrial Training to the more tangible hands
-
on support of the d
e-
veloper communities on these pla
t
forms.


Another suggestion of the reviewers was
to have some flagship event, towards the end of the project.
We therefore accepted an in
vitation,

to co
n
tri
b
ute to the SME in
i
ti
a
tives of the E
u
r
o
p
e
an Co
m
mi
s
sion,
and

co
-
organised
t
o
gether wi
th co
l
leagues from the Linked Open Data comm
u
nity
,
a hands
-
on d
e
ve
l-
o
p
ers wor
k
shop and hack
a
thon at the Eur
o
pean D
a
ta Forum 2012 in C
o
penhagen, pr
e
senting the latest
showcases and tools of Apache Sta
n
bol,