- From: Ian Hickson <ian@hixie.ch>
- Date: Mon, 5 Nov 2007 22:47:48 +0000 (UTC)
- To: Philip Taylor <philip@zaynar.demon.co.uk>
- Cc: HTML WG <public-html@w3.org>
On Tue, 21 Aug 2007, Philip Taylor wrote:
>
> A common structure for sets of pages is:
>
> Table of contents
> / \
> / \
> Section A Section B
> / | \ / | \
> / | \ / | \
> P1 P2 P3 P4 P5 P6
>
> LaTeX2HTML provides various examples:
> http://www.lanl.gov/thermoacoustics/Manual/DelEdoc.html
> http://www.cs.cmu.edu/afs/cs/project/jair/pub/volume16/drummond02a-html/drummond02a-html.html
> http://docs.python.org/lib/lib.html
>
> When each page has important information (e.g. the 'section' pages have
> an introductory paragraph for that section), a user would like to follow
> "next" links through TOC -> A -> P1 -> P2 -> P3 -> B -> P4 -> P5 -> P6.
> (The "next" buttons in the given examples do that.)
>
> When the 'section' pages don't have any useful information (e.g. they're
> just sublists of the table of contents), a user may like to follow P1 ->
> P2 -> P3 -> P4 -> P5 -> P6 instead.
>
> The current definition for "next" ("the link is leading to the document
> that is the next sibling of the current document") doesn't allow authors
> to handle either of those cases, instead requiring the user to follow
> several "up" and (implicit) "down" links to get from P3 to P4, thus
> preventing the user from concentrating fully on the finer details of
> thermoacoustic simulations. (Since the "down" links are never explicitly
> listed or ordered, there is no way for a UA to automatically determine a
> preorder traversal through the tree.)
I've split first/prev/next/last from the hierarchical keywords and made a
new 'sequence' section. Let me know if that works.
--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 5 November 2007 22:48:04 UTC