1 / 36

Personalization in the EPOS project

Personalization in the EPOS project. Leo Sauermann, Andreas Dengel, Ludger van Elst, Andreas Lauer, Heiko Maus, Sven Schwarz DFKI GmbH 12.06.2006. persona created using http://www.sp-studio.de/. Leo Sauermann. 1: no personalization without the person.

ulema
Download Presentation

Personalization in the EPOS project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Personalization in the EPOS project Leo Sauermann, Andreas Dengel, Ludger van Elst, Andreas Lauer, Heiko Maus, Sven Schwarz DFKI GmbH 12.06.2006 persona created using http://www.sp-studio.de/ Personalization in EPOS, SWP06, Budva 12.06.2006

  2. Leo Sauermann Personalization in EPOS, SWP06, Budva 12.06.2006

  3. 1: no personalization without the person Personalization in EPOS, SWP06, Budva 12.06.2006

  4. 2: no person without the subjective data of the person(from the computer’s perspective) Personalization in EPOS, SWP06, Budva 12.06.2006

  5. what do I do with this e-mail? where is Peter? Applications, data, web, trust, ontologies, … Paul Semantic Web • Results of the EPOS project Personalization in EPOS, SWP06, Budva 12.06.2006

  6. Paul Szenario of EPOS • Knowledge Worker „Paul“ using Desktop PC • Problem: Data about single ideas are stored in several applications and without context Files ↔ Emails Semantic Desktop Personalization in EPOS, SWP06, Budva 12.06.2006

  7. dc:language = AEHS • Adaptive Educational Hypermedia System AEHS • Document Space DOCS • User Model UM • Observations OBS • Adaptation Component AC Personalization in EPOS, SWP06, Budva 12.06.2006

  8. Three contributions • A representation of the user’s personal information items, including e-mails, files, and other data sources using RDF„native resources“ = DOCS • A representation of the user’s mental model in a formal representation, using several layered ontologies.„PIMO“ • A desktop service to capture the current actions of the user, representing the actions using RDF and then calculating the current context of the user.„Context Server“ = OBS • UM = DOCS + PIMO + OBS • Adaptive Applications Personalization in EPOS, SWP06, Budva 12.06.2006

  9. PIMO = Personal Information Model Personalization in EPOS, SWP06, Budva 12.06.2006

  10. From native structures to PIMO • Native data is expressed in RDF • DOCS • RDF/S vocabularies like foaf, vCard, Dublin Core • data + structures • Personal Information Model PIMO • Personal Concepts • Topics • Places • People • Types • Workflow • with relations to files and folders Personalization in EPOS, SWP06, Budva 12.06.2006

  11. PIMO isThe “personal ontology” • “shared” across applications • filled from DOCS, Company ontologies and domain ontologies • used by the – user • creates instances • creates classes & properties (on the fly) • annotates Personalization in EPOS, SWP06, Budva 12.06.2006

  12. PIMO Store adapter to RDF matchingto ontology RDF Database PIMO is filled • automatically from data aperture.sf.net (check it out!) Data Paul‘s files & e-mails Personalization in EPOS, SWP06, Budva 12.06.2006

  13. PIMO used and extended Personalization in EPOS, SWP06, Budva 12.06.2006

  14. Rep Lang basic superclasses Thing SystemItems PIMO ontology languages • PIMO-Basicdefines the basic language constructs. • PIMO-UpperA domain-independent ontology defining abstract sub-classes of Thing. • PIMO-Mid: More concrete sub-classes of upper-classes. The EPOS mid-level ontology serves to integrate various domain ontologies and provides classes for Person, Project, Company, etc. dfki.de/ont/pim/pimo domain-independent SemDesk Upper Level Person Role Time Document Organization ontology imports SemDesk Mid-Level domain-independent, adapted to Semantic Desktop and Nepomuk Contract Manager Project Offer Company Message Personalization in EPOS, SWP06, Budva 12.06.2006

  15. PIMO ontology languages • Domain ontologiesA set of domain ontologies where each describes a concrete domain of interest of the user. The user’s company and its organizational structure may be such a domain, or a shared public ontology. dfki.de/ont/pim/pimo Domain Model: Bibtech A Organizational Structure Report Heiko Car-Ent EPOS Report56 Personalization in EPOS, SWP06, Budva 12.06.2006

  16. all PIMO ontology layers basic superclasses Rep Lang Thing SystemItems dfki.de/ont/pim/pimo domain-independent SemDesk Upper Level sub-classes Person Role Time Document Organization Native Data Vocabularies representing extracted data in RDF/Smultiple vocabularies ontology imports SemDesk Mid-Level domain-independent, adapted to Semantic Desktop and Nepomuk foaf vCard image Person Image vEvent dublin core Contract Manager Project Offer Company Message aperture.semanticdesktop.org/data Domain Model: Bibtech A Organizational Structure Report Heiko Car-Ent EPOS Report56 Personalization in EPOS, SWP06, Budva 12.06.2006

  17. Paul imports all of them Paul Paul‘s PIMO - Personal Information Model Rep Lang SemDesk Upper Level Native Data Vocabularies SemDesk Mid-Level Domain: Bibtech A Domain: Paul’s company personal information model of one user Imports all other ontologies and defines extensions Ontology side Native Resources PIMO of Person:Paul Paul File X e-mail2 Report41 vCard H Project Z Personalization in EPOS, SWP06, Budva 12.06.2006

  18. User Model • UM = DOCS + PIMO + OBS • To capture a user model, we need to know • PIMO the categories/model of the user • DOCS the documents/e-mails attached to the categories • OBS the current context of the user • This holistic user model can now be used for several personalized applications Personalization in EPOS, SWP06, Budva 12.06.2006

  19. Bayesian Network Wf Task Wf Task PIM Basic PIM Upper TaCo PIM MidDFKI KM UA UA UA PIMMaus Domain Domain NOP NOP NOP NOP NOP Paul Context Service • Plugins gather user actions • Elicitation of task concepts • Notification of GUI Personalization in EPOS, SWP06, Budva 12.06.2006

  20. Context Representation • Context in EPOS • context of a knowledge worker • context shall support (personal) knowledge management • Contextual elements (CEs) • relevant documents, topics, places, actions, tasks, organizational entities, … • from the user's DOCS and PIMO • not alien data, but known, familiar entities and structures • Service Oriented Architecture • ContextService • gathers events using RDF messages from Plugins • represents context as RDF model, using the PIMO S. Schwarz. A context model for personal knowledge management. In Proceedings of the IJCAII WS. on Modeling and Retrieval of Context, Edinburgh, 2005. Personalization in EPOS, SWP06, Budva 12.06.2006

  21. Applications Personalization in EPOS, SWP06, Budva 12.06.2006

  22. Context Assistance • Sidebar • can be switched off • shows current context • documents • people • projects • topics • changes dynamically • use: open related information, pro-active, non-obtrusive assistance system Personalization in EPOS, SWP06, Budva 12.06.2006

  23. PIMO of Paul doc:… EPOS … Project:EposEPOS, DFKI,Maus, … = Application: Drop Box • Helps filing information • uses PIMO structures concepts and folders • uses DOCS for text similarity • Knows the users model and istrained by using it • process flow • files are stored into a Drop-Box folder • files are text-analysed and possible target folders are suggested • Drop-Box user interface shows • user selects a folder, classify • files are moved and classified • not used, but obvious:OBS – current context Personalization in EPOS, SWP06, Budva 12.06.2006

  24. Semantic Search • search over EPOS data (PIMO) • can be personalized using rules SPARQL queries • example # found something? -> infer other representations via SPARQL (?hit retrieve:item ?x) -> querySparql('CONSTRUCT { ?x pimbasic:hasOtherRepresentation ?y } ') # found a project? -> also show members (?hit retrieve:item ?project), (?project rdf:type org:Project) -> querySparql('CONSTRUCT { ?project org:containsMember ?m. }). • Innovation • search result expansion using SPARQL • customized rules for search – only when word “x” is searched, include these results, etc Personalization in EPOS, SWP06, Budva 12.06.2006

  25. Semantic Search Personalization in EPOS, SWP06, Budva 12.06.2006

  26. Evaluation Personalization in EPOS, SWP06, Budva 12.06.2006

  27. Methodology used for Evaluation in EPOS • Case Study Method • Case Study with 8 researchers from DFKI • Preperation Phase three months: users learn the system, bugfixing • Evaluation period of 1 week with daily usage • Daily interviews with questionnaire • Usage data collection • Explicit user feedback for proposals from context elicitation – user had to check if results were correct • General observations from questionnaire • Personal Ontology represents the view of the user (90% positive answers) • it is “valuable” for searching and classifying information • Semantic Desktop is perceived as “helpful in their daily work” Personalization in EPOS, SWP06, Budva 12.06.2006

  28. Example findings from Case Study • Move & Classify via EPOS DropBox • Filing is faster than before due to proposal of locations? • Yes on 40% of all days • There was still manual filing, but only in 8% of all reported filings • Multiple classification have been used • 2,5 categories per file: multicriterial classification • PIMO is populated on-the-fly Personalization in EPOS, SWP06, Budva 12.06.2006

  29. Lessons learned: changing the linker • After: • Resources can be “Tagged”, the metaphor is known from Web 2.0 applications. Tags are searched semi-automatically • Benefit is immediately seen • User interface is simpler • … to be evaluated again …. • Before: • Evaluation • Manual linking with the Linker was seldom used • Whereas semi-automatic linking was appreciated by means of Move & Classify, Topic-linking, PIM mapping • Redesign Personalization in EPOS, SWP06, Budva 12.06.2006

  30. Outlook Personalization in EPOS, SWP06, Budva 12.06.2006

  31. Our goal This is my personal computer Personalization in EPOS, SWP06, Budva 12.06.2006

  32. Desktop Applications Personal Wiki Application Plugins PIMO Editor Sesame2 Repository PIMO Store Resource Store Configuration Store Service Store Semantic Applications Web 2.0 Interfaces Domain Ontologies GnowsisServer ApertureCrawlers Outlook Clustering Ont. Matching Outlook Tagging Gui invocation Files filesystem Crawler Desktop Search e-mail server e-mail Lucene Index Personalization in EPOS, SWP06, Budva 12.06.2006

  33. Open source and reusable • gnowsis-betahttp://www.gnowsis.org • Nepomukhttp://nepomuk.semanticdesktop.org • MyMoryhttp://www.dfki.de/mymory • EPOS will be continued • our results are code for you Personalization in EPOS, SWP06, Budva 12.06.2006

  34. note: • Demo of Nepomuk today at the EU projects session • I can demo gnowsis beta 0.9 Personalization in EPOS, SWP06, Budva 12.06.2006

  35. Summary • The PIMO ontology stack and Paul’s PIMO allow us to personalize using precise knowledge about the user • User observation components identify contexts based on PIMO • Applications use PIMO + context in combination • open source, will be continued Personalization in EPOS, SWP06, Budva 12.06.2006

  36. Questions persona created using http://www.sp-studio.de/ Personalization in EPOS, SWP06, Budva 12.06.2006

More Related