W3C home > Mailing lists > Public > public-publ-wg@w3.org > February 2018

Re: Continuing discussion on Polyfills

From: Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
Date: Tue, 6 Feb 2018 10:33:58 +0100
Message-ID: <CA+KS-12pMPD2drpMnVZirx4TWXiehiP4JGc7r36SXRiqd0-AOQ@mail.gmail.com>
To: Jeff Buehler <jeff.buehler@knowbly.com>
Cc: deborah.kaplan@suberic.net, "Siegman, Tzviya - Hoboken" <tsiegman@wiley.com>, "Ruffilo, Nick" <Nick.Ruffilo@ingramcontent.com>, W3C Publishing Working Group <public-publ-wg@w3.org>
IMO we should separate things on the authoring side from the user agent
side.


*Authoring*
A Web Publication MUST be entirely readable without any kind of polyfill,
extension or specific browser support.
This means that all resources should be reachable through navigation,
ideally in a sequence that follows the reading order.

For every other affordance (I'm working on those in the lifecycle branch
<https://github.com/w3c/wpub/pull/130>), the author MAY attempt to support
them from the entry page (HTML document returned by the WP address). This
can be achieved by pointing to a Web App from that page.

*User agent*

A WP aware user agent SHOULD enhance the experience of reading a Web
Publication by providing additional affordances that won't clash with the
author's intent (easier said than done, user settings for example are very
difficult to handle).

IMO, presentation and navigation affordances MUST only enhance resources
that are within the scope of the WP which means:

   - all resources listed in the default reading order and list of resources
   - but this excludes the entry page or any other resource not listed in
   our collections

For resources that are not within the scope of a WP, a user agent MAY
provide two other affordances instead:

   - switch to publication mode
   - add to the list of publications
Received on Tuesday, 6 February 2018 09:34:42 UTC

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