lasso context-elicitation-framework- demo

www.lassoproject.org 1

KnowSe 2.0Context Elicitation Framework

Knowledge Management InstituteTU Graz

Contact: [email protected]

09.09.11


Motivation

09.09.11

„Can we build an open source

framework which easily allows to

explore the current situation the user is

in?“


Collect Data

• From different sources• Using various formats• Possible sources?– Sensors, crawlers, agents…– … which provide user related data

• For example:– Software sensors capturing user machine interactions

• e.g. mouse clicks, keyboard input

– Hardware sensors capturing physical conditions• e.g. heartbeat pulse, body temperature

09.09.11


Infer Knowledge

• Apply context elicication methods• Depend on the application• Take low-level data and generate higher level

concepts• Use knowledge– For further analysis– For visualization

09.09.11


Architectural Building Blocks

09.09.11


Generic Framework Components

09.09.11


Router

09.09.11

• Concurrent request handling• Data is dispatched for

interested triplificators only• The others remove

themselves from the list of candidates

• As soon as data is available, data is read and dispatched

• One or more interested triplificators possible

• If none is interested connection request is not processed



09.09.11


Registry

09.09.11

• Lists the orchestra of available components

• E.g. router, triplificators, elicitation components etc.

• Registration is done upon system start



09.09.11


Knowledge Base

09.09.11

• Storage format: RDF• Behind the scenes: Sesame as

RDF Framework API• Modes of editing:

– Triples level– Model level

• Model level supports working with ontologies in an object oriented fashion

• Cross language compiler converts OWL into Java interfaces

• ModelEditor provides a simple way of accessing entities in the ontology



09.09.11


Notificator

09.09.11

• Behind the scenes: Equinox implementation of the OSGI Event Administration Service

• Provides sending/receiving notifications– Between bundles– Synchronous/asynchronous

fashion


Application Dependend Framework Components

09.09.11


Triplificator

09.09.11

• Accept or deny requests from router– Multithreaded request

processing

• Converts data into triples• Transaction based storage

– If successful then commit– Otherwise rollback

• Broadcasts notifications via Notificator component



09.09.11


Elicitation Components

09.09.11

• Get active upon notifications sent by other components

• Execute queries over the knowledge space– Sparql 1.1 Query Language

Support

• Generate higher level concepts



09.09.11


Sink

09.09.11

• End of a processing chain• Transfer knowledge outside• “Refinder Sink”:

– Send information about resource similarity

– Via HTTP Post– Payload contains the RDF

graph



09.09.11


Orchestration

09.09.11

• Application developer defines– Set of components – Initialization of components– Shutdown of components

• Each application has its own orchestration


Wiki Visualization

09.09.11


Future work

09.09.11

• Develop first release candidate

• Make it publicly available– as Open Source Software

• We want to provide a ready to use set of components– Including sensors– Visualizations– And more to come

lasso context-elicitation-framework- demo

Technology

generic framework components09

elicitation components09

wiki visualization09

open source framework

analysisfor visualization09

software sensors

applicationtake lowlevel

knowledge spacesparql