Changes between Initial Version and Version 1 of Beyond Browsing: The Web of the Future


Ignore:
Timestamp:
Oct 21, 2009, 8:47:14 AM (15 years ago)
Author:
kthoden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Beyond Browsing: The Web of the Future

    v1 v1  
     1{{{
     2#!html
     3
     4    <h1>Beyond Browsing: The Web of the Future</h1>
     5
     6<p>The current paradigm of the web &mdash; in which the user
     7<i>browses,</i> leaving behind a clicktrail that is of interest
     8primarily to marketers &mdash; falls far short of the needs of
     9scientists and scholars. <i>Browsing</i> the web is scarcely more
     10interactive than <i>surfing</i> television channels. True
     11interactivity &mdash; which will allow the web finally to achieve its
     12potential as a medium for scholarly, political, and social dialogue
     13
     14&mdash; demands something other than the current browser/server
     15paradigm. New tools will be needed, whose developers recognize that
     16information <i>consumers</i> are also information <i>producers.</i>
     17Scholarship is an inherently recursive activity, in that the scholar
     18uses <i>existing</i> scholarship to produce <i>new</i> scholarship.
     19Knowledge undergoes a process of accretion, akin to the formation of a
     20pearl; one exemplary model is a page of the <a
     21href="http://ccat.sas.upenn.edu/rs/2/Judaism/talmud.html"
     22target="_blank">Talmud</a>, on which there is a hierarchical
     23arrangement of commentary, super-commentary, annotation, and
     24cross-reference that spreads from center to margin.</p>
     25
     26<p>Information production is possible within the web browser of today
     27&mdash; using <a href="http://en.wikipedia.org/wiki/Wiki"
     28target="_blank">Wikis</a>, or content management systems such as <a
     29href="http://www.zope.org/" target="_blank">Zope</a>. But these tools
     30seem like primitive intruders in an environment that was engineered
     31primarily for publication. True interactivity demands a new tool: not
     32a <i>browser,</i> but an <i>interagent.</i> With these ideas in mind,
     33for the past few years, the <a href="http://www.mpiwg-berlin.mpg.de/"
     34target="_blank">Max-Planck-Institut f&uuml;r
     35Wissenschaftsgeschichte</a> has been developing, in collaboration with
     36
     37<a href="http://www.harvard.edu/" target="_blank">Harvard
     38University</a>, a prototype interagent called <i>Arboreal.</i>
     39Arboreal allows for flexible, non-linear navigation of arbitrary XML
     40documents and for granular annotation of these documents down to the
     41word- or term-level. Annotations themselves are XML data, which can be
     42shared, published, and further annotated in turn.</p>
     43
     44<p>Natural language is the primary means by which humans communicate
     45&mdash; though it is supplemented, of course, by formal languages and
     46other symbolic systems and by pictures and other audio-visual media.
     47Yet today's web browsers provide only the crudest tools to support
     48natural language documents. Most linguistic support in browsers is
     49focused on visual <i>presentation</i> of text in some writing system.
     50Even in this area, the technology comes up short: what browsers can
     51properly render Chinese or Mongolian in their traditional vertical
     52layouts or can adequately deal with Japanese ruby?<sup><a
     53href="#fn1">1</a></sup><a name="m1"></a> Beyond display, browsers also
     54typically allow for the <i>searching</i> of text &mdash; but again
     55only in an unsophisticated and inflexible way, which is of limited
     56value even for most western European languages, and is thoroughly
     57inadequate for highly inflected languages or languages written in
     58complex scripts.</p>
     59
     60<p>Tomorrow's interagents must provide more sophisticated linguistic
     61capabilities: language technology must be available from within the
     62interagent. Yet this is not to say that language technology should be
     63<i>built in</i> to the interagent; such a monolithic approach can only
     64fail users from complex and diverging linguistic, ethnic, and
     65professional backgrounds, and with equally heterogeneous needs and
     66interests. Rather, a <i>services-oriented</i> architecture is needed,
     67in which the interagent can communicate with linguistic web services
     68(via, for example, <a href="http://www.xmlrpc.com/"
     69target="_blank">XML-RPC</a> or <a
     70href="http://www.w3c.org/2000/xp/Group/" target="_blank">SOAP</a>) and
     71dynamically acquire new linguistic behaviors (via the dynamic
     72class-loading mechanisms offered by frameworks such as <a
     73href="http://java.sun.com/" target="_blank">Java</a> or <a
     74href="http://www.microsoft.com/net/" target="_blank">.NET</a>). Again,
     75Arboreal has been designed to implement these techniques: via web
     76services it can acquire morphological data that allow for lemmatized
     77searching, lexicon lookup, and other language-based functions. In
     78addition, it supports pluggable language behaviors that allow for
     79dynamic transliteration of writing systems such as Arabic, Greek, and
     80Chinese and for orthographically-normalized searching that renders the
     81spelling peculiarities of (e.g.) early modern texts transparent to the
     82user. These are critical and basic functions that will serve as the
     83foundation in the future for a richer set of facilities, including
     84term and keyword discovery, language-neutral searching based on
     85concepts rather than words, automatic summarization, and sophisticated
     86semantic linking.</p>
     87
     88    <hr>
     89<h2>Notes</h2>
     90<ol>
     91<li><a name="fn1"></a>Cf. Y. Haralambous, <q>Unicode et typographie:
     92un amour impossible?</q>, <cite>Document Num&eacute;rique</cite> 3/4
     93(2002), 105-37. Ruby annotation is dealt with in a W3C recommendation:
     94
     95<a href="http://www.w3.org/TR/ruby"
     96target="_blank">http://www.w3.org/TR/ruby</a>. [<a href="#m1">main
     97text</a>]
     98</ol>
     99}}}