Interactive Knowledge Stack - A Software Architecture for Semantic Content Management Systems

Interactive Knowledge Stack

A Software Architecture for

Semantic

Content Management Systems

Fabian Christ

July 2, 2012

Interactive Knowledge Stack - IKS

• Started in January 2009 – ends in December 2012

• Funded in part by a €6.58m grant from the European Union

• Consortium of 7 research and 6 industrial partners

Fabian Christ : IKS - A Software Architecture for Semantic CMS 2

IKS Project Goals

• A software architecture for semantically enabled

content management systems.

• An open-source community to bring semantic technologies

to content management system platforms.

Presentation &

Interaction

Knowledge

Representation

and Reasoning

Semantic Lifting

Persistence

User Interface

Knowledge

Repository

Knowledge

Models

Reasoning

Semantic User Interaction

Content

Data Model

Content

Repository

Knowledge

SCMS -

Semantic Content Management System

tratio

Knowledge

Extraction Pipelines

Content

Management

Semantic User Interface

Content Access Knowledge Access

Service Layer

RESTful Interface

Component Layer

Apache

Stanbol

Reasoners

Apache

Stanbol

Enhancer

Apache

Stanbol Rules

Apache

Stanbol

Ontology Manager

Apache

Stanbol

ContentHub

Apache

Stanbol

EntityHub

Apache

Stanbol

FactStoreStanbol

Enhancement

Engines Apache

Stanbol

CMS Adapter

IKS Features

• User Interface Library

& Widgets

• Content

Enhancement

• Entity

Management

• Ontology Management & Reasoning

• Indexing & Search

Linked

5 Fabian Christ : IKS - A Software Architecture for Semantic CMS

Short Demo of IKS 7.0

Content Enhancement Demo

with Apache Stanbol

and a VIE-based user interface.

IKS Demo Server

http://dev.iks-project.eu

Influence Factors

on the IKS Software Architecture

Functionality

Technology

People

• Implement functional requirements

• Use state-of-the-art web technologies

• Support semantic web standards

• Support distributed development

where people can work independently

The design of the IKS software architecture

is influenced by three factors:

Functionality

What is Semantic CMS?

Traditional CMS Semantic CMS

Atomic Unit • Document • Entity

Meta Data as • Strings • Defined Entity

• Linked Entities

Search for • Strings • Entities and their

relations

Manage • Documents and

their workflow

• Entities and their

domain model

Functionality

Top-Down Requirements

Requirements Analysis

Architecture

Fabian Christ : IKS - A Software Architecture for Semantic CMS

Functionality

Functional Layers from the

Description of Work

Presentation and

Interaction

Semantic Lifting

Knowledge

Representation

and Reasoning

Persistence

Functionality

Content Management

Functionality

User Interface

Content

Data Model

Content

Repository

tratio

Content

Management

Content Access

Functionality

Knowledge Management

Functionality

Presentation &

Interaction

Knowledge

Representation

and Reasoning

Semantic Lifting

Persistence

Knowledge

Repository

Knowledge

Models

Reasoning

Knowledge

Knowledge Access

Functionality

Design

Presentation &

Interaction

Knowledge

Representation

and Reasoning

Semantic Lifting

Persistence

User InterfaceK

tratio

Knowledge

Repository

Knowledge

Models

Reasoning

Content

Data Model

Content

Repository

Knowledge

Functional Building Blocks

tratio

Knowledge

Content

Management

Semantic User Interface

Content Access Knowledge Access

Functionality

Influence Factors

Functionality

Technology

People

• Use state-of-the-art web technologies

• Support semantic web standards

• Support distributed development

Technology

Functionality • Content enhancement, entity management,

ontology management, reasoning, …

Bottom-Up

Technology Development

INTERPRET

Persistence

Store KReS

Technology

Do Not Replace –

But Extend

• No need to replace existing systems for content management

• IKS components offer service oriented integration

Traditional

Technology

Extend by Using Semantic Services

Technology

Service Orientation

• The IKS offers RESTful web service interfaces

• Each feature is available via a simple HTTP request

Reasoner

Ontology Manager

Entity ManagerEnhancer

Search

Open Linked Data

Technology

RESTful Interfaces

• “Representational State Transfer (REST) [is an] architectural

style for distributed hypermedia systems.”

Key Aspects

• Stateless services

• Resource oriented organization of data and services

Source: Roy Thomas Fielding, Architectural Styles and the Design of Network-based Software

Architectures, PhD Thesis, http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm, 2000

Technology

IKS/enhancer

Client

Resource

Stateless

Service Call

Representation

of Resources

• REST applied to HTTP

• Each resource has an URI

• By accessing the URI the resource can be retrieved in different

representations (formats)

GET /enhancer Host: localhost:8080 Accept: text/html

GET /enhancer Host: localhost:8080 Accept: application/json

Technology

RESTful Integration

• RESTful interfaces make integration easy

• Required technology for sending HTTP requests is available in

any traditional CMS

• Support for standards like the Resource Description Framework

(RDF), JSON for Linked Data (JSON-LD)

Traditional

Technology

Request

HTTP Response as RDF,

JSON-LD

Technology

Influence Factors

Functionality

Technology

People • Support distributed development

Technology

People

• Content enhancement, entity management,

• RESTful HTTP interfaces

• Standards like RDF, JSON-LD, …

Development Team

• Distributed

– Germany, Turkey, Italy, Austria,

Swiss, France, (Finland)

• Different Interests

– Researchers want to follow their

own research topics

– Industrial partners want

working software

– No central lead

• Know how

– Java, JavaScript, Web technologies

– Semantic web standards

People

OSGi for Flexibility

• IKS components are OSGi bundles

People

»bundle«

Enhancer

Export

Import

»bundle«

Enhancement

Engine

»bundle«

Entityhub

»bundle«

Contenthub

»bundle«

Ontology

Manager

R REST API

Team 1 Team 2

Team 3 Team 4 Team 5

Common Basis

»bundle«

Library A

»bundle«

Library B

»bundle«

Library C

»bundle«

Entityhub

»bundle«

Contenthub

»bundle«

Ontology

Manager

Dependency

Management

People

Different Release

Configurations People

»bundle«

Entityhub

»bundle«

Contenthub

»bundle«

Ontology

Manager

Variant 1

»bundle«

Reasoner

»bundle«

Enhancer

Variant 2

Summary on Influence Factors

Functionality

Technology

People

• Content enhancement, entity management,

• RESTful HTTP interfaces

• Standards like RDF, JSON-LD, …

• OSGi bundles for distributed development

• OSGi bundlists for releases packaging

The IKS software architecture for

semantic content management systems supports

IKS Software Architecture

Bundle Layer

RESTful Service Layer

Apache

Stanbol

Reasoners

Apache

Stanbol

Enhancer

Apache

Stanbol Rules

Apache

Stanbol

Ontology Manager

Apache

Stanbol

ContentHub

Apache

Stanbol

EntityHub

Apache

Stanbol

FactStore

Stanbol

Enhancement

Engines

User Interface LayerVIE

Widgets

Apache

Stanbol

CMS Adapter

Library A Library B ...

Common

Bundles

Integration Patterns at Service Level

• Search based on enhanced content

1. Apache Stanbol Entityhub to specify entities of interest

2. Apache Stanbol Enhancer to retrieve metadata for entities

3. Apache Stanbol Contenthub storage service to store content

plus enhancements

4. Apache Stanbol Contenthub keyword search service to search

for previously stored content and enhancements

»bundle«

Entityhub

»bundle«

Contenthub

»bundle«

Enhancer

Client

3. + 4.

Iterative Development

INTERPRET

Persistence

Store KReS

8.0 Middle-

Requirements Analysis

Architecture

IKS 3.0, 4.0, …, 7.0

Lessons Learned

• Each partner was able to

contribute his functionality

• No central lead

• Ship stable configurations

• Allow lab mode for

components

• Adopters select

functionality they like to

• Modularity big plus from

industrial perspective

• Impact

• Less integration at

component level

• No shared storage

• Sometimes duplicate

functionalities

• Collection of features

instead of a consistent

s-lab – Software Quality Lab

Universität Paderborn

Zukunftsmeile 1

33102 Paderborn

Tel.: (05251) 60 5390 / 5391

http://s-lab.upb.de

info@s-lab.upb.de

Thank you

for your attention.

Follow me @fctwitt

Interactive Knowledge Stack - A Software Architecture for Semantic Content Management Systems

Technology

An Interactive Approach to Semantic Modelingf Indoor Scenes … · 2014-09-05 · An Interactive Approach to Semantic Modeling of Indoor Scenes with an RGBD Camera Tianjia Shao Weiwei

Towards Interactive File Browsing and Searching using ...€¦ · Towards Interactive File Browsing and Searching using Semantic Hierarchy Pedro Teixeira, Daniel Gonçalves and Manuel

DeepSI: Interactive Deep Learning for Semantic Interaction

Growing Semantic Grammars Marsal Gavaldà Carnegie Mellon University and Interactive Systems August 4, 2000

Semantic framework for interactive animation generation ... · Semantic framework for interactive animation generation and its ... (RamaprasadandPapagari 2009) ... 22:149–165 1

From Interactive to Semantic Image Segmentation

ISWC 2012 - Industry Track - Linked Enterprise Data: leveraging the Semantic Web stack in a corporate IS environment

Hazel: Semantic Foundations for Interactive Programming Tools · Hazel: Semantic Foundations for Interactive Programming Tools Cyrus Omar Carnegie Mellon University IBM PL Day 2016

Defining the Data Stack - Interactive Advertising Bureau · Your data stack will likely be composed of a combination of first, second and third party data. What percentage each takes

Filtering & Selecting Semantic Web Services with Interactive Composition Techniques

IKS Public Report 2010 - CORDIS · IKS Public Report 2010 “In only two years, the Interactive Knowledge Stack (IKS) project has released its first working demo of a semantic knowledge

The Interactive Dining Table - Semantic Scholar...Large-scale interactive surfaces, such as interactive tables or whiteboards, are now a regular sight in research labs, showrooms or

Comparing and Contrasting Semantic Web Stack and XBRL Stackxbrlsite.azurewebsites.net/2017/Library/SemanticWebStack_XBRLStack.pdf · Comparing and Contrasting Semantic Web Stack and

Structured Dynamics' Semantic Technologies Product Stack

POI Pulse: A Multi-Granular, Semantic Signatures …hu/papers/poipulse.pdfPOI Pulse: A Multi-Granular, Semantic Signatures-Based Information Observatory for the Interactive Visualization

Agile data science: Distributed, Interactive, Integrated, Semantic, Micro Service

Semantic Web - STI Innsbruck · 5 Web2.0 services + ONLIM APIs (separate slideset) 6 Semantic Web 7 Semantic Web Service Stack (WSMO, WSML, WSMX) 8 OWL-S and the others 9 Semantic

1 An Interactive Visual Analytic Tool for Semantic

IKS – Interactive Knowledge Stack for Semantic Content ... · 4/29/2010 · | IKS has 6 SME CMS technology providers | 4 of them are fully based on open source CMS The CMS Vendors

PragmaticWeb 4.0 - Towards an active and interactive Semantic Media Web