That issue has now been addressed, allowing Mozilla to support the codec in its Firefox Web browser.

The WebM video format is based on the VP8 video codec, something Google acquired last year from On2 Technologies, a New York-based video compression developer, for $106.5 million. At that time, Google announced it intended to use the codec technology it now owned to "make the overall Web experience better for users."

Since the acquisition, Google has open-sourced the codec, fixed the licensing issues (as noted above) and added WebM support into its own Web browser, Google Chrome, the latter taking place just last week.

WebM is an alternative to the H.264 codec, which is currently used by Apple to display video on the iPad and iPhone and is supported within Adobe's Flash player, among other things. Although H.264 is available royalty-free right now, it's owned by the MPEG LA consortium, a group that has announced the codec will only remain royalty-free until Dec. 31, 2015. After this license term is up, it's suspected that there will be charges for its use going forward.

Where to Find It

One of the first sites to implement WebM, was, of course, Google's own video property, YouTube. To utilize the new codec, which is still in testing, one can enable the "HTML5 experiment" following instructions from the WebM's project page. In addition to Google Chrome and now Firefox, Microsoft too has announced support for WebM in its upcoming Web browser, IE9, after an end user installs the necessary codec (VP8). Apple has so far made no comment on whether or not its Safari browser will do the same.

As for Mozilla, WebM is now available in the Firefox nightly builds, the experimental builds that will, in time, lead up to the public release of Firefox 4, expected to arrive in beta form later this month.

Updated June 10th, to clarify Firefox 4 launch this month is beta, not the public release.

As an example http://flickr.com/services/oembed?url=http://flickr.com/photos/bees/2362225867/ returns:

<oembed>
	<version>1.0</version>
	<type>photo</type>
	<title>Bacon Lollys</title>
	<author_name>bees</author_name>
	<author_url>http://www.flickr.com/photos/bees/</author_url>
	<cache_age>3600</cache_age>
	<provider_name>Flickr</provider_name>
	<provider_url>http://www.flickr.com/</provider_url>
	<width>500</width>
	<height>375</height>
	<url>
		http://farm4.static.flickr.com/3040/2362225867_4a87ab8baf.jpg
	</url>
</oembed>

Early adopters of the oEmbed spec are Flickr, Viddler, Pownce, Qik, and Revision3. Viddler has created a form to test the web service, so you can see it in action.

Essentially, oEmbed makes it easier to access photos and videos with a simple URL. Standardizing how things are embedded means that, for example, a social network could allow users to simply embed media from oEmbed enabled sites just by entering a URL to a photo or video -- and the "customer" site wouldn't need to deal with multiple APIs from each provider.