Debian Codegraph @

rfc4839.html

raw
1 <pre>Network Working Group G. Conboy
2 Request for Comments: 4839 J. Rivlin
3 Category: Informational eBook Technologies, Inc.
4 J. Ferraiolo
5 IBM
6 April 2007
7
8
9 <span class="h1">Media Type Registrations for</span>
10 <span class="h1">the Open eBook Publication Structure (OEBPS) Package File (OPF)</span>
11
12 Status of This Memo
13
14 This memo provides information for the Internet community. It does
15 not specify an Internet standard of any kind. Distribution of this
16 memo is unlimited.
17
18 Copyright Notice
19
20 Copyright (C) The IETF Trust (2007).
21
22 Abstract
23
24 This document serves to register a media type for the Open eBook
25 Publication Structure (OEBPS) Package Files.
26
27 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
28
29 The present document registers a media type for the Open eBook
30 Publication Structure (OEBPS) Package File (OPF). The OPF file is an
31 XML file that describes an OEBPS Publication [<a href="#ref-OEBPS" title="&quot;Open eBook Publication Structure 1.2&quot;">OEBPS</a>]. It identifies
32 all other files in the publication and provides descriptive
33 information about them. OPF and its related standards are maintained
34 and defined by the International Digital Publishing Forum (IDPF).
35
36 The media type defined here is needed to correctly identify OPF files
37 when they are edited on disk, referenced in OEBPS Container files, or
38 used in other places where media types are used.
39
40 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Security Considerations</span>
41
42 The OPF files contain well-formed XML conforming to the XML 1.0
43 specification.
44
45 Clearly, it is possible to author malicious files which, for example,
46 contain malformed data. Most XML parsers protect themselves from
47 such attacks by rigorously enforcing conformance.
48
49
50
51
52 <span class="grey">Conboy, et al. Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc4839">RFC 4839</a> Media Type Registrations for OPF April 2007</span>
55
56
57 All processors that read OPF files should rigorously check the size
58 and validity of data retrieved.
59
60 There is no current provision in the OEBPS Package File standard for
61 encryption, signing, or authentication within the file format.
62
63 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations</span>
64
65 IANA has registered the media type application/oebps-package+xml as
66 specified in <a href="#section-3.1">Section 3.1</a>. The registration uses the template present
67 in [<a href="./rfc4288" title="&quot;Media Type Specifications and Registration Procedures&quot;">RFC4288</a>].
68
69 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Media Type for Downloadable Sounds</span>
70
71 Type name: application
72
73 Subtype name: oebps-package+xml
74
75 Required parameters: none
76
77 Optional parameters: none
78
79 Encoding considerations: OPF files are UTF-8 or UTF-16
80 encoded XML
81
82 Security considerations: none
83
84
85 Interoperability considerations: none
86
87 Published specification: Specification is published by the
88 International Digital Publishing
89 Forum and can be found at
90 <a href="http://www.idpf.org/oebps/oebps1.2/download/oeb12-xhtml.htm">http://www.idpf.org/oebps/</a>
91 <a href="http://www.idpf.org/oebps/oebps1.2/download/oeb12-xhtml.htm">oebps1.2/download/oeb12-xhtml.htm</a>
92
93 Applications which use this media type:
94 1) eBook Technologies, Inc.
95 eBook reading system.
96 2) Microsoft Reader
97 3) OSoft reader
98 4) Content Reserve Publishing
99 System
100 5) IDPF Container WG
101 6) PC Reader.com
102 7) MobiPocket reader
103
104
105
106
107
108 <span class="grey">Conboy, et al. Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc4839">RFC 4839</a> Media Type Registrations for OPF April 2007</span>
111
112
113 Additional information:
114
115 Magic number(s): none
116
117 File extension(s): .opf
118
119 Macintosh file type code(s): TEXT
120
121 Person &amp; email address to contact for further information:
122 Nick Bogaty ([email protected])
123
124 Intended usage: COMMON
125
126 Restrictions on usage: None
127
128 Author: International Digital Publishing
129 Forum (www.idpf.org)
130
131 Change controller: International Digital Publishing
132 Forum (www.idpf.org)
133
134 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Normative References</span>
135
136 [<a id="ref-OEBPS">OEBPS</a>] "Open eBook Publication Structure 1.2", International
137 Digital Publishing Forum (IDPF), New York, NY USA, 2002.
138
139 [<a id="ref-RFC4288">RFC4288</a>] Freed, N. and J. Klensin, "Media Type Specifications and
140 Registration Procedures", <a href="https://www.rfc-editor.org/bcp/bcp13">BCP 13</a>, <a href="./rfc4288">RFC 4288</a>, December 2005.
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164 <span class="grey">Conboy, et al. Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc4839">RFC 4839</a> Media Type Registrations for OPF April 2007</span>
167
168
169 Authors' Addresses
170
171 Garth Conboy
172 eBook Technologies, Inc.
173 7745 Herschel Avenue
174 La Jolla, CA 92037
175
176 Phone: (858) 551-4950
177 EMail: [email protected]
178
179
180 John Rivlin
181 eBook Technologies, Inc.
182 7745 Herschel Avenue
183 La Jolla, CA 92037
184
185 Phone: (650) 255-3389
186 EMail: [email protected]
187
188
189 Jon Ferraiolo
190 IBM
191 Menlo Park, CA
192
193 Phone: (650) 926-5865
194 EMail: [email protected]
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220 <span class="grey">Conboy, et al. Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc4839">RFC 4839</a> Media Type Registrations for OPF April 2007</span>
223
224
225 Full Copyright Statement
226
227 Copyright (C) The IETF Trust (2007).
228
229 This document is subject to the rights, licenses and restrictions
230 contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
231 retain all their rights.
232
233 This document and the information contained herein are provided on an
234 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
235 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
236 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
237 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
238 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
239 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
240
241 Intellectual Property
242
243 The IETF takes no position regarding the validity or scope of any
244 Intellectual Property Rights or other rights that might be claimed to
245 pertain to the implementation or use of the technology described in
246 this document or the extent to which any license under such rights
247 might or might not be available; nor does it represent that it has
248 made any independent effort to identify any such rights. Information
249 on the procedures with respect to rights in RFC documents can be
250 found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
251
252 Copies of IPR disclosures made to the IETF Secretariat and any
253 assurances of licenses to be made available, or the result of an
254 attempt made to obtain a general license or permission for the use of
255 such proprietary rights by implementers or users of this
256 specification can be obtained from the IETF on-line IPR repository at
257 <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
258
259 The IETF invites any interested party to bring to its attention any
260 copyrights, patents or patent applications, or other proprietary
261 rights that may cover technology that may be required to implement
262 this standard. Please address the information to the IETF at
263 [email protected].
264
265 Acknowledgement
266
267 Funding for the RFC Editor function is currently provided by the
268 Internet Society.
269
270
271
272
273
274
275
276 Conboy, et al. Informational [Page 5]
277 </pre>