ontology aware software service agents: meeting ordinary user needs on the semantic web

Download Ontology Aware Software Service Agents: Meeting Ordinary User Needs on the Semantic Web

Post on 19-Jan-2016

15 views

Category:

Documents

1 download

Embed Size (px)

DESCRIPTION

Ontology Aware Software Service Agents: Meeting Ordinary User Needs on the Semantic Web. Muhammed Al-Muhammed. April 19, 2005. The Challenge. Reduce information overload Find and use services. - PowerPoint PPT Presentation

TRANSCRIPT

  • Ontology Aware Software Service Agents: Meeting Ordinary User Needs on the Semantic WebMuhammed Al-MuhammedApril 19, 2005

  • 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.

  • 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

  • Approach Task ontologyDomain ontologyProcess ontology CharacteristicsTask specification: Free-form textRequest recognition: find best task ontologyTask executionSpecialize task ontology processesExecute generated code

  • Domain Ontology ComponentsObject sets = concepts Relationship setsConstraints UsesTask knowledgeTask recognition

  • Domain Ontology

  • Domain Ontology Augmented with data frames A data frame defines information about a conceptIts internal and external representationIts contextual keywords or phrasesOperations along with contextual keywords or phrases

  • Data Frames

  • Task Recognition A task domain determination Input: a task specification, domain ontologies Output: a marked domain ontology A domain-independent process

  • 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.

  • 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.

  • 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.

  • 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.

  • 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 |

    Distanceinternal representation : realtextual representation: ((\d+(\.\d+)?)|(\.\d+))context keywords/phrases: miles | mile | kilometers | Within(d1: Distance, 20)returns (Boolean)context keywords/phrases: within | not more than | | return (d1d2)end

  • Process Ontology Process to execute tasks in a domain StatenetStates Transitions, based on ECA rules

  • Process Ontology

  • Task Execution Domain-independent subprocessesCoded onceSpecialized for a domain A domain-dependent subprocessFully determined (given the task specification and domain ontology)Automatically generated

  • Task View Creation

  • Task View Creation

  • Creation of Additional Task ConstraintsDate NextWeek(d1: Date, d2: Date)returns (Boolean)context keywords/phrases: next week | week from now | endDistanceinternal representation: realtextual representation: ((\d+(\.\d+)?)|(\.\d+)) context keywords/phrases: miles | mile | kilometers | Within(d1: Distance, 20)returns (Boolean)context keywords/phrases: within | not more than | | return (d1d2)end

  • Creation of Additional Task Constraints

    Taskimposed constraints: NextWeek(d1: Date, d2: Date) Person(x) is at Address(a1) and Dermatologist(y) is at Address(a2) and Within(DistanceBetween(a1, a2), 20) i2 (Dermatologist(y) accepts Insurance(i2 ) and Equal(i1, i2))

  • Obtaining Information from the System

    Appointment -> Dermatologist Insurance Time 4:00 Date Person Address Name Taskimposed constraints: NextWeek(d1: Date, d2: Date) Person(x) is at Address(a1) and Dermatologist(y) is at Address(a2) and Within(DistanceBetween(a1, a2), 20) i2 (Dermatologist(y) accepts Insurance(i2 ) and Equal(i1, i2))

  • Obtaining Information from the System

    Taskimposed constraints: NextWeek(d1: Date, d2: Date) Person(x) is at Address(a1) and Dermatologist(y) is at Address(a2) and Within(DistanceBetween(a1, a2), 20) i2 (Dermatologist(y) accepts Insurance(i2 ) and Equal(i1, i2))

  • Obtaining Information from the UserTaskimposed constraints: NextWeek(d1: Date, d2: Date) Person(x) is at Address(a1) and Dermatologist(y) is at Address(a2) and Within(DistanceBetween(a1, a2), 20) i2 (Dermatologist(y) accepts Insurance(i2 ) and Equal(i1, i2))

  • Obtaining Information from the User

    Taskimposed constraints: NextWeek(d1: Date, d2: Date) Person(x) is at Address(a1) and Dermatologist(y) is at Address(a2) and Within(DistanceBetween(a1, a2), 20) i2 (Dermatologist(y) accepts Insurance(i2 ) and Equal(i1, i2))

  • Constraint SatisfactionTaskimposed constraints: NextWeek(d1: Date, d2: Date) Person(x) is at Address(a1) and Dermatologist(y) is at Address(a2) and Within(DistanceBetween(a1, a2), 20) i2 (Dermatologist(y) accepts Insurance(i2 ) and Equal(i1, i2))

  • Constraint Satisfaction

    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.), 20)

    (Dermatologist(Dermatologist0) accepts Insurance(IHC ) and Equal(IHC,IHC) or Dermatologist(Dermatologist0) accepts Insurance(DMBA) and Equal(IHC,DMBA))

    Person(Person100) is at Address(Provo 300 State St.) and Dermatologist(Dermatologist1) is at Address(Lindon 12 Main St.) and Within(DistanceBetween(Provo 300 State St., Lindon 12 Main St.), 20)

    (Dermatologist(Dermatologist1) accepts Insurance(DMBA) and Equal(IHC,DMBA))

  • 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)

  • 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)

  • FinalizationNextWeek(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) i2 (Dermatologist(Dermatologist0) accepts Insurance(i2) and Equal(IHC, i2))

  • Testing Black box testingConcept recognitionConstraint recognitionDomain recognitionExecution performance White box testing for the processes of the system such as NegotiationObtaining information from the user

  • Delimitations Recognition and execution of complex tasksCompositional tasksAlternative tasksConditional tasks Graphical or vocal specification of tasks

  • ContributionsSimplification of everyday task executionfind and use versus specifyAutomatic process generation for task executionDomain recognition and specializationAutomatic information gathering from both system and user Constraint satisfactionNegotiationPrototype implementation

Recommended

View more >