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

Re: [pwp] Progressive enhancement of digital books

From: Florian Rivoal <florian@rivoal.net>
Date: Thu, 3 Dec 2015 19:01:28 +0900
Cc: Dave Cramer <Dave.Cramer@hbgusa.com>, Luc Audrain <LAUDRAIN@hachette-livre.fr>, W3C Digital Publishing IG <public-digipub-ig@w3.org>, Robin Berjon <robin@berjon.com>
Message-Id: <1F3580A4-D7E4-4744-906D-D6125E4A238C@rivoal.net>
To: Ivan Herman <ivan@w3.org>

> On 03 Dec 2015, at 18:01, Ivan Herman <ivan@w3.org> wrote:
>> On 2 Dec 2015, at 17:25, Cramer, Dave <Dave.Cramer@hbgusa.com> wrote:
>> On Dec 2, 2015, at 4:27 AM, AUDRAIN LUC <LAUDRAIN@hachette-livre.fr> wrote:
>>> For the sake of the demo, I donąt see why in slide 5, you donąt give
>>> href="nav.html" in the link in c0001.html?
>>> Obviously as the link points to a non existant file, it doesnąt work in
>>> ordinary browser as shown in slide 5.
>>> but with a link pointing to nav.html, it should work or is index.html a
>>> reserved name?
>> I did a poor job of explaining. If you have the URL of the folder, but don't know what's inside the folder, a browser won't generally display any of the content unless it finds an index.html file (or something like an .htaccess file, if the server supports it). But if we have nav.html and rename it to index.html, then any browser will open index.html when you go to the folder URL. It's just a convention that makes it easy to find this critical document.
> For my understanding: what this means that the 'index.html' (or 'nav.html') would not only be the TOC but something much more complex, essentially the cover page of the publication, right?
> What this touches upon is my question the other day, which is still something to discuss: if the URL 'U' identifies the PWP, what does a HTTP GET return? My approach, up to now, was that the return would be the manifest. In your case, would it be the index.html that links to the manifest?

This is where I show how naďve I am...

Why cannot index.html be the manifest (while being the cover page etc at the same time)? We'd need additional conventions beyond the normal semantics of HTML, what's wrong with that?

As far as I understand, that's the approach taken by scholarly HTML, and the one that epub0 was advocating.

 - Florian
Received on Thursday, 3 December 2015 10:02:00 UTC

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