RFC 4839

RFC 4839 📄💖

• Title: Media Type Registrations for the Open eBook Publication Structure (OEBPS) Package File (OPF) ✨
• Authors: Garth Conboy and John Rivlin (eBook Technologies, Inc.), Jon Ferraiolo (IBM) 🎀
• Category: Informational 🌸
• Date: April 2007 📅
• Stream: Network Working Group 🧚
• Obsoletes / Updates: this RFC doesn't list any, so it doesn't obsolete or update anything 🙈

---

Status of This Memo ✨

okay so this memo is just for info, bestie. 💅 It is NOT an Internet standard of any kind, and you can share it as much as you want 🦋

Copyright Notice 🎀

Copyright (C) The IETF Trust (2007). 💜

Abstract 🌈

this doc is basically here to register a media type for OEBPS Package Files, aka the files that make eBooks go 📚✨

1. Introduction 🌸

okay so this doc registers a media type for the Open eBook Publication Structure (OEBPS) Package File (OPF) 🧚 The OPF file is an XML file that describes an OEBPS Publication [OEBPS]. It's giving table of contents for the whole book: it names every other file in the publication and gives info about each one 📖 OPF and its related standards are maintained and defined by the International Digital Publishing Forum (IDPF) 🫶

the media type is needed so OPF files get identified correctly when they're edited on disk, when they're referenced in OEBPS Container files, and anywhere else media types get used 💅 it's lowkey essential 🔥

2. Security Considerations 💀

ok this section is serious, bestie 🙈 OPF files contain well-formed XML that follows the XML 1.0 specification ✨

clearly, someone can totally write a malicious file that, for example, has malformed data 😭 most XML parsers protect themselves from these attacks by strictly enforcing conformance, which is iconic of them 👑

all processors that read OPF files should rigorously check the size and validity of the data they retrieve 💜 (note the lowercase "should" here, it's not a BCP 14 requirement, but it's still a very good idea 🫶)

there is currently no provision in the OEBPS Package File standard for encryption, signing, or authentication within the file format 💀 so keep that in mind, periodt 💅

3. IANA Considerations 🦋

IANA has registered the media type application/oebps-package+xml as specified in Section 3.1. ✨ The registration uses the template present in [RFC4288] 🍓

3.1. Media Type for Downloadable Sounds 🎧

yes, the heading says "Downloadable Sounds," even though the type is for OPF files. it's a little mismatched, but the name stays as written 🙈 here's the full registration template, verbatim:

   Type name:                         application

   Subtype name:                      oebps-package+xml

   Required parameters:               none

   Optional parameters:               none

   Encoding considerations:           OPF files are UTF-8 or UTF-16
                                      encoded XML

   Security considerations:           none


   Interoperability considerations:   none

   Published specification:           Specification is published by the
                                      International Digital Publishing
                                      Forum and can be found at
                                      http://www.idpf.org/oebps/
                                      oebps1.2/download/oeb12-xhtml.htm

   Applications which use this media type:
                                      1) eBook Technologies, Inc.
                                         eBook reading system.
                                      2) Microsoft Reader
                                      3) OSoft reader
                                      4) Content Reserve Publishing
                                         System
                                      5) IDPF Container WG
                                      6) PC Reader.com
                                      7) MobiPocket reader

   Additional information:

      Magic number(s):                none

      File extension(s):              .opf

      Macintosh file type code(s):    TEXT

   Person & email address to contact for further information:
                                      Nick Bogaty (nbogaty@idpf.org)

   Intended usage:                    COMMON

   Restrictions on usage:             None

   Author:                            International Digital Publishing
                                      Forum (www.idpf.org)

   Change controller:                 International Digital Publishing
                                      Forum (www.idpf.org)

4. Normative References 📚

here are the references, complete and exact:

   [OEBPS]   "Open eBook Publication Structure 1.2", International
             Digital Publishing Forum (IDPF), New York, NY USA, 2002.

   [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and
             Registration Procedures", BCP 13, RFC 4288, December 2005.

Authors' Addresses 🧚

here's where you can find the authors, bestie 🫶

   Garth Conboy
   eBook Technologies, Inc.
   7745 Herschel Avenue
   La Jolla, CA 92037

   Phone: (858) 551-4950
   EMail: gc@ebooktechnologies.com


   John Rivlin
   eBook Technologies, Inc.
   7745 Herschel Avenue
   La Jolla, CA 92037

   Phone: (650) 255-3389
   EMail: john@ebooktechnologies.com


   Jon Ferraiolo
   IBM
   Menlo Park, CA

   Phone: (650) 926-5865
   EMail: jferrai@us.ibm.com

Full Copyright Statement 💜

Copyright (C) The IETF Trust (2007). 🌈

this document is subject to the rights, licenses and restrictions in BCP 78. Except as set out there, the authors keep all their rights 💅

the document and the info in it are provided on an "AS IS" basis, and the contributor, the organization they represent or are sponsored by (if any), the Internet Society, the IETF Trust, and the Internet Engineering Task Force all disclaim every warranty. Here's the full disclaimer, verbatim, because the wording matters:

   THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Intellectual Property 🔥

the IETF doesn't take a position on whether any IPR (intellectual property rights) claimed for this tech is valid or in scope, or whether you can get a license for it. It also hasn't made any independent effort to find those rights 🙈 info on how RFC docs handle rights is in BCP 78 and BCP 79 📖

you can check out IPR disclosures made to the IETF Secretariat, plus any license assurances, or the results of attempts to get a general license, at the IETF online IPR repository: http://www.ietf.org/ipr 🦋

the IETF also invites anyone to flag copyrights, patents, patent applications, or other proprietary rights that might cover tech needed to implement this standard. Send that to ietf-ipr@ietf.org 💌

Acknowledgement 🌸

funding for the RFC Editor function is currently provided by the Internet Society ✨ thank you, sis 🫶