News

Tool Checks for 'Custom XML' in Word Files

Microsoft's court loss to i4i LP has spawned a make-shift tool to check for patent-infringing technology in Word files.

The free tool can be used to scan .DOCX and .DOCM Word files. It generates a log file that lists "custom XML" code references in the Word files. The unsupported tool is described by Gray Knowlton, a Microsoft product management team leader for Office developers, and it can be downloaded at his blog page here.

Custom XML is a term used by Microsoft to describe user-defined schemas in XML, according to the inventor of the technology, Michel Vulpe, founder and CTO of i4i. Microsoft was enjoined from selling copies of Office 2007 and Office 2003 that use this technology after Jan. 10, according to a court decision, which was upheld on appeal.

The scanning tool may be just for the morbidly curious. Existing users of Office 2007 and Office 2003 do not have to stop using those products, nor do they even have to care that custom XML code is used in those products. Those who buy Office products today however will use updated technology, or they will be prompted by Microsoft to apply a patch that avoids the infringing technology.

"The documents identified by the tool as containing custom XML markup are themselves not affected by the ruling, and require no action on your part," Knowlton explained in the blog. "What positive scan results will indicate are documents that will behave differently when opened in patched and unpatched versions of Office."

Knowlton added that the tool can be used to help determine "possible areas of impact for your specific IT environment."

In other posts in his blog, Knowlton explained that the custom XML technology can also be identified by "pink tags" that show up around the tagged content. The court's judgment against Microsoft doesn't apply to ECMA and ISO/IEC standards for Office Open XML, according to Knowlton.

"Even if Word's specific implementation of custom XML support does infringe the i4i patent (which Microsoft does not believe to be the case), i4i has never claimed that its patent is essential to the OXML standard," Knowlton wrote in his blog. Microsoft is currently seeking a rehearing of the i4i case.

Some news accounts reported that copies of Office 2007 and Office 2003 were removed from store shelves after the Jan. 10 injunction date. However, the Microsoft Store in Mission Viejo, Calif. currently stocks all editions of the products, according to a "store associate" via telephone. Possibly, there's disruption in ordering the products online. An attempt to order full editions of Office 2007 from Microsoft's online store produced a "temporarily out of stock" message. However, a check at Amazon.com showed the products to be in stock.

About the Author

Kurt Mackie is senior news producer for 1105 Media's Converge360 group.

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