Subject: Link Behaviors
From: email@example.com (David G. Durand)
Date: Mon, 30 Dec 1996 12:19:34 -0500
From firstname.lastname@example.org Mon Dec 30 12: 12:58 1996
>>o the primitives used to locate objects within it, traverse it, and
>Primitives? Need to clarify. Functions?
As far as I can tell, we need query functions, and the ability to specify a
Offer choice of options (menu or list as appropriate to display device)
navigate, replacing current document,
navigate, creating a new display area (as appropriate to display device)
Highlight linkend (since it may not be in the markup, this cannot be
part of normal rendering)
Can anyone think of any other link behavior we need?
>Proposals are needed.
And starting, I think.
> To get the credibility needed for acceptance,
>not only the spec, but appendices on implementation and/or working
>code will be needed.
I have not seen any suggestion that is remotely problematic enough to
necessitate this yet. It may happen, but not yet.
I am not a number. I am an undefined character.
David Durand email@example.com \ david@dynamicDiagrams.com
Boston University Computer Science \ Sr. Analyst
http://www.cs.bu.edu/students/grads/dgd/ \ Dynamic Diagrams
MAPA: mapping for the WWW \__________________________