W3C home > Mailing lists > Public > public-digipub-ig@w3.org > June 2015

Re: [packaging] TAG discusses the packaging spec

From: AUDRAIN LUC <LAUDRAIN@hachette-livre.fr>
Date: Tue, 2 Jun 2015 16:23:37 +0200
To: Ivan Herman <ivan@w3.org>, Dave Cramer <dauwhe@gmail.com>
CC: W3C Digital Publishing IG <public-digipub-ig@w3.org>
Message-ID: <D19388DD.4CAF5%laudrain@hachette-livre.fr>
+1
Luc



Le 02/06/2015 15:38, « Ivan Herman » <ivan@w3.org> a écrit :

>The reference [4] is actually interesting (I do not claim to understand
>everything in the mails, unfortunately):
>
>[[[
>Ilya and I had a chance to chat this afternoon and he had a brilliant
>idea:
>what if there were a preamble section that allowed the package to simply
>be
>a hint to UA to start fetching a list of (not-included) resources?
>
>This would let you invoke one with:
>
>    <link rel="package" href="/lib/brand.pack">
>
>Note the lack of a "scope" attribute.
>
>The contents of "brand.back" wouldn't be a resources, but instead is a
>list
>of URLs to request. This would let a site reduce the number (and
>repetition) of <link rel="prefetch"> tags in the first (crucial bytes).
>This could be done by using the preamble section
><
>http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
>> of the package to
>include a structured list of URLs to preflight.
>
>]]]
>
>
>This resembles a bit to what we discussed yesterday: that we need a
>'virtual' package, or the concept of an abstract document even when
>things are not physically packed. This 'brand.pack' in the core may be
>considered as some sort of a manifest listing all the files that belong
>to a book; much like a opf file in EPUB. Ie, if the URL request returns
>that file then all other constituents are on the Web, if it returns a
>full package then, well, it has to be unpacked in the client.
>
>Something like thatŠ:-)
>
>Ivan
>
>
>
>> On 02 Jun 2015, at 01:47 , Dave Cramer <dauwhe@gmail.com> wrote:
>> 
>> I've been looking at the issues in the packaging spec github repository
>>[1]. One issue is to address feedback from the April 2015 F2F. Turns out
>>this is the TAG F2F, and minutes of the discussion of packaging are at
>>[2].
>> 
>> For context, it helps to read the thread on public-web-perf [3][4][5].
>> 
>> Thanks,
>> 
>> Dave
>> 
>> [1] https://github.com/w3ctag/packaging-on-the-web/issues
>> [2] 
>>https://github.com/w3ctag/meetings/blob/gh-pages/2015/04-sfo/04-22-minute
>>s.md#packaging-with-special-guest-ilya-httpsgithubcomw3ctagpackaging-on-t
>>he-web
>> [3] 
>>https://lists.w3.org/Archives/Public/public-web-perf/2015Jan/0027.html
>> [4] 
>>https://lists.w3.org/Archives/Public/public-web-perf/2015Jan/0038.html
>> [5] 
>>https://lists.w3.org/Archives/Public/public-web-perf/2015Jan/0041.html
>> 
>> 
>> 
>> 
>> 
>
>
>----
>Ivan Herman, W3C
>Digital Publishing Activity Lead
>Home: http://www.w3.org/People/Ivan/
>mobile: +31-641044153
>ORCID ID: http://orcid.org/0000-0003-0782-2704
>
>
>
>
Received on Tuesday, 2 June 2015 14:24:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:36:02 UTC