News

Court Upholds Ruling Against Microsoft in i4i Case

Microsoft has lost another round in the ongoing patent infringement lawsuit filed by i4i, a Toronto-based developer of collaborative content solutions and technologies.

The suit, filed March 2007, alleges Microsoft infringed on an i4i-patented technology that creates a "metacode map" allowing "a computer to manipulate the structure of a document without reference to content," according to the patent. i4i claims in the lawsuit that Microsoft infringed on the patent when it introduced a version of Word in 2003 with XML editing capabilities.

Last year, a federal court jury in Texas awarded i4i $290 million in damages, plus interest and court costs. The court also ordered Microsoft to stop selling future versions of Word that contain the technology. Microsoft subsequently issued a patch for Word 2007 and 2003 disabling the technology, but appealed the ruling.

In December 2009, the U.S. Court of Appeals for the Federal Circuit upheld the ruling and injunction against selling Word versions containing the disputed technology. Microsoft's appeal was based on trial procedure precedents, according to court documents.

On Wednesday, the court issued a revised opinion upholding the lower court's trial procedures and ruling, as well as offered a more detailed analysis, saying that "Microsoft willfully infringed on i4i's patent."

"This is a very good result for us in our ongoing pursuit to protect our company's patent on this technology," said Loudon Owen, chairman of i4i, in a telephone interview. "The fact that the three judges found that Microsoft willfully infringed on our patent is obviously a good sign, but it's not the end of the line."

Owen said he expects Microsoft to pursue its appeal all the way to the Supreme Court.

A Microsoft spokesperson said by phone that "Microsoft is not officially commenting on the case," but added that Microsoft will pursue an "en banc" review of the ruling by a full panel of 12 judges.

Owen speculated that it would take a consensus of seven judges to overturn the ruling, and said i4i is fully prepared to continue a long-term effort to protect its assets and build its company.

"It has been a drain on our resources, there's no question, but we believe in the technology and we are looking forward, not backward," Owen said. "We have an injunction [to stop Microsoft], we have a product, we have an award of $290 million dollars plus interest, and we have an opportunity to build our business."

An en banc review is expected to be filed in the Federal Court of Appeals in the near future, according to an i4i statement and sources close to Microsoft.

About the Author

Herb Torrens is an award-winning freelance writer based in Southern California. He managed the MCSP program for a leading computer telephony integrator for more than five years and has worked with numerous solution providers including HP/Compaq, Nortel, and Microsoft in all forms of media.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube