This was not an implementation problem. The concept itself was at fault.
The old-fashioned idea that some kind of tree/hierarchy with standard
names for top/next/last/up/down had to exist in the document, was at fault.
Tool implementors, less experienced with hypertext than the tool *users*,
built heavily on the idea of hierarchy. I see the same trend in this recent
discussion, with a longer and longer list of assumed-relationships that are
less and less guaranteed to apply to hypertext documents, and don't care to
see the mistake repeated.
-- Craig Hubley Business that runs on knowledge Craig Hubley & Associates needs software that runs on the net craig@passport.ca 416-778-6136 416-778-1965 FAX Seventy Eaton Avenue, Toronto, Ontario, Canada M4J 2Z5