Since H264 was implemented in the open with open and large membership to the body, it is more difficult for some company to come out of the woodwork and say, "Hey, we have a patent that H264 rides on, but we didn't know it until now" Note, QCOM tried this with H264 several years ago and got their butt handed to them by the courts (http://www.broadcom.com/press/release.php?id=1037466). People have had 10 years to examine this open specification. I think its reasonable to say that one would have found a violation by now. And almost all the majors are already either licensees or licensors. There's a slim chance that there's a patent floating around in some patent troll portfolio that hasn't been examined, but that's the only real vector I can see of a legitimate surprise H264 patent violation.
Whereas with WebM its been in the public domain less than a year. It could feasibly take a few years for it to be reaonable that anyone who would have done due diligence to have done so. It's completely reasonable that in a year from now Siemans comes out and says, "WebM infringes these three patents we have". A court is not likely to throw it out saying they've been sitting on them.
This is the true genious of the WebM license. It means even if this does happen in the future, Google can destroy whoever has this patent through a massive counter. It also means that any challenge would have to be made extremely carefully.
edited for spelling :)
> Its severely bound in what it can be by trying to avoid
> H.264's existing patents.
Doesn't that describe anything that isn't h.264? Might as well say that h.264 got there and patented everything good, so they must have won. We should just pack up and go home, they get to have a monopoly on video codecs for the next 14+ years.Yeah probably - ask the Theora guys how hard its been ;-) The upside is that it could very much, out of necessity, drive some considerable advancement in video compression algorithms.
>VP8 is not a standard. It was developed secretly by a single company, and until recently, had only a single working implementation. The public wasn’t open to collaboration on the specification until the bitstream spec was frozen, including the bugs that existed within.
This is an interesting point. One I had never even realized.