28.06.2013 Views

Papers in PDF format

Papers in PDF format

Papers in PDF format

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

There are three other systems that provide support for chronological awareness based on different designs and<br />

implementations. They are briefly exam<strong>in</strong>ed <strong>in</strong> this subsection, then followed by a comparative evaluation.<br />

WEBWATCH<br />

WebWatch is a client-side chronological awareness system for keep<strong>in</strong>g track of changes <strong>in</strong> selected web documents.<br />

Given an HTML document referenc<strong>in</strong>g URLs on the web, it produces a filtered list, conta<strong>in</strong><strong>in</strong>g only those URLs that<br />

have been modified s<strong>in</strong>ce a given time. The criteria used for filter<strong>in</strong>g can be given as a global sett<strong>in</strong>g that applies to all<br />

URLs, or can be derived automatically, us<strong>in</strong>g the time of user's last visit to the document, as recorded by the web<br />

browser <strong>in</strong> the user's local HTML (e.g., bookmark) file. In contrast with the simple time-l<strong>in</strong>e list<strong>in</strong>g strategy used <strong>in</strong><br />

CHRONO, WebWatch stores its arguments <strong>in</strong> a parameter file. Once the users have customized the program to their<br />

needs, us<strong>in</strong>g its graphical front-end, they can have it run periodically <strong>in</strong> unattended mode.<br />

KATIPO<br />

Katipo is another client-side chronological awareness system built for Mac<strong>in</strong>tosh that shares many similar concepts with<br />

WebWatch. It reads through the Global History file ma<strong>in</strong>ta<strong>in</strong>ed by some web browsers check<strong>in</strong>g for documents that<br />

have changed s<strong>in</strong>ce the last time a user viewed them. The basic difference between it and WebWatch is that it uses the<br />

Global History file as its reference for check<strong>in</strong>g URLs, whereas WebWatch uses the Bookmark file.<br />

URL-MINDER<br />

URL-m<strong>in</strong>der is a centralized system that keeps track of resources on the Net and sends registered users e-mail whenever<br />

their personally registered resources change. Users can have URL-m<strong>in</strong>der keeps track of any web resource accessible via<br />

HTTP. It keeps track of one web page, image file, or other Internet resource at a time. It tracks the actual HTML<br />

markup, b<strong>in</strong>ary contents, or ASCII contents of the URL users have submitted. If an HTML page <strong>in</strong>cludes a GIF or JPEG<br />

graphic, the URL-m<strong>in</strong>der will <strong>in</strong>form them via E-mails when the reference to the graphic changes. The URL-m<strong>in</strong>der<br />

currently checks on users' registered URL's at least once per week, and will <strong>in</strong>form users if it fails to retrieve their<br />

registered URL after try<strong>in</strong>g twice.<br />

SYSTEMS EVALUATION WITHIN THE<br />

METHODOLOGICAL FRAMEWORK<br />

This section presents a comparative evaluation of the four chronological awareness support systems discussed earlier:<br />

CHRONO, WebWatch, Katipo, and URL-m<strong>in</strong>der. Each system has its unique approaches for achiev<strong>in</strong>g chronological<br />

awareness for web users and complement each other along four ma<strong>in</strong> dimensions.<br />

The first dimension, the locus of responsibility, differentiates who is responsible for ma<strong>in</strong>ta<strong>in</strong><strong>in</strong>g the record-keep<strong>in</strong>g<br />

mechanisms for chronological awareness. For example, CHRONO is a server-side system <strong>in</strong> which chronological<br />

list<strong>in</strong>gs are be<strong>in</strong>g updated and kept at the web server-side. Thus, CHRONO can be thought of as offer<strong>in</strong>g "chronological<br />

awareness on demand". WebWatch and Katipo, however, put the responsibility of ma<strong>in</strong>ta<strong>in</strong><strong>in</strong>g chronological awareness<br />

on the client-side. Both client side systems periodically monitor specific pages at various web sites and report whether<br />

or not they have been changed recently. F<strong>in</strong>ally, URL-m<strong>in</strong>der requires its users to register at a centralized site.<br />

The second dimension, the level of 'work group' hierarchy, signifies that all of the current chronological awareness<br />

support systems are ma<strong>in</strong>ly focused at the group level (and to some extend at the organizational level). Collectively,<br />

they are support<strong>in</strong>g chronological awareness of <strong>in</strong><strong>format</strong>ion resource typified by closely-coupled collaboration at the<br />

group level.<br />

The third dimension, the method of locat<strong>in</strong>g changes, <strong>in</strong>volves two different ways of locat<strong>in</strong>g documents that have been<br />

changed: brows<strong>in</strong>g and target<strong>in</strong>g. CHRONO uses the brows<strong>in</strong>g approach <strong>in</strong> order to facilitate the chronological<br />

brows<strong>in</strong>g characteristic. Conversely, WebWatch, Katipo, and URL-m<strong>in</strong>der employ a target<strong>in</strong>g approach <strong>in</strong> which they<br />

are targeted on specific pages or <strong>in</strong><strong>format</strong>ion that users have previously specified.<br />

F<strong>in</strong>ally, the fourth dimension, the complexity of user <strong>in</strong>teraction, denotes system usability <strong>in</strong> terms of simplicity vs.<br />

customization. CHRONO and URL-m<strong>in</strong>der are <strong>in</strong> the simplicity category; their user <strong>in</strong>terfaces are simple and familiar to

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!