News

EC Official Talks Open Standards, Raps Microsoft

A speech given yesterday by Neelie Kroes, the European commissioner for competition, skewered Microsoft without mentioning the company by name. In the speech, Kroes makes reference to Microsoft's outlaw status in failing to meet the European Commission's competition guidelines.

"The Commission has never before had to issue two periodic penalty payments in a competition case," she said, in a reference that only applies to Microsoft.

The two penalties originally were assessed at 280.5 million Euros and 899 million Euros, which would be a total of about $1.8 billion today. The penalties were associated with Microsoft's interface documentation royalty charges to competitors on work-group server technology, which were deemed excessive, causing the EC to fine Microsoft. Microsoft has appealed the latter penalty, which comes on top of the EC's fines.

Kroes' speech strongly advocated the use of open standards-based software. She said that purchasers of technology should implement a policy passed by the EC last year.

"For all future IT developments and procurement procedures, the Commission shall promote the use of products that support open, well-documented standards," she said in the speech. "Interoperability is a critical issue for the Commission, and usage of well-established open standards is a key factor to achieve and endorse it."

She recommended the adoption of that approach "with vigor." Moreover, the Commission has the responsibility to help governments avoid technology lock-ins.

"The Commission must do its part. It must not rely on one vendor, it must not accept closed standards, and it must refuse to become locked into a particular technology -- jeopardizing maintenance of full control over the information in its possession," she said.

The speech comes after Microsoft received a setback on its Office Open XML document format standard, which is used in Office 2007 applications. OOXML was approved in April as an international standard known as ISO/IEC 29500. However, four participating member countries have since appealed that decision, which essentially suspends ISO/IEC 29500 until those concerns are resolved.

Kroes' position echoes that of groups like the British Educational Communications and Technology Agency, an advisor to the U.K. government on technology issues, which has weighed in on supporting interoperability and given the thumbs down to using Office 2007. Other groups, such as the Canadian Library Association, have adopted a similar view on avoiding OOXML.

Ironically, Microsoft itself plans to support a rival document format standard, OpenDocument Format, which is used in productivity suites sponsored by Sun Microsystems and IBM. ODF support will be added when Office 2007 Service Pack 2 is released. Microsoft plans to "extend" support for OOXML in Office 14, which is the code name for the next major Office upgrade.

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