# Office Open XML file formats

<tr class=""><th style="text-align:left; ">Internet media type</th>
   <td class="" style="">application/vnd.openxmlformats-officedocument.wordprocessingml.document[1]</td></tr><tr class=""><th style="text-align:left; ">Developed by</th>
<td class="" style="">Microsoft, Ecma, ISO/IEC</td></tr><tr class=""><th style="text-align:left; ">Type of format</th>
<td class="" style="">Document file format</td></tr><tr class=""><th style="text-align:left; ">Extended from</th>
<td class="" style="">XML, DOC, WordProcessingML</td></tr><tr class=""><th style="text-align:left; ">Standard(s)</th>
<td class="" style="">ECMA-376, ISO/IEC 29500</td></tr><tr class=""><th style="text-align:left; ">Website</th>
<td class="" style="">ECMA-376, ISO/IEC 29500:2008</td></tr>


</table>

Filename extension File:X-office-document.svg .docx or .docm
<tr class=""><th style="text-align:left; ">Internet media type</th>
   <td class="" style="">application/vnd.openxmlformats-officedocument.presentationml.presentation[1]</td></tr><tr class=""><th style="text-align:left; ">Developed by</th>
<td class="" style="">Microsoft, Ecma, ISO/IEC</td></tr><tr class=""><th style="text-align:left; ">Type of format</th>
<td class="" style="">Presentation</td></tr><tr class=""><th style="text-align:left; ">Extended from</th>
<td class="" style="">XML, PPT</td></tr><tr class=""><th style="text-align:left; ">Standard(s)</th>
<td class="" style="">ECMA-376, ISO/IEC 29500</td></tr><tr class=""><th style="text-align:left; ">Website</th>
<td class="" style="">ECMA-376, ISO/IEC 29500:2008</td></tr>


</table>

Filename extension File:X-office-presentation.svg .pptx or .pptm
<tr class=""><th style="text-align:left; ">Internet media type</th>
   <td class="" style="">application/vnd.openxmlformats-officedocument.spreadsheetml.sheet[1]</td></tr><tr class=""><th style="text-align:left; ">Developed by</th>
<td class="" style="">Microsoft, Ecma, ISO/IEC</td></tr><tr class=""><th style="text-align:left; ">Type of format</th>
<td class="" style="">Spreadsheet</td></tr><tr class=""><th style="text-align:left; ">Extended from</th>
<td class="" style="">XML, XLS, SpreadsheetML</td></tr><tr class=""><th style="text-align:left; ">Standard(s)</th>
<td class="" style="">ECMA-376, ISO/IEC 29500</td></tr><tr class=""><th style="text-align:left; ">Website</th>
<td class="" style="">ECMA-376, ISO/IEC 29500:2008</td></tr>


</table>

The Office Open XML file formats are a set of file formats that can be used to represent electronic office documents. There are formats for word processing documents, spreadsheets and presentations as well as specific formats for material such as mathematical formulae, graphics, bibliographies etc.

The formats were developed by Microsoft and first appeared in Microsoft Office 2007. They were standardized between December 2006 and November 2008, first by the Ecma International consortium, where they became ECMA-376, and subsequently, after a contentious standardization process, by the ISO/IEC's Joint Technical Committee 1, where they became ISO/IEC 29500:2008.

Filename extension File:X-office-spreadsheet.svg .xlsx or .xlsm

## Container

File:Open Packaging Convention.png
Container structure of Part 2 of the Ecma Office Open XML standard, ECMA-376

Office Open XML documents are stored in Open Packaging Convention (OPC) packages, which are ZIP files containing XML and other data files, along with a specification of the relationships between them.[2] Depending on the type of the document, the packages have different internal directory structures and names. An application will use the relationships files to locate individual sections (files), with each having accompanying metadata, in particular MIME metadata.

A basic package contains an XML file called [Content_Types].xml at the root, along with three directories: _rels, docProps, and a directory specific for the document type (for example, in a .docx word processing package, there would be a word directory). The word directory contains the document.xml file which is the core content of the document.

[Content_Types].xml
This file provided MIME type information for parts of the package, using defaults for certain file extensions and overrides for parts specificied by IRI.
_rels
This directory contains relationships for the files within the package. To find the relationships for a specific file, look for the _rels directory that is a sibling of the file, and then for a file that has the original file name with a .rels appended to it. For example, if the content types file had any relationships, there would be a file called [Content_Types].xml.rels inside the _rels directory.
_rels/.rel
This file is where the package relationships are located. Applications look here first. Viewing in a text editor, one will see it outlines each relationship for that section. In a minimal document containing only the basic document.xml file, the relationships detailed are metadata and document.xml.
docProps/core.xml
This file contains the core properties for any Office Open XML document.
word/document.xml
This file is the main part for any Word document.

### Relationships

An example relationship file (word/_rels/document.xml.rels), is:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<Relationships
xmlns="http://schemas.microsoft.com/package/2005/06/relationships">
<Relationship Id="rId1"
Type="http://schemas.microsoft.com/office/2006/relationships/image"
Target="http://en.wikipedia.org/images/wiki-en.png"
TargetMode="External" />
<Relationship Id="rId2"
Target="http://www.wikipedia.org"
TargetMode="External" />
</Relationships>

As such, images referenced in the document can be found in the relationship file by looking for all relationships that are of type http://schemas.microsoft.com/office/2006/relationships/image. To change the used image, edit the relationship.

The following code shows an example of inline markup for a hyperlink:

<w:hyperlink r:id="rId2" w:history="1"
xmlns:r="http://schemas.openxmlformats.org/officeDocument/2006/relationships"
xmlns:w="http://schemas.openxmlformats.org/wordprocessingml/2006/main">

In this example, the Uniform Resource Locator (URL) is represented by "rId2". The actual URL is in the accompanying relationships file, located by the corresponding "rId2" item. Linked images, templates, and other items are referenced in the same way.

Pictures can be embedded or linked using a tag:

 <v:imagedata w:rel="rId1" o:title="example" />

This is the reference to the image file. All references are managed via relationships. For example, a document.xml has a relationship to the image. There is a _rels directory in the same directory as document.xml, inside _rels is a file called document.xml.rels. In this file there will be a relationship definition that contains type, ID and location. The ID is the referenced ID used in the XML document. The type will be a reference schema definition for the media type and the location will be an internal location within the ZIP package or an external location defined with a URL.

### Document properties

Office Open XML uses the Dublin Core Metadata Element Set and DCMI Metadata Terms to store document properties. Dublin Core is a standard for cross-domain information resource description and is defined in ISO 15836:2003.

An example document properties file (docProps/core.xml) that uses Dublin Core metadata, is:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<dc:title>Office Open XML</dc:title>
<dc:subject>File format and structure</dc:subject>
<dc:creator>Wikipedia</dc:creator>
<cp:keywords>Office Open XML, Metadata, Dublin Core</cp:keywords>
<dc:description>Office Open XML uses ISO 15836:2003</dc:description>
<cp:lastModifiedBy>Wikipedia</cp:lastModifiedBy>
<cp:revision>1</cp:revision>
<dcterms:created xsi:type="dcterms:W3CDTF">2008-06-19T20:00:00Z</dcterms:created>
<dcterms:modified xsi:type="dcterms:W3CDTF">2008-06-19T20:42:00Z</dcterms:modified>
<cp:category>Document file format</cp:category>
<cp:contentStatus>Final</cp:contentStatus>
</cp:coreProperties>

## Document markup languages

An Office Open XML file may contain several documents encoded in specialized markup languages corresponding to applications within the Microsoft Office product line. Office Open XML defines multiple vocabularies using 27 namespaces and 89 schema modules.

The primary markup languages are:

• WordprocessingML for word-processing
• PresentationML for presentations

Shared markup language materials include:

• Office Math Markup Language (OMML)
• DrawingML used for vector drawing, charts, and for example, text art (additionally, though deprecated, VML is supported for drawing)
• Extended properties
• Custom properties
• Variant Types
• Custom XML data properties
• Bibliography

In addition to the above markup languages custom XML schemas can be used to extend Office Open XML.

### Design approach

Patrick Durusau, the editor of ODF, has viewed the markup style of OOXML and ODF as representing two sides of a debate: the "element side" and the "attribute side". He notes that OOXML represents "the element side of this approach" and singles out the KeepNext element as an example:

<w:pPr>
<w:keepNext/>
…
</w:pPr>

In contrast, he notes ODF would use the single attribute fo:keep-next, rather than an element, for the same semantic.[3]

The XML Schema of Office Open XML emphasizes reducing load time and improving parsing speed.[4] In a test with applications current in April 2007, XML-based office documents were slower to load than binary formats.[5] To enhance performance, Office Open XML uses very short element names for common elements and spreadsheets save dates as index numbers (starting from 1899 or from 1904).[citation needed] In order to be systematic and generic, Office Open XML typically uses separate child elements for data and metadata (element names ending in Pr for properties) rather than using multiple attributes, which allows structured properties. Office Open XML does not use mixed content but uses elements to put a series of text runs (element name r) into paragraphs (element name p). The result is terse[citation needed] and highly nested in contrast to HTML, for example, which is fairly flat, designed for humans to write in text editors and is more congenial for humans to read.

The naming of elements and attributes within the text have attracted some criticism. There are three different syntaxes in OOXML (ECMA-376) for specifying the color and alignment of text depending on whether the document is a text, spreadsheet, or presentation. Rob Weir (an IBM employee and co-chair of the OASIS OpenDocument Format TC) asks "What is the engineering justification for this horror?". He contrasts with OpenDocument: "ODF uses the W3C's XSL-FO vocabulary for text styling, and uses this vocabulary consistently".[6]

Some have argued the design is based too closely on Microsoft applications. In August 2007, the Linux Foundation published a blog post calling upon ISO National Bodies to vote "No, with comments" during the International Standardization of OOXML. It said, "OOXML is a direct port of a single vendor's binary document formats. It avoids the re-use of relevant existing international standards (e.g. several cryptographic algorithms, VML, etc.). There are literally hundreds of technical flaws that should be addressed before standardizing OOXML including continued use of binary code tied to platform specific features, propagating bugs in MS-Office into the standard, proprietary units, references to proprietary/confidential tags, unclear IP and patent rights, and much more".[7]

The version of the standard submitted to JTC 1 was 6546 pages long. The need and appropriateness of such length has been questioned.[8][9] Google stated that "the ODF standard, which achieves the same goal, is only 867 pages"[8]

### WordprocessingML (WML)

Word processing documents use the XML vocabulary known as WordprocessingML normatively defined by the schema wml.xsd which accompanies the standard. This vocabulary is defined in clause 11 of Part 1.[10]

Spreadsheet documents use the XML vocabulary known as SpreadsheetML normatively defined by the schema sml.xsd which accompanies the standard. This vocabulary is described in clause 12 of Part 1.[10]

Each worksheet in a spreadsheet is represented by an XML document with a root element named <worksheet> in the http://schemas.openxmlformats.org/spreadsheetml/2006/main Namespace.

The representation of date and time values in SpreadsheetML has attracted some criticism. ECMA-376 1st edition does not conform to ISO 8601:2004 "Representation of Dates and Times". It requires that implementations replicate a Lotus 1-2-3 [11] bug that dictates that 1900 is a leap year, which in fact it isn't. Products complying with ECMA-376 would be required to use the WEEKDAY() spreadsheet function, and therefore assign incorrect dates to some days of the week, and also miscalculate the number of days between certain dates.[12] ECMA-376 2nd edition (ISO/IEC 29500) allows the use of 8601:2004 "Representation of Dates and Times" in addition to the Lotus 1-2-3 bug-compatible form.[13][14]

### PresentationML (PML)

Presentation (slide show) documents use the XML vocabulary known as PresentationML normatively defined by the schema pml.xsd which accompanies the standard. This vocabulary is defined in clause 13.[10]

### Office MathML (OMML)

Office Math Markup Language is a mathematical markup language which can be embedded in WordprocessingML, with intrinsic support for including word processing markup like revision markings,[15] footnotes, comments, images and elaborate formatting and styles.[16] The OMML format is different from the World Wide Web Consortium (W3C) MathML recommendation that does not support those office features, but is partially compatible[17] through XSL Transformations.

The following Office MathML example defines the fraction: $\frac{\pi}{2}$

<m:oMathPara><!-- mathematical block container used as a paragraph -->
<m:oMath><!-- mathematical inline formula -->
<m:f><!-- a fraction -->
<m:num><m:r><m:t>π</m:t></m:r></m:num><!-- numerator containing a single run of text -->
<m:den><m:r><m:t>2</m:t></m:r></m:den><!-- denominator containing a single run of text -->
</m:f>
</m:oMath>
</m:oMathPara>

Some have queried the need for Office MathML (OMML) instead advocating the use of MathML, a W3C recommendation for the "inclusion of mathematical expressions in Web pages" and "machine to machine communication".[18]

### DrawingML

File:DrawingML example.png
Example of DrawingML charts

DrawingML is the vector graphics markup language used in Office Open XML documents. Its major features are the graphics rendering of text elements, graphical vector-based shape elements, graphical tables and charts.

The DrawingML table is the third table model in Office Open XML (next to the table models in WordprocessingML and SpreadsheetML) and is optimized for graphical effects and its main use is in presentations created with PresentationML markup. DrawingML contains graphics effects (like shadows and reflection) that can be used on the different graphical elements that are used in DrawingML. In DrawingML you can also create 3d effects, for instance to show the different graphical elements through a flexible camera viewpoint. It is possible to create separate DrawingML theme parts in an Office Open XML package. These themes can then be applied to graphical elements throughout the Office Open XML package.[19]

DrawingML is unrelated to the other vector graphics formats such as SVG. These can be converted to DrawingML to include natively in an Office Open XML document. This is a different approach to that of the OpenDocument format, which uses a subset of SVG, and includes vector graphics as separate files.

A DrawingML graphic's dimensions are specified in English Metric Units (EMUs). It is so called because it allows an exact common representation of dimensions originally in either English or Metric units. This unit is defined as 1/360,000 of a centimeter and thus there are 914,400 EMUs per inch, and 12,700 EMUs per point. This unit was chosen so that integers can be used to accurately represent most dimensions encountered in a document. Floating point cannot accurately represent a fraction that is not a sum of powers of two and the error is magnified when the fractions are added together many times, resulting in misalignment. As an inch is exactly 2.54 centimeters, or 127/50, 1/127 inch is an integer multiple of a power-of-ten fraction of the meter (2×10−4 m). To accurately represent (with an integer) 1 μm = 10−6 m, a divisor of 100 is further needed. To accurately represent the point unit, a divisor of 72 is needed, which also allows divisions by 2, 3, 4, 6, 8, 9, 12, 18, 24, and 36 to be accurate. Multiplying these together gives 127×72×100 = 914,400 units per inch; this also allows exact representations of multiples of 1/100 & 1/32 inch. According to Rick Jelliffe, programmer and standards activist (ISO, W3C, IETF), EMUs are a rational solution to a particular set of design criteria.[20]

Some have criticised the use of DrawingML (and the transitional-use-only VML) instead of W3C recommendation SVG.[21] VML did not become a W3C recommendation.[22]

## Foreign resources

### Non-XML content

OOXML documents are typically composed of other resources in addition to XML content (graphics, video, etc.).

Some have criticised the choice of permitted format for such resources: ECMA-376 1st edition specifies "Embedded Object Alternate Image Requests Types" and "Clipboard Format Types", which refer to Windows Metafiles or Enhanced Metafiles – each of which are proprietary formats that have hard-coded dependencies on Windows itself. The critics state the standard should instead have referenced the platform neutral standard ISO/IEC 8632 "Computer Graphics Metafile".[12]

### Foreign markup

The Standard provides three mechanisms to allow foreign markup to be embedded within content for editing purposes:

• Smart tags
• Custom XML markup
• Structured Document Tags

These are defined in clause 17.5 of Part 1.

## Compatibility settings

Versions of Office Open XML contain what are termed "compatibility settings". These are contained in Part 4 ("Markup Language Reference") of ECMA-376 1st Edition, but during standardization were moved to become a new part (also called Part 4) of ISO/IEC 29500:2008 ("Transitional Migration Features").

These settings (including element with names such as autoSpaceLikeWord95, footnoteLayoutLikeWW8, lineWrapLikeWord6, mwSmallCaps, shapeLayoutLikeWW8, suppressTopSpacingWP, truncateFontHeightsLikeWP6, uiCompat97To2003, useWord2002TableStyleRules, useWord97LineBreakRules, wpJustification and wpSpaceWidth) were the focus of some controversy during the standardisation of DIS 29500.[23] As a result, new text was added to ISO/IEC 29500 to document them.[24]

An article in Free Software Magazine has criticized the markup used for these settings. Office Open XML uses distinctly named elements for each compatibility setting, each of which is declared in the schema. The repertoire of settings is thus limited — for new compatibility settings to be added, new elements may need to be declared, "potentially creating thousands of them, each having nothing to do with interoperability".[25]

## Extensibility

The standard provides two types of extensibility mechanism, Markup Compatibility and Extensibility (MCE) defined in Part 3 (ISO/IEC 29500-3:2008) and Extension Lists defined in clause 18.2.10 of Part 1.

## References

1. 1.0 1.1 1.2 Microsoft. "Register file extensions on third party servers". microsoft.com. Retrieved 2009-09-04.
2. Tom Ngo (December 11, 2006). "Office Open XML Overview" (PDF). Ecma International. p. 6. Retrieved 2007-01-23.
3. Patrick Durusau (21 October 2008). "Old Wine In New Skins".
4.
5. George Ou (2007-04-27). "MS Office 2007 versus Open Office 2.2 shootout". ZDnet.com. Retrieved 2007-04-27.
6. Rob Weir (14 March 2008). "Disharmony of OOXML".
7. John Cherry (14 March 2008). "OOXML — vote "No, with comments"".
8. 8.0 8.1 "Google's Position on OOXML as a Proposed ISO Standard". Google. 2008-02. "If ISO were to give OOXML with its 6546 pages the same level of review that other standards have seen, it would take 18 years (6576 days for 6546 pages) to achieve comparable levels of review to the existing ODF standard (871 days for 867 pages) which achieves the same purpose and is thus a good comparison. Considering that OOXML has only received about 5.5% of the review that comparable standards have undergone, reports about inconsistencies, contradictions and missing information are hardly surprising"
9.
10. 10.0 10.1 10.2
11. Kyd, Charley (October 2006). "How to Work With Dates Before 1900 in Excel". ExcelUser. Retrieved 2009-09-16.
12. 12.0 12.1
13. "ECMA-376 2nd edition Part 1 (3. Normative references)". Ecma-international.org. Retrieved 2009-09-16.
14.
15. Jesper Lund Stocholm (2008-01-29). "Do your math — OOXML and OMML". A Mooh Point blog. Retrieved 2008-02-12.
16. Murray Sargent (2007-06-05). "Science and Nature have difficulties with Word 2007 mathematics". MSDN blogs. Retrieved 2007-07-31.
17. David Carlisle (2007-05-09). "XHTML and MathML from Office 2007". David Carlisle. Retrieved 2007-09-20.
18.
19. Wouter Van Vugt (2008-11-01). "Open XML Explained e-book". Openxmldeveloper.org. Retrieved 2007-09-14.
20. Monday April 16, 2007 5:24AM by Rick Jelliffe in Technical (2007-04-16). "Why EMUs? - O'Reilly XML Blog". Oreillynet.com. Retrieved 2009-05-19.
21. "The X Factor". reddevnews.com. October 2007.
22. "VML — the Vector Markup Language". W3.org. 1998-05-13. Retrieved 2009-05-19.
23.
24. "ECMA-376 2nd edition Part 4 (paragraph 9.7.3)". Ecma-international.org. Retrieved 2009-09-16.
25. "ODF/OOXML technical white paper — A white paper based on a technical comparison between the ODF and OOXML formats". Free Software Magazine. ""... OOXML chose this route. Rather than create an application-definable configuration tag there is a unique tag for each setting ... Currently, the only application's unique settings that are catered for are the applications that the standard's authors have decided to include, ... For other applications to be added, further tag names would need to be defined in the specification, potentially creating thousands of them, each having nothing to do with interoperability .."."