1. Košice, 10 February 20061 Experience Management based on Text Notes The EMBET System Michal Laclavik

2. Košice, 10 February 20062 Overview Applications Motivation, history Experience Management Approach Ontology Knowledge Model Modeling Methodology EMBET Architecture Algorithms Applications Conclusion

3. Košice, 10 February 20063 Collaboration among users Knowledge Sharing Recommendation Representation of Experience or Knowledge Text Notes Objectives, Application of the system

4. Košice, 10 February 20064 Motivation, problem area In Pellucid IST Project Active Hint approach AH = action on resource(s) in context + explanation Many AHs in Pellucid: See Text Note in this context because is useful In K-Wf Grid project Need for sharing of expert knowledge Text Notes Natural way for people If we are able to detect context of note - note can help others better then other formalized knowledge People like to enter notes or memos to remind something to themselves or others

5. Košice, 10 February 20065 State of the Art – Ontologies, Knowledge Ontologies Knowledge Representation OWL-DL compatible with Description Logic Query and Storage Engines available RDF, OWL, RDQL based Application domain Knowledge Management (KM) is the process through which organizations generate value from their intellectual and knowledge-based assets (Source: CIO Magazine) Experience Management is special kind of KM – based on “lessons learned” Characters Data Information Knowledge Actions Syntax Semantics Pragmatics Reasoning (Bergman, 2002, Experience Management)

6. Košice, 10 February 20066 Research Challenges Experience (Knowledge) Management Text Processing Knowledge, Semantic, Ontologies Semantic Annotation Domain Models (Flood Prediction, Traffic Simulation, …) User Interaction Knowledge Relevance, Problem detection

7. Košice, 10 February 20067 Experience Management Approach Problem p Problem Space (P) In EMS Case-Lesson pairs (c, l) Case Space (C) lesson space (L). maps problem space to case space c = f(p)

8. Košice, 10 February 20068 General vs. EMBET Approach General EM Approach Characterize a problem Transform the problem from the space P to the space C. Choose from the cases the most "useful" lesson from the case-lesson pairs stored in the database Apply that lesson. EMBET EM Approach User context detection from environment which describes problem P Our Model is described by ontology and Notes are stored with associated context, which describes space C Notes represent learned lesson L which is associated with space C (note context). The note context is matched with a user problem described by the detected user context. The user context is wider than the note context and as a result all applicable notes are matched and returned. Applying the lesson is left to the user be reading appropriate notes.

9. Košice, 10 February 20069 Thesis Objectives Design of Generic Ontology model for Experience management with extension for different application domains Design of Modeling Methodology for extension of the Ontology based Knowledge Model for different applications Design & Development of generic and customizable EMBET Experience Management software with the Ontology Knowledge Model Evaluation of results on a real pilot operation

10. Košice, 10 February 200610 Used Methods and Methodologies Knowledge management, system design Unified Modeling Language – UML CommonKADS Protégé as Tool for CommonKADS Formal methods for describing ontology based models Description Logic Graph Ontology representation

11. Košice, 10 February 200611 Used Tools and Software Protégé Ontology Editor Support for OWL ontology format Can be used as modeling tool Jena – Semantic Web Framework for Java Support for OWL – best available OWL API Support for RDQL model querying

12. Košice, 10 February 200612 Ontology Knowledge Model Objective: Design of Generic Ontology model for Experience management with extension for different application domains

13. Košice, 10 February 200613 Ontology Knowledge Model Based on Events, Resources, Actions, Actors, Context Formally Described using Sets, Description Logic (compatible with OWL-DL), Graph Representation Actor Context updating function/algorithm (Actor/User Environment State) C A new = f C (e a,C A old ) Resources updating function/algorithm (result of fulfilled actor/user goals) R A new = f R (C A new,R A old )

14. Košice, 10 February 200614 Modeling Methodology Objective: Design of Modeling Methodology for extension of the Ontology based Knowledge Model for different applications

15. Košice, 10 February 200615 Modeling Methodology Extending Model with Protégé Editor following CommonKADS models Organizational or Environment Model Task Model Agent or Actor Model Includes implementation of algorithms for context and resource updating Results Ontology developed in Protégé which can be exported in OWL format. Concrete Algorithms for each actor (often algorithms are similar or same) which updates actors' context C A new and resources R A new.

16. Košice, 10 February 200616 Design & Development of EMBET System Objective: Design & Development of generic and customizable EMBET Experience Management software with the Ontology Knowledge Model

17. Košice, 10 February 200617 Use Case Display Note Enter Note Vote on Relevance Enter Problem

18. Košice, 10 February 200618 Knowledge Cycle 1 Matching User Context or Problem 2 Displaying Relevant Notes 3 User take Decisions or Actions 4 User feedback and knowledge update (4) Enter Note (4) Pattern Detection Annotation Note with Context (1, 4) Compare Current User Context And Note Context (1, 4) Displaying context List (4) User approve and submit context of note (2) Notes are displayed to user in detected user context (4) Vote on note, Updating relevance

19. Košice, 10 February 200619 Architecture and GUI XML messages JSP Pages HTML Output JSTL XSLT Style Sheets CSS EMBET GUI RDF OWL XML messages Knowledge Notes Feedback On knowledge Update Knowledge Context Update EMBET Core Knowledge Notes Detection Context Detection Store Knowledge Memory

20. Košice, 10 February 200620 Class Diagram Memory Ontology Anotate Core EventHandler DetectContext

21. Košice, 10 February 200621 Algorithms Actor (User) Context updating algorithm C A new = f C (e a,C A old ) Resources (Notes) updating algorithm R A new = f R (C A new,R A old ) Procedure updateContext(Event e) // e - new event in the system relevant to actor begin actor = e.actor; //event is related to some actor (user) if e.action = Create or e.context is empty then begin //when a resource is added (like note) or context of event is empty //we can add context of actor to the event while c = foreach(actor.context) do e.context += c; end else begin //if actor (user) performed some action or action related to user happened //we need to update actor context based on received event context remove(actor.context); while c = foreach(e.context) do actor.context += c; end Procedure updateResources(Actor actor) begin // unlink any notes of actor unlinkActorNotes(actor); while noteS = foreach(Note from Memory) do begin // checking defined note context elements matchAll = true; while c = foreach(noteS.context) and matchAll do begin if actor.context has not c matchAll = false; end //new note is added to actor if matchAll addProperty(actor.resource, noteS); end

22. Košice, 10 February 200622 Annotation Text of note is matched by regular expressions Domain (Application) elements described in ontology model are detected

23. Košice, 10 February 200623 Applications Objective: Evaluation of Results on real pilot operation.

24. Košice, 10 February 200624 Example of Use – Adding the Note

25. Košice, 10 February 200625 Example of Use – Definition of Problem

26. Košice, 10 February 200626 Conclusion and Future Work

27. Košice, 10 February 200627 Major Outcomes/Results EMBET is system for: User Problem Definition Experience Management Collaboration Knowledge Sharing

28. Košice, 10 February 200628 Conclusion and outlook Tested and Evaluated on: Pellucid IST Project K-Wf Grid IST Project Can be used also in non Grid application Intranet Systems CRM, ERP Systems which can communicate Context Customization Domain Ontology Model (main resources in the domain) Interface communicating context/problem of the user

29. Košice, 10 February 200629 Future work RAPORT APVT project (01/2005-12/2007): Research and development of a knowledge based system to support workflow management in organizations with administrative processes model and algorithms will be reused and extended Annotation of emails K-Wf Grid EU 6FP RTD IST project (2004-2007) evaluation on more applications, improvement of context detection NAZOU SPVV Project (09/2004-11/2007): Tools for acquisition, organization and maintenance of knowledge in an environment of heterogeneous information resources OnTeA semantic annotation

30. Košice, 10 February 200630 Thank you ! Michal Laclavik

31. Košice, 10 February 200631 Questions & Answers

32. Košice, 10 February 200632 Methodologies Based on CommonKADS Protégé Tied with Extensible model for discrete environments based on Events

33. Košice, 10 February 200633 Experience Management Systems EM as in Bergman Book – methodology for EM application EMBET Generic

34. Košice, 10 February 200634 Annotation Annotation solutions – semantic tags OnTeA - Mapping with existing individuals in ontology models