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.
http://www.lassoproject.org/
3. 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 www.lassoproject.org 3
4. 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 www.lassoproject.org 4
7. Router 09.09.11 www.lassoproject.org 7 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
9. Registry 09.09.11 www.lassoproject.org 9 Lists the orchestra of available components E.g. router, triplificators, elicitation components etc. Registration is done upon system start
11. Knowledge Base 09.09.11 www.lassoproject.org 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
13. Notificator 09.09.11 www.lassoproject.org 13 Behind the scenes: Equinox implementation of the OSGI Event Administration Service Provides sending/receiving notifications Between bundles Synchronous/asynchronous fashion
15. Triplificator 09.09.11 www.lassoproject.org 15 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
17. Elicitation Components 09.09.11 www.lassoproject.org 17 Get active upon notifications sent by other components Execute queries over the knowledge space Sparql 1.1 Query Language Support Generate higher level concepts
19. Sink 09.09.11 www.lassoproject.org 19 End of a processing chain Transfer knowledge outside “Refinder Sink”: Send information about resource similarity Via HTTP Post Payload contains the RDF graph
21. Orchestration 09.09.11 www.lassoproject.org 21 Application developer defines Set of components Initialization of components Shutdown of components Each application has its own orchestration
27. Future work 09.09.11 www.lassoproject.org 27 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