Distributed Information Retrieval Using a Multi-Agent System and The Role of Logic Programming.

Slides:



Advertisements
Similar presentations
FIPA Interaction Protocol. Request Interaction Protocol Summary –Request Interaction Protocol allows one agent to request another to perform some action.
Advertisements

Lecture 6/2/12. Forms and PHP The PHP $_GET and $_POST variables are used to retrieve information from forms, like user input When dealing with HTML forms.
1 Chapter 12 Working With Access 2000 on the Internet.
OCT1 Principles From Chapter One of “Distributed Systems Concepts and Design”
1 Information Retrieval and Extraction 資訊檢索與擷取 Chia-Hui Chang, Assistant Professor Dept. of Computer Science & Information Engineering National Central.
Information Retrieval and Extraction 資訊檢索與擷取 Chia-Hui Chang National Central University
Systems Architecture, Fourth Edition1 Internet and Distributed Application Services Chapter 13.
PubMed Search Options (Basic Course: Module 6). Table of Contents  History  Advanced Search  Accessing full text articles from HINARI/PubMed  Failure.
Introduction 2: Internet, Intranet, and Extranet J394 – Perancangan Situs Web Program Sudi Manajemen Universitas Bina Nusantara.
Chapter 11 ASP.NET JavaScript, Third Edition. 2 Objectives Learn about client/server architecture Study server-side scripting Create ASP.NET applications.
CGI Programming: Part 1. What is CGI? CGI = Common Gateway Interface Provides a standardized way for web browsers to: –Call programs on a server. –Pass.
The chapter will address the following questions:
Form Handling, Validation and Functions. Form Handling Forms are a graphical user interfaces (GUIs) that enables the interaction between users and servers.
INTRODUCTION TO WEB DATABASE PROGRAMMING
CO1552 Web Application Development HTML Forms. Websites can be made more interactive by providing facilities for users to provide data To get user entered.
T U T O R I A L  2009 Pearson Education, Inc. All rights reserved Bookstore Web Application Introducing Visual Web Developer 2008 Express and the.
1 3 Web Proxies Web Protocols and Practice. 2 Topics Web Protocols and Practice WEB PROXIES  Web Proxy Definition  Three of the Most Common Intermediaries.
Chapter 16 The World Wide Web Chapter Goals ( ) Compare and contrast the Internet and the World Wide Web Describe general Web processing.
Server-side Scripting Powering the webs favourite services.
4-1 INTERNET DATABASE CONNECTOR Colorado Technical University IT420 Tim Peterson.
思科网络技术学院理事会. 1 Application Layer Functionality and Protocols Network Fundamentals – Chapter 3.
Interoperability Scenario Producing summary versions of compound multimedia historical documents.
Chapter 16 The World Wide Web. 2 The Web An infrastructure of information combined and the network software used to access it Web page A document that.
Lesson 2 — The Internet and the World Wide Web
Information Systems: Databases Define the role of general information systems Describe the elements of a database management system (DBMS) Describe the.
HOW WEB SERVER WORKS? By- PUSHPENDU MONDAL RAJAT CHAUHAN RAHUL YADAV RANJIT MEENA RAHUL TYAGI.
CS 390- Unix Programming Environment CS 390 Unix Programming Environment Topics to be covered: Distributed Computing Fundamentals.
Web Services Week 7 Aims: A detailed look at the underlying mechanisms for communication between web services Objectives: SOAP, WSDL, UDDI.
1 Technologies for distributed systems Andrew Jones School of Computer Science Cardiff University.
Copyrighted material John Tullis 10/17/2015 page 1 04/15/00 XML Part 3 John Tullis DePaul Instructor
Using Client-Side Scripts to Enhance Web Applications 1.
Active Server Pages  In this chapter, you will learn:  How browsers and servers interacted on the Internet when the Internet first became popular 
Website Development with PHP and MySQL Saving Data.
1 Welcome to CSC 301 Web Programming Charles Frank.
1 © Netskills Quality Internet Training, University of Newcastle HTML Forms © Netskills, Quality Internet Training, University of Newcastle Netskills is.
HTML Basics BCIS 3680 Enterprise Programming. Web Client/Server Architecture 2  Your browser (the client) requests a Web page from a remote computer.
XHTML & Forms. PHP and the WWW PHP and HTML forms – Forms are the main way users can interact with your PHP scrip Typical usage of the form tag in HTML.
Microsoft FrontPage 2003 Illustrated Complete Creating a Form.
The Intranet.
WWW: an Internet application Bill Chu. © Bei-Tseng Chu Aug 2000 WWW Web and HTTP WWW web is an interconnected information servers each server maintains.
Search Tools and Search Engines Searching for Information and common found internet file types.
1 Web Servers (Chapter 21 – Pages( ) Outline 21.1 Introduction 21.2 HTTP Request Types 21.3 System Architecture.
Chapter 29 World Wide Web & Browsing World Wide Web (WWW) is a distributed hypermedia (hypertext & graphics) on-line repository of information that users.
Web Design and Development. World Wide Web  World Wide Web (WWW or W3), collection of globally distributed text and multimedia documents and files 
Module: Software Engineering of Web Applications Chapter 2: Technologies 1.
Web Services. 2 Internet Collection of physically interconnected computers. Messages decomposed into packets. Packets transmitted from source to destination.
27.1 Chapter 27 WWW and HTTP Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
Internet Applications (Cont’d) Basic Internet Applications – World Wide Web (WWW) Browser Architecture Static Documents Dynamic Documents Active Documents.
8 Chapter Eight Server-side Scripts. 8 Chapter Objectives Create dynamic Web pages that retrieve and display database data using Active Server Pages Process.
Web Services An Introduction Copyright © Curt Hill.
ASP-2-1 SERVER AND CLIENT SIDE SCRITPING Colorado Technical University IT420 Tim Peterson.
The basics of knowing the difference CLIENT VS. SERVER.
1 Java Server Pages A Java Server Page is a file consisting of HTML or XML markup into which special tags and code blocks are inserted When the page is.
© 2004 IBM Corporation WS-ResourceFramework Service Groups Tom Maguire.
Unit-6 Handling Sessions and Cookies. Concept of Session Session values are store in server side not in user’s machine. A session is available as long.
3M Partners and Suppliers Click to edit Master title style USER GUIDE Supplier eInvoicing USER GUIDE The 3M beX environment: Day-to-day use.
Collecting Copyright Transfers and Disclosures via Editorial Manager™ -- Editorial Office Guide 2015.
General Architecture of Retrieval Systems 1Adrienn Skrop.
XML 1. Chapter 8 © 2013 Pearson Education, Inc. Publishing as Prentice Hall SAMPLE XML SCHEMA (XSD) 2 Schema is a record definition, analogous to the.
Dynamic/Deferred Document Sharing (D3S) Profile for 2010 presented to the IT Infrastructure Technical Committee Karen Witting February 1, 2010.
Topic 4: Distributed Objects Dr. Ayman Srour Faculty of Applied Engineering and Urban Planning University of Palestine.
Navigation Mimi Opkins CECS 493 Fall Static Navigation  In a simple web application, navigation is static. That is, clicking a particular button.
1 Chapter 1 INTRODUCTION TO WEB. 2 Objectives In this chapter, you will: Become familiar with the architecture of the World Wide Web Learn about communication.
Programming Logic and Design Seventh Edition
Introduction Web Environments
Chapter 27 WWW and HTTP.
Application layer Lecture 7.
PHP and Forms.
Lecture 5: Functions and Parameters
WEB SERVICES From Chapter 19, Distributed Systems
Presentation transcript:

Distributed Information Retrieval Using a Multi-Agent System and The Role of Logic Programming

Why Multi-Agents Systems? The Distributed Information Retrieval task deals with the collection of information from multiple and usually heterogeneous information sources that exist in a distributed environment. To cope with the Information Management problem of Distributed Information Retrieval, we use a Multi-Agent System.

System Architecture: One way to address this problem is to use information agents. These distributed information retrieval agents should be able to: Accept a request from a human or agent client. Translate this request into a language understood by the information sources. Identify the information sources that contain information relevant to the request. Pose the request to these sources. Collect the corresponding results. Process the returned results and Present the results to the client.

The role of Logic Programming: First, the query language used to express the user‘s requests is a Prolog variant. There is a set of predicates that the user has to use in order to express his request. These predicates correspond to attributes that characterize the aspects of the supported information. The role of constraints: The main advantages of using constraints are: 1. For the users: constraints can be used to flexibly specify partial requests where the level of approximation is varying. 2. For the information providers: constraints can be used to dynamically augment processing abilities by filtering result items on a per constraint basis.

The roles of the agents: Scanner Assistant: This assistant handles the identification of the web pages that contain the desired information. The main argument that it takes is the top URL. This URL can be of two types: - A http location, - A local directory name, file://archive/file://archive/

Extractor Agent: This agent has now the task to detect which of them contain actually relevant information, to extract this information and to represent it in an attribute-based format. The extractor goes through web pages to spot any textual portions that are used to describe some technical paper and then examine each small textual part. Finally, the detection of the above attributes is performed with the assistance of other formatting information.

User Agent: The graphical interface that handles the input of the user query is based on a WWW browser form. Using the below form the user enters the query in a Prolog-like form and sets various arguments that determine a customized processing. After the user submits his query with its associated options, the user agent transforms it into a message structure. The transformed query is then sent to the corresponding information request facilitator for further processing and appropriate forwarding.

In Figure given below we can see the way that the results are displayed back to the user. They are displayed through the same web interface via an HTML page.

Information Request Facilitator: The facilitator can subscribe to the matchmaker for attribute values (like specific authors or topics) that are considered very probable to be requested. Using information of the most recent and most frequent queries, the information request facilitator may find information supply facilitators that successfully processed a query similar to the current one, in order to pass it to them. Matchmaker: Matchmakers are either requests related to the processing of a specific query or subscriptions about popular attribute values. The relationship (synonym, hyponym, hypernym) between any requested topic and the actually supported ones indicated in the matchmaker response, will be forwarded to the user agent.

Information Supply Facilitator: When the source agents register with information supply facilitator, the source agents send an abstracted form of the information they possess. This summary information includes the attribute values that occur in a repeated manner in the information bases of the source agents. The summary information has to be done in order to identify which of the registered source agents declared that they contain information like the one that the query expresses.

Information Source Agent: The final destination of our example query is the information source agent (or briefly source agent). The documents that provided a successful query evaluation will be returned to the user agent. If however the evaluation does not produce any successful results, then the information supply facilitator will be notified for this failure. If the information request facilitator receives general failures from all the information supply facilitators, then the user agent is notified for a final and complete failure.