For detailed information check out one of the blog entries from Brian Jones & Zeyad Rajabi, Eric White or Gray Knowlton.

Eric White has a great description of the two components of the SDK;

As with the CTPs, the RTM version of the Open XML SDK consists of two principle components:

• A .NET managed class library that provides capabilities for reading, writing, modifying, and validating Open XML documents.

• A productivity tool that includes the ability to diff Open XML documents, a C# code generator, and tools to explore and read about the class library and the standard.

About the Library

Some of the key characteristics of the library are:

• You can use a powerful functional programming approach to write applications that generate documents, spreadsheets, and presentations.

• You can use Language Integrated Query (LINQ) to retrieve data and content from documents, spreadsheets, and presentations.

• You can write code to open, modify, and save documents.

• You can use validation functionality to be more certain that your documents conform to the IS29500 standard and will be able to be opened using Microsoft Office and other conforming applications. Document formats, by their very nature, are involved. The validation functionality in the Open XML SDK is a big help when writing real-world solutions.

About the Tool

Key features of the tool are:

• You can compare two Open XML documents to see exact changes in their markup. This is one of the best ways to learn about Open XML markup. If you want to understand which elements and attributes represent a feature that you want to interact with, create a document without the feature, copy the document to a new document, modify the new document, and compare to the old. After determining the elements and attributes that changed, you can research them in the Open XML specification.

• You can build a document generation program with a minimum of effort. You supply the tool with a sample document. You can then generate C# code that that will generate the entire document, a specific part, or a specific element with its children elements. This code is generated in a style that takes advantage of ‘functional construction’. By this, I mean that any element (or its descendant elements) can be generated in a single expression. You don’t need to write multiple statements. This ability to generate content in an expression instead of a statement means that you can use LINQ queries and projections to formulate new descendant content for an element. It’s a powerful approach.

• The ability to explore the Open XML specification, the implementation notes, and the Open XML SDK class hierarchy in the tool means that you have one integrated tool to do much of the work that is necessary to build sophisticated document generation systems.

Download the SDK

Download the Open XML SDK 2.0 for Microsoft Office
This download provides strongly typed part and content classes for use with Office 2007 & Office 2010 Open XML documents. http://www.microsoft.com/downloads/details.aspx?FamilyID=c6e744e5-36e9-45f5-8d8c-331df206e0d0

It seems that back on the 16th June OpenXPS, the Open XML Paper Specification, was approved as an ECMA standard by their 97th General Assembly meeting, OpenXPS will be known as ECMA-388.

A basic outline can be found on the specification download page;

This Standard defines OpenXPS, the Open XML Paper Specification. OpenXPS describes a set of conventions for the use of XML and other widely available technologies to describe the content and appearance of paginated documents. It is written for developers who are building systems that process OpenXPS content.

A primary goal is to ensure the interoperability of independently created software and hardware systems that produce or consume OpenXPS content. This Standard defines the requirements that systems processing OpenXPS Documents must satisfy in order to achieve interoperability.

This Standard describes a paginated-document format called the OpenXPS Document. The format requirements are an extension of the packaging requirements described in the Open Packaging Conventions (OPC) Standard. That Standard describes packaging and physical format conventions for the use of XML, Unicode, ZIP, and other technologies and specifications, to organize the content and resources that make up any document. They are an integral part of the OpenXPS Standard, and are included by reference.

Many XML-based building blocks within OpenXPS make use of the conventions described in the Markup Compatibility and Extensibility Standard that is relied upon by the OPC Standard to facilitate future enhancement and extension of OpenXPS markup. As such, that Markup Compatibility and Extensibility Standard is included by reference.

The specification itself has yet to be posted, but will be available from this link once it is.

For those wanting to find out more, Stephen McGibbon provides pointers to an explanatory whitepaper in XPS and PDF format.

The maintenance of OpenXML within ISO appears to be moving forward well.

From Alex’s blog post;

Overall, WG 4 is making excellent progress. To date, 169 defects have been collected for OOXML (check out the defect log) and the majority of these have either been closed, or a resolution agreed. Amendments were started for 3 of the 4 parts of OOXML to allow a bunch of small corrections to be put in place, and the even-more-minor problems will be fixed by publishing technical corrigenda. Overall, I think stakeholders in OOXML can feel pretty confident that the Standard is being sensibly and efficiently maintained.

I was personally very pleased to see National Bodies well-represented (the attendance list is here [tbc]) – to the extent that I’d now ideally like to see some more big vendors coming to the table so their views can be heard. Microsoft (of course) was; but where (for example) are Apple, Oracle and the other vendors who participated in Ecma TC 45 while OOXML was being drafted? To them – and to anybody who wants to get involved in this important work – I say: participate!

Over at Rick Jelliffe’s blog Rick has been carrying out something of an exposé of the unfortunate imbalance in the stakeholders represented in the maintenance of ODF at OASIS (something which will become even more acute if Sun is, in the end, snapped-up by IBM). Personally I think Rick is right that it is vitally important to have a good mix of voices at the standardisation table: big vendors, small vendors, altruistic experts, users, government representatives, etc. WG 4 is getting there, but it too has some way to go.

The international participation in the IS29500 maintenance process appears to be both climbing and broadening beyond the original actors.

We have been talking for a while now about running one of those workshops in South East Asia, and we finally have a date for it. The intention is to run a DII workshop in Singapore on March 16th and 17th.

For now we are starting to think about topics that would be valuable to discuss during the time that we have. Initial ideas include looking at China’s Uniform Office Format (UOF) and how it interoperates with other document formats, along with spending some time looking at the extensive work that has been taking place with DAISY in the region.

Any other ideas are welcome, please feel free to drop your thoughts in the comments of this post or hit the “contact” button on the right and send me an email.

I’ll share the venue details a little closer to the time, it will most likely be in a hotel somewhere in Singapore’s CBD. Like previous workshops attendance is open to anybody who is interested, and conversations will be as interactive as possible.

On Thursday, December 4, 2008 the Ecma General Assembly voted to approve International Standard (IS) ISO/IEC 29500 (Office Open XML) as ECMA-376 Edition 2.

Office Open XML is an open standard for word-processing documents, presentations and spreadsheets that is intended to be implemented by multiple applications on multiple platforms. A primary rationale behind the standard is to ensure the long-term preservation of documents to maintain compatibility with continuing advances in the field of information technology.

The work to standardize Office Open XML started in December 2005 in Ecma International via its Technical Committee 45 (TC45), which included representatives from Apple, Barclays Capital, BP, The British Library, Essilor, Intel, Microsoft, NextPage, Novell, Statoil, Toshiba and the United States Library of Congress.

This means that IS29500 and ECMA-376 are now aligned, so all the changes that occurred within the spec as revision one of the ECMA standard went through ISO approval are now rolled back into the original document.

ISO/IEC 29500 is a standard for word-processing documents, presentations and spreadsheets that is intended to be implemented by multiple applications on multiple platforms. One of its objectives is to ensure the long-term preservation of documents created over the last two decades using programmes that are becoming incompatible with continuing advances in the field of information technology.

The release explains the four parts of the standard that have been published, and how to find them.

The ISO catalogue entry for IS29500 explains that the documents can be downloaded for free from the ITTF. Here are the links for parts 1, 2, 3 & 4.

He posts frequently, and sometime over the last week has been kind enough to compile a table of contents for his recent work. The entire ToC is here, I’ve pulled out his Open XML focused posts below.

Open XML

Open XML SDK and LINQ to XML

Transforming Open XML Documents using XSLT

Transforming Open XML Documents to Flat OPC Format

Transforming Flat OPC Format to Open XML Documents

The Flat OPC Format

Creating Data-Bound Content Controls using the Open XML SDK and LINQ to XML

Create a List of All Parts in an Open XML Document

OpenXmlCodeTester: Validating Code in Open XML Documents

Using LINQ to XML to Retrieve Content Controls in Word 2007

Remove Comments

Remove Personal Information

Accept Revisions

Automated Processing of Open XML Documents using PowerShell

Extract Comments

OpenXML Content Types in an XML Document

Bulk Convert DOC to DOCX

The Legacy Hashing Algorithm in Open XML

Automated Processing of Open XML Documents using PowerShell

NORWEGIAN MEMBERS of the Technical Committee of that country’s International Standards Organisation (ISO) body Standard Norge have resigned their posts to protest the approval of Microsoft’s OOXML document formats proposal in defiance of the majority recommendation.

In all, 13 of the committee’s 23 members have resigned, a majority of the membership.

On the face of it this is pretty dramatic stuff.

Rick Jelliffe spent a little time trying to work out what had happened and who these thirteen committee members were.

His conclusion;

So if we take these 13, and subtract people who either work for competitors of Microsoft or affiliated with the NUUG/FOSS industry/community, we get…1 person (the esteemed Steve Pepper) by my count.

Of course, affiliation does not mean bought or rote votes: I am the last person to think that, except perhaps for people without technical competence. ODF’s Patrick Durusau, for example, is paid by Sun but his value is largely that he is independent and knowledgeable. And even parrots have value, if they fairly advocate their stakeholder’s view. (Of course, most people like to consider themselves mavericks, even when violently agreeing with each other and the conventional wisdom of their peers.)

But all that being said, I tend to think that a walkout by [people who see themselves as commercial and non-commercial] competitors may generate more scepticism, fairly or unfairly, than, say, a walk-out by prospective users.

The whole post is worth a read, as are the comments.

One in particular from Fredrik E. Nilsen sheds some light on what might really be going on;

12 of the 13 members who walked out (all except Steve Pepper) joined Standard Norge K/185 when the OOXML-process started.

Lars Marius Garshol is a long time member of SN K/185 and has commented the situation at Arstechnica:

“What’s happened here is that lots of people joined the committee to oppose the standard, and while in the committee that’s all they’ve done. Now that OOXML has been approved, they no longer have any reason to be in the committee, so they are leaving. That’s hardly the committee imploding.

It is actually a great shame. Many minds came together to work on the process to standardize OpenXML bringing a wide array of relevant expert opinions. In many cases there was disagreement, but I have always held the view that there was a lot to be gained from the debate.

The workshop will be held on the Microsoft Redmond Campus on the 24th and 25th October. I managed to attend the last one, which covered ODF and Office SP2, and it was a great opportunity to talk directly with the product groups about what they’re doing in this area.

Doug talks a about why we’re doing this and how to sign up if you are interested, as with the last DII workshop it is open to anybody who wants to attend.

We heard from some of the attendees of the July workshop that they’d like to see a similar event around Open XML interop, and that’s why we’re doing this event. It will be in Redmond again because that’s the only way we can realistically get multiple Office PMs involved, and attendees of the July event found the direct interaction with our technical experts to be very useful. This workshop is not restricted to Open XML interop (and certainly not just to our own implementation of Open XML), however, so any other document interop topics can be added to the agenda, time permitting.

Like the last workshop, this is a free event that is part of the Document Interoperability Initiative, and the goal is to share information with the developer community and solicit feedback on how we can work together to improve interoperability. To register for the event, send me your name, email, and company/organization via this contact form, and we’ll follow up with more details including hotel recommendations and related information.

He also mentions that the date is the Thursday and Friday before PDC in LA, which will make it easier for PDC attendees to join this session.

Some of the new features include;

The OpenXmlDiff utility identifies differences in the markup in two Open XML documents.

The Open XML Class Explorer helps you determine which strongly typed class to use for a specific task, and includes the text of the relevant section of the ECMA-376 spec for each class.

The Open XML Document Reflector takes a target document as input, and with a few clicks it shows you the C# code needed to generate that document (or a section of it) with the Open XML SDK. This tool will be a huge time-saver for those who need to write code to generate documents to match a template defined by others.