W3C home > Mailing lists > Public > public-publ-wg@w3.org > August 2017

Re: Proposal: Using HTML's nav element as manifest

From: Dave Cramer <dauwhe@gmail.com>
Date: Wed, 16 Aug 2017 16:19:20 -0400
Message-ID: <CADxXqOzGWzvDyrXOJfnVJuV+04tEh0Gg4PkQF-ZvrUQ4WqVuWQ@mail.gmail.com>
To: Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
Cc: W3C Publishing Working Group <public-publ-wg@w3.org>
On Wed, Aug 16, 2017 at 3:39 PM, Hadrien Gardeur <
hadrien.gardeur@feedbooks.com> wrote:

> Hello Dave,
> You're conflating two different things here:
>    - list of primary resources in reading order (spine in EPUB)
>    - table of contents (which is navigation)
> They can be the same thing for a novel like Moby Dick but they can also be
> vastly different, for instance a ToC could:
>    - only point to some, not all primary resources
> It's easy enough to change the visual display of certain list items, or an
entire nav element. But I think it's a useful default for everything to

>    - point to the same resource multiple times (for example using
>    fragments to specific locations in a resource)
This is not a problem. We can just say that the "spine" is the unique
resources; a TOC can refer to them as many times as needed

>    - point to resources in an order that's not the reading order
> I'd be interested to see examples of this; in any case this sounds
potentially confusing for the reader.

> Saying that a list of primary resources duplicates a ToC (or any other
> navigation) is therefore incorrect in the general case.
There are tradeoffs to be made, of course.  I feel this proposal makes the
vast majority of potential use cases much simpler.


Received on Wednesday, 16 August 2017 20:19:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:52:16 UTC