- From: Baldur Bjarnason <baldur@rebus.foundation>
- Date: Fri, 28 Jul 2017 12:13:19 -0400
- To: Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
- Cc: Laurent Le Meur <laurent.lemeur@edrlab.org>, Leonard Rosenthol <lrosenth@adobe.com>, "Teixeira, Mateus" <mteixeira@wwnorton.com>, "public-publ-wg@w3.org" <public-publ-wg@w3.org>
+1 to that, Hadrien Got a bit worried there that we were going to make it hard for publications to function properly as regular websites as well. 😊 - best - Baldur Bjarnason baldur@rebus.foundation > On 28 Jul 2017, at 11:49, Hadrien Gardeur <hadrien.gardeur@feedbooks.com> wrote: > > Hello Baldur, > > I think that this is a separate discussion, but just to be clear: I don't expect WP to be navigation-less at all. I expect them to at least behave like normal websites, with basic links to next/previous resources and eventually other options too (such as a table of contents). > > For this reason, I don't think that there will ever be a parallel Web like AMP but for WP. > > Progressive enhancements and Web Apps dedicated to reading such WPs will be in the same boat: they'll have to live with the fact that these WP have at least some navigation, and attempts to enhance them somehow. They will also be in charge of the type of customization that this task force is addressing. > > From a Readium-2 perspective, I expect the following behaviour for WP support: > • defaults to a webview where we don't attempt to inject any style > • basic navigation added on top of the webview (move between primary resources, get access to ToC and similar navigation) > • reader mode, ideally the one provided by the platform, in order to let the user customize experience > For these last two points, we'll have to figure out a way where Web Apps or progressive enhancements won't get in the way, which is far easier said than done. > > Hadrien
Received on Friday, 28 July 2017 16:13:44 UTC