Following on from one of the sessions that took place as part of the DII workshop on ODF and Office SP2 in Redmond Doug Mahugh has written up what was described as the guiding principles for the ODF implementation in Microsoft Office.

This blog post covers the main presentation from our ODF workshop that took place in Redmond last week: Peter Amstein’s explanation of the guiding principles behind our support of ODF in Office 2007 SP2. I’ve added explanations of some of the details that were covered verbally in the workshop, but if anything’s not clear here, please let me know.

Why ODF 1.1?

We’re implementing ODF 1.1 in our initial release of ODF support. We chose this version because it is the most current approved ODF specification, and because it is the version of ODF that current release versions of most other applications such as OpenOffice also support. We will support ODF in Word, Excel and PowerPoint, using the file extensions .odt, .ods, and .odp. The exact release date for Office 2007 SP2 has not been announced yet, but we expect ODF support to be available sometime in the first half of 2009.

Guiding Principles

As we set out to build in support for ODF, we developed a set of principles to guide our implementation team. Those principles are:

• Adhere to the ODF 1.1 Standard
• Be Predictable
• Preserve User Intent
• Preserve Editability
• Preserve Visual Fidelity

The conversation was a fascinating part of the day where the development leads talked through the complex set of decisions that they have had to make as they build ODF support into the products.

I would encourage anybody interested in this topic to read Doug’s whole post…

As the announcement happened while those of us here in Asia were sleeping peacefully pretty much everything that could have been said on the topic has already been said, so I thought it might be more useful to present more of a round up of what I’ve been reading this morning.

First of all a little about the announcement itself.

There is a lot more to this than just support for ODF in the Microsoft Office product, although obviously the native support for ODF is a focus for many of the words that have been written overnight.

The company also announced plans to offer greater support for a number of alternative document formats – including Open Document Format (ODF) v1.1, Adobe Portable Document Format (PDF) 1.5, PDF/A and XML Paper Specification (XPS) – within Word 2007, Excel 2007 and PowerPoint 2007.  

In addition, Microsoft will support the future maintenance and evolution of these format standards by participating on the standards committees charged with these activities. This means that Microsoft folks will join the OASIS ODF TC and participate alongside IBM, Sun, Novell and everybody else present.

Finally ODF will be added to the list of specifications that are covered by the Open Specification Promise, ensuring that every developer has access to any intellectual property that Microsoft might put forwards during these maintenance processes.

The Microsoft blogs that first carried the announcement were the usual folks.

Jason Matusow looks at this announcement in the context of the companies continuing commitment to interoperability as a tenant of the way we design products and collaborate with the rest of the industry. Jason and I share views on the issue of so called “single standards” and he eloquently explains that further in his post.

This is not about any one document format “winning” – it is about enabling customers to evaluate and use document formats that make the most sense for them. Just as the MS deal with JBOSS didn’t mean we were saying that J2 was better than .NET – it is that we want our customers to have the most positive experience possible when using our product.

Doug Mahugh talks about some of the more technical details of the announcement, as well as discussing what this means to existing initiatives. He talks about our continued commitment to the translator projects for ODF, DAISY, UOF etc. and links to the ODF Translator team blog where they have just kicked off version two of that project.

Finally Doug answers a question I was asked over dinner earlier this week… we’ll be adding APIs that allow third parties to intercept the ODF load and save paths so if anybody disagrees with our implementation then all the tools are available for them to write their own.

Gray Knowlton digs around the “Why?” question, again one that came up in my dinner conversation earler this week. Why now? Why when OpenXML just got approval? etc.

Success in our industry (like a lot of other industries) boils down to successfully addressing the needs of customers. By offering greater choice for file formats, our products address more scenarios and provide greater flexibility in enabling specific solutions. From a pragmatic standpoint, adding ODF to Office allows us to re-focus Office on product capabilities rather than a debate about file formats. We’re quite comfortable when we compete in the marketplace on these merits.

Looking around the blogosphere this morning the announcement appears to be very well received by just about everybody, as I said earlier in this post most people seem to be focused on the component of this announcement that talks about native ODF support in Microsoft Office, but it is important to recognize that this is bigger than just that one item.

The announcement, in my view, demonstrates a strong commitment to the Interoperability Principles that we shared earlier this year. As always there is still much work to be done, but this is a great step in the right direction.

If you want to read a little more then here are some links that you might find useful. There is a lot more out there, feel free to link anything addition that you find in the comments of this post.

Press: PC World NZ, Information Week, CNet News, SD Times, New York Times, itWire, Slashdot(!)

Blogs: Stephen McGibbon (MS), Jerry Fishenden (MS), Brian Jones (MS), Jesper Lund Stocholm, Richard Koman, Andy Updegrove, Bob Sutor, Ed Brill, GeekZone NZ, Joe Wilcox, Eric White (MS), Savio Rodrigues

On a final note, I feel compelled to pull one paragraph out of Bob Sutor’s (IBM) post;

There is no reason for more governments and organizations not to start mandating the use of ODF. If you are not using ODF today, you should put adoption plans in place.

There is an area where Microsoft and IBM seem to disagree.

My own personal view on this, which appears to be shared by a majority of the customers I work with, is that mandating a single standard for anything IT related is generally not a great move for government.

IT standards, like any area of technology, move on.

Governments need to remain ready to move with the technology that is in use by their citizens and businesses, mandates for information technology standards often do little more than operate as a hurdle to doing this.