What are you talking about, there are dozens of applications, tools and products that use, create and convert OOXML documents. You make it sound like the format is used only by Microsoft products.
As a .Net developer, I may be bias, but I have very little issue with how Microsoft went about this OOXML standarization. If I'm going to release an application that can uses document formats and I'm writing my application in .Net I want to use a format that my clients can open with the most popular application easily and a format I can create quickly.
The format allows developers, favoring .Net, to create documents in their own applications that follow standards that will function across the board.
Microsoft, as a software developer, has requirements and demands from customers and to think an open format like ODF can solve all of those strictly is silly. Microsoft isn't going away and the developer community around Microsoft products and technologies is incredibly large. You, again, make it sound like people are locked-in to Microsoft-only, when customers could use any number of developers that can read/convert/edit OOXML documents.
Discussion on:
Message 12 of 1
IBM Sponsored Resources
Resources from our Sponsor
- Oracle Exadata vs IBM: Netezza Compared
- Forrester TEI Report
- CIA Whitepaper
- Harnessing the Power of Advanced Analytics
- Tapping into Unleashed Business Potential with Advanced Analytics
- Unlock Analytic Performance with Revolution R for Enterprise and IBM: Netezza Data Warehouse Appliance
The best of ZDNet, delivered
ZDNet Newsletters
Get the best of ZDNet delivered straight to your inbox
