Office Open XML: Difference between revisions

Browse history interactively ← Previous editContent deleted Content addedVisual WikitextInline

Revision as of 18:56, 16 August 2007 edit69.73.191.92 (talk) →EU definition of an Open Standard: Reverted back to hAls version as it is supported by the open standard article already on wikipedia.← Previous edit		Latest revision as of 11:23, 28 December 2024 edit undoSerethSurkow (talk \| contribs)2 editsm Archive.org link added
Line 1:		Line 1:
			{{Short description\|Family of document file formats}}
	{{POV}}
	{{~~self-published~~}}		{{Redirect\|docx}}
			{{Distinguish\|OpenDocument\|Open Office XML\|Microsoft Office XML formats}}
			{{stack\|
			{{Office Open XML}}
			{{Infobox file format
			\| name = Office Open XML Document
			\| icon = .docx icon.svg
			\| iconcaption = The OOXML Document icon, as appears on the ] web service
			\| screenshot =
			\| caption =
			\| extension = .docx, .docm
			\| mime = application/vnd.<br />openxmlformats-officedocument.<br />wordprocessingml.<br />document<ref name="mimetype">{{cite web \| url = https://www.iana.org/assignments/media-types/application/vnd.openxmlformats-officedocument.wordprocessingml.document \| title = application/vnd.openxmlformats-officedocument.wordprocessingml.document \| publisher = ] \| access-date = 2024-11-03 \| date=2011-02-25 \| website = www.iana.org }}</ref>
			\| type code =
			\| uniform type =
			\| magic =
			\| owner = ], ], ], ]
			\| released = {{Start date and age\|2006\|12\|07\|df=yes}}
			\| latest release version = 4th edition
			\| latest release date = {{Start date and age\|2016\|10\|26\|df=yes}}
			\| genre = ]
			\| container for =
			\| contained by =
			\| extended from = ], ], ]
			\| extended to =
			\| standard = ECMA-376, ISO/IEC 29500
			\| url = ,
			\| open = Yes<ref name="ExckertEtZiesing2009">{{cite web
			\| url=http://regmedia.co.uk/2009/08/20/fokus_odf_ooxml_report.pdf
			\| title=Document Interoperability: Open Document Format and Office Open XML
			\|author1=Klaus-Peter Eckert \|author2=Jan Henrik Ziesing \|author3=Ucheoma Ishionwu \| page=90
			\| publisher=Fraunhofer Verlag}}</ref>
			}}
			{{Infobox file format
			\| name = Office Open XML Presentation
			\| icon = .pptx icon.svg
			\| logo =
			\| screenshot =
			\| caption =
			\| extension = .pptx, .pptm
			\| mime = application/vnd.<br />openxmlformats-officedocument.<br />presentationml.<br />presentation <ref> {{cite web \| url = https://www.iana.org/assignments/media-types/application/vnd.openxmlformats-officedocument.presentationml.presentation \| title = application/vnd.openxmlformats-officedocument.presentationml.presentation \| publisher = ] \| access-date = 2024-11-03 \| date=2011-03-14 \| website = www.iana.org }} </ref>
			\| type code =
			\| uniform type =
			\| magic =
			\| owner = ], ], ], ]
			\| released = {{Start date and age\|2006\|12\|07\|df=yes}}
			\| latest release version = 3rd edition
			\| latest release date = {{Start date and age\|2011\|06\|29\|df=yes}}
			\| genre = ]
			\| container for =
			\| contained by =
			\| extended from = ], ]
			\| extended to =
			\| standard = ECMA-376, ISO/IEC 29500
			\| url = ,
			\| open = Yes
			}}
			{{Infobox file format
			\| name = Office Open XML Workbook
			\| icon = .xlsx icon.svg
			\| logo =
			\| screenshot =
			\| caption =
			\| extension = .xlsx, .xlsm
			\| mime = application/vnd.<br />openxmlformats-officedocument.<br />spreadsheetml.<br />sheet<ref> {{cite web \| url = https://www.iana.org/assignments/media-types/vnd.openxmlformats-officedocument.spreadsheetml.sheet \| title = vnd.openxmlformats-officedocument.spreadsheetml.sheet \| publisher = ] \| access-date = 2024-11-03 \| date=2011-03-16 \| website = www.iana.org }} </ref>
			\| type code =
			\| uniform type =
			\| magic =
			\| owner = ], ], ], ]
			\| released = {{Start date and age\|2006\|12\|07\|df=yes}} (as Microsoft Open XML)
			\| latest release version = 3rd edition
			\| latest release date = {{Start date and age\|2011\|06\|29\|df=yes}}
			\| genre = ]
			\| container for =
			\| contained by =
			\| extended from = ], ], ]
			\| extended to =
			\| standard = ECMA-376, ISO/IEC 29500
			\| url = ,
			\| open = Yes
			}}
			}}

			'''Office Open XML''' (also informally known as '''OOXML''')<ref>{{cite web\|url=https://wiki.documentfoundation.org/LibreOffice_OOXML\|title=The Document Foundation, LibreOffice and OOXML\|access-date=2016-03-22\|publisher=]}}</ref> is a ], ]-based ] developed by ] for representing ]s, ]s, ]s and ] documents. ] standardized the initial version as ECMA-376. ] and ] standardized later versions as ISO/IEC 29500.
	{{distinguish2\|] (an unrelated ])}}

			] provides read support for ECMA-376, full support for ISO/IEC 29500 Transitional, and read support for ISO/IEC 29500 Strict.<ref>{{Cite web \|url=https://learn.microsoft.com/en-us/previous-versions/office/office-2010/cc179190(v=office.14) \|title=Overview of the XML file formats in Office 2010 \|website=Office 2010 Resource Kit \|publisher=Microsoft \|date=5 August 2011}}</ref> ] and later fully support ISO/IEC 29500 Strict,<ref name="Office 2013 File Formats">{{cite web \|url=https://learn.microsoft.com/en-us/previous-versions/office/office-2013-resource-kit/cc179191(v=office.15) \|title=XML file name extension reference for Office 2013 \|website=Office 2013 Resource Kit \|publisher=Microsoft \|date=26 December 2016 }}</ref> but do not use it as the default file format because of backwards compatibility concerns.<ref name="Office 2016 file formats">{{cite web\|url=https://www.loc.gov/preservation/digital/formats/fdd/fdd000401.shtml\|title=XLSX Strict (Office Open XML), ISO 29500-1:2008-2016\|website=]\|access-date=2018-09-09}}</ref>
	'''Office Open XML''' (commonly referred to as '''OOXML''' or '''Open XML''') is an ]-based file format specification for electronic documents such as memos, reports, books, ]s, ]s, ]s and ] documents. The specification was originally developed by ] as a successor of its binary office file formats and was published by ] as the '''Ecma 376''' standard in December 2006.<ref name="pr_tc45_dec2006">{{cite press release
	\| url=http://www.ecma-international.org/news/PressReleases/PR_TC45_Dec2006.htm
	\| title=Ecma International approves Office Open XML standard
	\| date=] ]
	\| accessdate=2006-12-08
	\| publisher=]
	}}</ref> The is available for free at Ecma International.

	Office Open XML uses a number of dedicated XML ] in fileparts that are placed in an ] file container. The format specification includes ]s that can be used to validate the XML syntax.

	The format is currently undergoing a ] process within the ].

	==Background==		==Background==

			In 2000, Microsoft released an initial version of an ]-based format for Microsoft Excel, which was incorporated in Office XP. In 2002, a new file format for Microsoft Word followed.<ref name="ooxmlhistory">{{cite web\|author=Brian Jones\|date=2007-01-25\|title=History of office XML formats (1998–2006)\|url=https://docs.microsoft.com/en-us/archive/blogs/brian_jones/history-of-office-xml-formats-1998-2006\|archive-url=\|archive-date=\|access-date=2020-12-31\|website=\|publisher=MSDN blogs}}</ref> The Excel and Word formats—known as the ]—were later incorporated into the 2003 release of Microsoft Office.
	] has long been using ] formats for electronic office documents. These formats are the most used file formats for Office documents due to the dominant market position of Microsoft Office. Microsoft used to limit licensing to these file formats only for governments and noncommercial use. Currently Microsoft offers the binary format specifications to everyone under a royalty free ] not to sue <ref>{{cite web
	\| url=http://support.microsoft.com/kb/840817/en-us#
	\| title=How to extract information from Office files by using Office file formats and schemas
	\| publisher=Microsoft
	\| date=2007-03-27
	\| accessdate=2007-07-10 }} </ref>. Because of this the formats were fairly difficult to interpret by other commercial or free software developers and never fully interoperable although a very good level of support was achieved.
	In 2002 Microsoft released a file format for ] that was based on ] instead, WordProcessingML, <ref> {{Cite web
	\| url=http://blogs.msdn.com/brian_jones/archive/2007/01/25/office-xml-formats-1998-2006.aspx
	\| title=History of office XML formats (1998-2006)
	\| author=Brian Jones
	\| Publisher=MSDN blogs
	\| date=2007-01-25 }} </ref> and in 2003 it released the full ] and made them available under royalty-free licensing.

			Microsoft announced in November 2005 that it would co-sponsor standardization of the new version of their XML-based formats through ] as "Office Open XML".<ref>{{cite web \| url = https://news.microsoft.com/2005/11/21/qa-microsoft-co-sponsors-submission-of-office-open-xml-document-formats-to-ecma-international-for-standardization/ \| title = Microsoft Co-Sponsors Submission of Office Open XML Document Formats to Ecma International for Standardization \| publisher = Microsoft \| date = 2005-11-21}}</ref><ref></ref> The presentation was made to Ecma by Microsoft's ] and Isabelle Valet-Harper.<ref></ref><ref>{{Cite web \|url=http://www.ecma-international.org/activities/Office%20Open%20XML%20Formats/TC45_GA_Dez05.pdf/ \|title=Slides presented by the TC45 committee to Ecma International \|access-date=2011-06-08 \|archive-url=https://web.archive.org/web/20111021022009/http://www.ecma-international.org/activities/Office%20Open%20XML%20Formats/TC45_GA_Dez05.pdf/ \|archive-date=2011-10-21 \|url-status=dead }}</ref>
	The 2003 formats did not use a package file format but still used a single file format with embedded items like pictures as binary encoded within the XML. A new version of WordprocessingML is used in Office Open XML.

			==Standardization process==
	In 2004 governments and mainly the European Union recommended both ] and Microsoft to standardize their XML office file formats through an official Standardisations organization. <ref> {{cite web
			{{Main\|Standardization of Office Open XML}}
	\| url=http://ec.europa.eu/idabc/en/document/2592/5588
	\| title=TAC approval on conclusions and recommendations on open document formats
	\| author=Telematics between Administrations Committee based on IDA expert group on open document formats
	\| publisher=IDABC - European eGovernment Services
	\| date=2004-05-25
	\| accesdate=2007-07-30}} </ref>
	OASIS then based on these recommendations <ref>{{cite web
	\|url=http://www.oasis-open.org/archives/office/200409/msg00000.html
	\|title=News from IDA, ISO and TC roadmap
	\|author=Micheal Brauer(Sun)
	\|publisher=OASIS
	\|date=2007-09-01 }}</ref> decided to submit their Open Office XML format for ISO standardization renamed as Open Document Format the term used in EU recommendations. Following this in December 2005 Microsoft decided to standardize the new versions of their Microsoft Office XML formats under development for MS Office 12 through Ecma (renamed as Ecma Office Open XML).

			Microsoft submitted initial material to ] Technical Committee TC45, where it was standardized to become ECMA-376, approved in December 2006.<ref>{{cite web \| url = http://www.ecma-international.org/news/PressReleases/PR_TC45_Dec2006.htm \| title = Ecma International approves Office Open XML standard \| publisher = Ecma International \| date = 2006-12-07}}</ref>
	The development and standardization of Office Open XML takes place against a groundswell of interest in open, standards-based technologies by commercial and government organizations.

			This standard was then fast-tracked in the ] of ISO and IEC. After initially ], an amended version of the format received the necessary votes for approval as an ISO/IEC Standard as the result of a ] fast-tracking standardization process that concluded in April 2008.<ref name="ISOIECapproval">{{cite web \| url = https://www.iso.org/news/2008/04/Ref1123.html \| title = ISO/IEC DIS 29500 receives necessary votes for approval as an International Standard \| date = 2008-04-02 \| publisher = ISO}}</ref> The resulting four-part International Standard (designated ISO/IEC 29500:2008) was published in November 2008<ref>{{cite web \| url = http://www.iso.org/iso/pressrelease.htm?refid=Ref1181 \| title = Publication of ISO/IEC 29500:2008, Information technology—Office Open XML formats \| date = 2008-11-18 \| access-date = 2008-11-19 \| publisher = ISO \| author = ISO/IEC \| archive-date = 2009-07-06 \| archive-url = https://web.archive.org/web/20090706154539/http://www.iso.org/iso/pressrelease.htm?refid=Ref1181 \| url-status = dead }}</ref> and can be downloaded from the ].<ref>{{cite web \| url = https://standards.iso.org/ittf/PubliclyAvailableStandards/index.html \| title = Freely Available Standards \| publisher = ITTF (ISO/IEC) \| date = 2008-11-18 \| access-date = 2023-09-26 }}</ref> A technically equivalent set of texts is published by Ecma as ''ECMA-376 Office Open XML File Formats—2nd edition'' (December 2008); they can be downloaded from their website.<ref name="StandardECMA376">{{cite web \| url = https://www.ecma-international.org/publications-and-standards/standards/ecma-376/ \| title = Standard ECMA-376 \| publisher = Ecma-international.org \| access-date = 2009-05-19 }}</ref>
	==File format and structure==
	The Office Open XML file is an ] package containing the individual files that form the basis of the document. In addition to XML files with Office markup data, the ZIP package can also include embedded (binary) files in formats such as ], ], ] or ].

			The ISO/IEC standardization of Office Open XML was controversial and embittered,<ref name="infoworld-embittered">{{cite news
	According to Microsoft, Office Open XML is ] with Microsoft Office versions 2000, XP and 2003 using Microsoft Office Compatibility Pack.<ref name="office_compat">{{cite web
			\| last=Kirk
	\| title=How to use earlier versions of Excel, PowerPoint, and Word to open and save files from 2007 Office programs
			\| first=Jeremy
	\| url=http://support.microsoft.com/kb/924074
			\| title=ISO publishes Office Open XML specification
	\| publisher=Microsoft
			\| newspaper=]
	\| accessdate=2007-02-09
			\| date=19 November 2008
	}}</ref>
			\| url=https://www.infoworld.com/article/2654142/iso-publishes-office-open-xml-specification.html

			\| access-date = 12 June 2010}}</ref> with much discussion both about the specification and about the standardization process.<ref>{{cite web \|url=https://arstechnica.com/uncategorized/2008/10/norwegian-standards-body-implodes-over-ooxml-controversy/ \|title=Norwegian standards body implodes over OOXML controversy \|date=3 October 2008 \|publisher=Ars Technica}}</ref> According to '']'', "OOXML was opposed by many on grounds it was unneeded, as software makers could use ] (ODF), a less complicated office software format that was already an international standard."<ref name="infoworld-embittered" /> The same ''InfoWorld'' article reported that ] (which supports the ] format) threatened to leave standards bodies that it said allow dominant corporations like Microsoft to wield undue influence. The article further says that Microsoft was accused of co-opting the standardization process by leaning on countries to ensure that it got enough votes at the ISO/IEC for Office Open XML to pass, although it does not specify exactly who accused Microsoft.<ref name="infoworld-embittered" />
	===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 - Wordprocessing
	* SpreadsheetML - Spreadsheets
	* PresentationML - Presentation

	For drawing
	* DrawingML
	* ] (deprecated)

	Shared markup language materials include:
	* OMML (Office Math Markup Language)
	* Extended properties
	* Custom properties
	* Variant Types
	* Custom XML data properties
	* Bibliography

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

	The ] of OOXML can be characterized as being highly ], highly systematic and with an emphasis on reducing load time and improving parsing speed. In an a test with current implementations XML based office documents still were to be a lot slower than binary formats.<ref>{{cite web
	\| url=http://blogs.zdnet.com/Ou/?p=480
	\| title=MS Office 2007 versus Open Office 2.2 shootout
	\| author=George Ou
	\| date=2007-04-27
	\| accessdate=2007-04-27
	\| publisher=ZDnet.com}}</ref>. For speed, OOXML uses very short element names for common elements and spreadsheets save dates as index numbers (starting from 1899 or from 1904). In order to be systematic and generic, OOXML 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. OOXML 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 ], for example, which is fairly flat, designed for humans to write in ] and is more or less congenial for humans to read.

	=====OMML=====

	Included with Office Open XML is Office Math ML (OMML). This is a mathematical markup language which can integrate with the WordprocessingML markup. This means that the math zones can also include word processing markup like revision markings, footnotes, comments, images and elaborate formatting and styles. <ref> {{Cite web
	\| url=http://blogs.msdn.com/murrays/archive/2007/06/05/science-and-nature-have-difficulties-with-word-2007-mathematics.aspx
	\| title=Science and Nature have difficulties with Word 2007 mathematics
	\| author=Murray Sargent
	\| publisher=MSDN blogs
	\| date=2007-06-05
	\| accessdate=2007-07-31}}</ref>
	The format is different from the W3C MathML recommendation but compatible through relatively simple ]. For example Microsoft Office 2007 ships with such XSL transformation files allowing MathML to by copied from a clipboard with XSL transformation into OMML. During XSL transformation from OMML to MathML any WordprocessingML related markup should be lost because MathML does not allow for other markup in math zones.

	=== Container structure ===
	Office Open XML files conform to the Open Packaging Convention and different applications have characteristic directory structures and file names within these packages. An OPC-aware application will use the relationships files rather than directory names and file names to locate individual files. In OPC terminology, a file is a ''part''. A ''part'' also has accompanying metadata, in particular ] metadata.

	Office Open XML format uses a ] for packaging ] and other data files.<ref name="ecma_tc45_white_paper">{{cite web
	\| url=http://www.ecma-international.org/news/TC45_current_work/OpenXML%20White%20Paper.pdf
	\| title=Office Open XML Overview
	\| author=Tom Ngo
	\| pages=6
	\| format=PDF
	\| publisher=Ecma International
	\| date=] ]
	\| accessdate=2007-01-23
	}}</ref>

	A basic Office Open XML file contains an XML file called ''.xml'' at the root level of the ZIP package, along with three folders: ''_rels'', ''docProps'', and a directory specific for the document type (for example, in a .docx word processing file that would be a ''word'' directory). The ''word'' directory contains the ''document.xml'' file which is the core content of the document.

	; .xml file : This file describes the content of the ZIP package. It also contains a mapping for file extensions and overrides for specific ]s.
	; _rels Folder: The ''_rels'' folders are where one goes to find the relationships for any given part within the package. To find the relationships for a specific part, one looks for the ''_rels'' folder that is a sibling of one's part. If the part has relationships, the ''_rels'' folder will contain a file that has one's original part name with a ''.rels'' appended to it. For example, if the content types part had any relationships, there would be a file called '''' inside the ''_rels'' folder.
	; _rels/.rel : The root level ''_rels'' folder always contains a part called ''.rels''. This URI (''/_rels/.rels'') and ''/.xml'' are the only two reserved URIs for parts in files that adhere to Office Open XML conventions. This is where the "package relationships" are located. Whenever one opens a file using these conventions, one always starts by going to the ''_rels/.rels'' file. All relationship files are represented with XML. If one opens it in a text editor, one will see a bunch of XML that outlines each relationship for that part. In a minimal word document containing only the basic ''document.xml'', the top level parts are two ] parts, and the ''document.xml'' part.
	; word/document.xml : This is the main part for any Word document. If one views it in an XML editor, one will see a pretty basic XML file. The body of the word processing document is contained in this part.

	====Relationships====
	=====Relationship files in Office Open XML=====
	An example relationship file in Office Open XML (for example word/_rels/document.xml.rels)

	<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
	<Relationships
	xmlns="<nowiki>http://schemas.microsoft.com/package/2005/06/relationships</nowiki>">
	<Relationship Id="rId1"
	Type="<nowiki>http://schemas.microsoft.com/office/2006/relationships/image</nowiki>"
	Target="<nowiki>http://en.wikipedia.org/images/wiki-en.png</nowiki>"
	TargetMode="External" />
	<Relationship Id="rId2"
	Type="<nowiki>http://schemas.microsoft.com/office/2006/relationships/hyperlink</nowiki>"
	Target="<nowiki>http://www.wikipedia.org</nowiki>"
	TargetMode="External" />
	</Relationships>
	Relationship files allow navigation of the package without having to open up each part. For example, images that are referenced in a Word document can be found in the relationship file by looking for all relationships that are of type <code><nowiki>http://schemas.microsoft.com/office/2006/relationships/image</nowiki></code>. To point to a different image, you just edit the relationship.

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

	<w:hyperlink w:rel="rId2" w:history="1">

	In this example, the URL is represented by "rId2". The actual URL is located by the corresponding "rId2" item in the accompanying relationships file. Linked images, templates, and other items are referenced in the same way. The locations of referenced items can be updated by editing the relationships file.

	=====Embedded or linked media file relations=====
	Pictures can be embedded or linked in the XML files using a tag:

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

	This is the reference to the image file. In Office Open XML, all references are done via relationships. For example a document.xml part has a relationship to the image part. The actual URI is located by the corresponding "rId1" item in the accompanying relationships file. There is a _rels folder in the ZIP package, 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 a type, an ID and a 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 an URL.

	==Standardization==
	=== Creation of Ecma 376 ===

	Microsoft stated that Office Open XML would be an ], and submitted it to the ] standardization process. On ] Ecma created technical committee 45 (TC45) in order to "produce a formal standard for office productivity applications that is fully compatible with the Office Open XML Formats, submitted by Microsoft". The proposal was co-sponsored by ], ], ], the ], ], ], ], ], ] and ].<ref name="tc45_press">{{cite web
	\| title=The new open standard safeguards the continued use of billions of existing documents
	\| url=http://www.ecma-international.org/news/PressReleases/PR_TC45_Dez2005.htm
	\| publisher=Ecma International
	\| accessdate=2007-01-28
	}}</ref>

	The TC45 committee is co-chaired by two Microsoft employees;<ref name="tc45_main">{{cite web
	\| title= TC45 - Office Open XML Formats
	\| url=http://www.ecma-international.org/memento/TC45.htm
	\| publisher=Ecma International
	\| accessdate=2007-02-08
	}}</ref>
	it also includes members from ], ], ], ], ], ], ], ] and ].<ref name="pr_tc45_dec2006" />

	At the General Assembly meeting on ], Ecma International approved Office Open XML as an Ecma standard (Ecma 376).<ref name ="pr_tc45_dec2006" /> The General Assembly also approved submission of the text to the Fast Track mechanism of ], which — if successful — would result in it becoming an ISO standard.

	A or a can be downloaded from Ecma international.

	=== Submission to ISO ===

	As an ISO external Category A liaison, Ecma have submitted Ecma 376 to the ISO Fast Track process, the same process available to National Standard Organizations. To meet the requirements of this process, <ref name="jtc1-directives">{{cite web
	\| title=ISO/IEC JTC 1 Directives, 5th Edition, Version 2.0
	\| url=http://www.jtc1sc34.org/repository/0725c.htm
	\| publisher=iso
	\| accessdate=2007-01-28
	}}</ref>
	Ecma have submitted the documents "Explanatory report on Office Open XML Standard (Ecma-376) submitted to JTC 1 for fast-track"<ref name = "JTC report"></ref> and "Licensing conditions that Microsoft offers for Office Open XML".<ref name = "JTC licensing"></ref>

	=== Contradiction Phase ===

	The fast track process allows a 30 day review period by national standardizing bodies (NBs), during this period NBs may identify to the JTC 1 Secretariat any perceived contradiction with other JTC 1, ISO or IEC standards. If such a contradiction is alleged, "the JTC 1 Secretariat and ITTF shall make a best effort to resolve the matter"<ref name="jtc1-directives"/>. At the end of the 30 day review 20 countries submitted responses, the majority of which were either negative or equivocal. The full text of the national bodies' submissions is available from the .

	==== Contradiction Phase Voting ====

	The following table attempts to summarise the positions of the ISO member countries that voted in the contradiction phase. It should be noted that a lot of countries (such as the USA represented by ]) did not respond in the contradictions phase as it is not required if no perceived contradictions are found. However, some national bodies, such as ANSI, took an extremely narrow view of what constituted a contradiction. It should also be noted that the large number of submissions received was unprecedented.

	{\| class="wikitable"
	\|-
	\| Country
	\| Supportive?
	\| Equivocal?
	\| Against?
	\| Abstain?
	\| What they said
	\|-
	\| Australia
	\|
	\|align="center" \|x
	\|
	\|
	\| More investigation should precede fast tracking
	\|-
	\| Canada
	\|
	\|
	\|align="center" \|x
	\|
	\| Perceived contradictions must be resolved before any ballot
	\|-
	\| Czech Republic
	\|
	\|align="center" \|x
	\|
	\|
	\| DIS 29500 should be placed on the normal standards track
	\|-
	\| Denmark
	\|
	\|align="center" \|x
	\|
	\|
	\| A ballot will clarify the suitability of DIS 29500
	\|-
	\| Finland
	\|
	\|
	\|
	\|align="center" \|x
	\| DIS 29500 should be placed on the normal standards track
	\|-
	\| France
	\|
	\|align="center" \|x
	\|
	\|
	\| It is difficult to interpret the JTC 1 Directives
	\|-
	\| Germany
	\|
	\|
	\|align="center" \|x
	\|
	\| More investigation should precede fast tracking
	\|-
	\| Hungary
	\|
	\|
	\|
	\|align="center" \|x
	\| We abstain because of disagreement in our committee
	\|-
	\| India
	\|
	\|
	\|
	\|align="center" \|x
	\| We need more time
	\|-
	\| Italy
	\|
	\|
	\|
	\|align="center" \|x
	\| It is difficult to interpret the JTC 1 Directives
	\|-
	\| Japan
	\|
	\|align="center" \|x
	\|
	\|
	\| We hope IPR and technical issues are resolved in the ballot
	\|-
	\| Kenya
	\|
	\|
	\|align="center" \|x
	\|
	\| DIS 29500 is too large to be fast tracked
	\|-
	\| Malaysia
	\|
	\|
	\|align="center" \|x
	\|
	\| We have identified many contradictions
	\|-
	\| Netherlands
	\|
	\|
	\|
	\|align="center" \|x
	\| We abstain
	\|-
	\| New Zealand
	\|
	\|
	\|align="center" \|x
	\|
	\| Contradictions mean DIS 29500 should be withdrawn from fast track
	\|-
	\| Norway
	\|
	\|align="center" \|x
	\|
	\|
	\| More investigation should precede fast tracking
	\|-
	\| Romania
	\|align="center" \|x
	\|
	\|
	\|
	\| "We agree with the project as it is"
	\|-
	\| Singapore
	\|
	\|align="center" \|x
	\|
	\|
	\| We hope the contradictions can be resolved
	\|-
	\| Sweden
	\|
	\|align="center" \|x
	\|
	\|
	\| We are not in a position to have a view
	\|-
	\| UK
	\|
	\|
	\|align="center" \|x
	\|
	\| DIS 29500 should be placed on the normal standards track
	\|-
	\| '''TOTALS'''
	\| align="center" \|1
	\| align="center" \|8
	\| align="center" \|6
	\| align="center" \|5
	\|
	\|}

	Ecma responded to the issues raised during the contradiction period with a document reviewing the national bodies' comments.<ref name = "ECMA">{{cite web
	\| url=http://www.ecma-international.org/news/TC45_current_work/Ecma%20responses.pdf
	\| title= Response Document: National Body Comments from 30-Day Review of the Fast Track Ballot for ISO/IEC DIS 29500 (ECMA-376) “Office Open XML File Formats”
	\| publisher=Ecma International
	\| date=2007-02-28
	\| accessdate=2007-04-03 }}</ref> This document cites the objections raised by the national bodies, and shows the comments overlap considerably with material on the Web created by opponents of Office Open XML, particularly from the Grokdoc<ref name="grokdoc"/> site. There have been suggestions by Microsoft employees and others that the national bodies' documents were not written by them, but by Microsoft competitors,<ref> {{cite web
	\| url=http://blogs.msdn.com/brian_jones/archive/2007/04/20/a-few-updates-on-the-openxml-formats.aspx
	\| title=A few updates on the OpenXML formats
	\| author=Brian Jones
	\| accessdate=2007-05-04}}</ref> referring to the author metadata of the PDF submission by Kenya that contain the names of an IBM Germany employee, and a Malaysian ODF supporter.<ref> {{cite web
	\| url=http://notes2self.net/archive/2007/06/22/quot-there-is-no-reason-to-be-browbeaten-into-thinking-that-there-should-only-be-one-document-format-quot.aspx
	\| title="There is no reason to be browbeaten into thinking that there should only be one document format."
	\| author=Stephen McGibbon
	\| accessdate=2007-06-22}}</ref>
	However, national bodies are permitted to source technical skills as required.

	=== Five-Month Ballot ===

	The JTC 1 directives<ref name="jtc1-directives"/> state that ''regardless'' of whether or not resolution is reached on the question of contradiction, a five-month ballot commences immediately. So, on 2007-04-02 the ISO JTC 1 Secretariat duly informed Ecma International that the five-month DIS 29500 (Office Open XML) ballot period had started and would close on 2007-09-02.<ref>{{cite web
	\| url=http://www.ecma-international.org/news/PressReleases/PR_TC45_April2007.htm
	\| title=Office Open XML reaches next step in ISO/IEC process
	\| publisher=Ecma International
	\| date=2007-04-02
	\| accessdate=2007-04-03 }}</ref>

	At the end of the five-month letter ballot, all the technical comments that have been made are consolidated and redistributed so that the voting nations may form a view on them in their totality. The secretariat then may decide to arrange for a special ballot resolution meeting (BRM) to take place no sooner than two and one-half months after the ballot has closed.

	=== Response to the Ballot ===

	After the 5 month letter ballot closes, the proposer (Ecma) has a chance to respond to the comments made by the national bodies that voted. They may combine, de-duplicate, label and group the comments and then attempt to liaise informally with national bodies, to try and arrive at a set of revisions that are acceptable.

	The result of Ecma's activity will be a "Disposition of Comments" document – effectively a set of proposed revisions to the DIS 29500 text designed to be acceptable to all the national bodies who disapproved of the text in the letter ballot. It is this series of edits which effectively forms the agenda for the subsequent Ballot Resolution Meeting, and on which the attendees of that meeting will be asked to form opinions.

	=== Ballot Resolution Process ===

	During the 6 month period (of a one month contradiction phase, and 5-month letter ballot) the national bodies are able to cast a vote of approval, disapproval or abstention. P-members are required to vote. The ballot resolution process is the process which follows this vote.

	In the event there is not 100% support, or overwhelming disapproval, of DIS 29500 there can be a Ballot Resolution Meeting (BRM) if needed, in which comments submitted with ballot votes can be resolved. The BRM will have been called at the discretion of the secretariat at the end of the ] voting. The outcome of this meeting effectively decides whether DIS 29500 succeeds or fails in its bid to become a full International Standard. The DIS 29500 BRM is provisionally scheduled for Q1 2008.

	==== Who Attends the BRM? ====

	The participants in the BRM are representatives of the national bodies, the proposer (Ecma), and support and administrative staff.

	The national bodies who attend this meeting are:

	* (who have to send representatives);
	* those that voted "disapprove" during the five-month ballot, who have a ''duty'' to send a delegation to this meeting. (JTC 1 Directives<ref name='jtc1-directives'/> clause 13.7);
	* optionally, those who voted to "approve" DIS 29500.

	The meeting is expected to attract between 40 and 100 participants.

	==== Meeting Process ====

	During this meeting, the participants consider each of Ecma's responses to the comments gathered in the preceding process. Each comment is thus effectively "resolved" by the meeting's participants either:

	* agreeing to a proposed alteration of the text by Ecma
	* agreeing to withdraw that comment (if, for example, it is incorrect)
	* otherwise agreeing to amend the text or ignore a comment following discussion

	In this way, a set of editorial changes to the text is agreed that, collectively, implies a new revised document. The meeting then agrees whether this final "implied" document is acceptable for publication as a full International Standard.

	==== Voting Procedures ====

	JTC 1 states that decisions at the BRM should be reached preferably by consensus, but that any unavoidable votes should be taken according to normal JTC 1 procedures (JTC 1 Directives<ref name='jtc1-directives'/> clause 13.8). According to these procedures a vote at the meeting is passed if:

	* At least two-thirds of the P-members voting shall have approved
	* Not more than one-quarter of the total number of votes cast are negative

	Votes are taken only of those present at the meeting, and "P-members" for the purposes of this clause are P-members of JTC 1 (not SC 34); votes from the ] are '''not''' carried forward to the BRM. {{Fact\|date=August 2007}}.

	Abstentions are excluded from the count. (JTC 1 Directives<ref name='jtc1-directives'/> clause 9.6)

	===== Eligibility to Vote =====

	Any country that voted (i.e. either "approve with comments", "disapprove with comments" or "abstain") in the ] may vote at the BRM. Countries that did '''not''' vote in that letter ballot may not vote at the BRM.

	Countries may change their position to any of "approve", "disapprove" or "abstain" during the course of the BRM.{{Fact\|date=August 2007}}

	===== The Arithmetic of the Votes =====

	Voting is on a simple, one-country/one-vote basis, but the vote counting is complicated by the fact that there are two classes of voting country. Those with most voting power are the 33 . For any vote to pass at the BRM, at least two-thirds of these countries (that are present at the meeting), must vote positively.

	If that hurdle is cleared, the votes of all countries present (including the JTC 1 P-Members) are counted. For a vote to pass, the total negative votes for this combined group must not exceed one-quarter of those countries eligible to vote.

	==== Final Outcome ====

	If this meeting fails to agree on a final text, the proposal of OOXML for fast-tracking fails and the procedure is terminated: if the meeting ''does'' agree on a final text, any required changes are applied by the editor and OOXML is passed for publication as an ISO standard.

	=== ISO Maintenance Regime ===

	The maintenance regime for OOXML (should it become an ISO Standard) is yet to be determined. Ecma have however tabled a for discussion by SC34 at scheduled to take place in December 2007 in ].

	=== National Body Activity ===

	Some countries opened their scrutiny procedure to public view during the 5 month ballot:

	* The ] is publishing comments they receive on DIS 29500 . An archive of email exchanged between members of (who provide recommendations on the U.S. position) is available . When voting on a position, the INCITS V1 committee divided, with Microsoft and Ecma TC45 members Nextpage and BP voting for "approve with comments" on the one hand, and a group including IBM, Sun and ] voting for "disapprove with comments" on the other hand. The committee thus failed to reach agreement on a recommendation to its parent committee.<ref> {{ cite web
	\|url=http://www.ibiblio.org/bosak/v1mail/200707/2007Jul13-175415.eml
	\|title=Email with appended notes from INCITS/V1 meeting on 2007-07-13 }}</ref>. Subsequently the INCITS Executive Board held a ballot for a position of "Approval with comments" and to include all comments processed or non-processed by the V1 committee.<ref> {{cite web
	\| url=http://blogs.msdn.com/dmahugh/archive/2007/07/19/incits-executive-board-to-vote-on-approval-with-comments.aspx
	\| title=INCITS Executive Board to vote on "approve with comments
	\| author= Doug Mahugh
	\| date=2007-07-19
	\| publisher=MSDN blogs }}</ref> This ballot did not achieve the necessary two-thirds majority<ref> {{cite web
	\| url=http://ballot.itic.org/itic/tallyvote.taf?function=vote&committee=INCITS&ballot_id=2212
	\| title=Vote Tally for INCITSLB2212
	\| author=INCITS
	\| date=2008-08-14
	\| publisher=INCITS}}</ref> which makes it likely ANSI (on behalf of the US) will abstain in the ISO ballot.

	* The ] used an open Wiki (read-only to the public; read/write for BSI technical committee members) to help coordinate the UK's input into the ballot. While active, the site gathered 630 comments on the text. The main page of the wiki is , and specific comments on DIS 29500 are . Beyond this, the deliberations and voting of BSI are confidential.

	* The ] (SCC) is seeking comments on a proposal to adopt Office Open XML (Open XML) as an international open standard. The forum soliciting comments ''from Canadians only'' is .

	==Licensing==		==Licensing==
	] provides its standard specifications for free without copyright restrictions <ref>{{ cite web
	\|url=http://www.ecma-international.org/memento/index.html
	\|title=What is Ecma International
	\|Publisher=Ecma International}} </ref>
	and under the which requires participating and approving member organisations to make available their patent rights under a reasonable and non-discriminatory basis (see ]).

	Microsoft which is a main contributor to the Ecma standard provided a '''covenant not to sue'''<ref>{{cite web
	\| title=Microsoft Covenant Regarding Office 2003 XML Reference Schemas
	\| url=http://www.microsoft.com/office/xml/covenant.mspx
	\| publisher=Microsoft
	\| accessdate=2006-07-11
	}}</ref>. The covenant received a mixed reception, with some like ] identifying problems<ref>{{cite web
	\| url=http://www.groklaw.net/articlebasic.php?story=20051202135844482
	\| title=2 Escape Hatches in MS's Covenant Not to Sue
	\| accessdate=2007-01-29
	\| publisher=Groklaw
	}}</ref> and others (such as ]) endorsing it.<ref>{{cite web
	\| url=http://blogs.zdnet.com/BTL/?p=2192
	\| title=Top open source lawyer blesses new terms on Microsoft’s XML file format
	\| first=David
	\| last=Berlind
	\| date=] ]
	\| accessdate=2007-01-27
	\| publisher=ZDNet
	}}</ref>

			Under the Ecma International code of conduct in patent matters,<ref>{{cite web \| url = https://www.ecma-international.org/policies/by-ipr/code-of-conduct-in-patent-matters/ \| title = Code of Conduct in Patent Matters \| publisher = Ecma International}}</ref> participating and approving member organizations of ECMA are required to make their patent rights available on a ] (RAND) basis.
	Microsoft also added the Office Open XML format to their '''Microsoft Open Specification Promise''' in which Microsoft irrevocably promises ''not to assert any Microsoft Necessary Claims against you for making, using, selling, offering for sale, importing or distributing any implementation to the extent it conforms to a Covered Specification ("Covered Implementation")''. The ''Office Open XML 1.0 - Ecma 376'' and its predecessor ] are among the covered specifications.<ref name = "OSP"> {{cite web
	\| title=Microsoft Open Specification Promise
	\| url=http://www.microsoft.com/interop/osp/default.mspx
	\| publisher=Microsoft
	\| date=2006-09-12
	\| accessdate=2007-04-22
	\| }} </ref>

			Holders of patents which concern ISO/IEC International Standards may agree to a standardized license governing the terms under which such patents may be licensed, in accord with the ]/]/] common patent policy.<ref>{{cite web \| url = https://isotc.iso.org/livelink/livelink/Open/6344764 \| title = ISO/IEC/ITU common patent policy}}</ref>
	The Office Open XML format therefore can be used under the Covenant not to Sue or the Open Specification Promise.

			Microsoft, the main contributor to the standard, provided a covenant not to sue<ref>{{cite web \| url = https://xml.coverpages.org/ni2006-09-12-a.html \| title = Microsoft's Open Specification Promise Eases Web Services Patent Concerns. \| date = September 12, 2006 \| access-date = 2015-04-18 }}</ref> for its patent licensing. The covenant received a mixed reception, with some like the ] ] criticizing it,<ref>{{cite web\|url=https://web.archive.org/web/20240724061306/http://www.groklaw.net/article.php?story=20051202135844482 \|title=2 Escape Hatches in MS's Covenant Not to Sue \|date=December 4, 2005 \|website=]}}</ref> and others such as ], (an attorney and lecturer at ]), endorsing it.<ref>{{cite web \| url = https://www.zdnet.com/article/top-open-source-lawyer-blesses-new-terms-on-microsofts-xml-file-format/ \| title = Top open source lawyer blesses new terms on Microsoft's XML file format \| first = David \| last = Berlind \| date = November 28, 2005 \| access-date = 2007-01-27 \| publisher = ZDNet }}</ref>
	In support of the licensing arrangements Microsoft commissioned an analysis from the London legal firm Baker & Mckenzie.<ref>{{cite web
	\| url=http://www.bakernet.com/NR/rdonlyres/CC54A6B6-79E8-4E0D-B290-C836D5F70867/0/OpenXML.pdf
	\| title=Standardization and Licensing of Microsoft’s Office Open XML Reference Schema
	\| author=Baker & McKenzie
	\| publisher= Baker & Mckenzie
	\| accessdate=2007-02-01
	\| year=2006
	\| month=June}}</ref>

			Microsoft has added the format to their '']''<ref name="OSP">{{cite web \| title = Microsoft Open Specification Promise \| url = https://learn.microsoft.com/en-us/openspecs/dev_center/ms-devcentlp/1c24c7c8-28b0-4ce1-a47d-95fe1ff504bc \| publisher = Microsoft \| date = 2007-02-15 \| access-date = 2015-04-18 }}</ref> in which
	The ''Microsoft Open Specification Promise'' was included in documents submitted to ISO in support of the Ecma 376 fast track submission.<ref name = "JTC licensing" />. In response to criticism of the licensing, ECMA provided the following statements:
	:*Contributions to Ecma were made under the Ecma Code of Conduct in Patent Matters, which we believe to be in line with ISO/IEC IPR policy.
	:*The OSP enables both open source and commercial software to implement DIS 29500.

			<blockquote>Microsoft irrevocably promises not to assert any Microsoft Necessary Claims against you for making, using, selling, offering for sale, importing or distributing any implementation to the extent it conforms to a Covered Specification </blockquote>
	====EU defintion of an Open Standard====
	With Ecma International publishing the specification for free and patents made irrevocably available on a royalty-free basis, Office Open XML conforms to the ].

			This is limited to applications which do not deviate from the ISO/IEC 29500:2008 or Ecma-376 standard and to parties that do not "file, maintain or voluntarily participate in a patent infringement lawsuit against a Microsoft implementation of such Covered Specification".<ref>{{cite web \| url = https://www.ecma-international.org/publications-and-standards/ \| title = Ecma formal publications \| publisher = Ecma International\|quote=Ecma Standards and Technical Reports are made available to all interested persons or organizations, free of charge and licensing restrictions}}</ref><ref>{{cite web \| url = http://www.microsoft.com/Interop/osp/default.mspx \| title = Microsoft Open Specification Promise \| publisher = Microsoft.com}}</ref>
			The Open Specification Promise was included in documents submitted to ISO/IEC in support of the ECMA-376 fast-track submission.<ref name="JTC licensing">{{cite web\|url=https://www.jtc1sc34.org/repository/0810c.htm \|title=Licensing conditions that Microsoft offers for Office Open XML \|publisher=Jtc1sc34.org \|date=2006-12-20 \|access-date=2009-05-19}}</ref>
			Ecma International asserted that, "The OSP enables both open source and commercial software to implement ".<ref name="ecma-responses-pdf">{{cite web \| url = http://www.ecma-international.org/news/TC45_current_work/Ecma%20responses.pdf \| title = Microsoft Word — Responses to Comments and Perceived Contradictions.doc \| access-date = 2009-09-16}}</ref>

			==Versions==
	* The standard is adopted and will be maintained by a not-for-profit organisation, and its ongoing development occurs on the basis of an open decision-making procedure available to all interested parties (consensus or majority decision etc.). <ref name="IEF"> {{cite web
	\| url=http://europa.eu.int/idabc/en/document/3761
	\| title=European Interoperability Framework for pan-European eGovernment Services
	\| author=IDABC - European eGovernment Services
	\| date=2004
	\| accessdate=2007-07-30 }}</ref>
	* The standard has been published and the standard specification document is available either freely or at a nominal charge. It must be permissible to all to copy, distribute and use it for no fee or at a nominal fee. <ref name="IEF"/>
	* The intellectual property — i.e. patents possibly present — of (parts of) the standard is made irrevocably available on a royalty-free basis. <ref name="IEF"/>
	* There are no constraints on the re-use of the standard.<ref name="IEF"/> .

			The Office Open XML specification exists in several versions.
	==Adoption==
	Office Open XML is the default ] format. For older versions such as Office 2000, Office XP and Office 2003 a compatibility pack is provided.<ref>{{cite web
	\| url=http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=941B3470-3AE9-4AEE-8F43-C6BB74CD1466
	\| title=Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats
	\| publisher=Microsoft
	\| date=2006-11-06
	\| accessdate=2007-11-18 }}</ref> The compatibility pack can also be used as a stand alone converter with Office 97.

			=== ECMA-376 1st edition (2006) ===
	* Microsoft Office Open XML File Format Converter for Mac 0.2 (Beta)<ref>{{cite web\|url=http://www.microsoft.com/mac/downloads.aspx?pid=download&location=/mac/download/Office2004/ConverterBeta_0_2.xml&secid=4&ssid=36&flgnosysreq=True\|title=Microsoft Office Open XML File Format Converter for Mac 0.2 (Beta)\|publisher=Microsoft\|date=] ]}}</ref>Microsoft had previously advised users of Office 2007 to save their files in the old Office binary format<ref>{{cite web
			The ECMA standard is structured in five parts to meet the needs of different audiences.<ref name="StandardECMA376" />
	\| url=http://blogs.msdn.com/macmojo/archive/2006/12/05/converters-coming-free-and-fairly-fast.aspx
			;
	\| title=Converters Coming! Free and (Fairly) Fast.
			;Part 1. Fundamentals
	\| author=sherjo
			:* Vocabulary, notational conventions and abbreviations
	\| publisher=The Office for Mac Team Blog
			:* Summary of primary and supporting markup languages
	\| date=2006-12-6
			:* Conformance conditions and interoperability guidelines
	\| accessdate=2007-03-18}}</ref> until a file converter is released.
			:* Constraints within the Open Packaging Conventions that apply to each document type
	* Beta testing has started on Microsoft ], which will support the format. The final version is scheduled to release in the mid-] ].<ref>{{cite web \| url=http://www.forbes.com/feeds/ap/2007/08/02/ap3979609.html \| title=Microsoft Delays Office for Mac Release \| author=Forbes \| date=August 2, 2007 }}</ref>
			;
			;Part 2. Open Packaging Conventions
			:* The ] (OPC), for the package model and physical package, is defined and used by various document types in various applications from multiple vendors.
			:* It defines core properties, thumbnails, digital signatures, and authorizations & encryption capabilities for parts or all of the contents in the package.
			:* XML schemas for the OPC are declared as XML Schema Definitions (XSD) and (non-normatively) using ] (ISO/IEC 19757-2)
			;
			;Part 3. Primer
			:* Informative (non-normative) introduction to WordprocessingML, SpreadsheetML, PresentationML, DrawingML, ] and Shared MLs, providing context and illustrating elements through examples and diagrams
			:* Describes the custom XML data-storing facility within a package to support integration with business data
			;
			;Part 4. Markup Language Reference
			:* Contains the reference material for WordprocessingML, SpreadsheetML, PresentationML, DrawingML, Shared MLs and Custom XML Schema, defining every element and attribute including the element hierarchy (parent/child relationships)
			:* XML schemas for the markup languages are declared as XSD and (non-normatively) using RELAX NG
			:* Defines the custom XML data-storing facility
			;
			;Part 5. Markup Compatibility and Extensibility
			:* Describes extension facilities of OpenXML documents and specifies elements & attributes through which applications can operate across different extensions.

			Later versions of the ECMA-376 standard are aligned and technically equivalent to the corresponding ISO standard.
	*]'s ] '08 suite supports Office Open XML word processing, spreadsheet and presentation file formats in ], ] and ] (respectively). <ref>{{cite web
	\| url= http://www.apple.com/iwork/pages/#compatible
	\| title= Apple - iWork - Pages
	\| accessdate=2007-07-08}}</ref> <ref>{{cite web
	\| url= http://www.apple.com/iwork/numbers/#compatibility
	\| title= Apple - iWork - Numbers
	\| accessdate=2007-07-08}}</ref> <ref>{{cite web
	\| url= http://www.apple.com/iwork/keynote/#share
	\| title= Apple - iWork - Keynote
	\| accessdate=2007-07-08}}</ref>

			=== ISO/IEC 29500:2008 ===
	*]'s ] will support Office Open XML in the next version of OS X, Leopard.<ref>{{cite web
			The ISO/IEC standard is structured into four parts:<ref name="StandardIS29500">{{cite web\| url=https://www.iso.org/search.html?q=29500&hPP=10&idx=all_en&p=0&hFR%5Bcategory%5D%5B0%5D=standard\| title=ISO search for "29500"\| publisher=]\| date=2009-06-05}}</ref> Parts 1, 2 and 3 are independent standards; for example, Part 2, specifying ], is used by other file formats including ] and ]. Part 4 is to be read as a modification to Part 1, which it requires.
	\| url=http://uneasysilence.com/archive/2006/12/8702/
	\| title = OS X leopard Text Edit to Support Office 2007?
	\| publisher = uneasysilence
	\| acessdate = 2007-02-14}} </ref>

			A technically equivalent set of texts is also published by Ecma as ECMA-376 2nd edition (2008).
	* ]'s ] supports Office Open XML attachments in emails <ref> {{cite web
	\| url=http://manuals.info.apple.com/en/iPhone_User_Guide.pdf#page=48
	\| title="iPhone User's Guide"
	\| format=PDF
	\| publisher=Apple, Inc. }}</ref>

			;
	*] has announced that by mid-2007 its WordPerfect Office suite will support Office Open XML as well as ].<ref>
			;Part 1. Fundamentals & Markup Language Reference
	{{cite web
			:Consisting of 5560 pages, this part contains:
	\| url= http://www.corel.com/servlet/Satellite?c=Content_C1&cid=1153321430604&lc=en&pagename=CorelCom%2FLayout&pressId=1164741065876
			:* Conformance definitions
	\| title=Corel WordPerfect Office To Support Open Document Format and Microsoft Office Open XML
			:* Reference material for the XML document markup languages defined by the Standard
	\| publisher=corel
			:* XML schemas for the document markup languages declared using ] and (non-normatively) ]
	\| accessdate=2007-01-30}}
			:* Defines the foreign markup facilities
	</ref>
			;
			;Part 2. Open Packaging Conventions
			: Consisting of 129 pages, this part contains:
			:* A description of the Open Packaging Conventions (package model, physical package)
			:* Core properties, ]s and ]s
			:* XML schemas for the OPC are declared using ] and (non-normatively) ]
			;
			;Part 3. Markup Compatibility and Extensibility
			: Consisting of 40 pages, this part contains:
			:* A description of ''extensions'': elements & attributes which define mechanisms allowing applications to specify alternative means of negotiating content
			:* Extensibility rules are expressed using ]
			;
			;Part 4. Transitional Migration Features
			: Consisting of 1464 pages, this part contains:
			:* Legacy material such as compatibility settings and the graphics markup language ]
			:* A list of syntactic differences between this text and ECMA-376 1st Edition

			The standard specifies two levels of document & application conformance, ''strict'' and ''transitional,'' for each of WordprocessingML, PresentationML and SpreadsheetML, and also specifies applications' descriptions of ''base'' and ''full''.
	*] has limited SpreadsheetML markup language support.<ref>{{cite web
	\| url=http://www.gnome.org/projects/gnumeric/
	\| title=GNOME Office / Gnumeric
	\| publisher=GNOME.org
	\| accessdate=2006-07-28}}</ref>

			===Compatibility between versions===
	*] has created an Office Open XML plugin for the of ]<ref>{{cite web
			The intent of the changes from ECMA-376 1st Edition to ISO/IEC 29500:2008 was that a valid ECMA-376 document would also be a valid ISO 29500 Transitional document;<ref>{{cite web\| url=http://idippedut.dk/post/2009/06/23/Re-introducing-onoff-values-to-ST-OnOff-in-OOXML-Part-4.aspx\| title=Re-introducing on/off-values to ST-OnOff in OOXML Part 4\| access-date=2009-09-29\| archive-date=2009-06-26\| archive-url=https://web.archive.org/web/20090626065627/http://idippedut.dk/post/2009/06/23/Re-introducing-onoff-values-to-ST-OnOff-in-OOXML-Part-4.aspx\| url-status=dead}}</ref> however, at least one change introduced at the BRM—refusing to allow further values for xsd:boolean—had the effect of breaking backwards-compatibility for most documents.<ref>{{cite web\| url=http://www.adjb.net/post/OOXML-and-Office-2007-Conformance-a-Smoke-Test.aspx\| title=OOXML and Office 2007 Conformance: a Smoke Test\| access-date=2009-09-29\| archive-url=https://web.archive.org/web/20100428091855/http://www.adjb.net/post/OOXML-and-Office-2007-Conformance-a-Smoke-Test.aspx\| archive-date=2010-04-28\| url-status=dead}}</ref> A fix for this had been suggested to ]/WG 4, and was approved in June 2009 as a recommendation for the first revision to Office Open XML.<ref>{{cite web\| url=http://kikaku.itscj.ipsj.or.jp/sc34/open/1239.pdf\| title=Minutes of the Copenhagen Meeting of ISO/IEC JTC1/SC34/WG4\| date=2009-06-22\| access-date=2009-09-29\| archive-url=https://web.archive.org/web/20140512224125/http://kikaku.itscj.ipsj.or.jp/sc34/open/1239.pdf\| archive-date=2014-05-12\| url-status=dead}} page 15</ref>
	\| url=http://download.novell.com/SummaryFree.jsp?buildid=ESrjfdE4U58~
	\| title=Download OpenOffice.org–OpenXML translator
	\| publisher=Novell
	\| accessdate=2007-03-02}}</ref>. An Office Open XML import filter is slated for inclusion in version 2.3 of the OpenOffice.org project<ref>{{cite web
	\| url=http://www.openoffice.org/issues/show_bug.cgi?id=79123
	\| title=Issue 79123 - Integrate a first version of the import filter for ooxml wordprocessing documents
	\| publisher=OpenOffice.org
	\| accessdate=2007-07-09}}</ref>.

			Applications capable of reading documents compliant to ECMA-376 Edition 1 would regard ISO/IEC 29500-4 Transitional documents containing ] dates as corrupt.<ref>{{cite web \|url=http://kikaku.itscj.ipsj.or.jp/sc34/wg4/archive/sc34-wg4-2011-0173.zip \|format=PDF \|title=ISO/IEC 29500-4:2008/Draft Amd2:2011 - Draft - Information technology — Document description and processing languages — Office Open XML File Formats — Part 4: Transitional Migration Features - AMENDMENT 2 \|date=2011-03-02 \|access-date=2011-04-04 \|archive-url=https://web.archive.org/web/20140512232105/http://kikaku.itscj.ipsj.or.jp/sc34/wg4/archive/sc34-wg4-2011-0173.zip \|archive-date=2014-05-12 \|url-status=dead }}</ref>
	*docXConverter by Panergy Ltd. converts from WordprocessingML to ] (RTF). DocXConverter can be used to transfer WordprocessingML data to other applications that read RTF data such as Word 97.<ref>{{cite web
	\| url=http://www.panergy-software.com/products/docxconverter/features.html
	\| title=docXConverter - Features
	\| publisher=panergy
	\| accessdate=2007-01-31 }} </ref>

	* Datavis' DocumentsToGo for ] supports Office Open XML documents.<ref> {{cite web
	\| url=http://www.dataviz.com/products/documentstogo/premium/index.html
	\| title="DocumentsToGo for PalmOS Premium Edition"
	\| publisher=Datavis }}</ref>

			==Application support==
	* Datawatch supports Office Open XML spreadsheets in its report ] tool Monarch v9.0<ref>{{cite web
			{{Main\|List of software that supports Office Open XML}}
	\| url=http://www.datawatch.com/datawatch/news.asp?display=detail&id=128
			Some older versions of Microsoft Word and Microsoft Office are able to read and write <code>.docx</code> files after installation of the free compatibility pack provided by Microsoft,<ref name="omso">{{cite web\|url=https://www.microsoft.com/en-us/download/details.aspx?id=32858\|title=Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats (Version 3)\|publisher=Microsoft\|date=2007-06-18\|access-date=2018-06-23}}</ref> although some items, such as equations, are converted into images that cannot be edited.<ref>. Office.microsoft.com. Retrieved on 2013-07-17.</ref>
	\| title=Datawatch Announces Availability of Monarch V.9.0; Supports Microsoft® Windows Vista™ and Extends Excel Capabilities
	\| Author=Datawatch
	\| Publisher=Datawatch.com
	\| date=2007-02-27 }}</ref>

			Starting with ], the Office Open XML file formats have become the default file format<ref name="microsoft.com">{{cite web \| url = http://www.microsoft.com/Presspass/press/2008/may08/05-21ExpandedFormatsPR.mspx?rss_fdn=Press%20Releases \| title = Microsoft Expands List of Formats Supported in Microsoft Office \| publisher = Microsoft \| access-date = 2008-05-21 }}</ref> of ].<ref name="courierpress.com">{{cite web \| url = http://www.courierpress.com/news/2008/oct/24/microsofts-future-lies-somewhere-beyond-the/ \| title = Microsoft's future lies somewhere beyond the Vista by Evansville Courier & Press \| publisher = Courierpress.com \| access-date = 2009-05-19 \| archive-date = 2014-07-10 \| archive-url = https://web.archive.org/web/20140710192710/http://www.courierpress.com/news/2008/oct/24/microsofts-future-lies-somewhere-beyond-the/ \| url-status = dead }}</ref><ref name="knowledge.wharton.upenn.edu">{{cite web \| url = http://knowledge.wharton.upenn.edu/article.cfm?articleid=1795 \| title = Rivals Set Their Sights on Microsoft Office: Can They Topple the Giant? - Knowledge@Wharton \| publisher = Knowledge.wharton.upenn.edu \| access-date = 2009-05-19}}</ref> However, due to the changes introduced in the Office Open XML standard, Office 2007 is not wholly in compliance with ISO/IEC 29500:2008.<ref name="notOOXML">{{cite web \| author = Andy Updegrove \| url = http://consortiuminfo.org/standardsblog/article.php?story=20080521092930864 \| title = Microsoft Office 2007 to Support ODF — and not OOXML \| date = 21 May 2008 \| publisher = ConsortiumInfo.org \| access-date = 2009-05-19 \| archive-date = 2008-05-23 \| archive-url = https://web.archive.org/web/20080523233233/http://www.consortiuminfo.org/standardsblog/article.php?story=20080521092930864 \| url-status = dead }}</ref>
	==Arguments in Support and Criticism of OOXML Standard==
			] includes support for opening documents of the ISO/IEC 29500:2008-compliant version of Office Open XML, but it can only save documents conforming to the ''transitional'', not the ''strict'', schemas of the specification.<ref name="docx23">{{cite web \|url=https://arstechnica.com/microsoft/news/2010/04/iso-ooxml-convener-microsofts-format-heading-for-failure.ars \|title=ISO OOXML convener: Microsoft's format "heading for failure" \|date=2 April 2010 \|publisher=Ars Technica}}</ref><ref name="docx22">{{cite web
	===Arguments in Support===
			\|url=http://www.adjb.net/post/Microsoft-Fails-the-Standards-Test
	Organizations and individuals supporting Office Open XML have provided arguments for standardization<ref>{{cite web
			\|title=Microsoft Fails the Standards Test
	\| url=http://www.openxmlcommunity.org/summary.aspx
			\|work=Where is an end of it?
	\| title=Hear what Ecma has to say about Open XML (paragraph: Key benefits of Open XML)
			\|last=Brown
	\| author=Open XML community
			\|first=Alex
	\| publisher=OpenXMLcommunity.org }}</ref>.
			\|publisher=Alex Brown's weblog
			\|date=31 March 2010
			\|access-date=23 June 2018
			}}</ref> Note that the intent of the ISO/IEC is to allow the removal of the transitional variant from the ISO/IEC 29500 standard.<ref name="docx22"/> ] and later fully support ISO/IEC 29500 Strict,<ref name="Office 2013 File Formats">{{cite web \|url=https://learn.microsoft.com/en-us/previous-versions/office/office-2013-resource-kit/cc179191(v=office.15) \|title=XML file name extension reference for Office 2013 \|website=Office 2013 Resource Kit \|publisher=Microsoft \|date=26 December 2016 }}</ref> but do not use it as the default file format because of backwards compatibility concerns.<ref name="Office 2016 file formats">{{cite web\|url=https://www.loc.gov/preservation/digital/formats/fdd/fdd000401.shtml\|title=XLSX Strict (Office Open XML), ISO 29500-1:2008-2016\|website=]\|access-date=2018-09-09}}</ref>

			The ability to read and write Office Open XML format is, however, not limited to Microsoft Office; other office products are also able to read & write this format:
	====User Base Argument====
			* ] for Online, Mobile and Desktop apps are able to open and save Office Open XML files.<ref>{{Cite web\|last=\|first=\|date=2 November 2020\|title=Collabora Online 6.4.0-released\|url=https://www.collaboraoffice.com/press-releases/collabora-online-6-4-0-released/}}</ref>
			* ] is able to read and write <code>DOCX</code> and <code>XLSX</code> files in its word processor & spreadsheet applications.
			* ] is able to open and save Office Open XML files.<ref name=":0">{{cite web\|url = http://wiki.documentfoundation.org/LibreOffice_OOXML\|title = LibreOffice OOXML\|access-date = 22 March 2012}}</ref>
			* ] from version 3.0 can import Office Open XML files but not save them.<ref>{{cite web\|url = http://www.openoffice.org/dev_docs/features/3.0/#Microsoft_Office_2007_Import_Filters\|title = OpenOffice.org 3.0 New Features\|date = 2008-10-13\|access-date = 2009-10-24}}</ref> Version 3.2 improved this feature with read support even for password-protected Office Open XML files.<ref>{{cite web\|url = http://www.openoffice.org/dev_docs/features/3.2/\|title = OpenOffice.org 3.2 New Features\|year = 2010\|access-date = 2010-11-13}}</ref><ref>{{cite web\| url=https://www.theregister.co.uk/2010/02/13/openoffice_review\| title=OpenOffice 3.2 - now with less Microsoft envy\| author=Scott Gilbertson\| date=13 February 2010\| access-date=18 Feb 2013\| publisher=The Register\| quote=the ability to open password-protected Word, Excel, and PowerPoint files}}</ref><ref>{{cite web\| url=http://www.openoffice.org/development/releases/3.2.0.html\| title=3.2.0 (build OOO320_m12) - Release Notes\| access-date=18 Feb 2013\| quote=Import of password protected Microsoft Office XML files }}</ref>
			* The ] fork of OpenOffice could also write OOXML files.
			* ] from version 2.2 and later was able to import OOXML files.
			* ] is able to import Office Open XML files.
			* ], an OpenOffice.org fork for OS X can import, supported saving to OOXML in 2017, NeoOffice was discontinued in 2024.
			* ], Online and Desktop editors compatible with OOXML and ] files

			Other office products that offer import support for the Office Open XML formats include:
	The most widely used office productivity packages have previously relied on various proprietary ] formats. For users of the binary formats there could an advantage to migrating to an open XML standard that is '''backward compatible''' with the features of previous binary file formats. Office Open XML for this purpose explicitly states as a goal of the format <ref></ref> to preserve investments in existing files and applications
			* ] (included with ])
			* ]
			* ]
			* ]
			* ]
			* ]
			* ]
			* ]
			* ]

			== See also ==
	====Key Benefits Arguments====
			* ]
	ECMA has provided the following key benefits arguments for standardization : High Fidelity Migration to Open Formats, Enhanced Interoperability, Compactness, Low Barriers to Developer Adoption, Integration with Business Data, Internationalization, Room for Innovation, Accessibility, and Long Term Document Preservation. See also
			* ]

			* ]
	====Policy Arguments====
			* ]
	ECMA has provided the following policy arguments in favor of standardization<ref></ref> with respect to Overlap in Scope with ISO/IEC 26300:2006 (ODF): Overlap in Scope of ISO/IEC standards is common and can serve a practical purpose, OpenXML addresses distinct user requirements, ODF and OpenXML are Structured to Meet Different User Requirements, OpenXML and ODF can and do coexist.

	Microsoft attacked ]'s fundamental opposition to the Open XML standardization process<ref></ref>
	:*"Ecma almost unanimously agreed to submit Open XML as a standard for ratification by ISO/IEC JTC1 with only IBM dissenting."
	:*"IBM led a global campaign urging national bodies to ... not even consider Open XML, because ODF had made it through ISO/IEC JTC1 first – in other words, that Open XML should not even be considered on its technical merits because a competing standard had already been adopted. This campaign to stop even the consideration of Open XML in ISO/IEC JTC1 is a blatant attempt to use the standards process to limit choice in the marketplace for ulterior commercial motives – and without regard for the negative impact on consumer choice and technological innovation."

	====Technical Arguments====
	* The use of the Open Packaging specification which allows for Indirection, Chunking and Relative indirection. <ref> {{cite web
	\| url=http://www.oreillynet.com/xml/blog/2007/07/can_a_file_be_odf_and_open_xml.html#comment-1027843
	\| title=(comment on) Can a file be ODF and Open XML at the same time ?
	\| author=Rick Jeliffe
	\| date=2007-07-29
	\| accessdate=2007-08-06
	\| publisher=O'Reilly XML.com }}</ref>
	* Due to ZIP compression files are smaller than the currently widely used binary formats <ref name="ecma_tc45_white paper"/>
	* It supports custom data elements for integration of data specific to an application or an organisation that wants to use the format.
	* It is currently the only open document standard to define spreadsheet formulae.
	* Office Open XML contains alternate representations for the XML schemas and extensibility mechanisms using RELAX NG (ISO/IEC 19757-2) and NVDL (ISO/IEC 19757-4) <ref name="ecma_tc45_white paper"/>
	* OpenXML contains no restriction on image, audio or video types. For example, images can be in Microsoft WMF, GIF, PNG, TIFF, PICT, JPEG or any other image type (§1:14.2.12).
	* Embedded controls can be of any type, such as ] or ] (§1:15.2.8).
	* WordprocessingML font specifications can include font metrics and ] information to assist in finding a substitution font if the original is not available (§3:2.10.5). <ref name="ecma_tc45_white paper"/>
	* Alternate Content Block (§3:2.18.4) A solution to define alternate content (like an image) which can be used in various situations where a consuming application might not be capable of interpreting what a producing application wrote. <ref name="ecma_tc45_white paper"/>
	* Internationalization supporting all kind of features needed for support by multiple nations. For example date representation: In WordprocessingML (§4:2.18.7) and SpreadsheetML (§4:3.18.5), calendar dates can be written using Gregorian (three variants), Hebrew, Hijri, Japanese (Emperor Era), Korean (Tangun Era), Saka, Taiwanese, and Thai formats and for example several internationalization related spreadsheet conversion functions. <ref name="ecma_tc45_white paper"/>
	* Custom XML schema extensibility allowing implementations to the format with features. That can for instance facilitate conversion from other formats and future features that are not part of the official specification yet. <ref name="ecma_tc45_white paper"/>

	===Criticism===
	The Office Open XML standard has been the subject of wide and varied debate in the software industry. Many of the participants in the approval process are generally supportive of eventual ISO standardization, but are unwilling to support the ISO fast track process until their issues are resolved. At 6000 pages long, the specification is difficult to quickly evaluate.<ref>{{ cite web
	\|url=http://community.zdnet.co.uk/blog/0,1000000567,10004805o-2000331777b,00.htm
	\|title=Six thousand pages, one month, no chance...
	\|accessdate=2007-02-03}}
	</ref> A core point of concern is the existence an ISO document format ISO 26300:6000 and a potential overlap of the new Office Open XML format. Most critics suggest Microsoft to adopt ISO 26300:6000 as its default format for future versions of Microsoft Office. Objectors also complain that user confusion regarding the two standards would be even greater because of the similarity of the "Office Open XML" name to both "OpenDocument" and "OpenOffice".<ref name="grokdoc">{{cite web
	\| title=EOOXML objections
	\| url=http://www.grokdoc.net/index.php/EOOXML_objections
	\| publisher=grokdoc
	\| accessdate=2007-01-02
	}}</ref>

	====Criticism by government bodies====
	The US Department of Defense cites several potential problems with the format, including <ref></ref>:
	#Binary information in the standard that would lead to security concerns.
	#The referencing of unexplained backward compatibility modes that might pose a problem for third party implementers.
	#The use of proprietary file formats within the open standard appears to cause potential intellectual property ownership concerns.

	==== Criticism by competitors and free software and open source ====
	The parties contributing in this debate include organizations supporting OpenDocument and advocates of ] and ], <ref> {{cite web
	\| url=http://www.odfalliance.org/resources/OfficeOpenXMLFactSheet.pdf
	\| title=Office Open XML factsheet
	\| author=ODF Alliance
	\| accesdate=2007}} </ref> and companies such as ].
	They have lobbied heavily against the standardization of OOXML in its current form due to technical and legal issues in the format. In addition to several specific issues noted below, an overall premise is that the format was inherently closed in many respects and thus ''a poor candidate for a global standard''.<ref
	name="achieving_openness">{{cite web
	\| url=http://www.onlamp.com/pub/a/onlamp/2007/06/14/achieving-openness-a-closer-look-at-odf-and-ooxml.html
	\| title=Achieving Openness: A Closer Look at ODF and OOXML
	\| author=Sam Hiser
	\| pages=1
	\| format=HTML
	\| publisher=ONLamp.com
	\| date=] ]
	\| accessdate=2007-07-12}}</ref>
	They criticize the duplication of, overlap with, and inability to merge with the OpenDocument Format.

	Various competitors of Microsoft have criticized the ISO standardization of Office Open XML, e.g., to DIS 29500 : the consideration of
	ECMA-376 OOXML for ISO standardization] and .

	==== Legal Uncertainty ====
	* Scope of the Patent Licensing does cover only required features of the standard, but not the entire standard. Specifically Microsoft's Covenant not to sue grants patent use "that are necessary to implement only the required portions of the Covered Specification that are described in detail and not merely referenced in such Specification." Also Microsoft's Open Specification Promise only protects what is explicitly specified in the standard. <ref></ref>

	====Technical Criticisms====
	*Reliance on application-defined behaviors to support important functionality that should be documented or supported via existing standards. For example, book 4 section 6.1.2.19 defines the "equationxml" attribute of "shape" elements, "used to rehydrate an equation using the Office Open XML Math syntax"; however, the "actual format of the contents of this attribute are application-defined".<ref name="grokdoc"/>
	* , a serial date format, is used in SpreadsheetML. The format incorrectly treats 1900 as a ] in order to remain backward compatible with previous versions of ] and in ]. The criticism is twofold; dates before 1/3/1900 cannot be used and the ] standard for the representation of time and date should have been used instead of the serial date format. <ref>{{cite web\|
	first=Joel\|last=Spolsky\|
	authorlink=Joel Spolsky\|
	date=2006-06-16\|
	title=My First BillG Review\|
	work=Joel on Software\|
	url=http://www.joelonsoftware.com/items/2006/06/16.html\|
	accessdate=2007-01-31}}</ref>
	*Use of DrawingML and ] instead of ], and of a new mathematical format instead of ]. MathML and SVG are ] recommendations. VML is deprecated and should only occur in uncommon files converted from the ].
	*Internal inconsistencies and omissions. For example, book 4 section 2.18.4 lists styles such as "apples", "scaredCat", and "heebieJeebies", but does not fully define these styles. Missing properties include height, width, color depth, and orientation.<ref name="grokdoc"/>
	*Inconsistent notations for percentage units. In book 4, section 2.18.85 uses predefined symbols (like "pct15" for 15%) in 5 or 2.5 percent increments, section 2.15.1.95 uses a decimal number giving the percentage, section 2.18.97 uses a number in fiftieths of a percent, and section 5.1.12.41 uses a number in thousandths of a percent.<ref name="grokdoc"/>
	*Inflexible numbering format. For example, book 4 section 2.18.66 describes a numbering format that is fixed to a few countries and contradicts both the W3C ] recommendation and ] ISO 10646 standard.<ref name="grokdoc"/>
	*Non-standard, inflexible ] naming. For example, book 4 sections 3.3.1.61 define a "paperSize" attribute for which values 1 through 68 are predefined standard paper sizes such as A4 paper.<ref name="grokdoc"/>
	*Non-standard language codes and color names.<ref name="grokdoc"/>
	*Non-extensible bitmasks, some elements attributes are defined as bitmasks. For example, book 4 section 2.8.2.16 "sig (Supported Unicode Subranges and Code Pages)" describes the <w:sig> element, the attributes of which are all bitmasks.<ref name="grokdoc"/>
	*Legacy document rendering compatibility is identified using (deprecated) tags. For example, book 4 section 2.15.3.6, "autoSpaceLikeWord95", “useWord97LineBreakRules”, “useWord2002TableStyleRules", and book 4 section 2.15.3.31, "lineWrapLikeWord6", and "suppressTopSpacingWP" for a 16-year-old version of ].<ref name="grokdoc"/>. These items should only occur in OOXML documents that were converted from predecessor Microsoft Office documents.
	* Errors in the spreadsheet formula specifications confirmed by Microsoft<ref> {{cite web
	\| url=http://blogs.msdn.com/brian_jones/archive/2007/07/12/spreadsheet-formula-bugs.aspx
	\| title=Spreadsheet formula bugs
	\| date=2007-07-12
	\| accesdate=2007-07-13
	\| author=Brian Jones
	\| publisher= MSDN blogs }}</ref>.


	OpenOffice.org in Denmark have submitted objections to ECMA 376 to the Danish National Body () <ref>{{cite paper
	\| author =
	\| title = Objections to Ecma 376 from OpenOffice.org in Denmark
	\| version =
	\| publisher = OpenOffice.org in Denmark
	\| date = 2007-06-25
	\| url = http://doc.oooforum.dk/Filer/ISO_kommentar_OpenOffice_org.pdf
	\| format = pdf
	\| accessdate = 2007-07-03}}</ref>. The 22 page submission goes into some detail.

	==References==		==References==
			{{Reflist\|colwidth=30em}}
	{{reflist\|2}}

	== ~~See also~~ ==		==Further reading==
			{{Refbegin\|colwidth=30em}}
	* ]
			* {{cite web
	* ]
			\|url = https://www.ecma-international.org/publications-and-standards/standards/ecma-376/
	* ]
			\|title = Standard ECMA-376: Office Open XML File Formats; 1st edition (December 2006) and 2nd edition (December 2008)
			\|work = ECMA Standards
			\|publisher = ]
			\|access-date = 21 October 2010
			}}
			* {{cite web
			\|url = https://www.iso.org/committee/45374/x/catalogue/
			\|title = JTC 1/SC 34 - Document description and processing languages
			\|work = ]
			\|publisher = ]
			\|access-date = 21 October 2010
			}}
			* {{cite web
			\|url = https://www.iso.org/iso/faqs_isoiec29500
			\|title = FAQs on ISO/IEC 29500
			\|work = ISO News and Media
			\|publisher = ]
			\|access-date = 21 October 2010
			}}
			* {{cite web
			\|url=http://www.adjb.net/post/Microsoft-Fails-the-Standards-Test
			\|title=Microsoft Fails the Standards Test
			\|work=Where is an end of it?
			\|last=Brown
			\|first=Alex
			\|publisher=Alex Brown's weblog
			\|date=31 March 2010
			\|access-date=23 June 2018
			}}
			* {{cite book
			\|title = Office 2003 XML: Integrating Office with the Rest of the World
			\|chapter = Chapter 2: The WordprocessingML Vocabulary
			\|chapter-url = http://oreilly.com/catalog/officexml/chapter/ch02.pdf
			\|first1 = Evan
			\|last1 = Lenz
			\|first2 = Mary
			\|last2 = McRae
			\|first3 = Simon
			\|last3 = St.Laurent
			\|publisher = ]
			\|date = May 2004
			\|isbn = 978-0-596-00538-2
			\|url-access = registration
			\|url = https://archive.org/details/office2003xml00simo
			}}
			* {{cite web
			\|url = https://wiki.openoffice.org/search/?title=Documentation/FAQ/General/How_do_I_open_Microsoft_Office_2007_files%3F
			\|title = How do I open Microsoft Office 2007 files?
			\|work = OpenOffice.org Wiki
			\|publisher = Oracle
			\|date = 7 September 2009
			\|access-date = 21 October 2010
			}}
			* {{cite web
			\|url = http://katana.oooninja.com/w/reference_sample_documents
			\|title = Reference and sample documents
			\|work = OpenOffice.org Ninja
			\|date = 8 December 2008
			\|access-date = 21 October 2010
			\|archive-date = 24 October 2010
			\|archive-url = https://web.archive.org/web/20101024174349/http://katana.oooninja.com/w/reference_sample_documents
			\|url-status = dead
			}}
			* {{cite journal
			\|url = https://papers.ssrn.com/sol3/papers.cfm?abstract_id=1201708
			\|ssrn = 1201708
			\|title = Lost in Translation: Interoperability Issues for Open Standards - ODF and OOXML as Examples
			\|journal = ]
			\|publisher = Social Science Electronic Publishing, Inc
			\|date = September 2008
			\|last1 = Shah
			\|first1 = Rajiv C.
			\|last2 = Kesan
			\|first2 = Jay P.
			}}
			{{Refend}}

	==External links==		==External links==
			{{Commons category\|OOXML}}
	===General Office Open XML===
			*
	* , Microsoft's site for developers
	* Microsoft's site for customers and partners
	* {{PDFlink\|\|1.22 ]<!-- application/pdf, 1282611 bytes -->}}
	* , Wouter van de Vlugt

			{{ISO standards}}
	===OOXML criticism===
			{{Ecma International Standards}}
	* , Wired article on Office Open XML
			{{Microsoft Office}}
	*, includes blog posts critical to OOXML
			{{Office document file formats}}
	*
			{{Document markup languages}}
	*
			{{Authority control}}
	*, writing on open standards
	* blogs on Office Open XML and W3C Accessibility Guidelines.

			]
	=== OOXML support===
			]

			]
	*, blog of Brian Jones who is a Microsoft Office program manager
			]
	* commentary in LinuxWorld by Gary Edwards (member of the OASIS opendocument Technical Committee)
			]
	* commentary in Ars Technica

	===Converters and Tools===
	* that allows you to edit XML parts and validate parts against the Ecma schemas created by Info Support's Wouter van Vugt.
	* developed by .
	* , Open source, server-side creation of Excel 2007 files (SpreadsheetML)
	* for Microsoft Office XP, 2003 and 2007
	* Convert from docx to doc online (non-free conversion)
	* OpenXML Writer is an opensource text editor for creating Office Open XML Wordprocessing files (.docx)
	* Microsoft's official converter for Office 2000, XP and 2003
	* Shareware to convert docx files on Mac and Windows

	]
	]		]
			]
	]		]
	]		]
	]
	]

	]
	]
	]
	]
	]
	]
	]
	]
	]

Latest revision as of 11:23, 28 December 2024

Family of document file formats "docx" redirects here. For other uses, see docx (disambiguation). Not to be confused with OpenDocument, Open Office XML, or Microsoft Office XML formats.

Office Open XML
Office Open XML file formats Open Packaging Conventions Open Specification Promise Office Open XML software Comparison of Office Open XML software
v t e

Office Open XML Document
The OOXML Document icon, as appears on the Microsoft OneDrive web service
Filename extension	.docx, .docm
Internet media type	application/vnd. openxmlformats-officedocument. wordprocessingml. document
Developed by	Microsoft, Ecma, ISO, IEC
Initial release	7 December 2006; 18 years ago (2006-12-07)
Latest release	4th edition 26 October 2016; 8 years ago (2016-10-26)
Type of format	Document file format
Extended from	XML, DOC, WordProcessingML
Standard	ECMA-376, ISO/IEC 29500
Open format?	Yes
Website	ECMA-376, ISO/IEC 29500-1:2016

Office Open XML Presentation

Filename extension	.pptx, .pptm
Internet media type	application/vnd. openxmlformats-officedocument. presentationml. presentation
Developed by	Microsoft, Ecma, ISO, IEC
Initial release	7 December 2006; 18 years ago (2006-12-07)
Latest release	3rd edition 29 June 2011; 13 years ago (2011-06-29)
Type of format	Presentation
Extended from	XML, PPT
Standard	ECMA-376, ISO/IEC 29500
Open format?	Yes
Website	ECMA-376, ISO/IEC 29500:2016

Office Open XML Workbook

Filename extension	.xlsx, .xlsm
Internet media type	application/vnd. openxmlformats-officedocument. spreadsheetml. sheet
Developed by	Microsoft, Ecma, ISO, IEC
Initial release	7 December 2006; 18 years ago (2006-12-07) (as Microsoft Open XML)
Latest release	3rd edition 29 June 2011; 13 years ago (2011-06-29)
Type of format	Spreadsheet
Extended from	XML, XLS, SpreadsheetML
Standard	ECMA-376, ISO/IEC 29500
Open format?	Yes
Website	ECMA-376, ISO/IEC 29500:2016

Office Open XML (also informally known as OOXML) is a zipped, XML-based file format developed by Microsoft for representing spreadsheets, charts, presentations and word processing documents. Ecma International standardized the initial version as ECMA-376. ISO and IEC standardized later versions as ISO/IEC 29500.

Microsoft Office 2010 provides read support for ECMA-376, full support for ISO/IEC 29500 Transitional, and read support for ISO/IEC 29500 Strict. Microsoft Office 2013 and later fully support ISO/IEC 29500 Strict, but do not use it as the default file format because of backwards compatibility concerns.

Background

In 2000, Microsoft released an initial version of an XML-based format for Microsoft Excel, which was incorporated in Office XP. In 2002, a new file format for Microsoft Word followed. The Excel and Word formats—known as the Microsoft Office XML formats—were later incorporated into the 2003 release of Microsoft Office.

Microsoft announced in November 2005 that it would co-sponsor standardization of the new version of their XML-based formats through Ecma International as "Office Open XML". The presentation was made to Ecma by Microsoft's Jean Paoli and Isabelle Valet-Harper.

Standardization process

Main article: Standardization of Office Open XML

Microsoft submitted initial material to Ecma International Technical Committee TC45, where it was standardized to become ECMA-376, approved in December 2006.

This standard was then fast-tracked in the Joint Technical Committee 1 of ISO and IEC. After initially failing to pass, an amended version of the format received the necessary votes for approval as an ISO/IEC Standard as the result of a JTC 1 fast-tracking standardization process that concluded in April 2008. The resulting four-part International Standard (designated ISO/IEC 29500:2008) was published in November 2008 and can be downloaded from the ITTF. A technically equivalent set of texts is published by Ecma as ECMA-376 Office Open XML File Formats—2nd edition (December 2008); they can be downloaded from their website.

The ISO/IEC standardization of Office Open XML was controversial and embittered, with much discussion both about the specification and about the standardization process. According to InfoWorld, "OOXML was opposed by many on grounds it was unneeded, as software makers could use OpenDocument Format (ODF), a less complicated office software format that was already an international standard." The same InfoWorld article reported that IBM (which supports the ODF format) threatened to leave standards bodies that it said allow dominant corporations like Microsoft to wield undue influence. The article further says that Microsoft was accused of co-opting the standardization process by leaning on countries to ensure that it got enough votes at the ISO/IEC for Office Open XML to pass, although it does not specify exactly who accused Microsoft.

Licensing

Under the Ecma International code of conduct in patent matters, participating and approving member organizations of ECMA are required to make their patent rights available on a reasonable and non-discriminatory (RAND) basis.

Holders of patents which concern ISO/IEC International Standards may agree to a standardized license governing the terms under which such patents may be licensed, in accord with the ISO/IEC/ITU common patent policy.

Microsoft, the main contributor to the standard, provided a covenant not to sue for its patent licensing. The covenant received a mixed reception, with some like the Groklaw blog criticizing it, and others such as Lawrence Rosen, (an attorney and lecturer at Stanford Law School), endorsing it.

Microsoft has added the format to their Open Specification Promise in which

Microsoft irrevocably promises not to assert any Microsoft Necessary Claims against you for making, using, selling, offering for sale, importing or distributing any implementation to the extent it conforms to a Covered Specification

This is limited to applications which do not deviate from the ISO/IEC 29500:2008 or Ecma-376 standard and to parties that do not "file, maintain or voluntarily participate in a patent infringement lawsuit against a Microsoft implementation of such Covered Specification". The Open Specification Promise was included in documents submitted to ISO/IEC in support of the ECMA-376 fast-track submission. Ecma International asserted that, "The OSP enables both open source and commercial software to implement ".

Versions

The Office Open XML specification exists in several versions.

ECMA-376 1st edition (2006)

The ECMA standard is structured in five parts to meet the needs of different audiences.

Part 1. Fundamentals

Vocabulary, notational conventions and abbreviations
Summary of primary and supporting markup languages
Conformance conditions and interoperability guidelines
Constraints within the Open Packaging Conventions that apply to each document type

Part 2. Open Packaging Conventions

The Open Packaging Conventions (OPC), for the package model and physical package, is defined and used by various document types in various applications from multiple vendors.
It defines core properties, thumbnails, digital signatures, and authorizations & encryption capabilities for parts or all of the contents in the package.
XML schemas for the OPC are declared as XML Schema Definitions (XSD) and (non-normatively) using RELAX NG (ISO/IEC 19757-2)

Part 3. Primer

Informative (non-normative) introduction to WordprocessingML, SpreadsheetML, PresentationML, DrawingML, VML and Shared MLs, providing context and illustrating elements through examples and diagrams
Describes the custom XML data-storing facility within a package to support integration with business data

Part 4. Markup Language Reference

Contains the reference material for WordprocessingML, SpreadsheetML, PresentationML, DrawingML, Shared MLs and Custom XML Schema, defining every element and attribute including the element hierarchy (parent/child relationships)
XML schemas for the markup languages are declared as XSD and (non-normatively) using RELAX NG
Defines the custom XML data-storing facility

Part 5. Markup Compatibility and Extensibility

Describes extension facilities of OpenXML documents and specifies elements & attributes through which applications can operate across different extensions.

Later versions of the ECMA-376 standard are aligned and technically equivalent to the corresponding ISO standard.

ISO/IEC 29500:2008

The ISO/IEC standard is structured into four parts: Parts 1, 2 and 3 are independent standards; for example, Part 2, specifying Open Packaging Conventions, is used by other file formats including XPS and Design Web Format. Part 4 is to be read as a modification to Part 1, which it requires.

A technically equivalent set of texts is also published by Ecma as ECMA-376 2nd edition (2008).

Part 1. Fundamentals & Markup Language Reference

Consisting of 5560 pages, this part contains:

Conformance definitions
Reference material for the XML document markup languages defined by the Standard
XML schemas for the document markup languages declared using XSD and (non-normatively) RELAX NG
Defines the foreign markup facilities

Part 2. Open Packaging Conventions

Consisting of 129 pages, this part contains:

A description of the Open Packaging Conventions (package model, physical package)
Core properties, thumbnails and digital signatures
XML schemas for the OPC are declared using XSD and (non-normatively) RELAX NG

Part 3. Markup Compatibility and Extensibility

Consisting of 40 pages, this part contains:

A description of extensions: elements & attributes which define mechanisms allowing applications to specify alternative means of negotiating content
Extensibility rules are expressed using NVDL

Part 4. Transitional Migration Features

Consisting of 1464 pages, this part contains:

Legacy material such as compatibility settings and the graphics markup language VML
A list of syntactic differences between this text and ECMA-376 1st Edition

The standard specifies two levels of document & application conformance, strict and transitional, for each of WordprocessingML, PresentationML and SpreadsheetML, and also specifies applications' descriptions of base and full.

Compatibility between versions

The intent of the changes from ECMA-376 1st Edition to ISO/IEC 29500:2008 was that a valid ECMA-376 document would also be a valid ISO 29500 Transitional document; however, at least one change introduced at the BRM—refusing to allow further values for xsd:boolean—had the effect of breaking backwards-compatibility for most documents. A fix for this had been suggested to ISO/IEC JTC 1/SC 34/WG 4, and was approved in June 2009 as a recommendation for the first revision to Office Open XML.

Applications capable of reading documents compliant to ECMA-376 Edition 1 would regard ISO/IEC 29500-4 Transitional documents containing ISO 8601 dates as corrupt.

Application support

Main article: List of software that supports Office Open XML

Some older versions of Microsoft Word and Microsoft Office are able to read and write .docx files after installation of the free compatibility pack provided by Microsoft, although some items, such as equations, are converted into images that cannot be edited.

Starting with Microsoft Office 2007, the Office Open XML file formats have become the default file format of Microsoft Office. However, due to the changes introduced in the Office Open XML standard, Office 2007 is not wholly in compliance with ISO/IEC 29500:2008. Office 2010 includes support for opening documents of the ISO/IEC 29500:2008-compliant version of Office Open XML, but it can only save documents conforming to the transitional, not the strict, schemas of the specification. Note that the intent of the ISO/IEC is to allow the removal of the transitional variant from the ISO/IEC 29500 standard. Microsoft Office 2013 and later fully support ISO/IEC 29500 Strict, but do not use it as the default file format because of backwards compatibility concerns.

The ability to read and write Office Open XML format is, however, not limited to Microsoft Office; other office products are also able to read & write this format:

Collabora Online for Online, Mobile and Desktop apps are able to open and save Office Open XML files.
SoftMaker Office 2010 is able to read and write DOCX and XLSX files in its word processor & spreadsheet applications.
LibreOffice is able to open and save Office Open XML files.
Apache OpenOffice from version 3.0 can import Office Open XML files but not save them. Version 3.2 improved this feature with read support even for password-protected Office Open XML files.
The Go-oo fork of OpenOffice could also write OOXML files.
KOffice from version 2.2 and later was able to import OOXML files.
Calligra Suite is able to import Office Open XML files.
NeoOffice, an OpenOffice.org fork for OS X can import, supported saving to OOXML in 2017, NeoOffice was discontinued in 2024.
OnlyOffice, Online and Desktop editors compatible with OOXML and OpenDocument files

Other office products that offer import support for the Office Open XML formats include:

References

"application/vnd.openxmlformats-officedocument.wordprocessingml.document". www.iana.org. IANA. 2011-02-25. Retrieved 2024-11-03.
Klaus-Peter Eckert; Jan Henrik Ziesing; Ucheoma Ishionwu. "Document Interoperability: Open Document Format and Office Open XML" (PDF). Fraunhofer Verlag. p. 90.
"application/vnd.openxmlformats-officedocument.presentationml.presentation". www.iana.org. IANA. 2011-03-14. Retrieved 2024-11-03.
"vnd.openxmlformats-officedocument.spreadsheetml.sheet". www.iana.org. IANA. 2011-03-16. Retrieved 2024-11-03.
"The Document Foundation, LibreOffice and OOXML". The Document Foundation. Retrieved 2016-03-22.
"Overview of the XML file formats in Office 2010". Office 2010 Resource Kit. Microsoft. 5 August 2011.
^ "XML file name extension reference for Office 2013". Office 2013 Resource Kit. Microsoft. 26 December 2016.
^ "XLSX Strict (Office Open XML), ISO 29500-1:2008-2016". Library of Congress. Retrieved 2018-09-09.
Brian Jones (2007-01-25). "History of office XML formats (1998–2006)". MSDN blogs. Retrieved 2020-12-31.
"Microsoft Co-Sponsors Submission of Office Open XML Document Formats to Ecma International for Standardization". Microsoft. 2005-11-21.
Casson and Ryan, Open Standards, Open Source Adoption in the Public Sector, and Their Relationship to Microsoft’s Market Dominance
Microsoft hands over Office XML specs to Ecma
"Slides presented by the TC45 committee to Ecma International". Archived from the original on 2011-10-21. Retrieved 2011-06-08.
"Ecma International approves Office Open XML standard". Ecma International. 2006-12-07.
"ISO/IEC DIS 29500 receives necessary votes for approval as an International Standard". ISO. 2008-04-02.
ISO/IEC (2008-11-18). "Publication of ISO/IEC 29500:2008, Information technology—Office Open XML formats". ISO. Archived from the original on 2009-07-06. Retrieved 2008-11-19.
"Freely Available Standards". ITTF (ISO/IEC). 2008-11-18. Retrieved 2023-09-26.
^ "Standard ECMA-376". Ecma-international.org. Retrieved 2009-05-19.
^ Kirk, Jeremy (19 November 2008). "ISO publishes Office Open XML specification". InfoWorld. Retrieved 12 June 2010.
"Norwegian standards body implodes over OOXML controversy". Ars Technica. 3 October 2008.
"Code of Conduct in Patent Matters". Ecma International.
"ISO/IEC/ITU common patent policy".
"Microsoft's Open Specification Promise Eases Web Services Patent Concerns". September 12, 2006. Retrieved 2015-04-18.
"2 Escape Hatches in MS's Covenant Not to Sue". Groklaw. December 4, 2005.
Berlind, David (November 28, 2005). "Top open source lawyer blesses new terms on Microsoft's XML file format". ZDNet. Retrieved 2007-01-27.
"Microsoft Open Specification Promise". Microsoft. 2007-02-15. Retrieved 2015-04-18.
"Ecma formal publications". Ecma International. Ecma Standards and Technical Reports are made available to all interested persons or organizations, free of charge and licensing restrictions
"Microsoft Open Specification Promise". Microsoft.com.
"Licensing conditions that Microsoft offers for Office Open XML". Jtc1sc34.org. 2006-12-20. Retrieved 2009-05-19.
"Microsoft Word — Responses to Comments and Perceived Contradictions.doc" (PDF). Retrieved 2009-09-16.
"ISO search for "29500"". International Organization for Standardization. 2009-06-05.
"Re-introducing on/off-values to ST-OnOff in OOXML Part 4". Archived from the original on 2009-06-26. Retrieved 2009-09-29.
"OOXML and Office 2007 Conformance: a Smoke Test". Archived from the original on 2010-04-28. Retrieved 2009-09-29.
"Minutes of the Copenhagen Meeting of ISO/IEC JTC1/SC34/WG4" (PDF). 2009-06-22. Archived from the original (PDF) on 2014-05-12. Retrieved 2009-09-29. page 15
"ISO/IEC 29500-4:2008/Draft Amd2:2011 - Draft - Information technology — Document description and processing languages — Office Open XML File Formats — Part 4: Transitional Migration Features - AMENDMENT 2". 2011-03-02. Archived from the original (PDF) on 2014-05-12. Retrieved 2011-04-04.
"Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats (Version 3)". Microsoft. 2007-06-18. Retrieved 2018-06-23.
Open a Word 2007 document in an earlier version of Word - Word - Office.com. Office.microsoft.com. Retrieved on 2013-07-17.
"Microsoft Expands List of Formats Supported in Microsoft Office". Microsoft. Retrieved 2008-05-21.
"Microsoft's future lies somewhere beyond the Vista by Evansville Courier & Press". Courierpress.com. Archived from the original on 2014-07-10. Retrieved 2009-05-19.
"Rivals Set Their Sights on Microsoft Office: Can They Topple the Giant? - Knowledge@Wharton". Knowledge.wharton.upenn.edu. Retrieved 2009-05-19.
Andy Updegrove (21 May 2008). "Microsoft Office 2007 to Support ODF — and not OOXML". ConsortiumInfo.org. Archived from the original on 2008-05-23. Retrieved 2009-05-19.
"ISO OOXML convener: Microsoft's format "heading for failure"". Ars Technica. 2 April 2010.
^ Brown, Alex (31 March 2010). "Microsoft Fails the Standards Test". Where is an end of it?. Alex Brown's weblog. Retrieved 23 June 2018.
"Collabora Online 6.4.0-released". 2 November 2020.
"LibreOffice OOXML". Retrieved 22 March 2012.
"OpenOffice.org 3.0 New Features". 2008-10-13. Retrieved 2009-10-24.
"OpenOffice.org 3.2 New Features". 2010. Retrieved 2010-11-13.
Scott Gilbertson (13 February 2010). "OpenOffice 3.2 - now with less Microsoft envy". The Register. Retrieved 18 Feb 2013. the ability to open password-protected Word, Excel, and PowerPoint files
"3.2.0 (build OOO320_m12) - Release Notes". Retrieved 18 Feb 2013. Import of password protected Microsoft Office XML files

External links

ISO/IEC 29500 standards

v t e ISO standards by standard number
List of ISO standards – ISO romanizations – IEC standards
1–9999	1 2 3 4 6 7 9 16 17 31 -0 -1 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 68-1 128 216 217 226 228 233 259 261 262 302 306 361 500 518 519 639 -1 -2 -3 -5 -6 646 657 668 690 704 732 764 838 843 860 898 965 999 1000 1004 1007 1073-1 1073-2 1155 1413 1538 1629 1745 1989 2014 2015 2022 2033 2047 2108 2145 2146 2240 2281 2533 2709 2711 2720 2788 2848 2852 2921 3029 3103 3166 -1 -2 -3 3297 3307 3601 3602 3864 3901 3950 3977 4031 4157 4165 4217 4909 5218 5426 5427 5428 5725 5775 5776 5800 5807 5964 6166 6344 6346 6373 6385 6425 6429 6438 6523 6709 6943 7001 7002 7010 7027 7064 7098 7185 7200 7498 -1 7637 7736 7810 7811 7812 7813 7816 7942 8000 8093 8178 8217 8373 8501-1 8571 8583 8601 8613 8632 8651 8652 8691 8805/8806 8807 8820-5 8859 -1 -2 -3 -4 -5 -6 -7 -8 -8-I -9 -10 -11 -12 -13 -14 -15 -16 8879 9000/9001 9036 9075 9126 9141 9227 9241 9293 9314 9362 9407 9496 9506 9529 9564 9592/9593 9594 9660 9797-1 9897 9899 9945 9984 9985 9995
10000–19999	10006 10007 10116 10118-3 10160 10161 10165 10179 10206 10218 10279 10303 -11 -21 -22 -28 -238 10383 10585 10589 10628 10646 10664 10746 10861 10957 10962 10967 11073 11170 11172 11179 11404 11544 11783 11784 11785 11801 11889 11898 11940 (-2) 11941 11941 (TR) 11992 12006 12052 12182 12207 12234-2 12620 13211 -1 -2 13216 13250 13399 13406-2 13450 13485 13490 13567 13568 13584 13616 13816 13818 14000 14031 14224 14289 14396 14443 14496 -2 -3 -6 -10 -11 -12 -14 -17 -20 14617 14644 14649 14651 14698 14764 14882 14971 15022 15189 15288 15291 15398 15408 15444 -3 -9 15445 15438 15504 15511 15686 15693 15706 -2 15707 15897 15919 15924 15926 15926 WIP 15930 15938 16023 16262 16355-1 16485 16612-2 16750 16949 (TS) 17024 17025 17100 17203 17369 17442 17506 17799 18004 18014 18181 18245 18629 18916 19005 19011 19092 -1 -2 19114 19115 19125 19136 19407 19439 19500 19501 19502 19503 19505 19506 19507 19508 19509 19510 19600 19752 19757 19770 19775-1 19794-5 19831
20000–29999	20000 20022 20121 20400 20802 20830 21000 21001 21047 21122 21500 21827 22000 22275 22300 22301 22395 22537 23000 23003 23008 23009 23090-3 23092 23094-1 23094-2 23270 23271 23360 23941 24517 24613 24617 24707 24728 25178 25964 26000 26262 26300 26324 27000 series 27000 27001 27002 27005 27006 27729 28000 29110 29148 29199-2 29500
30000+	30170 31000 32000 37001 38500 39075 40500 42010 45001 50001 55000 56000 80000
Category

v t e Standards of Ecma International
Application interfaces	ANSI escape code APIW Common Language Infrastructure Office Open XML OpenXPS
File systems (tape)	Advanced Intelligent Tape DDS DLT Super DLT Linear Tape-Open (Ultrium-1) VXA
File systems (disk)	CD-ROM CD File System (CDFS) FAT FAT12 FAT16 FAT16B FD UDF Ultra Density Optical Universal Media Disc Holographic Versatile Disc
Graphics	Universal 3D
Programming languages	C++/CLI C# Eiffel JavaScript (E4X, ECMAScript) Dart Minimal BASIC Full BASIC
Radio link interfaces	NFC UWB
Other	ECMA-35 JSON
List of Ecma standards (1961 – present)

Microsoft 365

History
A product of Microsoft

Microsoft Office

Windows	1.x 3.0 4.x 95 97 2000 XP 2003 2007 2010 2013 2016 2019 2021 2024
Mac	3.0 4.2 98 2001 X 2004 2008 2011 2016 2019 2021 2024

Applications
(list)

Desktop	Access Excel OneNote Outlook PowerPoint Project Publisher Teams Visio Word
Server	SharePoint Excel Services Project Server Search Server Skype for Business Server
Mobile	Excel Lens OneDrive OneNote Outlook PowerPoint Remote Sway Teams Word
Web	Bookings Delve Excel Forms Loop OneDrive OneNote Outlook on the web Outlook.com Planner PowerPoint Project SharePoint Stream Sway Teams To Do Video Viva Engage Word
Discontinued	Discontinued shared tools Accounting Classroom Docs.com Entourage FrontPage InfoPath InterConnect Kaizala Liquid Motion Live Meeting Lync Mail Office Assistant Office Live OneDrive Groups PerformancePoint Server Photo Editor PhotoDraw Picture Manager Project Portfolio Server Ribbon Hero Schedule+ SharePoint Designer SharePoint Workspace Skype for Business Snapshot Viewer for Access Vizact Word Viewer

Technologies

Category

v t e Multi-purpose office document file formats
Editable document formats	Compound Document Format Microsoft Office XML formats MO:DCA Office Open XML Open Document Architecture OpenDoc OpenDocument OpenOffice.org XML Revisable-Form Text Rich Text Format Uniform Office Format Word document
Fixed document formats	DjVu Envoy Open XML Paper Specification Portable Document Format
Related topics	Character encoding ASCII Unicode TeX

v t e Document markup languages
Office suite	Compound Document Format OOXML SpreadsheetML PresentationML WordprocessingML ODF UOF
Well-known	HTML XHTML MathML RTF TeX LaTeX Markdown
Lesser-known	AmigaGuide AsciiDoc BBCode CML C-HTML ConTeXt CrossMark DITA DocBook EAD Enriched text FHTML GML GuideML HDML HyTime IPF LilyPond LinuxDoc Lout MIF MAML MEI MusicXML OMDoc OpenMath Org-mode POD ReStructuredText RTML RFT S1000D Setext TEI Texinfo troff Wikitext WML WapTV XAML
List of document markup languages

Categories: