Re: Notes about the Web App manifest document

Hi W3C Digital Publishing IG:

I saw the was discussion yesterday about single file offline HTML - like 5DOC vs the common multi-file approach similar to a web site or eBook.

Right now only a single file PWP works and I ask - apart from non-core reasons - what is the benefit of multi-file container for the offline document?
The purpose of the offline document is to store, read and share it. 
A single html file is very easy to store, read and share.
It might be confusing to look inside, but that is not the core purpose.

Once the single file approach is abandoned, PWP is headed for complexity and delay.
The discussion about manifests is just one small part of a projected todo list.

The 5DOC production process takes content and code from many locations, but the samples show the process to combine resources into one file and download takes just a few seconds. And for long texts the download object could be pre-compiled.

Cheers
Mike


> On 26 May 2016, at 12:23, Ivan Herman <ivan@w3.org> wrote:
> 
> 
> I am not sure where to go from here. My ideal would be to have a “general” manifest file that would include whatever is generally useful or necessary, a (slightly more general) way of finding a manifest, general processing steps (which are part of the document) and then some clearer extension points/facilities for specific application areas, like Web Apps or PWP.
> 
> Feedbacks? Ideally, we should have some discussion in the IG, ending a more solid, and common view that we could put in as an issue/comment to the current document. With the hope that, via some joint work, we can get somewhere…
> 
> WDYT?
> 
> Ivan
> 
> ----
> 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
> 
> 
> 
>

Received on Thursday, 26 May 2016 14:42:18 UTC