An Extensible Semantic Wiki Architecture

An Extensible Semantic Wiki Architecture

The Semantic Wiki Extension Space

Jochen Reutelshöfer, Fabian Haupt,Florian Lemmerich and Joachim Baumeister,

University of WürzburgGermany

Semantic Wiki

• What is a Semantic Wiki?– „Semantically enriched“ content– Allowing for some additional functionality beyond reading

and browsing– Examples: Semantic MediaWiki, KIWI, SWIM, AceWiki,

SweetWiki,…• Problem:

– Wiki means: fast and simple

– enriching the content means: …

not so fast and not so simple (any more) ? Danger

Why Extending (Semantic) Wikis?

• Customization: tailored to specific applications– Lowers barriers of usage– Higher efficiency in formalization

• Extension: more complex knowledge management– Problem-solving knowledge, flowchart-editing– Advanced editing support

• Exploitation of further formalization techniques– NLP, Text Mining– Customized to a startup corpus

How Extending Semantic Wikis?

?

The Semantic Wiki Pipeline

Dimensions of Extensions

Knowledge Formalization

Comp.

ContributingUser

Meta-DataStorage

Reasoning Comp.

Knowledge Presentation

Comp.

ConsumingUser

Knowledge Formalization

Extension

Reasoning Extension

Knowledge Presentation

Extension

Semantic Wiki Extension Space

Presentation

Formalization

Reasoning

Formalization extension

Core functionality(minimal)

The KnowWE Minimal Core

Presentation

Reasoning

Formalization

Sesame2

+ OWLIM

Inline SPARQL Queries

Basic Markups

Extensions

Application: Hermes Wiki

• Developers: Chair of ancient greek history, 4-6 people (University of Würzburg)

• Task: Connecting explaining text, formalized time events and historical sources

• Purpose: Exam preparation for students• Content: > 500 pages, ~ 600 time events, >100

Google-maps, > 350 concepts (historical characters, places, peoples, rites…)

Article about the conquest of Alexander the Great

32 time events

In Wiki Source…

In Wiki Source…

Title ImportanceDate

Source

Description

Hermes OntologyConcept

Character Geogr. Location

Politician God Writer Historian Dynasty

TimeEvent

Source

Title

Description

ImportanceDate

describedBy locatedAt

hasDate

involves

Decorating Semantic Wikis

1. Hide/Disable Basic Functionality2. Add custom Knowledge Formalization and

Presentation Extensions tailored exactly to task and mental model of the user

Result: People don‘t need to know about SWs

Formalization Component:-Different markups-Visual editorsFor:-Rules-Decision Trees-Covering Models

Presentation Component:- Different interview methods

The d3web Extension

The d3web Extension

Knowledge Formalization

Extension

Reasoning Extension

Knowledge Presentation

Extension

-Markups-Tables-Editors

d3web reasoningengine

Interview methods

PosTagging Extension

The Semantic Wiki Pipeline

Knowledge Formalization

Extension

?

Multimodal Knowledge

• Knowledge of organizations is present in different shapes but referring to the same objects and relations of the domain

XML

Tabular dataText

Segmented Text

Flow charts

Functional Models

Rules

Cases

LogicImages

Semantic Wiki:

Authoring and Reasoning with knowledge • in different formats• from different authors • at different degrees of formality describing one topic.

Example page Clogged Air Filter from a car diagnosis knowledge system

KnowWE – A Semantic Wikifor Knowledge Engineering

Try out:http://knowwedemo.informatik.uni-wuerzburg.de

THANK YOU

Extension Points

• Modules– Introducing new „types“ (new markup)

• TagHandlers• Actions

– Actions initiated by user (e.g., transformation/refactoring of content)

• Renderers/Editors– Visual representation of types

• Revise Subtree Handlers– Traversation of content tree after save (e.g., meta-data

extraction, syntax check)

Conclusions

• Knowledge Wiki Environment• KnowWE Core version

(without any extension) ready for running/extension development

• Latest code on sourceforge• Ongoing development (driven

by the d3web-extension)• Basic functionality improving

with JSPWiki

KnowWE CoreIntroduce properties/hierarchies:

Presentation component:

Formalization components: