- From: Patrick Keating <pkeating@bluefirereader.com>
- Date: Thu, 3 Dec 2015 18:26:23 +0000
- To: Leonard Rosenthol <lrosenth@adobe.com>
- CC: "Cramer, Dave" <Dave.Cramer@hbgusa.com>, Nick Ruffilo <nickruffilo@gmail.com>, Ivan Herman <ivan@w3.org>, Florian Rivoal <florian@rivoal.net>, Luc Audrain <LAUDRAIN@hachette-livre.fr>, "W3C Digital Publishing IG" <public-digipub-ig@w3.org>, Robin Berjon <robin@berjon.com>
This sounds good to me. As reading system implemetor I find it *very* important to consider the publication in its entirety based on an order set of resources (like the spine of an EPUB). Parsing each file to construct this would not be very efficient. Patrick > On Dec 3, 2015, at 9:16 AM, Leonard Rosenthol <lrosenth@adobe.com> wrote: > > On 12/3/15, 8:47 AM, "Cramer, Dave" <Dave.Cramer@hbgusa.com> wrote: > >>>>> Would this suggest that there is not a global navigation that defines the order of all pages, and simply a relative positioning of next/prev in each document? Or would this be as as-well-as? >>> >>> That was my concern as well, Nick. I would expect that an RS/UA requires a full list of “sections” and their logical ordering so that (if desired) it could present some UX elements such as a TOC, “bookmarks” or whatever. >> >> A nav document should be required for all PWPs, just as it is for in EPUB3. Perhaps the logical ordering there could be considered primary, with prev/next allowing the content to function even in harsh environments. > > Provided that the Nav document also provided the full sequential ordering, that would seem like an excellent “best of both worlds” approach… > > >>> Effort for authoring, very little, true. Effort for the RS/UA, a LOT - since it would require opening & parsing every file to find the next links… >> >> I would expect that a reading environment that couldn't construct UX elements from the nav would not go parse every file. If the currently viewed file has prev/next, it's easy to know where to go next without parsing any other document. > > Agreed. Provided that the Nav had the necessary information to construct such things, I agree. > > Leonard >
Received on Thursday, 3 December 2015 18:26:57 UTC