Re: Re REL/REV links

Terry Allen (terry@ora.com)
Sat, 20 May 95 09:50:43 EDT

| > On Fri, 19 May 1995, Terry Allen wrote:
| >
| > > Your example suggests, though doesn't assert, that the sequential model
| > > would be the ordinary reading sequence. Here's another example:
| > > the book has within it several paths (selections from
| > > the contents), which I want to indicate by BEGIN-->NEXT-->END markup.
| > > Now I know I could use PATH/NODE for this purpose (in which case
| > > perhaps we don't need both PATH/NODE and BEGIN/END). But if I
| > > did mark up paths with BEGIN>END, then the BEGIN wouldn't necessarily
| > > be the TOP of the entire document (the book).
|
| Yes, there is an implication that there is a sequential
| path through a document that utilizes BEGIN/NEXT/PREVIOUS/END
| <LINK> values. I certainly would not assert that it would be
| the "ordinary" or even the usual reading sequence, only
| that it might be if the author/publisher chose to specify
| a sequence.
|
| You can't really have multiple BEGIN or END <LINK>s
| pointing to different URLs. How the heck would a
| user agent deal with that? I'll have to put in a
| note to that effect when I republish my proposal.

<LINK class="pathone" begin="http://foo">
<LINK class="pathtwo" begin="http://goo">

You can have them. How the UA deals with them is another matter.

| Agreed that BEGIN would not necessarily be the TOP.
| But when the top and beginning of a documemnt are the
| same, I am suggesting that you would only need to specify
| one or the other.

Okay.

Regards,

-- 
Terry Allen  (terry@ora.com)   O'Reilly & Associates, Inc.
Editor, Digital Media Group    101 Morris St.
			       Sebastopol, Calif., 95472
occasional column at:  http://gnn.com/meta/imedia/webworks/allen/

A Davenport Group sponsor. For information on the Davenport Group see ftp://ftp.ora.com/pub/davenport/README.html or http://www.ora.com/davenport/README.html