Re: [ietf-types] Mime Type Reg for "application/epub+zip"

MURATA Makoto <murata@hokkaido.email.ne.jp> Wed, 02 February 2011 23:59 UTC

Return-Path: <murata@hokkaido.email.ne.jp>
X-Original-To: ietf-types@core3.amsl.com
Delivered-To: ietf-types@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CEB23A6CA1 for <ietf-types@core3.amsl.com>; Wed, 2 Feb 2011 15:59:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id miu-J7dczE3s for <ietf-types@core3.amsl.com>; Wed, 2 Feb 2011 15:59:04 -0800 (PST)
Received: from pechora8.dc.icann.org (pechora8.icann.org [192.0.46.74]) by core3.amsl.com (Postfix) with ESMTP id 847F53A6C91 for <ietf-types@ietf.org>; Wed, 2 Feb 2011 15:59:03 -0800 (PST)
Received: from mail1.asahi-net.or.jp (mail1.asahi-net.or.jp [202.224.39.197]) by pechora8.dc.icann.org (8.13.8/8.13.8) with ESMTP id p1301kSf024715 for <ietf-types@iana.org>; Wed, 2 Feb 2011 19:02:08 -0500
Received: from [192.168.1.3] (y240121.dynamic.ppp.asahi-net.or.jp [118.243.240.121]) by mail1.asahi-net.or.jp (Postfix) with ESMTP id 2160DC5D3B; Thu, 3 Feb 2011 08:43:17 +0900 (JST)
Date: Thu, 03 Feb 2011 08:43:22 +0900
From: MURATA Makoto <murata@hokkaido.email.ne.jp>
To: <ietf-types@iana.org>
In-Reply-To: <010d01c7d9d4$b4f09bb0$6401a8c0@NICKDESK>
References: <010d01c7d9d4$b4f09bb0$6401a8c0@NICKDESK>
Message-Id: <20110203084317.FA8D.576FBF33@hokkaido.email.ne.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.56.04 [ja]
X-Greylist: Delayed for 00:18:25 by milter-greylist-4.2.3 (pechora8.dc.icann.org [192.0.46.74]); Wed, 02 Feb 2011 19:02:09 -0500 (EST)
Cc: 'Ric Wright' <riwright@adobe.com>, Nick Bogaty <nbogaty@idpf.org>, 'John Rivlin' <john@eBookTechnologies.com>, 'Garth Conboy' <gc@eBookTechnologies.com>
Subject: Re: [ietf-types] Mime Type Reg for "application/epub+zip"
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 23:59:05 -0000

Dear colleagues,

In 2007, IDPF (http://www.idpf.org/) submitted a request to register a
standard-tree media type "application/epub+zip" for EPUB documents. 
There were no discussions or registrations, however.  The I-D 
at that time, namely http://www.idpf.org/draft-idpf-mime-ocf-01.txt, has
already expired.

Since then, things have changed.  EPUB has become a very important 
e-book format, and is very widely used by Apple, Adobe, Sony, Barns & Noble, 
among others.  EPUB implementations appear to use "application/epub+zip".
The IDPF EPUB WG is actively designing the next version of EPUB, namely
EPUB3, and has committed to finish it in May, 2011.

Standardization of EPUB at ISO, IEC, or JTC1 is also being discussed 
at ISO/IEC JTC1/SC34/AHG4 (EPUB).    IDPF is involved.

Moreover, the EPUB WG of IDPF is currently talking about introducing
fragment identifiers for EPUB3.   A proposal is available at
http://code.google.com/p/epub-revision/wiki/ImplementationProposalFragmentIdentifier

For EPUB to be a good citizen of Internet, I think that registration 
of application/epub+zip is a necessary step.  I am wondering how we 
should go forward.  Here are some possibilities I can think of.

1) Create an IDPF EPUB3 spec,  describe everything about this media 
type (including possible frag. identifiers), and request for the
approval of IESG.

2) Create an ISO or IEC or JTC1 EPUB specification (possible EPUB2),
describe everything there, and request for the approval of IESG.

3) Begin with an I-D and describe everything there and try to reach 
 (proposed standard?) RFC status, and register the media type.

How do people feel?

Cheers,
-- 
MURATA Makoto <murata@hokkaido.email.ne.jp>