Distributed Artificial Distributed Artificial Intelligence Intelligence and Ontology-based Systems and Ontology-based Systems for Knowledge Management. for Knowledge Management. Fabien Gandon Post-doc “Semantic Web Services, Context Awareness and Privacy” Carnegie Mellon University Ph.D. “Distributed A.I. and Knowledge Management” I.N.R.I.A. Sophia Antipolis Lecturer (moniteur) computer science University Nice D.E.A. “Image processing and Vision systems” University Rouen Graduate engineer “Applied mathematics” I.N.S.A. Rouen
83
Embed
Distributed Artificial Intelligence and Ontology-based Systems for Knowledge Management. Fabien Gandon Post-doc “Semantic Web Services, Context Awareness.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Distributed Artificial IntelligenceDistributed Artificial Intelligenceand Ontology-based Systems for and Ontology-based Systems for Knowledge Management.Knowledge Management.
Fabien Gandon Post-doc “Semantic Web Services, Context Awareness and Privacy”
Carnegie Mellon University Ph.D. “Distributed A.I. and Knowledge Management”
The Man Who Mistook His Wife for a Hat : And Other Clinical Tales by Oliver W. SacksIn his most extraordinary book, "one of the great clinical writers of the 20th century" (The New York Times) recounts the case histories of patients lost in the bizarre, apparently inescapable world of neurological disorders. Oliver Sacks's The Man Who Mistook His Wife for a Hat tells the stories of individuals afflicted with fantastic perceptual and intellectual aberrations: patients who have lost their memories and with them the greater part of their pasts; who are no longer able to recognize people and common objects; who are stricken with violent tics and grimaces or who shout involuntary obscenities; whose limbs have become alien; who have been dismissed as retarded yet are gifted with uncanny artistic or mathematical talents.
If inconceivably strange, these brilliant tales remain, in Dr. Sacks's splendid and sympathetic telling, deeply human. They are studies of life struggling against incredible adversity, and they enable us to enter the world of the neurologically impaired, to imagine with our hearts what it must be to live and feel as they do. A great healer, Sacks never loses sight of medicine's ultimate responsibility: "the suffering, afflicted, fighting human subject."
• Annotation in RDF with XML syntax: <CoMMA:DocumentDocument rdf:about=“http://www-sop.inria.fr/aar.docaar.doc”> <CoMMA:TitleTitle>Annual activity report of ACACIAAnnual activity report of ACACIA</INRIA:Title> <CoMMA:AuthorAuthor> <CoMMA:PersonPerson rdf:about=“http://www.inria.fr/~rdiengrdieng/” /> </CoMMA:Author> </CoMMA:Document>
Ontology building in five steps Step 1 - Data collection and analysis
−Scenario-driven analysis: users’ scenario reports & grid−Motivate data collection internal & external to organization−Capture aspects conceptualization to assist scenarios
Extract: “... wonder if there are technical reportstechnical reports about UMTSUMTS, then...” “... what this managermanager or one of his colleaguescolleagues wrote for...”
Step 2 - Build a lexicon−Capture terms and their definitions−First intermediary representation of the ontology−Constraint: one and only one occurrence of a definition−Disambiguate terms, e.g.:
COLLEAGUE n. (lat. collega) someone who shares the same profession || one of a group of people who work together.
[email protected] / [email protected] / 1616Methodological steps in ontology engineering (3)Methodological steps in ontology engineering (3)
Step 3 - Enriching lexicon structure−Split concepts, properties and attributes into different tables−Augment with relevant semantic aspects (e.g. subsumption)−Enrich, augment, refine, ... for both humans and machines−Taxonomic skeleton: top-down / bottom-up / middle-out
Step 4 - Script translating tables into RDFS
Class View Super class Other Terms Natural Language Definition Pr Manager Organization;
Person; Professional; director; Professional whose primary job is to
manage other people, directing their work activity. A Manager tells his or her subordinate workers what to do.
Cy
... ... ... ... ... ... UMTS
Domain; MobilePhoneProtocols;
U.M.T.S.; universal mobile telecommunications system
Mobile phone protocol of the 3G technology that delivers broadband information at speeds up to 2Mbit s/sec.
Us
... ... ... ... ... ... Technical Report
Document; Report; ; Report presenting technical details on a specific topic.
Us
... ... ... ... ... ... Relation Domain Range View Super Relation Other Terms Natural Language Definition Sy Tr Re Pr
Colleague Person Person Organisation; Acquaintance; co-worker; Acquaintance between two persons who work together
X Us
... ... ... ... ... ... ... ... ... ... ...
R5C8
Analysis of the three levels present in RDF(S)Analysis of the three levels present in RDF(S)
Ti A term Ci Intension concept Ci
Instance of concept
Ri Intension relation Ri
Instance of relation
Instanciation links
Extension concept Ci or relation Ri
Ci Ri
T1
T3 T4
T2 T5
Up to that step RDF(S) hasthe required expressiveness
C2
C1
C3
C4 C5 C6 C7 C8
R1
R2
R4 R5 R6
R3
Term used as a label
...<rdfs:Class rdf:ID="Department"> <rdfs:subClassOf rdf:resource="#OrganizationPart"/> <rdfs:comment xml:lang="en"> Organization part which is a sub division of of a Research Direction, corresponding to sub interest field e.g mobile transmission </rdfs:comment> <rdfs:label xml:lang="en">department</rdfs:label> <rdfs:label xml:lang="en">division</rdfs:label></rdfs:Class>...
Synonyms...<rdfs:Class rdf:ID="E-Mail"> <rdfs:subClassOf rdf:resource="#Mail"/> <rdfs:comment xml:lang="en"> Mail sent in electronic format over a computerized world-wide communication system </rdfs:comment> <rdfs:label xml:lang="en">e-mail</rdfs:label> <rdfs:label xml:lang="en">electronic mail </rdfs:label> <rdfs:label xml:lang="en">mail</rdfs:label></rdfs:Class>...<rdfs:Class rdf:ID="PostMail"> <rdfs:subClassOf rdf:resource="#Mail"/> <rdfs:comment xml:lang="en"> Mail transmitted via the post office </rdfs:comment> <rdfs:label xml:lang="en">mail</rdfs:label> <rdfs:label xml:lang="en">post mail</rdfs:label></rdfs:Class>...
<rdf:Property rdf:ID="colleaguecolleague"> <rdfs:subPropertyOf rdf:resource="#Acquaintance"/> <rdfs:range rdf:resource="#Person"/> <rdfs:domain rdf:resource="#Person"/> <cos:symmetric>true</cos:symmetric><cos:symmetric>true</cos:symmetric> <rdfs:comment xml:lang="enen">acquaintance between two personsacquaintance between two persons who work together.who work together.</rdfs:comment> <rdfs:comment xml:lang="frfr">accointance entre deux personnesaccointance entre deux personnes travaillant ensemble.travaillant ensemble.</rdfs:comment> <rdfs:label xml:lang="enen">colleaguecolleague</rdfs:label> <rdfs:label xml:lang="enen">co-workerco-worker</rdfs:label> <rdfs:label xml:lang="frfr">colleguecollegue</rdfs:label> <rdfs:label xml:lang="frfr">collegue de travailcollegue de travail</rdfs:label> </rdf:Property>
[email protected] / [email protected] / 1919Methodological steps in ontology engineering (5)Methodological steps in ontology engineering (5)
Step 5 - Factorizing knowledge (when needed)
−Declare algebraic properties of relations(symmetric / transitive / reflexive relations)
−No one generates all the instances of colleague by hand−"I am a colleague of X because
I work in the same group as X" (inference)−Encode axiomatic knowledge in rules and definitions
IFIF (rule for sufficient condition)(rule for sufficient condition) Group Include Person ?x?x Include Person ?y?y THENTHEN Person ?x?x ColleagueColleague Person ?y?y
−Abstract top & middle layer for corporate memory: reusable−Middle layer for domain: reusable in same domain−Extension layer: usable but not reusable−Reuse tested e.g., CSELT CSTB, APROBATIOM, KMP
Propose annotation-related services to others−Archive new annotations on documents of the memory−Search & retrieve references matching queries−Notify registered agents of the arrival of a new annotation
Interaction 1 - Annotation allocation− Pb: archives distributed all over organization− Mediator & archivists discuss best archive for new annot.− Contract-net (CfP, Proposal, Accept/Reject):
− Proposals: semantic distance new annotation - archive
Case 1 - literal values: lexicographical distance Case 2 - concept types: minimum length of path
between two types through least common super type
DistH(Type1,Type2) = Min(GPath(Type1,LCST)+GPath(Type2,LCST)) GPath(,): number of edges through generalization links LCST: least common super type = shared characteristics
Distance between two triples (conditional weighted sum)
Distance = allocation criteria of contract-net− "and the winner is..." the archivist with smallest distance− Cluster annotations & specialize archives− Improve query solving & respect knowledge distribution
[email protected] / [email protected] / 3434Interactions mediator-archivist in solving a queryInteractions mediator-archivist in solving a query
Interaction 2 - distributed query solving− Pb: archives of annotations distributed all over org.− Mediators & archivists share knowledge to solve a query− Composition of Query-Ref protocol for distributed solving
To pay by check and/or register by mail, do not use this form! Please download and complete the PDF form instead. You can also complete the PDF version of the form electronically, and then print it and either fax or mail the printout to AAAI. (Note: You can only save your data entry if you have Acrobat 4.0 or higher. Acrobat Reader allows you to complete the form and print it, but not save it.) Student registrants please note that you are still required to send hard copy proof of your full-time student status to the AAAI office in order to receive the discounted student registration rates.
First Name (and optional middle initial):Last Name (family or surname):Company or Affiliation:Mailing Address:City: State:USA Zip Code (Please enter your zip+4 code):Country: Foreign Postal Code:Work or Daytime Telephone:E-mail Address:Please select your tutorial(s) / workshop(s) and select the rateSunday AM Sunday PM Monday AM Monday PM $100* $300*To qualify for this price, you must also register for the IJCAI technical conference above.
Interface without context awarenessInterface without context awareness
To pay by check and/or register by mail, do not use this form! Please download and complete the PDF form instead. You can also complete the PDF version of the form electronically, and then print it and either fax or mail the printout to AAAI. (Note: You can only save your data entry if you have Acrobat 4.0 or higher. Acrobat Reader allows you to complete the form and print it, but not save it.) Student registrants please note that you are still required1) to send hard copy proof of your full-time student status to the AAAI office in order to receive the discounted student registration rates.
First Name (and optional middle initial):Last Name (family or surname):Company or Affiliation:Mailing Address:City: State:USA Zip Code (Please enter your zip+4 code):Country: Foreign Postal Code:Work or Daytime Telephone:E-mail Address:Please select your tutorial(s) / workshop(s) and select the rateSunday AM Sunday PM Monday AM Monday PM $100* $300*To qualify for this price, you must also register for the IJCAI technical conference above.
Hyp: Context-awareness to support mobile access to Context-awareness to support mobile access to semantic Webs and their servicessemantic Webs and their services
Context awareness State of the Art−Application leveraging context awareness
Active Badge [Want et al., 92] ParcTab [Schilit, 95] Oxygen
[Dertouzos, 99] GUIR [Hong & Llanday, 01] Aura [Garlan et al., 02] • Application dependent and heterogeneous
• Redundant and scattered
−Personal resources integration and unification• Toolkits and widgets for wrapping [Dey et al., 00]
• e-Wallet: awareness & privacy You are here
Hyp: Semantic Web & Services to provide a unified Semantic Web & Services to provide a unified secure interface to personal resources (e-Wallet)secure interface to personal resources (e-Wallet)
Privacy rulesPrivacy rules<sowl:ReadAccessRule> <rdfs:label>people can only know whether or not I am on campus</rdfs:label> <sowl:target> <mc:Person rdf:ID="&variable;#owner"> <mc:location rdf:resource="&variable;#location"/> </mc:Person> </sowl:target> <sowl:check> <rowl:And> <rowl:condition> <mc:E-Wallet rdf:ID="&variable;#e-Wallet"> <mc:owner> <mc:Person rdf:ID="&variable;#owner"/> </mc:owner> </mc:E-Wallet> </rowl:condition> <rowl:condition> <mc:Place rdf:ID="http://www.cmu.edu"> <mc:include rdf:resource="&variable;#location" /> </mc:Place> </rowl:condition> <rowl:not-condition> <qowl:Query rdf:ID="&variable;#query"> <qowl:sender rdf:resource="&variable;#owner" /> </qowl:Query> </rowl:not-condition> </rowl:And> </sowl:check> <sowl:revision> <mc:Person rdf:ID="&variable;#owner"> <mc:location rdf:resource="http://www.cmu.edu"/> </mc:Person> </sowl:revision></sowl:ReadAccessRule>
<sowl:ReadAccessRule> <rdfs:label>people can only know whether or not I am on campus</rdfs:label> <sowl:target> <mc:Person rdf:ID="&variable;#owner"> <mc:location rdf:resource="&variable;#location"/> </mc:Person> </sowl:target> <sowl:check> <rowl:And> <rowl:condition> <mc:E-Wallet rdf:ID="&variable;#e-Wallet"> <mc:owner> <mc:Person rdf:ID="&variable;#owner"/> </mc:owner> </mc:E-Wallet> </rowl:condition> <rowl:condition> <mc:Place rdf:ID="http://www.cmu.edu"> <mc:include rdf:resource="&variable;#location" /> </mc:Place> </rowl:condition> <rowl:not-condition> <qowl:Query rdf:ID="&variable;#query"> <qowl:sender rdf:resource="&variable;#owner" /> </qowl:Query> </rowl:not-condition> </rowl:And> </sowl:check> <sowl:revision> <mc:Person rdf:ID="&variable;#owner"> <mc:location rdf:resource="http://www.cmu.edu"/> </mc:Person> </sowl:revision></sowl:ReadAccessRule>
Privacy rule: grant access to location when on campus but obfuscate precisionPrivacy rule: grant access to location when on campus but obfuscate precision
Experiment #1 with early prototypeExperiment #1 with early prototype
Before the experiment:− Office for Human Research Protections approval
Institutional Review Board certificate− Selected group of 11 users, with a variety of profiles− Trained the 11 users during a 2-hour session + material
The 3-day experiment involved: − Message filtering agent: 44 messages and 484 feedbacks− Restaurant concierge agent: 28 recommendations− Logs were generated for each one of these events.
After the experiment:− Users had to fill a survey ~1/2 hour− Face-to-face de-briefing interviews ~15 minutes− Statistics on the logs
ACACIA Laboratory - INRIA Sophia Antipolis− Dr. Rose Dieng-Kuntz (Research Director – ACACIA project leader)
− Members of ACACIA team and logistics of INRIA Sophia− ATOS-Origin, CSTB, Deutsch Telekom T-Nova, Italia
Telecom, LIRMM and University of Parma − IST Program (CoMMA project)
School of computer science – Carnegie Mellon Uni.− Prof. Norman M. Sadeh (Mobile Commerce Laboratory Director,
SCS CMU, Free University of Amsterdam, European Commission)
− Members of myCampus team and logistic of ISRI− BBN, IBM, HP, Symbol and Boeing − IST Program (SWAP project)− Air Force Research Laboratory (contract F30602-02-2-0035)
− Defense Advanced Research Project Agency (DARPA) (contract F30602-98-2-0135)
ACACIA Laboratory - INRIA Sophia Antipolis− Dr. Rose Dieng-Kuntz (Research Director – ACACIA project leader)
− Members of ACACIA team and logistics of INRIA Sophia− ATOS-Origin, CSTB, Deutsch Telekom T-Nova, Italia
Telecom, LIRMM and University of Parma − IST Program (CoMMA project)
School of computer science – Carnegie Mellon Uni.− Prof. Norman M. Sadeh (Mobile Commerce Laboratory Director,
SCS CMU, Free University of Amsterdam, European Commission)
− Members of myCampus team and logistic of ISRI− BBN, IBM, HP, Symbol and Boeing − IST Program (SWAP project)− Air Force Research Laboratory (contract F30602-02-2-0035)
− Defense Advanced Research Project Agency (DARPA) (contract F30602-98-2-0135)