the reader page has interaction buttons for ‘next’ and ‘previous’, using the “spine” in the book’s manifest, as well as buttons for the offline storage and dump to zip

The discussion following the presentation concentrated on issues like how one would store, on long term, data like user’s preferences, annotations, etc. The value of having the reader javascript application attached to the reader page, ie, the fact that the “book” itself does not (necessarily) carry javascript was also emphasized.

One specific issue that came up (for future discussion) is whether the fact that that Service Workers rely on HTTPS (as opposed to HTTP) is, for publication, limiting or future looking?

Obviously, this is (at this moment) only a proof-of-concept; the goal is to see if a Service Worker based approach is feasible in the first place. There are other, similar experiments around the same subject, with different design decisions; these should be looked at in the future, too.

About Ivan Herman

Ivan Herman is the Technical Lead for Publishing@W3C. For more details, see http://www.w3.org/People/Ivan/