[xiph-commits] r14907 - trunk/standards
ivo at svn.xiph.org
ivo at svn.xiph.org
Sat May 17 19:11:45 PDT 2008
Author: ivo
Date: 2008-05-17 19:11:44 -0700 (Sat, 17 May 2008)
New Revision: 14907
Modified:
trunk/standards/draft-goncalves-rfc3534bis.txt
trunk/standards/draft-goncalves-rfc3534bis.xml
Log:
* XML cleanup
* Created table on how codec indentifiers map into the codecs parameter
* Took into account feedback from Alfred H?\195?\142nes on the wording on section 10.3, "Restrictions on usage"
Modified: trunk/standards/draft-goncalves-rfc3534bis.txt
===================================================================
--- trunk/standards/draft-goncalves-rfc3534bis.txt 2008-05-17 17:34:28 UTC (rev 14906)
+++ trunk/standards/draft-goncalves-rfc3534bis.txt 2008-05-18 02:11:44 UTC (rev 14907)
@@ -5,11 +5,11 @@
Internet-Draft S. Pfeiffer
Obsoletes: 3534 (if approved) C. Montgomery
Intended status: Standards Track Xiph
-Expires: October 23, 2008 April 21, 2008
+Expires: November 20, 2008 May 19, 2008
Ogg Media Types
- draft-goncalves-rfc3534bis-05
+ draft-goncalves-rfc3534bis-06
Status of This Memo
@@ -34,7 +34,7 @@
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
- This Internet-Draft will expire on October 23, 2008.
+ This Internet-Draft will expire on November 20, 2008.
Copyright Notice
@@ -52,29 +52,29 @@
-Goncalves, et al. Expires October 23, 2008 [Page 1]
+Goncalves, et al. Expires November 20, 2008 [Page 1]
-Internet-Draft Ogg Media Types April 2008
+Internet-Draft Ogg Media Types May 2008
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3
- 2. Changes since RFC 3534 . . . . . . . . . . . . . . . . . . 3
+ 2. Changes Since RFC 3534 . . . . . . . . . . . . . . . . . . 3
3. Conformance and Document Conventions . . . . . . . . . . . 3
4. Deployed Media Types and Compatibility . . . . . . . . . . 4
5. Relation Between the Media Types . . . . . . . . . . . . . 5
- 6. Encoding Considerations . . . . . . . . . . . . . . . . . . 5
+ 6. Encoding Considerations . . . . . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . 6
8. Interoperability Considerations . . . . . . . . . . . . . . 7
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . 7
10. Ogg Media Types . . . . . . . . . . . . . . . . . . . . . . 7
- 10.1. application/ogg . . . . . . . . . . . . . . . . . . . . . . 7
- 10.2. video/ogg . . . . . . . . . . . . . . . . . . . . . . . . . 8
- 10.3. audio/ogg . . . . . . . . . . . . . . . . . . . . . . . . . 9
- 11. Copying Conditions . . . . . . . . . . . . . . . . . . . . 10
- 12. References . . . . . . . . . . . . . . . . . . . . . . . . 10
- 12.1. Normative References . . . . . . . . . . . . . . . . . . . 10
+ 10.1. application/ogg . . . . . . . . . . . . . . . . . . . . . . 8
+ 10.2. video/ogg . . . . . . . . . . . . . . . . . . . . . . . . . 9
+ 10.3. audio/ogg . . . . . . . . . . . . . . . . . . . . . . . . . 10
+ 11. Copying Conditions . . . . . . . . . . . . . . . . . . . . 11
+ 12. References . . . . . . . . . . . . . . . . . . . . . . . . 11
+ 12.1. Normative References . . . . . . . . . . . . . . . . . . . 11
12.2. Informative References . . . . . . . . . . . . . . . . . . 11
@@ -108,9 +108,9 @@
-Goncalves, et al. Expires October 23, 2008 [Page 2]
+Goncalves, et al. Expires November 20, 2008 [Page 2]
-Internet-Draft Ogg Media Types April 2008
+Internet-Draft Ogg Media Types May 2008
1. Introduction
@@ -144,7 +144,7 @@
HTTP, included in multi-part documents, or used in other places where
media types [RFC2045] are used.
-2. Changes since RFC 3534
+2. Changes Since RFC 3534
o The type "application/ogg" is redefined.
o The types "video/ogg" and "audio/ogg" are defined.
@@ -164,9 +164,9 @@
-Goncalves, et al. Expires October 23, 2008 [Page 3]
+Goncalves, et al. Expires November 20, 2008 [Page 3]
-Internet-Draft Ogg Media Types April 2008
+Internet-Draft Ogg Media Types May 2008
An implementation is a software module that supports one of the media
@@ -215,16 +215,37 @@
continuing to decode the ones they can. Such precaution ensures
backward and forward compatibility with existing and future data.
- These media types can optionally use the codecs parameter described
- in [RFC4281]. Possible examples include:
+ These media types can optionally use the "codecs" parameter described
+ in [RFC4281]. Codecs encapsulated in Ogg require an 8 byte text
-Goncalves, et al. Expires October 23, 2008 [Page 4]
+Goncalves, et al. Expires November 20, 2008 [Page 4]
-Internet-Draft Ogg Media Types April 2008
+Internet-Draft Ogg Media Types May 2008
+ identifier at the beginning of the first header page, hence a
+ possible machine-readable method to identify the encapsulated codecs
+ would be through this header. The following table illustrates how
+ those header values map into strings that SHOULD be used in the
+ "codecs" parameter when dealing with Ogg media types.
+
+ Codec Identifier | Codecs Parameter
+ -----------------------------------------------------------
+ char[8]: '\x01vorbis' | vorbis
+ char[8]: '\x80theora' | theora
+ char[8]: 'Speex ' | speex
+ char[8]: '\177FLAC' | flac
+ char[8]: 'BBCD\0' | dirac
+ char[8]: 'OggMIDI\0' | midi
+ char[8]: 'CMML\0\0\0\0' | cmml
+ char[8]: 'PCM ' | pcm
+ char[8]: 'CELT ' | celt
+ char[8]: 'kate\0\0\0\0' | kate
+
+ Possible examples include:
+
o application/ogg; codecs="theora, cmml, ecmascript"
o video/ogg; codecs="theora, vorbis"
o audio/ogg; codecs=speex
@@ -252,6 +273,14 @@
content aimed at scientific and other applications that require
various multiplexed signals or streams of continuous data, with or
without scriptable control of content. For bitstreams containing
+
+
+
+Goncalves, et al. Expires November 20, 2008 [Page 5]
+
+Internet-Draft Ogg Media Types May 2008
+
+
visual, timed text, and any other type of material that requires a
visual interface, but which is not complex enough to warrant serving
under application/ogg, the video/ogg type is recommended. In
@@ -273,14 +302,6 @@
pipes); separate types are used to identify codecs such as in
real-time applications for the RTP payload formats of Theora
[ThRTP] video, Vorbis [VoRTP] or Speex [SpRTP] audio, as well as
-
-
-
-Goncalves, et al. Expires October 23, 2008 [Page 5]
-
-Internet-Draft Ogg Media Types April 2008
-
-
for identification of encapsulated data within Ogg through
Skeleton.
@@ -308,6 +329,14 @@
Issues may arise on applications that use Ogg for streaming or file
transfer in a networking scenario. In such cases, implementations
decoding Ogg and its encapsulated bitstreams have to ensure correct
+
+
+
+Goncalves, et al. Expires November 20, 2008 [Page 6]
+
+Internet-Draft Ogg Media Types May 2008
+
+
handling of manipulated bitstreams, of buffer overflows, and similar
issues.
@@ -329,14 +358,6 @@
or sensitive information; such failure constitutes an unknown factor
and is thus considered out of the scope of this document.
-
-
-
-Goncalves, et al. Expires October 23, 2008 [Page 6]
-
-Internet-Draft Ogg Media Types April 2008
-
-
8. Interoperability Considerations
The Ogg container format is device-, platform- and vendor-neutral and
@@ -361,6 +382,17 @@
10. Ogg Media Types
+
+
+
+
+
+
+Goncalves, et al. Expires November 20, 2008 [Page 7]
+
+Internet-Draft Ogg Media Types May 2008
+
+
10.1. application/ogg
Type name: application
@@ -385,14 +417,6 @@
Additional information:
-
-
-
-Goncalves, et al. Expires October 23, 2008 [Page 7]
-
-Internet-Draft Ogg Media Types April 2008
-
-
Magic number(s): The first four bytes, 0x4f 0x67 0x67 0x53,
correspond to the string "OggS".
@@ -418,6 +442,13 @@
Author: See "Authors' Addresses" section.
+
+
+Goncalves, et al. Expires November 20, 2008 [Page 8]
+
+Internet-Draft Ogg Media Types May 2008
+
+
Change controller: The Xiph.Org Foundation.
10.2. video/ogg
@@ -441,14 +472,6 @@
Applications which use this media type: Multimedia applications,
including embedded, streaming, and conferencing tools.
-
-
-
-Goncalves, et al. Expires October 23, 2008 [Page 8]
-
-Internet-Draft Ogg Media Types April 2008
-
-
Additional information:
Magic number(s): The first four bytes, 0x4f 0x67 0x67 0x53,
@@ -475,6 +498,13 @@
Author: See "Authors' Addresses" section.
+
+
+Goncalves, et al. Expires November 20, 2008 [Page 9]
+
+Internet-Draft Ogg Media Types May 2008
+
+
Change controller: The Xiph.Org Foundation.
10.3. audio/ogg
@@ -498,13 +528,6 @@
Applications which use this media type: Multimedia applications,
including embedded, streaming, and conferencing tools.
-
-
-Goncalves, et al. Expires October 23, 2008 [Page 9]
-
-Internet-Draft Ogg Media Types April 2008
-
-
Additional information:
Magic number(s): The first four bytes, 0x4f 0x67 0x67 0x53,
@@ -523,14 +546,21 @@
Ogg bitstream predominantly contains audio data. Content served
under the "audio/ogg" type SHOULD have an Ogg Skeleton logical
bitstream when using the default .oga file extension. The .ogg and
- .spx file extensions are a specialization that require no Skeleton
- due to concerns of backwards-compatibility with existing
+ .spx file extensions indicate a specialization that requires no
+ Skeleton due to backward compatibility concerns with existing
implementations. In particular, .ogg is used for Ogg files that
- contain only a Vorbis bitstream, while .spx files is used for Ogg
- files that contain only a Speex bitstream.
+ contain only a Vorbis bitstream, while .spx is used for Ogg files
+ that contain only a Speex bitstream.
Author: See "Authors' Addresses" section.
+
+
+Goncalves, et al. Expires November 20, 2008 [Page 10]
+
+Internet-Draft Ogg Media Types May 2008
+
+
Change controller: The Xiph.Org Foundation.
11. Copying Conditions
@@ -553,14 +583,6 @@
Bodies", RFC 2045, November 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
-
-
-
-Goncalves, et al. Expires October 23, 2008 [Page 10]
-
-Internet-Draft Ogg Media Types April 2008
-
-
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4281] Gellens, R., Singer, D., and P. Frojdh, "The Codecs
@@ -587,6 +609,14 @@
[Dirac] Dirac Group, "Dirac Specification",
<http://dirac.sourceforge.net/specification.html>.
+
+
+
+Goncalves, et al. Expires November 20, 2008 [Page 11]
+
+Internet-Draft Ogg Media Types May 2008
+
+
[Speex] Valin, J., "The Speex Codec Manual", February 2002,
<http://speex.org/docs/manual/speex-manual>.
@@ -609,14 +639,6 @@
[ThRTP] Barbato, L., "RTP Payload Format for Theora Encoded
Video", July 2006,
-
-
-
-Goncalves, et al. Expires October 23, 2008 [Page 11]
-
-Internet-Draft Ogg Media Types April 2008
-
-
<http://tools.ietf.org/html/
draft-barbato-avt-rtp-theora>.
@@ -635,6 +657,22 @@
[libogg] Xiph.Org Foundation, "The libogg API", June 2000,
<http://xiph.org/ogg/doc/libogg>.
+
+
+
+
+
+
+
+
+
+
+
+Goncalves, et al. Expires November 20, 2008 [Page 12]
+
+Internet-Draft Ogg Media Types May 2008
+
+
Authors' Addresses
Ivo Emanuel Goncalves
@@ -668,9 +706,27 @@
-Goncalves, et al. Expires October 23, 2008 [Page 12]
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Goncalves, et al. Expires November 20, 2008 [Page 13]
-Internet-Draft Ogg Media Types April 2008
+Internet-Draft Ogg Media Types May 2008
Full Copyright Statement
@@ -724,5 +780,5 @@
-Goncalves, et al. Expires October 23, 2008 [Page 13]
+Goncalves, et al. Expires November 20, 2008 [Page 14]
Modified: trunk/standards/draft-goncalves-rfc3534bis.xml
===================================================================
--- trunk/standards/draft-goncalves-rfc3534bis.xml 2008-05-17 17:34:28 UTC (rev 14906)
+++ trunk/standards/draft-goncalves-rfc3534bis.xml 2008-05-18 02:11:44 UTC (rev 14907)
@@ -6,7 +6,7 @@
<?rfc symrefs="yes" ?>
<?rfc rfcedstyle="yes" ?>
-<rfc ipr="full3978" docName="draft-goncalves-rfc3534bis-05" obsoletes="3534" category="std">
+<rfc ipr="full3978" docName="draft-goncalves-rfc3534bis-06" obsoletes="3534" category="std" submissionType="IETF" xml:lang="en">
<front>
<title>Ogg Media Types</title>
<author initials="I.E." surname="Goncalves" fullname="Ivo Emanuel Goncalves">
@@ -37,7 +37,7 @@
<uri>http://xiph.org</uri>
</address>
</author>
- <date day="21" month="April" year="2008"/>
+ <date day="19" month="May" year="2008"/>
<area>Internet</area>
<keyword>I-D</keyword>
<keyword>Internet-Draft</keyword>
@@ -52,16 +52,16 @@
</front>
<middle>
<section title="Introduction">
- <t>This document describes media types for Ogg, a data encapsulation format defined by the Xiph.Org Foundation for public use. Refer to "Introduction" in <xref target="RFC3533"/> and "Overview" in <xref target="Ogg"/> for background information on this container format.</t>
+ <t>This document describes media types for Ogg, a data encapsulation format defined by the Xiph.Org Foundation for public use. Refer to "Introduction" in <xref target="RFC3533"/> and "Overview" in <xref target="Ogg"/> for background information on this container format.</t>
<t>Binary data contained in Ogg, such as Vorbis and Theora, has historically been interchanged using the application/ogg media type as defined by <xref target="RFC3534"/>. This document obsoletes <xref target="RFC3534"/> and defines three media types for different types of content in Ogg to reflect this usage in the IANA media type registry, to foster interoperability by defining underspecified aspects, and to provide general security considerations.</t>
<t>The Ogg container format is known to contain <xref target="Theora"/> or <xref target="Dirac"/> video, <xref target="Speex"/> (narrow-band and wide-band speech), <xref target="Vorbis"/> or <xref target="FLAC"/> audio, and <xref target="CMML"/> timed text/metadata. As Ogg encapsulates binary data, it is possible to include any other type of video, audio, image, text or, generally speaking, any time-continuously sampled data.</t>
<t>While raw packets from these data sources may be used directly by transport mechanisms that provide their own framing and packet-separation mechanisms (such as UDP datagrams or RTP), Ogg is a solution for stream based storage (such as files) and transport (such as TCP streams or pipes). The media types defined in this document are needed to correctly identify such content when it is served over HTTP, included in multi-part documents, or used in other places where <xref target="RFC2045">media types</xref> are used.</t>
</section>
- <section title="Changes since RFC 3534">
+ <section title="Changes Since RFC 3534">
<t>
<list style="symbols">
- <t>The type "application/ogg" is redefined.</t>
- <t>The types "video/ogg" and "audio/ogg" are defined.</t>
+ <t>The type "application/ogg" is redefined.</t>
+ <t>The types "video/ogg" and "audio/ogg" are defined.</t>
<t>New file extensions are defined.</t>
<t>New Macintosh file type codes are defined.</t>
<t>The codecs parameter is defined for optional use.</t>
@@ -70,13 +70,13 @@
</t>
</section>
<section title="Conformance and Document Conventions">
- <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, <xref target="RFC2119"/> and indicate requirement levels for compliant implementations. Requirements apply to all implementations unless otherwise stated.</t>
+ <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, <xref target="RFC2119"/> and indicate requirement levels for compliant implementations. Requirements apply to all implementations unless otherwise stated.</t>
<t>An implementation is a software module that supports one of the media types defined in this document. Software modules may support multiple media types, but conformance is considered individually for each type.</t>
- <t>Implementations that fail to satisfy one or more "MUST" requirements are considered non-compliant. Implementations that satisfy all "MUST" requirements, but fail to satisfy one or more "SHOULD" requirements, are said to be "conditionally compliant". All other implementations are "unconditionally compliant".</t>
+ <t>Implementations that fail to satisfy one or more "MUST" requirements are considered non-compliant. Implementations that satisfy all "MUST" requirements, but fail to satisfy one or more "SHOULD" requirements, are said to be "conditionally compliant". All other implementations are "unconditionally compliant".</t>
</section>
<section title="Deployed Media Types and Compatibility">
<t>The application/ogg media type has been used in an ad-hoc fashion to label and exchange multimedia content in Ogg containers.</t>
- <t>Use of the "application" top-level type for this kind of content is known to be problematic, in particular since it obfuscates video and audio content. This document thus defines the media types,</t>
+ <t>Use of the "application" top-level type for this kind of content is known to be problematic, in particular since it obfuscates video and audio content. This document thus defines the media types,</t>
<t>
<list style="symbols">
<t>video/ogg</t>
@@ -86,11 +86,28 @@
<t>which are intended for common use and SHOULD be used when dealing with video or audio content respectively. This document also obsoletes the <xref target="RFC3534"/> definition of application/ogg and marks it for complex data (e.g. multitrack visual, audio, textual and other time-continuously sampled data), which is not clearly video or audio data and thus not suited for either the video/ogg or audio/ogg types. Refer to the following section for more details.</t>
<t>An Ogg bitstream generally consists of one or more logical bitstreams that each consist of a series of header and data pages packetising time-continuous binary data <xref target="RFC3533"/>. The content types of the logical bitstreams may be identified without decoding the header pages of the logical bitstreams through use of a <xref target="Skeleton"/> bitstream. Using Ogg Skeleton is REQUIRED for content served under the application/ogg type and RECOMMENDED for video/ogg and audio/ogg, as Skeleton contains identifiers to describe the different encapsulated data.</t>
<t>Furthermore, it is RECOMMENDED that implementations that identify a logical bitstream which they cannot decode SHOULD ignore it, while continuing to decode the ones they can. Such precaution ensures backward and forward compatibility with existing and future data.</t>
- <t>These media types can optionally use the codecs parameter described in <xref target="RFC4281"/>. Possible examples include:</t>
- <t>
+ <t>These media types can optionally use the "codecs" parameter described in <xref target="RFC4281"/>. Codecs encapsulated in Ogg require an 8 byte text identifier at the beginning of the first header page, hence a possible machine-readable method to identify the encapsulated codecs would be through this header. The following table illustrates how those header values map into strings that SHOULD be used in the "codecs" parameter when dealing with Ogg media types.</t>
+ <figure>
+ <artwork><![CDATA[
+ Codec Identifier | Codecs Parameter
+ -----------------------------------------------------------
+ char[8]: '\x01vorbis' | vorbis
+ char[8]: '\x80theora' | theora
+ char[8]: 'Speex ' | speex
+ char[8]: '\177FLAC' | flac
+ char[8]: 'BBCD\0' | dirac
+ char[8]: 'OggMIDI\0' | midi
+ char[8]: 'CMML\0\0\0\0' | cmml
+ char[8]: 'PCM ' | pcm
+ char[8]: 'CELT ' | celt
+ char[8]: 'kate\0\0\0\0' | kate
+ ]]></artwork>
+ </figure>
+ <t>Possible examples include:</t>
+ <t>
<list style="symbols">
- <t>application/ogg; codecs="theora, cmml, ecmascript"</t>
- <t>video/ogg; codecs="theora, vorbis"</t>
+ <t>application/ogg; codecs="theora, cmml, ecmascript"</t>
+ <t>video/ogg; codecs="theora, vorbis"</t>
<t>audio/ogg; codecs=speex</t>
</list>
</t>
@@ -138,16 +155,16 @@
<t>Published specification: RFC 3533</t>
<t>Applications which use this media type: Scientific and otherwise which require various multiplexed signals or streams of data, with or without scriptable control of content.</t>
<t>Additional information:</t>
- <t>Magic number(s): The first four bytes, 0x4f 0x67 0x67 0x53, correspond to the string "OggS".</t>
+ <t>Magic number(s): The first four bytes, 0x4f 0x67 0x67 0x53, correspond to the string "OggS".</t>
<t>File extension(s): .ogx</t>
<list style="hanging">
<t>RFC 3534 defined the file extension .ogg for application/ogg, which this document obsoletes in favor of .ogx due to concerns where, historically, some implementations expect .ogg files to be solely Vorbis-encoded audio.</t>
</list>
<t>Macintosh File Type Code(s): OggX</t>
- <t>Person & Email address to contact for further information: See "Authors' Addresses" section.</t>
+ <t>Person & Email address to contact for further information: See "Authors' Addresses" section.</t>
<t>Intended usage: COMMON</t>
<t>Restrictions on usage: The type application/ogg SHOULD only be used in situations where it is not appropriate to serve data under the video/ogg or audio/ogg types. Data served under the application/ogg type SHOULD use the .ogx file extension and MUST contain an Ogg Skeleton logical bitstream to identify all other contained logical bitstreams.</t>
- <t>Author: See "Authors' Addresses" section.</t>
+ <t>Author: See "Authors' Addresses" section.</t>
<t>Change controller: The Xiph.Org Foundation.</t>
</section>
<section title="video/ogg">
@@ -161,13 +178,13 @@
<t>Published specification: RFC 3533</t>
<t>Applications which use this media type: Multimedia applications, including embedded, streaming, and conferencing tools.</t>
<t>Additional information:</t>
- <t>Magic number(s): The first four bytes, 0x4f 0x67 0x67 0x53, correspond to the string "OggS".</t>
+ <t>Magic number(s): The first four bytes, 0x4f 0x67 0x67 0x53, correspond to the string "OggS".</t>
<t>File extension(s): .ogv</t>
<t>Macintosh File Type Code(s): OggV</t>
- <t>Person & Email address to contact for further information: See "Authors' Addresses" section.</t>
+ <t>Person & Email address to contact for further information: See "Authors' Addresses" section.</t>
<t>Intended usage: COMMON</t>
- <t>Restrictions on usage: The type "video/ogg" SHOULD be used for Ogg bitstreams containing visual, audio, timed text, or any other type of material that requires a visual interface. It is intended for content not complex enough to warrant serving under "application/ogg"; for example, a combination of Theora video, Vorbis audio, Skeleton metadata, and CMML captioning. Data served under the type "video/ogg" SHOULD contain an Ogg Skeleton logical bitstream. Implementations interacting with the type "video/ogg" SHOULD support multiplexed bitstreams.</t>
- <t>Author: See "Authors' Addresses" section.</t>
+ <t>Restrictions on usage: The type "video/ogg" SHOULD be used for Ogg bitstreams containing visual, audio, timed text, or any other type of material that requires a visual interface. It is intended for content not complex enough to warrant serving under "application/ogg"; for example, a combination of Theora video, Vorbis audio, Skeleton metadata, and CMML captioning. Data served under the type "video/ogg" SHOULD contain an Ogg Skeleton logical bitstream. Implementations interacting with the type "video/ogg" SHOULD support multiplexed bitstreams.</t>
+ <t>Author: See "Authors' Addresses" section.</t>
<t>Change controller: The Xiph.Org Foundation.</t>
</section>
<section title="audio/ogg">
@@ -181,13 +198,13 @@
<t>Published specification: RFC 3533</t>
<t>Applications which use this media type: Multimedia applications, including embedded, streaming, and conferencing tools.</t>
<t>Additional information:</t>
- <t>Magic number(s): The first four bytes, 0x4f 0x67 0x67 0x53, correspond to the string "OggS".</t>
+ <t>Magic number(s): The first four bytes, 0x4f 0x67 0x67 0x53, correspond to the string "OggS".</t>
<t>File extension(s): .oga, .ogg, .spx</t>
<t>Macintosh File Type Code(s): OggA</t>
- <t>Person & Email address to contact for further information: See "Authors' Addresses" section.</t>
+ <t>Person & Email address to contact for further information: See "Authors' Addresses" section.</t>
<t>Intended usage: COMMON</t>
- <t>Restrictions on usage: The type "audio/ogg" SHOULD be used when the Ogg bitstream predominantly contains audio data. Content served under the "audio/ogg" type SHOULD have an Ogg Skeleton logical bitstream when using the default .oga file extension. The .ogg and .spx file extensions are a specialization that require no Skeleton due to concerns of backwards-compatibility with existing implementations. In particular, .ogg is used for Ogg files that contain only a Vorbis bitstream, while .spx files is used for Ogg files that contain only a Speex bitstream.</t>
- <t>Author: See "Authors' Addresses" section.</t>
+ <t>Restrictions on usage: The type "audio/ogg" SHOULD be used when the Ogg bitstream predominantly contains audio data. Content served under the "audio/ogg" type SHOULD have an Ogg Skeleton logical bitstream when using the default .oga file extension. The .ogg and .spx file extensions indicate a specialization that requires no Skeleton due to backward compatibility concerns with existing implementations. In particular, .ogg is used for Ogg files that contain only a Vorbis bitstream, while .spx is used for Ogg files that contain only a Speex bitstream.</t>
+ <t>Author: See "Authors' Addresses" section.</t>
<t>Change controller: The Xiph.Org Foundation.</t>
</section>
</section>
More information about the commits
mailing list