W3C home > Mailing lists > Public > public-media-annotation@w3.org > May 2011

Re: follow up on the discussion in HTML5 about metadata access

From: Karl Dubost <karld@opera.com>
Date: Tue, 10 May 2011 15:27:31 -0400
Message-Id: <25467CE1-EB89-4422-98A9-93F7545B11DA@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>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>

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 19:31:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:17:42 UTC