Use of Ogg formats in HTML5

HTML
HTML and HTML5 Dynamic HTML XHTML XHTML Mobile Profile and C-HTML Canvas element Character encodings Document Object Model Font family HTML editor HTML element HTML Frames HTML5 video HTML scripting Web browser engine Quirks mode Style sheets Unicode and HTML W3C and WHATWG Web colors Web Storage Comparison of document markup languages web browsers layout engines for HTML HTML5 HTML5 Canvas HTML5 Media Non-standard HTML XHTML (1.1)
This box: view · talk · edit

The HTML5 draft specification adds video and audio elements for embedding video and audio in HTML documents. The specification had formerly recommended support for playback of Theora video and Vorbis audio encapsulated in Ogg containers to provide for easier distribution of audio and video over the internet by using open standards, but the recommendation was soon after dropped.

Motivation

Because many users, visitors and publishers alike, choose not to take part in the use of proprietary software, web content must be available through freely implementable open standards in order to reach these users. As multimedia is already mainstream on the web through proprietary data formats (such as Windows Media Video and MP4) and browser plugins (such as Adobe Flash Player), developers had hoped Theora and Vorbis would become part of the HTML5 specification.^[1]

Users not beholden to proprietary software could also see advantages:

• The potential for universal adoption of Theora and Vorbis, no matter the computer or the user, would ease "codec hell" by eliminating an unnecessary amount of codecs required to view and publish videos to a select few.
• Browser plugins needed to accommodate the many different codecs would then become a thing of the past:
  • Browsers could handle the playback of Theora and Vorbis and allow the user to customize the manner in which that was done.
  • Bugs and exploits in those obsolete plugins would affect the user less and less as they were phased out and not at all once they were ultimately removed.
  • The HTML5-conformant player, not having to be coded for compatibility with different browsers, could make bugs and exploits easier to find during browser development, and any exploits found would only be able to target that one browser.
• Free software encoders would compete with rival proprietary encoders, increasing encoder quality through competition.
• Embedding multimedia by the use of the clear and straightforward video and audio elements would require less effort than mastering the object element or learning ActionScript as required by Adobe Flash.

CTO at Opera Software, Håkon Wium Lie explained in a Google tech talk entitled "The <video> element" the proposal of Theora as the video format for HTML5:^[2]

I believe very strongly, that we need to agree on some kind of baseline video format if [the video element] is going to succeed. [...] We want a freely implementable open standard to hold the content we put out. That's why we developed the PNG image format. [...] PNG [...] came late to the party. Therefore I think it's important that from the beginning we think about this.

After the presentation, Lie was asked whether Opera will support other formats than Ogg:

My opinion is that browsers shouldn't support other codecs, at least not in the beginning, until we have established a baseline format. [...] We don't want to contaminate <video> with other formats.

Support

Opera Software and Mozilla have been advocates for including the Ogg formats into the HTML standard.^[3] Support has been available in experimental builds of Opera 9.5 since 2007,^[4] and Ogg Theora is fully supported since Opera 10.50.^[5] Gecko 1.9.1 (browsers based on this engine include Mozilla Firefox 3.5 and SeaMonkey 2.0^[6]), released on June 30, 2009, was the first non-experimental layout engine to support Ogg formats. Google Chrome included support in their 3.0 release (September 2009),^[7] along with support for H.264. However, not supporting MPEG-1 citing concerns over performance.^[8]

Opposition

On October 17, 2007, the World Wide Web Consortium encouraged interested people to take part in a "Video on the Web Workshop", held on December 12, 2007, for two days.^[9] A number of global companies were involved, submitting position papers.^[10] Among them, Nokia's paper^[11] 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", yet Xiph.org's codecs are licensed under a BSD-style permissive free software license and are therefore not proprietary in any accepted meaning of the word. Apple Inc., a member of the MPEG LA, has also opposed the inclusion of Ogg formats in the HTML standard on the grounds that H.264 performs better and is already more widely supported, citing patents on their codec's efficiency and the lack of precedents of "Placing requirements on format support", even at the "SHOULD" level, in HTML specifications.^[12]

In response to criticism, WHATWG has cited concerns over the Ogg formats still being within patent lifetime and thus vulnerable to unknown patents.^[13] Such submarine patents may also exist for non-free formats like MP3. Also, the AVC patent licensing policy is subject to change in a not-yet-clear manner.^[14]

Recommendation retracted

On December 10, 2007, the HTML 5 specification was updated,^[15] replacing the reference to Theora and Vorbis with a placeholder:^[16]

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: we need a codec that is known to not require per-unit or per-distributor licensing, that is compatible with the open source development model, that is of sufficient quality as to be usable, and that is not an additional submarine patent risk for large companies. This is an ongoing issue and this section will be updated once more information is available.^[17]

The removal of the Ogg formats from the specification made it completely file format neutral, like previous versions of HTML. The decision was criticized by a number of Web developers.^[18][19] A follow-up discussion also occurred on the W3C questions and answers blog.^[20]

See also

• HTML5 video

References

1. ^ RoughlyDrafted Magazine (6 July 2009). "Ogg Theora, H.264 and the HTML 5 Browser Squabble". RoughlyDrafted Magazine. http://www.roughlydrafted.com/2009/07/06/ogg-theora-h-264-and-the-html-5-browser-squabble/. Retrieved 14 February 2010. 
2. ^ "Håkon Wium Lie on the video element in HTML 5". Google Video. 2007-03-29. http://video.google.com/videoplay?docid=5545573096553082541&ei=LV6hSaz0JpbA2AKh4OyPDg&hl=un. Retrieved 2009-02-22. 
3. ^ "Mozilla, Opera Want to Make Video on the Web Easier". PC World. 2007-12-07. http://www.pcworld.com/article/id,140408-pg,1/article.html. Retrieved 2009-06-30. 
4. ^ "Opera release on Labs - Opera Developer Community". Dev.opera.com. 2007-11-07. http://dev.opera.com/articles/view/a-call-for-video-on-the-web-opera-vid/. Retrieved 2009-06-30. 
5. ^ Jägenstedt, Philip (2009-12-31). "(re-)Introducing <video> - Official blog for Core developers at Opera". Opera. http://my.opera.com/core/blog/2009/12/31/re-introducing-video. Retrieved 2010-01-02. 
6. ^ Kaiser, Robert (2009-10-28), SeaMonkey 2.0 - What's New in SeaMonkey 2.0, seamonkey-project.org, http://www.seamonkey-project.org/releases/seamonkey2.0/, retrieved 2009-10-31 
7. ^ Laforge, Anthony (September 15, 2009). "Google Chrome after a year: Sporting a new stable release". Google. http://googleblog.blogspot.com/2009/09/google-chrome-after-year-sporting-new.html. Retrieved 2009-09-22. 
8. ^ Fette, Ian (May 29, 2009). "whatwg MPEG-1 subset proposal for HTML5 video codec". WHATWG. http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-May/019992.html. Retrieved 2009-06-24. 
9. ^ "W3C Video on the Web Workshop". http://www.w3.org/2007/08/video/. Retrieved 2008-06-14. 
10. ^ "Workshop Papers". W3C. http://www.w3.org/2007/08/video/positions/. Retrieved 2009-06-23. 
11. ^ Wenger, Stephan (28 November 2007). "Web Architecture and Codec Considerations for Audio-Visual Services". W3C Workshop on Video on the Web, December 12–13, 2007. http://www.w3.org/2007/08/video/positions/Nokia.pdf. Retrieved 2008-02-25. 
12. ^ Stachowiak, Maciej (21 March 2007). "[whatwg] Codecs (was Re: Apple Proposal for Timed Media Elements)". whatwg mailing list mailing list. http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2007-March/010392.html. Retrieved 2008-02-25. 
13. ^ Hickson, Ian (11 December). "Re: [whatwg] Removal of Ogg is *preposterous*". whatwg mailing list mailing list. http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-December/013154.html. Retrieved 2008-02-25. 
14. ^ http://arstechnica.com/open-source/news/2009/07/decoding-the-html-5-video-codec-debate.ars
15. ^ Hickson, Ian (10 December 2007). "[whatwg] Video codec requirements changed". whatwg mailing list mailing list. http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-December/013135.html. Retrieved 2008-02-25. 
16. ^ "(X)HTML5 Tracking". HTML5.org. http://html5.org/tools/web-apps-tracker?from=1142&to=1143. Retrieved 2009-06-23. 
17. ^ "[whatwg] Removal of Ogg is *preposterous*". WHATWG mailing list. Lists.whatwg.org. 11 December. http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-December/013152.html. Retrieved 2009-08-25. 
18. ^ "The Attack Against Ogg Theora or: How I Learned to Stop Worrying and Love the Proprietary Web". Metavid. 11 December 2007. Archived from the original on 23 June 2009. http://google.com/search?q=cache:Fmc-sySHE0oJ:metavid.org/blog/2007/12/11/the-attack-against-ogg-theora-or-how-i-learned-to-stop-worrying-and-love-the-proprietary-web/+http://metavid.org/blog/2007/12/11/the-attack-against-ogg-theora-or-how-i-learned-to-stop-worrying-and-love-the-proprietary-web/&cd=1&hl=en&ct=clnk&gl=uk&client=firefox-a. Retrieved 2009-06-30. 
19. ^ "rudd-o.com". rudd-o.com. 2007-12-11. http://rudd-o.com/archives/2007/12/11/removal-of-ogg-vorbis-and-theora-from-html5-an-outrageous-disaster/. Retrieved 2009-06-30. 
20. ^ Connolly, Dan (December 18, 2007). "When will HTML 5 support <video>? Sooner if you help". W3C. http://www.w3.org/QA/2007/12/when_will_html_5_support_soone.html. Retrieved 2009-06-23. 

• Codecs for <audio> and <video> – Ian Hickson (summary of situation as of June 29, 2009)

External links

Ogg hosting websites using HTML5

These websites host user uploaded multimedia in Ogg formats and offers embedding at least with the use of audio or video elements:

• Dailymotion - openvideo
• Internet Archive