Re: follow up on service workers for publishing platform

Not sure when I'll have time in the near future, but I will make an attempt
at building a decoupled reading system.  I'll also do my best to
compartmentalize the code into the topics/sections that we discuss, so that
they can easily be demonstrated/removed/changed as necessary.  This example
is a proof of concept, which often means you throw all the code together at
once, but that doesn't mean that it needs to be in the same files (in the
source PWP file for example) for it to work.

-Nick

On Tue, Dec 1, 2015 at 9:44 AM, Ivan Herman <ivan@w3.org> wrote:

> Thanks for starting this Tzviya!
>
> On 1 Dec 2015, at 14:55, Siegman, Tzviya - Hoboken <tsiegman@wiley.com>
> wrote:
>
> Hi All,
>
>
>
> We had to close yesterday’s discussion about using Service Workers within
> a publishing platform before we finished the conversation [1].  I’ve put
> together a list of questions/discussion points that I think were floating
> around to restart the discussion. Please add to the list or adjust the
> questions as you see fit:
>
>
>
> 1.       The current model [2] requires the content to explicitly refer
> to the JS (service worker). (i.e. the scripts modify the content). Is this
> a problem for PWP?
>
> 2.       We established that it is possible to decouple scripts and the
> content for “offlinification” using  Service Workers.  We are interested in
> seeing code samples to this effect, not just establishing the fact that
> this is possible.  Samples welcome.
>
> 3.       We began to discuss the possibility of accessing components of
> the zip (or whatever packaging mechanism is in place) without downloading
> the whole package. For example, Readium streams.
>
> 4.       How do we (as a group) recommend approaching the file format for
> PWP? Let’s not necessarily get hung up on the details of Service Workers.
> We have yet to define what is in the package.
>
>
> 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:-)
>
> Ivan
>
>
>
>
>
> Tzviya
>
>
>
> [1] http://www.w3.org/2015/11/30-dpub-minutes.html#item01
>
> [2] https://dauwhe.github.io/epub-zero/acme-publishing/
>
>
>
> *Tzviya Siegman*
>
> Digital Book Standards & Capabilities Lead
>
> Wiley
>
> 201-748-6884
>
> tsiegman@wiley.com
>
>
>
>
>
> ----
> Ivan Herman, W3C
> Digital Publishing Lead
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> ORCID ID: http://orcid.org/0000-0003-0782-2704
>
>
>
>
>


-- 
- Nick Ruffilo
@NickRuffilo
http://Aerbook.com
http://twitch.tv/TheWizardLlewyn
http://ZenOfTechnology.com <http://zenoftechnology.com/>