No more shall the SDK for OpenXML be confused with the Word 2007 Content Control Toolkit.

The strong word “Part” used throughout the OpenXML API, starting with the abstraction OpenXmlPart, represents a location in the ZIP OpenXmlPackage. In the same manner that an XML document contains nodes (or a database store contains tables), an OpenXML Package contains parts. The OpenXmlPart, as of today, does not define anything (useful to me) inside of an XML file.

The SDK for OpenXML APIs do not define anything of significance inside of an XML file. This is most important piece of information I need about this SDK. It follows that the OpenXmlPart.GetStream() and OpenXmlPart.FeedData() methods are the most important members of the entire SDK for OpenXML. So, for example, silly me would be looking for a class called “DocumentPart” or (“GlossaryDocumentEntry”) in the OpenXML API which would correspond to the <w:docPart> element. As of today these types to do exist.

For more details on this rant, see:

http://kintespace.com/rasxlog/?p=923

With the announcement of an OpenXML roadmap comes a “Content object model including additional classes and methods for simplifying developer work within parts (example: methods for retrieving or modifying a specific paragraph, style, cell, or shape within a part)…”

[http://openxmldeveloper.org/archive/2008/03/13/OpenXMLSDK.aspx]

“You need to remember following keywords as these are used more often in the world: Package, Parts, Relations…”

[http://www.codeproject.com/KB/office/OpenXML_Very_Basics.aspx]