Re: Server control over history?

• Mail folder: WWW Talk Jan 94-present
• Next message: Dave_Raggett: "Re: SGML parsing, moving between formats"
• Previous message: Tim Berners-Lee: "Re: Proxy Servers"
• Maybe in reply to: Daniel W. Connolly: "Re: Server control over history? "

Errors-To: listmaster@www0.cern.ch
Date: Wed, 16 Feb 1994 14:44:37 --100
Message-id: <9402161337.AA17424@manuel.hpl.hp.com>
Errors-To: listmaster@www0.cern.ch
Reply-To: dsr@hplb.hpl.hp.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Dave_Raggett <dsr@hplb.hpl.hp.com>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Server control over history? 
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Length: 1066

Dan,

I couldn't retrieve the references you gave for managing history
using HyTime. In reading through the HyTime architectural forms
and background material, I didn't see anything directly relevant
to issues such as what can and can't be scrolled away.

My suggestion for extending the LINK attribute is a very natural
extension to HTML and builds on earlier precedents. We have
recently developed a flexible scheme for expressing hypertext
paths, where paths are themselves HTML documents. The ability
to specify images for such navigation buttons is already popular
in the WWW community, and my suggestion extends this to include
a document toolbar, using the LINK element.

HyTime's location ladders and event mapping etc. are largely
orthogonal to these ideas. Indeed, it is already clear how to
add the HyTime clink architectural form into HTML, as an alternative
to the current HREF and SRC attributes. Perhaps you could make
a more concrete proposal for how this would effect issues such
as management of history and visibility of navigation buttons.

Dave