Lasso context-elicitation-framework- demo


Published on

Project LASSO intends to deploy, improve and extend Linked Data (LD) infrastructure in three different use cases. Central feature of all use cases is a lookup service which helps to augment already existing, formalized knowledge with facts from the Linked Open Data (LOD) cloud. These three use cases are Semantic Desktop, Enterprise Collaboration and Inspiration Services. Currently available systems in all of these application domains are sparsely using data from the Semantic Web.

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Lasso context-elicitation-framework- demo

  1. 1. KnowSe 2.0Context Elicitation Framework<br />Knowledge Management Institute<br />TU Graz<br />Contact:<br />09.09.11<br /><br />1<br />
  2. 2. Motivation<br />09.09.11<br /><br />2<br />„Can we build an open source framework which easily allows to explore the current situation the user is in?“<br />
  3. 3. Collect Data<br />From different sources<br />Using various formats<br />Possible sources?<br />Sensors, crawlers, agents…<br />… which provide user related data<br />For example:<br />Software sensors capturing user machine interactions<br />e.g. mouse clicks, keyboard input<br />Hardware sensors capturing physical conditions<br />e.g. heartbeat pulse, body temperature<br />09.09.11<br /><br />3<br />
  4. 4. Infer Knowledge<br />Apply context elicication methods<br />Depend on the application<br />Take low-level data and generate higher level concepts<br />Use knowledge<br />For further analysis<br />For visualization<br />09.09.11<br /><br />4<br />
  5. 5. ArchitecturalBuilding Blocks<br />09.09.11<br /><br />5<br />
  6. 6. Generic Framework Components<br />09.09.11<br /><br />6<br />
  7. 7. Router<br />09.09.11<br /><br />7<br />Concurrent request handling<br />Data is dispatched for interested triplificators only<br />The others remove themselves from the list of candidates<br />As soon as data is available, data is read and dispatched<br />One or more interested triplificators possible<br />If none is interested connection request is not processed<br />
  8. 8. Generic Framework Components<br />09.09.11<br /><br />8<br />
  9. 9. Registry<br />09.09.11<br /><br />9<br />Lists the orchestra of available components<br />E.g. router, triplificators, elicitation components etc.<br />Registration is done upon system start<br />
  10. 10. Generic Framework Components<br />09.09.11<br /><br />10<br />
  11. 11. Knowledge Base<br />09.09.11<br /><br />11<br />Storage format: RDF<br />Behind the scenes: Sesame as RDF Framework API<br />Modes of editing:<br />Triples level<br />Model level<br />Model level supports working with ontologies in an object oriented fashion<br />Cross language compiler converts OWL into Java interfaces<br />ModelEditor provides a simple way of accessing entities in the ontology<br />
  12. 12. Generic Framework Components<br />09.09.11<br /><br />12<br />
  13. 13. Notificator<br />09.09.11<br /><br />13<br />Behind the scenes: Equinox implementation of the OSGI Event Administration Service<br />Provides sending/receiving notifications<br />Between bundles<br />Synchronous/asynchronous fashion<br />
  14. 14. ApplicationDependend Framework Components<br />09.09.11<br /><br />14<br />
  15. 15. Triplificator<br />09.09.11<br /><br />15<br />Accept or deny requests from router<br />Multithreaded request processing<br />Converts data into triples<br />Transaction based storage<br />If successful then commit<br />Otherwise rollback<br />Broadcasts notifications via Notificator component<br />
  16. 16. ApplicationDependend Framework Components<br />09.09.11<br /><br />16<br />
  17. 17. Elicitation Components<br />09.09.11<br /><br />17<br />Get active upon notifications sent by other components<br />Execute queries over the knowledge space<br />Sparql 1.1 Query Language Support<br />Generate higher level concepts<br />
  18. 18. ApplicationDependend Framework Components<br />09.09.11<br /><br />18<br />
  19. 19. Sink<br />09.09.11<br /><br />19<br />End of a processing chain<br />Transfer knowledge outside<br />“Refinder Sink”:<br />Send information about resource similarity<br />Via HTTP Post<br />Payload contains the RDF graph <br />
  20. 20. ApplicationDependend Framework Components<br />09.09.11<br /><br />20<br />
  21. 21. Orchestration<br />09.09.11<br /><br />21<br />Application developer defines<br />Set of components <br />Initialization of components<br />Shutdown of components<br />Each application has its own orchestration<br />
  22. 22. Wiki Visualization<br />09.09.11<br /><br />22<br />
  23. 23. Wiki Visualization<br />09.09.11<br /><br />23<br />
  24. 24. Wiki Visualization<br />09.09.11<br /><br />24<br />
  25. 25. Wiki Visualization<br />09.09.11<br /><br />25<br />
  26. 26. Wiki Visualization<br />09.09.11<br /><br />26<br />
  27. 27. Future work<br />09.09.11<br /><br />27<br />Develop first release candidate<br />Make it publicly available<br />as Open Source Software<br />We want to provide a ready to use set of components<br />Including sensors<br />Visualizations<br />And more to come<br />