Channels ▼


Microsoft Publishes Implementation Notes for File Formats in Office 2007

Microsoft has published documentation detailing its implementation of OASIS Open Document Format (ODF) version 1.1 support in Microsoft Office 2007 Service Pack 2, currently in beta and scheduled for release next year. Similarly detailed notes about the company's implementation of Open XML (Ecma 376 Edition 1) in Office will follow in the coming weeks.

These implementation notes offer a guide on how Microsoft is implementing ODF and Open XML within its Microsoft Office suite. The notes, available at no charge on the Document Interoperability Initiative (DII) site, are useful to developers seeking to enhance the interoperability of their solutions with Microsoft products.

"By publishing notes on how we are implementing file format standards in Microsoft Office, we are providing detail that others can use as a reference point for their own applications," said Doug Mahugh, senior project manager for Office interoperability. "We encourage other companies to take similar steps to help achieve greater interoperability across the industry."

Microsoft's implementation notes include the following:

  • Details on implementation decisions. When implementing a standard, an implementer may find the text ambiguous or more permissive than is appropriate for that particular implementation. In these cases implementers need to make a choice that best suits their application. This type of information enables developers to see the direction a vendor is taking and make informed decisions about their own efforts to interoperate.
  • Details on additional data written into files. File format standards typically allow additional application-specific information (such as certain user customizations) to be written to the file. By providing this information vendors allow developers to correctly interpret the additional data.
  • Details on implementation variances. With every application there may be instances where an implementer cannot follow the standard exactly for one reason or another. For example, general industry practice may differ from what is in the specification or users may have made clear that they need something different. In such cases, it is important for vendors to document their approach so other vendors can make fully informed decisions about how they will approach implementation.

Standardization is a useful first step in promoting interoperability, but more work is required among vendors to achieve the goal:

  • Shared stewardship in the ongoing evolution of the standards as they are maintained by the standards body. Microsoft is committed to being an active participant in the evolution of ODF, Open XML, XML Paper Specification and PDF standards. Microsoft has already made contributions to ODF in OASIS and is actively participating in the maintenance of Open XML in ISO/IEC.
  • Transparency. Vendors must be transparent when implementing standards in their own products. By publishing these implementation notes Microsoft is helping other developers and vendors make informed decisions on how they create their own implementations. In addition to the ODF notes, Microsoft will also publish similar implementation notes for Open XML in the coming months. This information will be updated over time as products change and based on feedback.
  • Collaboration. Vendors must collaborate with other vendors to identify and resolve real-world issues among implementations, and build tools and solutions to improve interoperability over time. Events such as the DII workshops around the world enable technical vendor discussions, labs and solution-enablement programs that help vendors develop solutions for effective data exchange between product implementations of document format standards.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.