- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Wed, 11 May 2011 07:32:45 +1000
- To: Karl Dubost <karld@opera.com>
- Cc: Leonard Rosenthol <lrosenth@adobe.com>, Henri Sivonen <hsivonen@iki.fi>, "tmichel@w3.org" <tmichel@w3.org>, "public-html@w3.org" <public-html@w3.org>, "public-media-annotation@w3.org" <public-media-annotation@w3.org>
Only in the way that PDF, smil, flash, or any other non-HTML content can be called "web content". IMO they are not a native part of the web, but an adjunct and require extra plugins to work in the Web browser. That you can serve any content from a Web server doesn't make it part of the Web, only part of the Internet. Regards, Silvia. Sent from my iPhone On 11/05/2011, at 5:27 AM, Karl Dubost <karld@opera.com> wrote: > > Le 6 mai 2011 à 19:14, Silvia Pfeiffer a écrit : >> I'm not going to elaborate this any further, but once you package it >> with additional resource and give it a different name, you have >> created a new resource type that is not "just supported" by UAs. > > huh? I might be missing something. It is perfectly possible to create a UA which deal with ePub content. Just stating the obvious below > > The UA Request > > GET /path/bovary.epub HTTP/1.1 > Host: www.example.com > User-Agent: Web-ebook-reader > Accept: application/epub > Accept-Language: fr > > The server Response > > HTTP/1.1 200 OK > Accept-Ranges: bytes > Content-Length: 1234567 > Content-Type: application/epub > … > >> It's not Web content any more. > > It *is* Web content. The fact that browsers can't unpack it is completely unrelated to the nature of the content. Any client can be developed to process it. > It is indeed not HTML5 content. > > > -- > Karl Dubost - http://dev.opera.com/ > Developer Relations & Tools, Opera Software >
Received on Tuesday, 10 May 2011 21:33:30 UTC