1. Personalization in EPOS, SWP06, Budva 12.06.2006 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/http://www.sp-studio.de/

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

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

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

5. Personalization in EPOS, SWP06, Budva 12.06.2006 Rom e Peter Paul’s mental model Paul’s concepts pimo-things Paul’s files and digital resources paul:Rome http://www.comune.roma.it/ relations to occurrences

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

7. Personalization in EPOS, SWP06, Budva 12.06.2006 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 Paul

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

9. Personalization in EPOS, SWP06, Budva 12.06.2006 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

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

11. Personalization in EPOS, SWP06, Budva 12.06.2006 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

12. Personalization in EPOS, SWP06, Budva 12.06.2006 PIMO is The “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

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

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

15. Personalization in EPOS, SWP06, Budva 12.06.2006 domain-independent SemDesk Upper Level PersonRoleDocumentOrganizationTime domain-independent, adapted to Semantic Desktop and Nepomuk SemDesk Mid-Level ManagerProject Contract CompanyOffer basic superclasses Rep Lang SystemItemsThing ontology imports Message dfki.de/ont/pim/pimo PIMO ontology languages PIMO-Basic defines the basic language constructs. PIMO-Upper A 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.

16. Personalization in EPOS, SWP06, Budva 12.06.2006 Organizational Structure Domain Model: Bibtech A HeikoCar-EntReport56 Report EPOS dfki.de/ont/pim/pimo PIMO ontology languages Domain ontologies A 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.

17. Personalization in EPOS, SWP06, Budva 12.06.2006 basic superclasses Rep Lang SystemItems domain-independent SemDesk Upper Level PersonRoleDocumentOrganizationTime domain-independent, adapted to Semantic Desktop and Nepomuk SemDesk Mid-Level ManagerProject Contract CompanyOffer representing extracted data in RDF/S multiple vocabularies Native Data Vocabularies vCard vEventdublin core foaf image PersonImage Thing sub-classes Organizational Structure Domain Model: Bibtech A HeikoCar-EntReport56 Report EPOS ontology imports Message aperture.semanticdesktop.org/data dfki.de/ont/pim/pimo all PIMO ontology layers

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

19. Personalization in EPOS, SWP06, Budva 12.06.2006 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

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

21. Personalization in EPOS, SWP06, Budva 12.06.2006 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.

22. Personalization in EPOS, SWP06, Budva 12.06.2006 Applications

23. Personalization in EPOS, SWP06, Budva 12.06.2006 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

24. Personalization in EPOS, SWP06, Budva 12.06.2006 Application: Drop Box Helps filing information uses PIMO structures concepts and folders uses DOCS for text similarity Knows the users model and is trained 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 doc: … EPOS … Project:Epos EPOS, DFKI, Maus, … PIMO of Paul =

25. Personalization in EPOS, SWP06, Budva 12.06.2006 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

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

27. Personalization in EPOS, SWP06, Budva 12.06.2006 Evaluation

28. Personalization in EPOS, SWP06, Budva 12.06.2006 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”

29. Personalization in EPOS, SWP06, Budva 12.06.2006 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

30. Personalization in EPOS, SWP06, Budva 12.06.2006 Lessons learned: changing the linker 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 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 ….

31. Personalization in EPOS, SWP06, Budva 12.06.2006 Semantic Search evaluated at Siemens SBS by Mark Siebert and Pierre Smits customization features used integrated a proposal ontology conclusion: Through peer search and semantic enhancements, recall was increased. Precision may decrease, depending on the setup and scenario.

32. Personalization in EPOS, SWP06, Budva 12.06.2006 Outlook

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

34. Personalization in EPOS, SWP06, Budva 12.06.2006 Semantic Applications Desktop Search Gnowsis Server Aperture Crawlers Outlook e-mail server filesystem Outlook PIMO Editor Crawler Ont. Matching Files e-mail Gui invocationTagging Clustering Desktop ApplicationsApplication Plugins Sesame2 Repository Resource Store PIMO Store Configuration Store Service Store Domain Ontologies Lucene Index Personal Wiki Web 2.0 Interfaces

35. Personalization in EPOS, SWP06, Budva 12.06.2006 EPOS will be continued our results are code for you Open source and reusable gnowsis-beta http://www.gnowsis.org http://www.gnowsis.org Nepomuk http://nepomuk.semanticdesktop.org http://nepomuk.semanticdesktop.org MyMory http://www.dfki.de/mymory http://www.dfki.de/mymory

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

37. Personalization in EPOS, SWP06, Budva 12.06.2006 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

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