Re: follow up on service workers for publishing platform

I have been doing a bit of work on a fork of Dave's example which removes
the need for the content to refer to JS, apart from in the index/manifest.
So the content chapters can be as they would be in an EPUB or a webpage,
with only the index file working as a sort of container for the rest. It
isn't fully working yet as I've been otherwise occupied, but it'll be
visible in that fork on github as soon as it is.

-Nick

Nick Barreto

*Co-founder & Technology Director**CANELO *| www.canelo.co
@canelo_co <https://twitter.com/canelo_co> | @nickbarreto
<http://www.twitter.com/nickbarreto>


On 1 December 2015 at 15:14, Cramer, Dave <Dave.Cramer@hbgusa.com> wrote:

> On Dec 1, 2015, at 9:44 AM, Ivan Herman <ivan@w3.org> wrote:
>
> Let me try to be a little bit more specific for this one. PWP being a kind
> of a conceptual thingy, I think what we have to talk about is what would we
> have to see in a manifest *representing* a PWP. What are the information
> that we need to get the whole architecture running?
>
> (We have a reference to manifests and their importance in the document,
> but it is only a skeleton without meat:-)
>
>
> In the Acme Publishing example, the manifest exists only to tell the
> service worker what files to cache to allow offline reading. I've also been
> experimenting with using the web application manifest spec [1]  to gain
> some additional functionality:
>
> 1. Allowing a publication to be saved to the home screen (maybe Santa will
> bring me an android device so I can test this)
> 2. Providing a title and icon for such a publication.
> 3. Defining which file should be opened first when a publication is saved
> (start_url)
> 4. Hinting at an appropriate display mode
> 5. Defining related applications (could the publications be opened in a
> formal ebook reading system app?)
> 6. Defining a preferred orientation for the publication (such "rendering
> metadata" is common in EPUB3 Fixed Layout).
>
> and so on.
>
> I'd love to see more concrete examples of what functions a manifest must
> serve.
>
> Thanks!
>
> Dave
>
>
> [1] http://www.w3.org/TR/appmanifest/
> This may contain confidential material. If you are not an intended
> recipient, please notify the sender, delete immediately, and understand
> that no disclosure or reliance on the information herein is permitted.
> Hachette Book Group may monitor email to and from our network.
>