28.06.2013 Views

Papers in PDF format

Papers in PDF format

Papers in PDF format

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Mockapetris 1987b].<br />

DNS-style type def<strong>in</strong>ition service might seem like overkill <strong>in</strong>itially and would result <strong>in</strong> delays for pioneer users of<br />

document types. Without a substantial local cache, document type queries would have to be sent across the Internet for<br />

practically every Web document viewed. An alternative would be to have documents <strong>in</strong>clude their type def<strong>in</strong>ition code<br />

at the top or reference a URL where such a def<strong>in</strong>ition might be found. This is how it is done with style sheets.<br />

Regardless of how the hierarchy is ma<strong>in</strong>ta<strong>in</strong>ed, develop<strong>in</strong>g the <strong>in</strong>itial core taxonomy is a daunt<strong>in</strong>g task. The taxonomies<br />

developed by librarians are only a partial solution because they do not generally concern themselves with the sorts of<br />

ephemera that constitute the bulk of Internet traffic. If we don't get the core taxonomy right, we won't reap the benefits<br />

of useful standard software.<br />

Conclusions<br />

Measured aga<strong>in</strong>st the yardstick of "how well does this Internet th<strong>in</strong>g work?", HTML is an underachiever. It lacks<br />

sufficient structural and <strong>format</strong>t<strong>in</strong>g tags to render many documents comprehensible much less aesthetic, even with the<br />

addition of style sheets. The META tag can be exploited to implement a document typ<strong>in</strong>g system. We need to develop a<br />

hierarchy of document types to facilitate implementation of programs that automatically process Web documents. This<br />

type system must support multiple <strong>in</strong>heritance. If we fail to develop some k<strong>in</strong>d of semantic tagg<strong>in</strong>g system, computers<br />

will be unable to render us any useful assistance with Web documents until the dawn of Artifical Intelligence, i.e.,<br />

natural language understand<strong>in</strong>g and common sense reason<strong>in</strong>g.<br />

References<br />

Mart<strong>in</strong> Gilbert 1991. Churchill A Life Henry Holt & Company, New York, page 595<br />

Lie, H.W., Bos, B. 1996. "Cascad<strong>in</strong>g Style Sheets, W3C Work<strong>in</strong>g Draft"<br />

(http://www.w3.org/pub/WWW/TR/WD-css1.html)<br />

Malone, Thomas W., Grant, Kenneth R., Lai, Jum-Yew, Rao, Ramana, and Rosenblitt, David 1987. "Semistructured<br />

Messages are Surpris<strong>in</strong>gly Useful for Computer-Supported Coord<strong>in</strong>ation." ACM Transactions on Office In<strong>format</strong>ion<br />

Systems, 5, 2, pp. 115-131.<br />

Malone, Thomas W., Yu, Keh-Cha<strong>in</strong>g, Lee, J<strong>in</strong>tae 1989. What Good are Semistructured Objects? Add<strong>in</strong>g Semiformal<br />

Structure to Hypertext. Center for Coord<strong>in</strong>ation Science Technical Report #102. M.I.T. Sloan School of Management,<br />

Cambridge, MA<br />

Mockapetris, P.V. 1987a. "Doma<strong>in</strong> Names: Concepts and Facilities," RFC 1034<br />

Mockapetris, P.V. 1987b. "Doma<strong>in</strong> Names: Concepts and Facilities," RFC 1035<br />

Ondaatje, Michael 1992. The English Patient. V<strong>in</strong>tage International, New York<br />

Stevens, W. Richard 1994. TCP/IP Illustrated, Volume 1: The Protocols. Addison-Wesley, Read<strong>in</strong>g, Massachusetts

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

Saved successfully!

Ooh no, something went wrong!