1

WEB SERVICES BASED INFORMATION ACCESS ARCHITECTURE

Christian Belbeze, Max Chevalier, Chantal Soulé-Dupuy

Institut de Recherche en Informatique de Toulouse ( IRIT ) Institut de Recherche en Informatique de Toulouse ( IRIT ) & Université Toulouse 1& Université Toulouse 1

FranceFrance

2

Agenda

User searching on the Web observation, difficulties and frustration

A software proposition to help users Individual assistance Web services as basic component The four Information access phases and involved

components Different Human Machine Interface for different users Sequence diagram Phase 2 and 3 samples Assessment

Conclusion

3

Experimentation: Users’ feeling searching the web.

Users’ satisfaction average is only 6,25/10

Users Usage Experience “Success” age Feeling

Annie rare >5 years 40 72 6.3

Celine monthly <1 years 50 11 4

Georges never 0 40 49 6

Guillaume

weekly between 1 and 5 years 100 11 7

Jean daily between 1 and 5 years 60 16 6.3

Lou rare between 1 and 5 years 50 7 5.5

Marie rare < 1 year 60 37 5.7

Paul weekly between 1 and 5 years 50 7 10

Yasmina monthly > 5 years 33 20 6.5

4

Experimentation: Users searching the web

All users’ presentations and observations are on http://www.mysissi.com

Notes and all measurements values are on http://www.mysissi.com/listebasesissibd.php

5

Difficulties to

1. Find the accurate keywords

2. Identify relevant Web sites

3. Extract raw information

Experimentation: Difficulties

6

An individual assistant to simplify Internet

Individual System to

Simplify Internet Services

7

An individual assistant to simplify Internet

Individualized assistance

A specific organization of individual components

Each Individual component is independent

User builds his own data processing chain collecting and managing individual components

Component could be developed by anyone

Components are naturally Web Services

8

The general architecture of the platform

9

Component Interface Architecture

10

The four Information Access Phases

1. Building query

2. Pickup in the heap

3. Just for me

4. As I want it , to save it and work on it

11

Phase 1: Building query

The goal is: Creating a valid query Choosing determinant keywords Being in the right semantic space …

Components could: Propose semantic spaces Translate acronyms to/from Small Message Service

Propose synonyms of keywords Propose lists of icons to replace words Translate keywords in other languages, and so on.

12

Phase 2: Pick up in heap

The goal is:Finding the relevant information in the proposed list

Components could: Place information-bubbles to explain URL Place information-bubbles to give an abstract of the

page Add a specific icon to explain contents, semantic

space, sources of information and its’ nature Display results via a specific metaphor Translate text in a specific language, and so on.

13

Phase 3: Just for me

The goal is: Getting information in the right format for a specific User

Components could: Ajust display or adapt colors (for people affected by color-blindness) and/or

adapt font size Colorize keywords Transform text into audio file or prepare to be printed in Braille Filter pornographic, violent images Adapt to specific hardware (phone, PDA…) Place information-bubbles giving a definition of “complex” word;

14

Phase 4: As I want it now

The goal is: Transforming information in the right format to be manipulate, stored

and shared

Components could: Transform and save file in multiple formats (Word to PDF, PDF to XML,

images to text using OCR, extract score from midi file …)

Compare contents with other ones Fax, iPrint or mail the document Analyze document (count word, ontological classification, …)

Summarize document content Search other documents having a similar content

15

Different types of Human Machine Interface

Phase 3

Phase 1  

Phase 2

Classical interface

Advanced interface

16

Sequence diagram Phase 2 for a specific user

Adapted Content

17

Original Site

Sequence diagram Phase 3 for a specific user

Adapted Content

18

Assessment

Observations in coherence with the previous studies Key words Universality of the difficulties …

Modeling the user Helping before qualifying Emergence of dynamic communities

Modeling the components Components could be combined to help user in

an infinity number of ways Open/shared space

19

Conclusion

A user in the center of a personalized and community device

An open/shared architecture

20

Questions ?

http://www.mysissi.com