Re: A followup/writeup on our Monday discussions (was Re: Continuing discussion on Polyfills)

+1 to Hadrien. I thought the whole point of this little web adventure was
to have publications that just work, today, out of the box, with no client
other than a browser. A UA could also then apply more UI and navigational
elements around that publication if it was capable, which is what we are
trying to spec (how do you know the order of the chapters in a book, what
is the title of the complete package, etc). This idea of a script
associated with the document to provide some of those behaviors seems
really problematic, again as Hadrien pointed out, when the UA supports some
of the features and the script supports others. I am still not sure why a
separate web app, extension, or whatever can't accomplish this just as
well. But I am assume I am missing another discussion where we explained
why we need the WP script.

On Wed, Feb 7, 2018 at 12:25 PM, Matt Garrish <matt.garrish@gmail.com>
wrote:

> Right, okay now I've got you, thanks for clearing that up for me.
>
>
>
> Matt
>
>
>
> *From:* Hadrien Gardeur [mailto:hadrien.gardeur@feedbooks.com]
> *Sent:* February 7, 2018 3:22 PM
>
> *To:* Matt Garrish <matt.garrish@gmail.com>
> *Cc:* Romain <rdeltour@gmail.com>; Ivan Herman <ivan@w3.org>; W3C
> Publishing Working Group <public-publ-wg@w3.org>
> *Subject:* Re: A followup/writeup on our Monday discussions (was Re:
> Continuing discussion on Polyfills)
>
>
>
> The entry page could indeed have a link to a WAM or it could simply
> provide a link that the user could follow as well.
>
>
>
> 2018-02-07 21:12 GMT+01:00 Matt Garrish <matt.garrish@gmail.com>:
>
> > The entry page would link to the fallback app, no need for a link in
> the manifest or for the browser to be WP-aware.
>
>
>
> Ah, so this isn't like having a default_applications for fallback apps,
> but the entry page is its own WAM?
>
>
>
> Matt
>
>
>
> *From:* Hadrien Gardeur [mailto:hadrien.gardeur@feedbooks.com]
> *Sent:* February 7, 2018 2:48 PM
> *To:* Matt Garrish <matt.garrish@gmail.com>
> *Cc:* Romain <rdeltour@gmail.com>; Ivan Herman <ivan@w3.org>; W3C
> Publishing Working Group <public-publ-wg@w3.org>
> *Subject:* Re: A followup/writeup on our Monday discussions (was Re:
> Continuing discussion on Polyfills)
>
>
>
> The entry page would link to the fallback app, no need for a link in the
> manifest or for the browser to be WP-aware.
>
>
>
> This wouldn't get in the way of other apps for the following reasons:
>
>    - a WP-aware browser would trigger the "switch to publication mode" or
>    "add to publication list" affordances on the entry page (or any other page
>    with a link to the manifest)
>    - web and native apps (including browser extensions) would only use
>    the entry page to detect the link as well, and then they would immediately
>    go to the first resource in the default reading order
>
>
>
>
>
> --
>
> Hadrien Gardeur
>
> Co-founder, Feedbooks
>
> http://www.feedbooks.com
>
> T: +33.6.63.28.59.69 <+33%206%2063%2028%2059%2069>
>
> E: hadrien.gardeur@feedbooks.com
>
> 54, rue de Paradis
> <https://maps.google.com/?q=54,+rue+de+Paradis+75010+Paris,+France&entry=gmail&source=g>
>
> 75010 Paris, France
> <https://maps.google.com/?q=54,+rue+de+Paradis+75010+Paris,+France&entry=gmail&source=g>
>