The ISO End Game -- Visual Studio Magazine

Desmond File

The ISO End Game

Yesterday, we were all expecting to hear the final results of the vote to make Microsoft Office Open XML (OOXML) an industry standard under the International Organization for Standardization (ISO). That announcement has been put off until tomorrow, but rumors persist that Microsoft may have narrowly won the support it needed to gain approval.

We'll be covering the ISO process and its implications in our next issue of Redmond Developer News magazine, but in the meantime, I'm left to wonder: What do developers think of the noisome ballot process that has brought OOXML to the doorstep of ISO ratification? What could have been done better? And what, perhaps, shouldn't have been done at all? E-mail me at mdesmond@reddevnews.com.

Posted by Michael Desmond on 04/01/2008

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.