See main article: Office Open XML.
| Office Open XML Document | |
| Extension: | .docx, .docm |
| Mime: | application/vnd. openxmlformats-officedocument. wordprocessingml. document[1] |
| Owner: | Microsoft, Ecma, ISO/IEC |
| Genre: | Document file format |
| Extended From: | XML, DOC, WordProcessingML |
| Standard: | ECMA-376, ISO/IEC 29500 |
| Url: | ECMA-376, ISO/IEC 29500:2008 |
| Office Open XML Presentation | |
| Extension: | .pptx, .pptm |
| Mime: | application/vnd. openxmlformats-officedocument. presentationml. presentation[2] |
| Owner: | Microsoft, Ecma, ISO/IEC |
| Genre: | Presentation |
| Extended From: | XML, PPT |
| Standard: | ECMA-376, ISO/IEC 29500 |
| Url: | ECMA-376, ISO/IEC 29500:2008 |
| Office Open XML Workbook | |
| Extension: | .xlsx, .xlsm |
| Mime: | application/vnd. openxmlformats-officedocument. spreadsheetml. sheet[3] |
| Owner: | Microsoft, Ecma, ISO/IEC |
| Genre: | Spreadsheet |
| Extended From: | XML, XLS, SpreadsheetML |
| Standard: | ECMA-376, ISO/IEC 29500 |
| Url: | ECMA-376, ISO/IEC 29500:2008 |
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 formulas, 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.
See main article: Open Packaging Conventions.
Office Open XML documents are stored in Open Packaging Conventions (OPC) packages, which are ZIP files containing XML and other data files, along with a specification of the relationships between them.[4] 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.
An example relationship file (word/_rels/document.xml.rels), is:
As such, images referenced in the document can be found in the relationship file by looking for all relationships that are of type <nowiki>http://schemas.microsoft.com/office/2006/relationships/image</nowiki>. To change the used image, edit the relationship.
The following code shows an example of inline markup for a hyperlink:
In this example, the Uniform Resource Locator (URL) is in the Target attribute of the Relationship referenced through the relationship Id, "rId2" in this case. Linked images, templates, and other items are referenced in the same way.
Pictures can be embedded or linked using a tag:
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.
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:
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:
Shared markup language materials include:
In addition to the above markup languages custom XML schemas can be used to extend Office Open XML.
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:
In contrast, he notes ODF would use the single attribute fo:keep-next, rather than an element, for the same semantic.[5]
The XML Schema of Office Open XML emphasizes reducing load time and improving parsing speed.[6] In a test with applications current in April 2007, XML-based office documents were slower to load than binary formats.[7] To enhance performance, Office Open XML uses very short element names for common elements and spreadsheets save dates as index numbers (starting from 1900 or from 1904).[8] 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 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 has 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".[9]
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".[10]
The version of the standard submitted to JTC 1 was 6546 pages long. The need and appropriateness of such length has been questioned.[11] [12] Google stated that "the ODF standard, which achieves the same goal, is only 867 pages"[11]
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.[13]
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.[13]
Each worksheet in a spreadsheet is represented by an XML document with a root element named in the