Ogg formats in HTML5
HTML 5 introduces new ways of inserting sound and video in webpages with the <audio> and <video> elements. Previously, the specification recommended the use of Ogg formats Vorbis and Theora, but this recommendation was later removed[1] after Apple[2] and Nokia[3] had opposed the move. Opera Software and Mozilla have been advocates for including the Ogg formats into the HTML standard[4][5] and have included native decoding for these formats in their browsers. Google is planning on including Vorbis and Theora support in Chrome[6].
On December 11, 2007, mention of the HTML 5 specification was updated replacing the reference to concrete formats with a placeholder:[7]
| Original | Replacement |
|---|---|
| User agents should support Ogg Theora video and Ogg Vorbis audio, as well as the Ogg container format | It would be helpful for interoperability if all browsers could support the same codecs. However, there are no known codecs that satisfy all the current players: […] This is an ongoing issue and this section will be updated once more information is available. |
The removal of the Ogg formats from the specification has been criticized by some Web developers.[8][9] In response to such criticism, WHATWG has cited concerns from influential companies including Nokia and Apple over the Ogg formats still being within patent lifetime and thus vulnerable to unexpected future patent challenges.[10] A follow-up discussion also occurred on the W3C questions and answers blog.[11]
Background
On October 17, 2007, the W3C encouraged interested people to take part in a "Video on the Web Workshop", held on December 12, 2007 for two days.[12] A number of global companies were involved, submitting position papers.[13] Among them, Nokia's paper states that "a W3C-led standardization of a 'free' codec, or the active endorsement of proprietary technology such as Ogg … by W3C, is, in our opinion, not helpful."[3] Whether Ogg is proprietary is debatable; while the formats are clearly open, they are designed and maintained by an international organization, Xiph.org. Ogg has followed a path similar to many other formats of the Internet age, such as PNG and GZip. While Xiph.org controls and defines the Ogg format specifications and their reference implementations, it does not own any patents and cannot control use of the formats, and the formats are thus not proprietary to Xiph.org, and thus rendering the claims unfounded.
References
- ^ Hickson, Ian (10 December 2007). "[whatwg] Video codec requirements changed". whatwg mailing list (Mailing list). Retrieved 2008-02-25.
{{cite mailing list}}: Unknown parameter|mailinglist=ignored (|mailing-list=suggested) (help) - ^ Stachowiak, Maciej (21 March 2007). "[whatwg] Codecs (was Re: Apple Proposal for Timed Media Elements)". whatwg mailing list (Mailing list). Retrieved 2008-02-25.
{{cite mailing list}}: Unknown parameter|mailinglist=ignored (|mailing-list=suggested) (help) - ^ a b Wenger, Stephan (28 November 2007). "Web Architecture and Codec Considerations for Audio-Visual Services" (PDF). W3C Workshop on Video on the Web, December 12-13, 2007. Retrieved 2008-02-25.
{{cite conference}}: Unknown parameter|booktitle=ignored (|book-title=suggested) (help) - ^ PC World - Mozilla, Opera Want to Make Video on the Web Easier
- ^ Opera <video> release on Labs - Opera Developer Community
- ^ http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-May/019992.html
- ^ html5.org
- ^ rudd-o.com
- ^ Abbadingo » Blog » Removal of Ogg Vorbis and Theora from HTML 5: an outrageous disaster
- ^ Hickson, Ian (11 December). "Re: [whatwg] Removal of Ogg is *preposterous*". whatwg mailing list (Mailing list). Retrieved 2008-02-25.
{{cite mailing list}}: Check date values in:|date=(help); Unknown parameter|mailinglist=ignored (|mailing-list=suggested) (help) - ^ "When will HTML 5 support <video>? Sooner if you help"
- ^ "W3C Video on the Web Workshop". Retrieved 2008-06-14.
- ^ http://www.w3.org/2007/08/video/positions/ position papers