Re: REL and REV attributes (Was: More comments on HTML 3.0)

Ian Graham (
Thu, 27 Apr 95 14:38:02 EDT

This is exactly what I meant. However, Larry Masinter has pointed out
that not all browsers use button bars (e.g. lynx, braille readers,
others I probably don't know about). It would be nice to know that
this approach could also be implemented in these special types of



> Regarding a "backup" tag/entity, this is solvable by the browsers with > information you can make available today. Here's an example file: > > <HEAD> ... > <LINK REL="Precedes" HREF="next.html"> > <LINK REV="Precedes" HREF="prev.html"> > <LINK REL="Subdocument" HREF="top.html"> > .... </HEAD> > <BODY> ... > <A HREF="top.html">Table of contents</a> -- > <A HREF="prev.html">Previous chapter</a> -- > <A HREF="next.html">Next chapter</a> > ... </BODY> > > Now, if the browsers sees a match between an anchor and a link with > the relationship REV="Precedes" or REL="Subdocument", it can do its > history manipulation trick. Assuming the user has checked that option, > of course :-) > > The framework for this has been available since the first HTML > specification, I think. <LINK> is probably the most ignored tag by > browsers in all of HTML. Something like Ian Graham's document control > button bar would be a great help. Make sure Author is on the list. > <LINK REV="made" HREF="mailto:..."> is one of the most frequently > encountered <LINK> constructs, thanks to Lynx.