Month: May 2010

Last night Google appears to have ended its silence about its willingness to standardize VP8 and WebM.

Cnet has updated a news article, “Mozilla trying to build VP8 into HTML5 video“, with Google’s response:

“We’re excited by the community’s response to the WebM project, and we support efforts to standardize the technology,” Google said in a statement.

Updated 10:28 p.m. PDT with Google comment.

Perhaps not the most ringing endorsement of standardization, but with the W3C’s Philippe Le Hegaret pointing out in the same article that “[t]o be seriously considered by the W3C HTML Working Group, the specification would need to go through a standards group”, it must have been increasingly difficult to remain silent (or hope to arm-twist Android partners into shouldering the patent risk).

Le Hegaret’s full statement points to potential responsible next steps on the standardization path:

“WebM/VP8 has the potential of providing a solution for the baseline video format of HTML5. To be seriously considered by the W3C HTML Working Group, the specification would need to go through a standards group and be developed under RF [royalty-free] licensing participation terms,” Philippe Le Hegaret, leader of Web video work at the W3C, said in a statement. “W3C remains interested in having a video format for HTML5 that is compatible with the W3C Royalty-Free Patent Policy.”

As I have argued, standardization in a royalty free process is the right path for open video.

UPDATE (Dept. of Beware of Non-Ringing Endorsements)

The Register’s Cade Metz followed up with Mozilla to clarify their advocacy of including VP8 in HTML5:

Though Cnet says that Mozilla is working to incorporate VP8 into HTML5, the organization tells us that John Lilly was “discussing the ideal scenario for VP8, not what Mozilla is currently doing.”

Last week I encouraged Google to rethink their VP8 open sourcing patent strategy and

“do the right open standards thing — join and contribute to responsible standards groups that are working to solve the royalty-free open standards need.”

The blog was picked up in Simon Phipps’ ComputerWorld blog, ZDNet, The Register, LWN and elsewhere.

At one level, this is a classic debate about what is “open” and what should be its hierarchy of values, priorities, and even basic definitions.

But is a “de facto” standard the same as an “open” standard?  No, at least not in the definition of open standards of OpenForum Europe, of which Google is a leading member.

But there is more to consider.  Google is including WebM in the next version of Android and rules Android device makers with a strong hand, necessarily playing favorites to steer the Android ship. So the message must be clear to Android device makers, suppliers, and wannabes to get on the WebM bandwagon.  And though Google is known as tough with patent trolls, Android device makers appear to have been either left to fend off patent attacks themselves, cut deals, or perhaps be quietly aided in patent litigation defense.

All commercially rational choices in the crazy, hard-nosed, twisted global mobile patent wars.  After all, look at where the patents came from in MPEG LA subsidiary MobileMedia’s law suits against Apple, HTC, and RIM (Nokia and Sony) and HTC’s counter suit against Apple (AMD through Saxon).

So is the net-net simply “until you take open source and put it in a product you can’t get sued,” so just watch the big boys force each other to take, or cave in to, patent risks in order to get to the head of the line for a promising platform?  And just hope in the meantime that royalty-free open standards for the Open Web escape cannon fodder, collateral damage, or sell-out status in the smart phone patent wars?

Unfortunately, patent hold-up gambits thrive on adopt-first-ask-questions-later scenarios of the sort Google seems to be arm-twisting for here.  Standards groups, regulators, and industry continue to grapple with this challenge.   See yesterday’s FTC/DOJ/PTO workshop and the EU’s draft guidelines for horizontal cooperation agreements that mention that “[t]here should be no bias in favour or against royalty free standards, depending on the relative benefits of the latter compared to other alternatives”.

But if vendors ignore open standards altogether, we all lose.

UPDATE

According to CNET, the W3C is taking the position that WebM/VP8 needs to go through a royalty free standards process:

“WebM/VP8 has the potential of providing a solution for the baseline video format of HTML5. To be seriously considered by the W3C HTML Working Group, the specification would need to go through a standards group and be developed under RF [royalty-free] licensing participation terms,” said Philippe Le Hegaret, leader of Web video work at the W3C, in a statement. “W3C remains interested in having a video format for HTML5 that is compatible with the W3C Royalty-Free Patent Policy.”

Much of the initial commentary on Google’s open sourcing of the VP8 codec it acquired in purchasing On2 has breathlessly, and uncritically, centered on the purported game-changing impact of the move.

But unfortunately, these commentaries miss an essential point that Google has studiously avoided mentioning the need to standardize royalty free codecs (not just release an open source snapshot).

But since forward motion is good simply because it is forward motion, shouldn’t one hesitate to look this gift horse in the mouth?

Unfortunately, in the case of multimedia codecs and technologies, ignoring open standards and instead presenting open sourcing as a fait accompli solution just works to the detriment of the entire open community.

The open Web needs royalty free standards (true, multi-stakeholder run standards, not unilateral actions) — that is its essential genius.  And without them, proprietary, vendor-controlled projects, even those that self-label as “open”, do little good and more likely more harm than good.  We all have the right to expect, and demand, that the Web’s current beneficiaries and leaders stay true to this fundamental open standards proposition, and not just forget it when convenient.  And this includes Google.

It is well known that many experts consider it now feasible to standardize serviceable royalty-free codecs.  MPEG (the standards group, not the unaffiliated license administrator MPEG LA) has even put out a resolution to that effect, and IETF has recently launched a royalty free codec activity in a similar spirit.  Google should get on board on this important trend, not undermine it with studied avoidance.  So far they have not.

It is important to understand that patent claims are typically handled under confidential non-disclosure agreements.  So unless there is a forcing function (litigation or standardization-required disclosure and review), there is no effective way to know who is actually claiming, and who is paying, what.  And there are documented cases of this going on for literally years.  So leaving VP8 code out in the open with nothing but a mutual non-assert license leaves the patent issue not only unaddressed, but up for capture by those with uncharitable agendas, and on their turf and time frame (let’s at least hope that’s sooner rather than later — but remember, forming patent pools rarely disclose all their patents up front).

Not a smart move, and hopefully one Google will realize the error of and correct quickly (here’s a useful cover story: we intended to smoke out patent holders all along, and we were going to get around to working with standards groups when we had the chance).  Contributing VP8 to a standards group with a strong patent disclosure policy would be a good corrective move; it would force lurking patent holders to come fully into the public. Not perfect, but a step forward.

Google’s open sourcing of VP8 is very different from Sun’s Open Media Stack codec work, and for that matter other responsible open video initiatives, which have based their work on identifiable IPR foundations, documented their patent strategy, and have been willing to work with bona-fide standards groups to address and resolve IPR issues.  When companies like Google ignore standards and go on their own in such important areas as video codec standards, they just undermine the very standards groups the open Web needs to thrive and grow.

We’d never accept a brand name company unilaterally declaring control of the next version of TCP/IP, HTML, or any other of a host of foundational Internet and Web standards simply by open sourcing something they’d bought.  Codecs will also be such a foundational component, a critically important one.  Just because the technology of codecs might be less familiar than some other technologies is no reason to abandon the royalty-free standardization philosophy that has built the Web.

Certainly not based on the complete feel-good-marketing non-explanation for this radical abandonment that Google has offered so far.   Because patent pool licensing is out of control?  No argument about that from me (or antitrust complainants Nero, VIZIO, and others).  Because Google “must have done its patent homework”?  OK, if so why not hand that homework in as a contribution to a standards group where it could get some expert scrutiny?

So I would encourage Google to do the right open standards thing — join and contribute to responsible standards groups that are working to solve the royalty-free open standards need.  Be a part of the royalty-free, open-standards solution, not part of the problem.

UPDATE

Tip of the hat to Xiph’s leader, Chris Montgomery, for good tongue-in-cheek humor:

“I, FOR ONE, WELCOME OUR NEW WEBM OVERLORDS“

Not to confuse: Xiph is wholeheartedly supporting WebM, but another interesting remark by Montgomery:

“But Monty isn’t worried about the MPEG-LA suing him or anyone at the WebM Project.

“The recent saber-rattling by Jobs felt more like a message to his own troops than
a warning shot to ours,” he says. “MPEG itself has always has an internal contingent
that has pushed hard for royalty-free baselines from MPEG, and the missives about
video codecs and patents were probably meant for them, not us.”