Re: Future browsers...

Tony Sanders <>
Message-id: <199311210208.UAA04980@austin.BSDI.COM>
Subject: Re: Future browsers... 
In-Reply-To: Sebastian Francis Heath's message of Sat, 20 Nov 1993 17:40:33 EST.
Organization: Berkeley Software Design, Inc.
Date: Sat, 20 Nov 1993 20:08:54 -0600
From: Tony Sanders <>
> for example, a user to select a word s/he doesn't understand and ask that 
> it be looked up in a dictionary/glossary  or a site name can be looked up 
> implementation.  Could there be an "<ISSELECTABLE>" tag with an 
That's exactly what <LINK REV="UseGlossary" HREF="...">
is supposed to do.  <LINK>/REL/REV seem to be the most misunderstood
(or at least under-implemented) part of the WWW design.

> somewhere on the page.  Obviously this is not just a client side change.
Actually, it pretty much is just a client side change.  All you have to
do is query the HREF with the selected word (using the standard "URL?query"
syntax).  Yes, you need server support for the query but that's not really
a "change" as we already know how to do queries.  Also, this would only
require a trivial amount of code in the browser (select current word and
initiate a normal URL jump).

> support window type choices.  What would people think of a public 
> access/kiosk version of the client?  
> The second request may seem to go against the spirit of the web.  I would 
Sounds easy enough to do.  You probably want a "start over" button or
something.  I don't think it goes against the spirit of the web at all.