I just saw that the Novell folks have released a version of OpenOffice with support for the Ecma Office Open XML formats (http://download.novell.com/SummaryFree.jsp?buildid=ESrjfdE4U58~). They announced this work awhile ago, but this is the first chance folks have had to actually download the builds and try it out. Very cool stuff.

So at this point we now have a few options for applications that support Open XML on a couple different platforms. We'll see more popping up over the summer too (for example Corel as well as the Mac version of MS Office).

I think at this point we can really move onto more productive and collaborative discussion and admit that we are no longer in any sort of "file format war." If we ever were really in a war, it's now over, and both sides are winners. Over the past few years, we've had two important file formats come into the market, OpenXML and ODF. Both were designed for different purposes, and both have been valuable additions to the market. Now we can also say that we have multiple implementations of both formats.

When discussing file formats, there are a number of things that can set one apart from others such as performance; file size; security; accessibility; extensibility; and support for different types of functionality like formulas, formatting, drawings, etc. Before looking at any of those things though, there are some fundamental issues that may be important to see addressed. These issues have recently been called out by various government bodies (like departments within Massachusetts, Minnesota, Texas, and now California).

The big reason people are excited about both ODF and OpenXML is that they enable the following:

  1. Long term availability – You want to know that 100 years from now, you'll still be able to access your data. This is a complex problem, as it can affect everything from the software you use to the hardware you use that software on. The key in terms of file formats is that everything in the file format is fully documented, and the stewardship for that documentation belongs to an independent standards body. ISO, Ecma, OASIS, and the W3C are all examples of organizations people feel comfortable trusting with the stewardship of that documentation.
  2. Freely available – You want to make sure that you don't need to worry about someone else holding rights over your documents. If there is IP behind the format technology for instance, you want to make sure there is some type of license available that will work for you. Not only that, but you want to make sure this will work for anyone else that you want to have access to your documents. All formats out there take slightly different approaches here (PDF, OpenXML, ODF, HTML, etc.), so it's important to pay attention to this.
  3. Fully interoperable and accessible – You want to know that people on other systems can still work with your files. This means that the format needs to be fully documented, and there is nothing in the format that would prevent it from working on a different system. A great indicator here is to look at the number of applications that support the format, and what systems those applications run on. HTML is a great example of an interoperable format. OpenXML and ODF are also both fully interoperable, but are also much younger. So while you don't see as many applications support OpenXML and ODF as you do HTML, you'll clearly start to see more and more pop up as time goes by.

It's those three points that really make, both OpenXML and ODF interesting formats. You now have OpenXML supported by multiple applications on multiple platforms, and you have the same with ODF. There are definitely still some growing pains to go through. The tools that support the ISO ODF standard aren't yet fully compliant, but I think we're heading in the right direction. The same will be true for the OpenXML support.

Let's keep the momentum going and focus more on what we can do with the formats. I'm going to start pointing out solutions that other people are building around Open XML using the "3rd party tools" tag: http://blogs.msdn.com/brian_jones/archive/tags/3rd+Party+Tools/default.aspx