The Office Open XML Spec

I’ve been meaning to dig into the details of the Office Open XML specs for a while, and now that I’m moderating the OpenXmlDeveloper.org site I’ve started doing exactly that. It’s a 2000-page document, and it’s not in “published” form yet, so it’s a bit challenging to dig through all the details and figure out what really matters in real-world document assembly and application integration scenarios.

I figured as long as I’m going through this process, I might as well take some friends and colleagues along for the ride. So if you’re new to Office Open XML and want learn more about it, check out my “Guided Tour of the Spec, Part 1: Packaging” post. Next I’m planning to cover the three specific markup languages WordProcessingML, SpreadsheetML, and PresentationML, then I’ll start posting some C# code samples that use the System.IO.Packaging API to do common tasks with the new file formats.

Mom, you may want to sit this one out, since your computer doesn’t have the latest build of Visual Studio installed. I’ll post some fun pictures this weekend for you instead.

This entry was posted on Thursday, March 30th, 2006 at 10:38 am. You can subscribe to comments on this post through its RSS feed.

1 comment posted:

  1. […] Packaging and the Office Open XML Spec Doug Mahugh, Office 2007 Technical Evangelist, has been digging into the details of the Office Open XML specs and blogs the spec’s key concepts for developers. In this post he covers “Packaging” of Office 2007 files and how the different parts are the chunks of content that make up the document.   The ability to develop your own .zip-files using the managed code creates lots of new opportunities for ISVs. Meanwhile I’m looking forward to Doug’s System.IO.Packaging API code examples to code these packages. Published Friday, March 31, 2006 10:16 AM by davbosch Filed Under: ISV Community […]

Have your say

Fields in bold are required. Email addresses are never published or distributed.

Some HTML code is allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>
URIs must be fully qualified (eg: http://www.domainname.com) and all tags must be properly closed.

Line breaks and paragraphs are automatically converted.

Please keep comments relevant. Off-topic, offensive or inappropriate comments may be edited or removed.