Ontology Aware Software Service Agents: Meeting Ordinary User Needs on the Semantic Web Muhammed Al-Muhammed April 19, 2005.

Slides:



Advertisements
Similar presentations
Semantically Grounded Briefings Bob Balzer, Neil Goldman, Marcelo Tallis Teknowledge
Advertisements

1 University of Namur, Belgium PReCISE Research Center Using context to improve data semantic mediation in web services composition Michaël Mrissa (spokesman)
A component- and message-based architectural style for GUI software
1 UIM with DAML-S Service Description Team Members: Jean-Yves Ouellet Kevin Lam Yun Xu.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Abhinn Kothari, 2009CS10172 Parth Jaiswal 2009CS10205 Group: 3 Supervisor : Huzur Saran.
CH02: Modeling the process and life cycle Process of developing software (organization and discipline in the activities) contribute to the quality of the.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
SmartER Semantic Cloud Sevices Karuna P Joshi University of Maryland, Baltimore County Advisors: Dr. Tim Finin, Dr. Yelena Yesha.
DSM Workshop, October 22 OOPSLA 2006 Model-Based Workflows Leonardo Salayandía University of Texas at El Paso.
Ontology Aware Software Service Agents: Meeting Ordinary User Needs on the Semantic Web Muhammed Al-Muhammed Supported in part by NSF.
Query Processing and Reasoning How Useful are Natural Language Interfaces to the Semantic Web for Casual End-users? Esther Kaufmann and Abraham Bernstein.
Ontology Aware Software Service Agents: Meeting Ordinary User Needs on the Semantic Web Muhammed J. Al-Muhammed Brigham Young University Supported by:
Semantic description of service behavior and automatic composition of services Oussama Kassem Zein Yvon Kermarrec ENST Bretagne France.
A Framework for Pay-as-you-go Extraction Ontology Based Information Retrieval Andrew Zitzelberger.
OWL-AA: Enriching OWL with Instance Recognition Semantics for Automated Semantic Annotation 2006 Spring Research Conference Yihong Ding.
White Box Testing and Symbolic Execution Written by Michael Beder.
Conceptual Model Based Semantic Web Services Muhammed J. Al-Muhammed David W. Embley Stephen W. Liddle Brigham Young University Sponsored in part by NSF.
Resolving Under Constrained and Over Constrained Systems of Conjunctive Constraints for Service Requests Muhammed J. Al-Muhammed David W. Embley Brigham.
Requirements Analysis Concepts & Principles
Annotating Documents for the Semantic Web Using Data-Extraction Ontologies Dissertation Proposal Yihong Ding.
Recognition and Satisfaction of Constraints in Free-Form Task Specification Muhammed Al-Muhammed.
Dynamic Matchmaking between Messages and Services in Multi-Agent Systems Muhammed Al-Muhammed David W. Embley Brigham Young University Supported in part.
Resolving Underconstrained and Overconstrained Systems of Conjunctive Constraints for Service Requests Muhammed J. Al-Muhammed David W. Embley Brigham.
Enriching OWL with Instance Recognition Semantics for Automated Semantic Annotation Stephen W. Liddle Information Systems Department Yihong Ding & David.
Ontology-Based Constraint Recognition in Free-Form Service Requests Muhammed J. Al-Muhammed Brigham Young University Sponsored in part by NSF (#
Semi-Automatic Generation of Mini-Ontologies from Canonicalized Relational Tables Chris Hathaway.
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
Audumbar Chormale Advisor: Dr. Anupam Joshi M.S. Thesis Defense
Artificial Intelligence Research Centre Program Systems Institute Russian Academy of Science Pereslavl-Zalessky Russia.
Systems Analysis and Design in a Changing World, 6th Edition
UML - Development Process 1 Software Development Process Using UML (2)
Katanosh Morovat.   This concept is a formal approach for identifying the rules that encapsulate the structure, constraint, and control of the operation.
Categories of Testing.
Requirements Analysis
A Generative and Model Driven Framework for Automated Software Product Generation Wei Zhao Advisor: Dr. Barrett Bryant Computer and Information Sciences.
Class Specification Implementation Graph By: Njume Njinimbam Chi-Chang Sun.
1 WSMX Web Service Modeling Execution WSMO Deliverable 13 Emilia Cimpian, Adrian Mocan, Matthew Moran, Eyal Oren, Michal Zaremba 3 March 2004.
Agent Model for Interaction with Semantic Web Services Ivo Mihailovic.
Spoken dialog for e-learning supported by domain ontologies Dario Bianchi, Monica Mordonini and Agostino Poggi Dipartimento di Ingegneria dell’Informazione.
1 ECE 453 – CS 447 – SE 465 Software Testing & Quality Assurance Instructor Kostas Kontogiannis.
SOFTWARE TESTING Scope of Testing  The dynamic Indian IT industry has always lured the brightest minds with challenging career.
UT DALLAS Erik Jonsson School of Engineering & Computer Science FEARLESS engineering Semantic Web Services CS - 6V81 University of Texas at Dallas November.
Knowledge Modeling, use of information sources in the study of domains and inter-domain relationships - A Learning Paradigm by Sanjeev Thacker.
An Aspect of the NSF CDI InitiativeNSF CDI: Cyber-Enabled Discovery and Innovation.
1 Introduction to Software Engineering Lecture 1.
An Ontological Framework for Web Service Processes By Claus Pahl and Ronan Barrett.
Elizabeth Furtado, Vasco Furtado, Kênia Sousa, Jean Vanderdonckt, Quentin Limbourg KnowiXML: A Knowledge-Based System Generating Multiple Abstract User.
Environment Change Information Request Change Definition has subtype of Business Case based upon ConceptPopulation Gives context for Statistical Program.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
Automata Based Method for Domain Specific Languages Definition Ulyana Tikhonova PhD student at St. Petersburg State Politechnical University, supervised.
Requirements Validation
Automating DAML-S Web Services Composition Using SHOP2 Based on an article by Dan Wu, Bijan Parsia, Evren Sirin, James Hendler and Dana Nau in Proceedings.
Personalized Recommendation of Related Content Based on Automatic Metadata Extraction Andreas Nauerz 1, Fedor Bakalov 2, Birgitta.
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Information Architecture & Design Week 9 Schedule - Web Research Papers Due Now - Questions about Metaphors and Icons with Labels - Design 2- the Web -
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Chapter – 8 Software Tools.
Sharing personal knowledge over the Semantic Web ● We call personal knowledge the knowledge that is developed and shared by the users while they solve.
Of 24 lecture 11: ontology – mediation, merging & aligning.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Towards a framework for architectural design decision support
About the Presentations
Web Ontology Language for Service (OWL-S)
Software Requirements Specification Document
Test Case Test case Describes an input Description and an expected output Description. Test case ID Section 1: Before execution Section 2: After execution.
Automated test.
Automated test.
Presentation transcript:

Ontology Aware Software Service Agents: Meeting Ordinary User Needs on the Semantic Web Muhammed Al-Muhammed April 19, 2005

(2) The Challenge Reduce information overload Find and use services I want to see a dermatologist next week; any day would be ok for me, at 4:00 p.m. The dermatologist must be within 20 miles from my home and must accept my insurance.

April 19, 2005 (3) Thesis Statement Hypothesis: it is possible to automate everyday tasks whose invocation results in establishing agreed-upon relationships in a domain ontology Validation: proof-of-concept prototype

April 19, 2005 (4) Approach Task ontology  Domain ontology  Process ontology Characteristics  Task specification: Free-form text  Request recognition: find best task ontology  Task execution Specialize task ontology processes Execute generated code

April 19, 2005 (5) Domain Ontology Components  Object sets = concepts  Relationship sets  Constraints Uses  Task knowledge  Task recognition

April 19, 2005 (6) Domain Ontology

April 19, 2005 (7) Domain Ontology Augmented with data frames A data frame defines information about a concept  Its internal and external representation  Its contextual keywords or phrases  Operations along with contextual keywords or phrases

April 19, 2005 (8) Data Frames Time … textual representation: “([2-9]|1[012]?)\s* :\s*([0-5]\d)\s*[AaPp]\s* \.?\s* [Mm]\s* \.?)” … end Distance internal representation: real textual representation: ((\d+(\.\d+)?)|(\.\d+)) context keywords/phrases: miles | mile | kilometers | … Within(d1: Distance, d2: Distance) returns (Boolean) contextual keywords/phrases: less than |  | … … end

April 19, 2005 (9) Task Recognition A task domain determination Input: a task specification, domain ontologies Output: a marked domain ontology A domain-independent process

April 19, 2005 (10) Appointment … context keywords/phrase: “appointment |want to see a |…” Dermatologist … context keywords/phrases: “([D|d]ermatologist) | …” I want to see a dermatologist next week; any day would be ok for me, at 4:00 p.m. The dermatologist must be within 20 miles from my home and must accept my insurance.

April 19, 2005 (11) Appointment … context keywords/phrase: “appointment |want to see a |…” Dermatologist … context keywords/phrases: “([D|d]ermatologist) | …” I want to see a dermatologist next week; any day would be ok for me, at 4:00 p.m. The dermatologist must be within 20 miles from my home and must accept my insurance.

April 19, 2005 (12) Appointment … context keywords/phrase: “appointment |want to see a |…” Dermatologist … context keywords/phrases: “([D|d]ermatologist) | …” I want to see a dermatologist next week; any day would be ok for me, at 4:00 p.m. The dermatologist must be within 20 miles from my home and must accept my insurance.

April 19, 2005 (13) Appointment … context keywords/phrase: “appointment |want to see a |…” Dermatologist … context keywords/phrases: “([D|d]ermatologist) | …” I want to see a dermatologist next week; any day would be ok for me, at 4:00 p.m. The dermatologist must be within 20 miles from my home and must accept my insurance.

April 19, 2005 (14) Appointment … context keywords/phrase: “appointment |want to see a |…” Dermatologist … context keywords/phrases: “([D|d]ermatologist) | …” I want to see a dermatologist next week; any day would be ok for me, at 4:00 p.m. The dermatologist must be within 20 miles from my home and must accept my insurance. Date … NextWeek(d1: Date, d2: Date) returns (Boolean) context keywords/phrases: next week | week from now | … Distance internal representation : real textual representation: ((\d+(\.\d+)?)|(\.\d+)) context keywords/phrases: miles | mile | kilometers | … Within(d1: Distance, “20”) returns (Boolean) context keywords/phrases: within | not more than |  | … return (d1  d2) … end

April 19, 2005 (15) Process Ontology Process to execute tasks in a domain Statenet  States  Transitions, based on ECA rules

April 19, 2005 (16) Process Ontology

April 19, 2005 (17) Task Execution Domain-independent subprocesses  Coded once  Specialized for a domain A domain-dependent subprocess  Fully determined (given the task specification and domain ontology)  Automatically generated

April 19, 2005 (18) Task View Creation

April 19, 2005 (19) Task View Creation

April 19, 2005 (20) Creation of Additional Task Constraints Date … NextWeek(d1: Date, d2: Date) returns (Boolean) context keywords/phrases: next week | week from now | … … end Distance internal representation: real textual representation: ((\d+(\.\d+)?)|(\.\d+)) context keywords/phrases: miles | mile | kilometers | … Within(d1: Distance, “20”) returns (Boolean) context keywords/phrases: within | not more than |  | … return (d1  d2) … end

April 19, 2005 (21) Creation of Additional Task Constraints Task  imposed constraints: NextWeek(d1: Date, d2: Date) Person(x) is at Address(a 1 ) and Dermatologist(y) is at Address(a 2 ) and Within(DistanceBetween(a 1, a 2 ), “20”)  i 2 (Dermatologist(y) accepts Insurance(i 2 ) and Equal(i 1, i 2 ))

April 19, 2005 (22) Obtaining Information from the System Appointment -> Dermatologist Insurance Time “4:00” Date Person Address Name Task  imposed constraints: NextWeek(d1: Date, d2: Date) Person(x) is at Address(a 1 ) and Dermatologist(y) is at Address(a 2 ) and Within(DistanceBetween(a 1, a 2 ), “20”)  i 2 (Dermatologist(y) accepts Insurance(i 2 ) and Equal(i 1, i 2 ))

April 19, 2005 (23) Obtaining Information from the System Appointment -> Dermatologist Dermatologist0 Dermatologist1 Insurance “IHC” “DMBA” Time “4:00” Date “5 Jan 05” “6 Jan 05” Person Address “Orem 600 State St.” “Lindon 12 Main St.” Name “Dr. Carter” “Dr. Larry” Task  imposed constraints: NextWeek(d1: Date, d2: Date) Person(x) is at Address(a 1 ) and Dermatologist(y) is at Address(a 2 ) and Within(DistanceBetween(a 1, a 2 ), “20”)  i 2 (Dermatologist(y) accepts Insurance(i 2 ) and Equal(i 1, i 2 ))

April 19, 2005 (24) Obtaining Information from the User Appointment -> Dermatologist Dermatologist0 Dermatologist1 Insurance “IHC” “DMBA” Time “4:00” Date “5 Jan 05” “6 Jan 05” Person Address “Orem 600 State St.” “Lindon 12 Main St.” Name “Dr. Carter” “Dr. Larry” Task  imposed constraints: NextWeek(d1: Date, d2: Date) Person(x) is at Address(a 1 ) and Dermatologist(y) is at Address(a 2 ) and Within(DistanceBetween(a 1, a 2 ), “20”)  i 2 (Dermatologist(y) accepts Insurance(i 2 ) and Equal(i 1, i 2 ))

April 19, 2005 (25) Obtaining Information from the User Appointment -> Dermatologist Dermatologist0 Dermatologist1 Insurance “IHC” “DMBA” Time “4:00” Date “5 Jan 05” “6 Jan 05” Person Person100 Address “Orem 600 State St.” “Lindon 12 Main St.” “Provo 300 State St.” Name “Dr. Carter” “Dr. Larry” “Lynn Jones” Task  imposed constraints: NextWeek(d1: Date, d2: Date) Person(x) is at Address(a 1 ) and Dermatologist(y) is at Address(a 2 ) and Within(DistanceBetween(a 1, a 2 ), “20”)  i 2 (Dermatologist(y) accepts Insurance(i 2 ) and Equal(i 1, i 2 ))

April 19, 2005 (26) Constraint Satisfaction Appointment -> Dermatologist Dermatologist0 Dermatologist1 Insurance “IHC” “DMBA” Time “4:00” Date “5 Jan 05” “6 Jan 05” Person Person100 Address “Orem 600 State St.” “Lindon 12 Main St.” “Provo 300 State St.” Name “Dr. Carter” “Dr. Larry” “Lynn Jones” Task  imposed constraints: NextWeek(d1: Date, d2: Date) Person(x) is at Address(a 1 ) and Dermatologist(y) is at Address(a 2 ) and Within(DistanceBetween(a 1, a 2 ), “20”)  i 2 (Dermatologist(y) accepts Insurance(i 2 ) and Equal(i 1, i 2 ))

April 19, 2005 (27) Constraint Satisfaction

April 19, 2005 (28) Constraint Satisfaction Task  imposed constraints: Person(Person100) is at Address((“Provo 300 State St.”) and Dermatologist(Dermatologist0) is at Address(“Orem 600 State St.”) and Within(DistanceBetween(“Provo 300 State St.”, “Orem 600 State St.”), “22”) Appointment ->  Dermatologist Dermatologist0 Insurance “IHC” “DMBA” Time “4:00” Date “5 Jan 05” Person Person100 Address “Orem 600 State St.” “Provo 300 State St.” Name “Dr. Carter” “Lynn Jones”

April 19, 2005 (29) Negotiation Task  imposed constraints: Person(Person100) is at Address((“Provo 300 State St.”) and Dermatologist(Dermatologist0) is at Address(“Orem 600 State St.”) and Within(DistanceBetween(“Provo 300 State St.”, “Orem 600 State St.”), “22”) Appointment ->  Dermatologist Dermatologist0 Insurance “IHC” “DMBA” Time “4:00” Date “5 Jan 05” Person Person100 Address “Orem 600 State St.” “Provo 300 State St.” Name “Dr. Carter” “Lynn Jones”

April 19, 2005 (30) Finalization NextWeek(“28 Dec 04”, “5 Jan 05”) Person(Person100) is at Address(“Provo 300 State St.”) and Dermatologist(Dermatologist0) is at Address(“Orem 600 State St.”) and Within(DistanceBetween(“Provo 300 State St.”, “Orem 600 State St.”), “22”)  i 2 (Dermatologist(Dermatologist0) accepts Insurance(i 2 ) and Equal(“IHC”, i 2 )) Appointment 7 Dermatologist0 “IHC” “DMBA” “4:00” “5 Jan 05” Person100 “Orem 600 State St.” “Provo 300 State St.” “Dr. Carter” “Lynn Jones”

April 19, 2005 (31) Testing “Black box” testing  Concept recognition  Constraint recognition  Domain recognition  Execution performance “White box” testing for the processes of the system such as  Negotiation  Obtaining information from the user

April 19, 2005 (32) Delimitations Recognition and execution of complex tasks  Compositional tasks  Alternative tasks  Conditional tasks Graphical or vocal specification of tasks

April 19, 2005 (33) Contributions Simplification of everyday task execution—find and use versus specify Automatic process generation for task execution  Domain recognition and specialization  Automatic information gathering from both system and user  Constraint satisfaction  Negotiation Prototype implementation