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.

Issues for Future Research<br />

There are three basic structures for texts:<br />

1. Stream<br />

2. Hierarchical object based<br />

3. Network object based<br />

Stream structured texts are based on a typescript model and are similar to those prepared with most word<br />

processors. They are l<strong>in</strong>ear sequences of text data, consist<strong>in</strong>g of a stream of words. Embedded markers<br />

<strong>in</strong>dicated events (such as the beg<strong>in</strong>n<strong>in</strong>g of a new l<strong>in</strong>e or a tab). The stream model can apply to non-text<br />

data as well; time-based media (sound, video) are almost always digitized as streams.<br />

In object-based structures, textual objects such as paragraphs or lists actually exist rather than be<strong>in</strong>g<br />

represented by events as <strong>in</strong> the stream based model. For example, <strong>in</strong> HTML (an object-based markup<br />

system) each object is def<strong>in</strong>ed by a beg<strong>in</strong>n<strong>in</strong>g of object marker (e.g. and an end-of object<br />

marker (). By contrast, a word processor (such as Microsoft Word) marks a paragraph<br />

strictly by the end of paragraph event, and except for a few selection commands, does not deal with text<br />

objects per se. Anyone who has reviewed student papers (or conference proceed<strong>in</strong>gs) submitted <strong>in</strong><br />

mach<strong>in</strong>e-readable form has experienced the wide range of <strong>format</strong>t<strong>in</strong>g events used by different authors to<br />

def<strong>in</strong>e textual structures. On the other hand, there is only one way to def<strong>in</strong>e, for example, an unordered<br />

list <strong>in</strong> HTML, which treats such lists as objects rather than as a sequence of <strong>format</strong>t<strong>in</strong>g commands.<br />

Software for publish<strong>in</strong>g large documents (such as Framemaker) as well as markup systems developed<br />

for large documents (such as most document type def<strong>in</strong>itions <strong>in</strong> SGML) usually adapt a hierarchical object<br />

based organization [Goldfarb 1990]. The hierarchical structure is traditional and the reasons for it are<br />

twofold. First, it has significant advantages <strong>in</strong> simplify<strong>in</strong>g the human <strong>in</strong><strong>format</strong>ion process<strong>in</strong>g problems<br />

aris<strong>in</strong>g from large structures [Lehman 1990]. Second, given the enforced l<strong>in</strong>ear structure of pr<strong>in</strong>t, it is<br />

easy to implement. However, as any author who has ever force-fit a series of ideas <strong>in</strong>to a hierarchical<br />

outl<strong>in</strong>e knows, the structure often does not fit the content.<br />

Network object based structures attempt to deal with this problem by adapt<strong>in</strong>g an object-based model but<br />

not requir<strong>in</strong>g a hierarchical structure. Such structures are difficult to implement <strong>in</strong> pr<strong>in</strong>t (although<br />

footnotes and cross-references make the attempt); they are trivial <strong>in</strong> a computer-based document. They<br />

place additional demands on the user <strong>in</strong> terms of cognitive process<strong>in</strong>g.<br />

In terms of this theoretical differentiation of text types, the exploratory study described above offers<br />

evidence that users do not f<strong>in</strong>d that www-based implementation of the stream model and the shallow<br />

hierarchical object based model (book, chapter, section) add value to pr<strong>in</strong>ted versions except <strong>in</strong> terms of<br />

currency. Unfortunately, the structure of our study did not allow us to dist<strong>in</strong>guish between more deeply<br />

hierarchical object based structures and network object based structures. The question for designers of<br />

www-based educational and reference material is whether users f<strong>in</strong>d one or the other of these two<br />

structures better for the communication of <strong>in</strong><strong>format</strong>ion, and how a web-based hierarchical structure<br />

compares with a pr<strong>in</strong>ted one <strong>in</strong> terms of user acceptance. We plan to test these questions <strong>in</strong> future studies.<br />

Conclusion<br />

As the Web's popularity has grown, the skills needed to f<strong>in</strong>d, read, and manipulate Hypertext documents<br />

will become more common. At the same time, it is important that authors of www-based material design<br />

and write them to take advantage of the new medium rather than mechanically translat<strong>in</strong>g from an older<br />

form.<br />

References

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

Saved successfully!

Ooh no, something went wrong!