Misplaced Pages

Office Open XML: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 12:03, 30 September 2009 editHAl (talk | contribs)3,031 edits Undid revision 317050097 by Scientus (talk). Reverting repeated disruptive edits and vandalism by user:Scientus.← Previous edit Latest revision as of 11:23, 28 December 2024 edit undoSerethSurkow (talk | contribs)2 editsm Archive.org link added 
(745 intermediate revisions by more than 100 users not shown)
Line 1: Line 1:
{{Short description|Family of document file formats}}
{{distinguish2|] (a deprecated format used by early versions of OpenOffice.org), or ] (deprecated formats used by earlier versions of Microsoft Office)}}
{{Redirect|docx}}
{{Distinguish|OpenDocument|Open Office XML|Microsoft Office XML formats}}
{{stack|
{{Office Open XML}}
{{Infobox file format {{Infobox file format
| name = Office Open XML Document | name = Office Open XML Document
| icon = ] | icon = .docx icon.svg
| logo = | iconcaption = The OOXML Document icon, as appears on the ] web service
| screenshot = | screenshot =
| caption = | caption =
| extension = <code>.docx</code> or <code>.docm</code> | extension = .docx, .docm
| mime = application/vnd.<br />openxmlformats-officedocument.<br />wordprocessingml.<br />document<ref name="mimetype">{{ cite web | url = http://technet.microsoft.com/en-us/library/cc179224.aspx | title = Register file extensions on third party servers | author = Microsoft | date = | accessdate = 2009-09-04 | publisher = microsoft.com }}</ref> | 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 = | type code =
| uniform type = | uniform type =
| magic = | magic =
| owner = ], ], ]/] | owner = ], ], ], ]
| released = | released = {{Start date and age|2006|12|07|df=yes}}
| latest release version = | latest release version = 4th edition
| latest release date = | latest release date = {{Start date and age|2016|10|26|df=yes}}
| genre = ] | genre = ]
| container for = | container for =
Line 21: Line 25:
| extended to = | extended to =
| standard = ECMA-376, ISO/IEC 29500 | standard = ECMA-376, ISO/IEC 29500
| url = , | 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 {{Infobox file format
| name = Office Open XML Presentation | name = Office Open XML Presentation
| icon = ] | icon = .pptx icon.svg
| logo = | logo =
| screenshot = | screenshot =
| caption = | caption =
| extension = <code>.pptx</code> | extension = .pptx, .pptm
| mime = application/vnd.<br />openxmlformats-officedocument.<br />presentationml.<br />presentation<ref name="mimetype" /> | 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 = | type code =
| uniform type = | uniform type =
| magic = | magic =
| owner = ], ], ]/] | owner = ], ], ], ]
| released = | released = {{Start date and age|2006|12|07|df=yes}}
| latest release version = | latest release version = 3rd edition
| latest release date = | latest release date = {{Start date and age|2011|06|29|df=yes}}
| genre = ] | genre = ]
| container for = | container for =
Line 44: Line 53:
| extended to = | extended to =
| standard = ECMA-376, ISO/IEC 29500 | standard = ECMA-376, ISO/IEC 29500
| url = , | url = ,
| open = Yes
}} }}
{{Infobox file format {{Infobox file format
| name = Office Open XML Workbook | name = Office Open XML Workbook
| icon = ] | icon = .xlsx icon.svg
| logo = | logo =
| screenshot = | screenshot =
| caption = | caption =
| extension = <code>.xlsx</code> | extension = .xlsx, .xlsm
| mime = application/vnd.<br />openxmlformats-officedocument.<br />spreadsheetml.<br />sheet<ref name="mimetype" /> | 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 = | type code =
| uniform type = | uniform type =
| magic = | magic =
| owner = ], ], ]/] | owner = ], ], ], ]
| released = | released = {{Start date and age|2006|12|07|df=yes}} (as Microsoft Open XML)
| latest release version = | latest release version = 3rd edition
| latest release date = | latest release date = {{Start date and age|2011|06|29|df=yes}}
| genre = ] | genre = ]
| container for = | container for =
Line 67: Line 77:
| extended to = | extended to =
| standard = ECMA-376, ISO/IEC 29500 | standard = ECMA-376, ISO/IEC 29500
| url = , | url = ,
| open = Yes
}}
}} }}
'''Office Open XML''' (also referred to as '''OOXML''', or '''Open XML''') is a ] for representing ]s, ]s, ]s and ] documents. An Office Open XML file is a ]-compatible ] package containing ] documents and other resources. Office Open XML standard is an ]/] standard; the specification is freely available from ISO for individual and non-redistributable use only.<ref name=free_ISO>{{ cite web | url = http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html | title = Freely Available Standards | publisher = ITTF (ISO) | date = 2008-11-18 }}</ref> or freely to copy without any restriction from the ] website.{{Citation needed|date=September 2009}}

Microsoft submitted the specification to ] Technical Committee TC45, where it was standardized as ECMA-376 in 2006.

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=http://www.iso.org/iso/pressrelease.htm?refid=Ref1123
| title=ISO/IEC DIS 29500 receives necessary votes for approval as an International Standard
| date=2008-04-02
| publisher=ISO}}</ref> and 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
| accessdate=2008-11-19
| publisher=ISO
| author=ISO/IEC}}</ref> and as ECMA-376 Office Open XML File Formats - 2<sup>nd</sup> edition (December 2008). ISO/IEC 29500:2008 is a 4 part standard specification that can be freely downloaded.<ref>{{cite web
| url=http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html
| title=Freely Available Standards
| publisher=ITTF (ISO)
| date=2008-11-18}}</ref> resulting in ] ISO/IEC 29500:2008,<ref name="ISOIECapproval">{{ cite web | url = http://www.iso.org/iso/pressrelease.htm?refid=Ref1123 | title = ISO/IEC DIS 29500 receives necessary votes for approval as an International Standard | date = 2008-04-02 | publisher = ISO }}</ref> 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&nbsp;— Office Open XML formats | date = 2008-11-18 | accessdate = 2008-11-19 | publisher = ISO | author = ISO/IEC }}</ref> and as ECMA-376 Office Open XML File Formats - 2nd edition (December 2008). ISO/IEC 29500:2008 is a 4 part standard specification.<ref name=free_ISO/><ref name="StandardECMA376">{{ cite web | url = http://www.ecma-international.org/publications/standards/Ecma-376.htm | title = Standard ECMA-376 | publisher = Ecma-international.org | accessdate = 2009-05-19 }}</ref>


'''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.
Starting with ], the Office Open XML file formats (ECMA-376) have become the default file format of ].<ref>{{ 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 | accessdate = 2009-05-19 }}</ref><ref>{{ 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 | accessdate = 2009-05-19}}</ref> However, due to the changes introduced in a later version, Office 2007 is not entirely in compliance with ISO/IEC 29500:2008.<ref name=ODFA_communityone>{{ cite web | url = http://www.odfalliance.org/resources/IssueBriefImplementations.pdf | title = OOXML Implementations: A Community of One | publisher = ODF Alliance | date = 2008-02-20 | accessdate = 2009-05-19 }}</ref><ref name="SupportedFormats">{{ cite web | url = http://www.microsoft.com/Presspass/press/2008/may08/05-21ExpandedFormatsPR.mspx | title = Microsoft Expands List of Formats Supported in Microsoft Office | publisher = Microsoft.com | date = 2008-05-21 | accessdate = 2009-05-19 }}</ref><ref name=cwO14>{{ cite web | last = Lai | first = Eric | url = http://www.computerworld.com/action/article.do?command=viewArticleBasic&taxonomyName=Protocols+and+Standards&articleId=9089258&taxonomyId = 141&pageNumber=1 | title = FAQ: Office 14 and Microsoft's support for ODF | publisher = Computerworld.com | date = 2008-05-27 | accessdate = 2009-05-19 }}</ref><ref name=notOOXML>{{ cite web | author = Andy Updegrove | url = http://consortiuminfo.org/standardsblog/article.php?story=20080521092930864 | title = Microsoft Office 2007 to Support ODF&nbsp;— and not OOXML | publisher = ConsortiumInfo.org | accessdate = 2009-05-19 }}</ref> Microsoft has stated that the planned ] will be the first version to implement the ISO/IEC 29500:2008 compliant version of Office Open XML.


] 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>
== Background ==


==Background==
Prior to the ], the core applications of the ] software suite (primarily ], ], and ]) by default stored their data in ]s. Historically, these files were difficult for other applications to interoperate with, due to the lack of publicly available information. Before 2007 ] offered these binary format specifications under a royalty-free license and since 2007 the formats are directly downloadable from their site under a 'covenant not to sue' as part of its ].<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><ref>{{cite web
| url=http://www.microsoft.com/interop/docs/officebinaryformats.mspx
| title=Microsoft Office Binary (doc, xls, ppt) File Formats
| publisher=Microsoft
| date=2008-02-15
| accessdate=2008-04-05}}</ref> Due to Microsoft previously keeping their file formats secret, other office software had great difficulty obtaining full levels of interoperability.
Microsoft came under increasing pressure to adopt an open file format, in particular several nations adopted rules that official documents should be in an open format.


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 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.
| 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> The Excel and Word formats&nbsp;– known as the ]&nbsp;– 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 ] 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>
In May 2004, governments and the ] recommended to Microsoft that they publish and standardize their XML Office formats through a standardization organization.<ref name="ooxmlhistory" /><ref>{{cite web
| 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&nbsp;— European eGovernment Services
| date=2004-05-25
| accessdate=2007-07-30}}</ref> Microsoft announced in November 2005 that it would standardize the new version of their XML-based formats through ], as "Ecma Office Open XML".<ref>{{cite web
| url=http://www.microsoft.com/presspass/features/2005/nov05/11-21Ecma.mspx
| title=Microsoft Co-Sponsors Submission of Office Open XML Document Formats to Ecma International for Standardization
| publisher=Microsoft
| date=2005-11-21}}</ref>


== Standardization == ==Standardization process==
{{Main|Standardization of Office Open XML}} {{Main|Standardization of 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>
Office Open XML was standardized first by ] as ECMA-376 (published 7 December 2006). This standard was then fast-tracked in the ] of ] and ] where it became an International Standard, ISO/IEC 29500:2008 (published November 2008).<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=December 7, 2006
| accessdate=2006-12-08
| publisher=]
}}</ref><ref>{{cite web
|url=http://www.ecma-international.org/activities/General/presentingecma.ppt
|title=Ecma International
|date=2009-06
|publisher=Ecma International}}</ref><ref>{{cite web
|url=http://www.ecma-international.org/publications/index.html
|title=Ecma formal publications
|publisher=Ecma-international.org
|accessdate=2009-05-19}}</ref><ref>{{cite web
|url=http://www.xmlopen.org/ooxml-wiki/resources/BSI_OOXML_2007_05.pdf
|title=Office OpenXML
|author=Adam Farquhar
|date=2007-05
|publisher=Britisch Standard institute}}</ref><ref>{{cite web
|url=http://www.mass.gov/Aitd/docs/policies_standards/etrmv4dot0/etrmv4dot0information.rtf
|title=Massachusetts Enterprise Technical Reference Model&nbsp;– Version 4.0
|publisher=Commonwealth of Massachusetts
|date=2007-08-01}}</ref><ref>http://www.itscj.ipsj.or.jp/sc34/open/1026.pdf</ref><ref>{{cite journal
| title = Office Open XML wird als weltweiter ISO/IEC-Standard anerkannt
| journal = ntz Fachzeitschrift für Informations- und Kommunikationstechnik
| publisher = VDE-Verlag
| issue = 3-4
| page = 10
| location = Berlin
| year = 2008
| url = http://www.vde-verlag.de/ntz.html
| issn = 0948-728X}}</ref><ref>{{cite web
|url=http://www.techtree.com/India/News/ISO_puts_Microsofts_OOXML_Standard_on_Hold/551-90178-580.html
|title=India > News > Software > ISO puts Microsoft's OOXML Standard on Hold
|publisher=Techtree.com
|date=2008-06-12
|accessdate=2009-05-19}}</ref>


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>
== Licensing ==
=== Availability of the standard ===
] provides free access to the specifications that also "can be freely copied by all interested parties without restrictions".<ref>{{cite web
|url=http://www.ecma-international.org/memento/index.html
|title=What is Ecma International
|publisher=Ecma International}}</ref>


The ISO/IEC standardization of Office Open XML was controversial and embittered,<ref name="infoworld-embittered">{{cite news
ISO has added the document to its "list of freely available standards"; ISO permits everyone to download the standard for free also allowing them to print one copy of the standard and states that users may not ].<ref>{{cite web
| last=Kirk
|url=http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html
| first=Jeremy
|title=Freely Available Standards
| title=ISO publishes Office Open XML specification
|publisher=ISO
| newspaper=]
|accessdate={{date|2009-09-22}}}}</ref>
| date=19 November 2008
| 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" />


==Licensing==
=== Royalty free licensing on patented technology ===
Microsoft, the biggest contributor to the standard, has provided additional royalty free licensing for any possible technologies required to implement or use Office Open XML.
Under the Ecma International code of conduct in patent matters,<ref>{{cite web
| url=http://www.ecma-international.org/memento/codeofconduct.htm
| title=Code of Conduct in Patent Matters
| publisher=Ecma International}}</ref> participating and approving member organisations of ECMA are required to make available their patent rights on a ] (RAND) basis. While making patent rights available on a RAND basis is considered a common minimum patent condition for a standard, international standardization has a clear preference for royalty-free patent licensing.


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, a main contributor to the 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> for its patent licensing. The covenant received a mixed reception, with some (like the ] ]) 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 ], an attorney and lecturer at ]) 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=November 28, 2005
| accessdate=2007-01-27
| publisher=ZDNet
}}</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>
Microsoft has added the format to their '']''<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> in which


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>
<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>


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
subject to certain restrictions. Office Open XML can therefore be used under the ''Covenant Not to Sue'' or the ''Open Specification Promise'' which both are forms of royalty free licensing.


<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>
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=http://www.jtc1sc34.org/repository/0810c.htm |title=Licensing conditions that Microsoft offers for Office Open XML |publisher=Jtc1sc34.org |date=2006-12-20 |accessdate=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&nbsp;— Responses to Comments and Perceived Contradictions.doc |format=PDF |date= |accessdate=2009-09-16}}</ref>


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>
== File format and structure ==
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&nbsp;— Responses to Comments and Perceived Contradictions.doc | access-date = 2009-09-16}}</ref>
Office Open XML uses a file package conforming to the ]. This format uses mechanisms from the ] and contains the individual files that form the basis of the document. In addition to Office markup, the package can also include embedded files such as images, videos, or other documents.


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


The Office Open XML specification exists in several versions.
The primary markup languages are:
* WordprocessingML for word-processing
* SpreadsheetML for spreadsheets
* PresentationML for presentations

Shared markup language materials include:
* Office Math Markup Language (])
* ] used for vector drawing, charts, and for example, text art (additionally, though deprecated, ] is supported for drawing)
* Extended properties
* Custom properties
* Variant Types
* Custom XML data properties
* Bibliography

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

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

==== Office MathML (OMML) ====

Office Math Markup Language is a mathematical markup language which can be embedded in WordprocessingML, with intrinsic support for including word processing markup like revision markings,<ref>{{cite web
| url=http://idippedut.dk/post/2008/01/Do-your-math---OOXML-and-OMML.aspx
| title=Do your math&nbsp;— OOXML and OMML
| date=2008-01-29
| accessdate=2008-02-12
| author=Jesper Lund Stocholm
| publisher=A Mooh Point blog}}</ref> 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 OMML format is different from the ] (W3C) ] recommendation that does not support those office features, but is partially compatible<ref>{{cite web
| url=http://dpcarlisle.blogspot.com/2007/04/xhtml-and-mathml-from-office-20007.html
| title=XHTML and MathML from Office 2007
| author=David Carlisle
| publisher=David Carlisle
| date=2007-05-09
| accessdate=2007-09-20}}</ref> through ].

The following Office MathML example defines the ]: <math>\frac{\pi}{2}</math>

<source lang="xml">
<m:oMathPara>
<m:oMath>
<m:f>
<m:num><m:r>
<m:t>π</m:t>
</m:r></m:num>
<m:den><m:r>
<m:t>2</m:t>
</m:r></m:den>
</m:f>
</m:oMath>
</m:oMathPara>
</source>

==== DrawingML ====<!-- ] links to here -->
]

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

The DrawingML table is the third table model in Office Open XML (next to the table models in WordprocessingML and SpreadsheetML) and is optimized for graphical effects and its main use is in presentations created with PresentationML markup.
DrawingML contains graphics effects (like shadows and reflection) that can be used on the different graphical elements that are used in DrawingML.
In DrawingML you can also create 3d effects, for instance to show the different graphical elements through a flexible camera viewpoint.
It is possible to create separate DrawingML theme parts in an Office Open XML package. These themes can then be applied to graphical elements throughout the Office Open XML package.<ref>{{cite web
| url=http://openxmldeveloper.org/articles/1970.aspx
| title=Open XML Explained e-book
| author=Wouter Van Vugt
| date=2008-11-01
| accessdate=2007-09-14
| publisher=Openxmldeveloper.org}}</ref>

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

A DrawingML graphic's dimensions are specified in ]s (EMUs). It is so called because it allows an exact common representation of dimensions originally in either English or Metric units. This unit is defined as 1/360,000 of a ] and thus there are 914,400 EMUs per ], and 12,700 EMUs per ]. This unit was chosen so that integers can be used to accurately represent most dimensions encountered in a document. Floating point cannot accurately represent a fraction that is not a sum of powers of two and the error is magnified when the fractions are added together many times, resulting in misalignment. As an inch is exactly 2.54 centimeters, or 127/50, 1/127&nbsp;inch is an integer multiple of a power-of-ten fraction of the meter (2×10<sup>−4</sup>&nbsp;m). To accurately represent (with an integer) 1&nbsp;μm = 10<sup>−6</sup>&nbsp;m, a divisor of 100 is further needed. To accurately represent the ] unit, a divisor of 72 is needed, which also allows divisions by 2, 3, 4, 6, 8, 9, 12, 18, 24, and 36 to be accurate. Multiplying these together gives 127×72×100 = 914,400 units per inch; this also allows exact representations of multiples of 1/100 & 1/32&nbsp;inch. According to ], programmer and standards activist (ISO, W3C, IETF), EMUs are a rational solution to a particular set of design criteria.<ref>{{cite web|author=Monday April 16, 2007 5:24AM by Rick Jelliffe in Technical |url=http://www.oreillynet.com/xml/blog/2007/04/what_is_an_emu.html |title=Why EMUs? - O'Reilly XML Blog |publisher=Oreillynet.com |date=2007-04-16 |accessdate=2009-05-19}}</ref>

=== Container structure ===
{{Main|Open Packaging Conventions}}
]
Office Open XML documents are stored in ] (OPC) packages, which are ]s containing ] and other data files, along with a specification of the relationships between them.<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
| page=6
| format=PDF
| publisher=Ecma International
| date=December 11, 2006
| accessdate=2007-01-23
}}</ref> Depending on the type of the document, the packages have different internal directory structures and names. An application will use the relationships files to locate individual sections (files), with each having accompanying metadata, in particular ] metadata.

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

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

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

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

As such, images referenced in the 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 change the used image, edit the relationship.

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

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

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

===== Embedded or linked media file relations =====
Pictures can be embedded or linked using a tag:

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

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

==== Document properties ====
Office Open XML uses the ] ] Element Set and ] Metadata Terms to store document properties. Dublin Core is a standard for cross-domain information resource description and is defined in .

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

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

== Structure of the standard ==
=== ISO/IEC 29500:2008 ===

The ISO/IEC standard is structured into four parts, each of which are independent standards.<ref name="StandardIS29500">{{cite web
| url=http://www.iso.org/iso/search.htm?qt=29500&published=on&active_tab=standards
| title=ISO&nbsp;— You searched for "29500" in title and abstract
| publisher=]
| date=2009-06-05}}</ref>
Part 2 specifying ] is, for example, used by other files formats including ] and ]. The ISO/IEC 29500:2008 version is also known ECMA-376 2nd edition (2008)

;Part 1. Fundamentals and Markup Language Reference (5560 pages)
:Contains conformance definitions
: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
:Schemas are included in the text
;Part 2. Open Packaging Conventions (129 pages)
:Defines the Open Packaging Conventions (package model, physical package)
:Defines core properties, ]s and ]s
:XML schemas for the OPC are declared as ] (XSD) and (non-normatively) using ] (ISO/IEC 19757-2)
;Part 3. Markup Compatibility and Extensibility (40 pages)
:Describes extension facilities of OpenXML documents and specifies elements and attributes by which applications with different extensions can interoperate
:Extensibility rules are expressed using ] (ISO/IEC 19757-4)
;Part 4. Transitional Migration Features (1464 pages)
:Contains reference material of legacy and transitional interest
:Contains controversial material such as compatibility settings and the graphics markup language VML
:Contains list of differences between ECMA-376 1st edition and ISO/IEC 29500:2008 (ECMA-376 2nd edition)

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

=== ECMA-376 1<sup>st</sup> edition (2006) ===


=== ECMA-376 1st edition (2006) ===
The ECMA standard is structured in five parts to meet the needs of different audiences.<ref name="StandardECMA376" /> The ECMA standard is structured in five parts to meet the needs of different audiences.<ref name="StandardECMA376" />
;

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

;Part 2. Open Packaging Conventions ;Part 2. Open Packaging Conventions
:Defines the Open Packaging Conventions (package model, physical package) :* The ] (OPC), for the package model and physical package, is defined and used by various document types in various applications from multiple vendors.
:Defines core properties, thumbnails and digital signatures :* 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) :* XML schemas for the OPC are declared as XML Schema Definitions (XSD) and (non-normatively) using ] (ISO/IEC 19757-2)
;

;Part 3. Primer ;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 :* 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 :* Describes the custom XML data-storing facility within a package to support integration with business data
;

;Part 4. Markup Language Reference ;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) :* 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 :* XML schemas for the markup languages are declared as XSD and (non-normatively) using RELAX NG
:Defines the custom XML data storing facility :* Defines the custom XML data-storing facility
;

;Part 5. Markup Compatibility and Extensibility ;Part 5. Markup Compatibility and Extensibility
:Describes extension facilities of OpenXML documents and specifies elements and attributes by which applications with different extensions can interoperate :* Describes extension facilities of OpenXML documents and specifies elements & attributes through which applications can operate across different extensions.
:Extensibility rules are expressed using NVDL (ISO/IEC 19757-4)


Later versions of the ECMA-376 standard are aligned and technically equivalent to the corresponding ISO standard.
=== Compatibility between versions ===
The intent of the changes from ECMA-376 1st edition to ISO 29500 was that a valid ECMA-376 document would 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|accessdate=2009-09-29}}</ref>, but 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.griffinbrown.co.uk/blog/2008/04/17/OOXMLAndOffice2007ConformanceASmokeTest.aspx|title=OOXML and Office 2007 Conformance: a Smoke Test|accessdate=2009-09-29}}</ref> A fix for this has been suggested to JTC1/SC34/WG4, and was approved in June 2009 to go forward as a recommendation for the first amendment to OOXML.<ref>{{cite web|url=http://www.itscj.ipsj.or.jp/sc34/open/1239.pdf|title=Minutes of the Copenhagen Meeting of ISO/IEC JTC1/SC34/WG4|date=2009-06-22|accessdate=2009-09-29}} page 15</ref>


== Support and criticism == === ISO/IEC 29500:2008 ===
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.
{{Criticism section|date=September 2009}}


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


;
=== Implementations ===
;Part 1. Fundamentals & Markup Language Reference
Several software products implement support for reading and/or writing documents in the Office Open XML document format. For example:
:Consisting of 5560 pages, this part contains:
* Office software companies including ], ],<ref>{{cite web|author=Apple Computer, Inc. |url=http://www.apple.com/pro/tips/word_files.html?sr=hotnews |title=Pro&nbsp;— Tips&nbsp;— Editing Word Files&nbsp;— Without Word |publisher=Apple |date=1999-03-26 |accessdate=2009-09-16}}</ref> ],<ref>{{cite web
:* Conformance definitions
| url=http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9058038
:* Reference material for the XML document markup languages defined by the Standard
| title=Lotusphere: Whoops! IBM products support Microsoft's Open XML doc format
:* XML schemas for the document markup languages declared using ] and (non-normatively) ]
| date=2008-01-20
:* Defines the foreign markup facilities
| author=Eric Lai
;
| publisher=Computerworld.com}}</ref> ], ],<ref>{{cite web
;Part 2. Open Packaging Conventions
|url=http://www.novell.com/prblogs/?p=299
: Consisting of 129 pages, this part contains:
|title=http://www.novell.com/prblogs/?p=299
:* A description of the Open Packaging Conventions (package model, physical package)
|date=2007-03-05
:* Core properties, ]s and ]s
| author=Kevan Barney}}</ref> ] and ]<ref>
:* XML schemas for the OPC are declared using ] and (non-normatively) ]
{{cite web
;
|url=http://googledocs.blogspot.com/2009/06/file-formats-keep-on-coming-announcing.html
;Part 3. Markup Compatibility and Extensibility
|title=The file formats keep on coming! Announcing .xlsx and .docx support
: Consisting of 40 pages, this part contains:
|publisher=Official Google Docs Blog
:* A description of ''extensions'': elements & attributes which define mechanisms allowing applications to specify alternative means of negotiating content
|date=2009-06-01
:* Extensibility rules are expressed using ]
|accessdate=2009-06-05}}</ref><ref>{{cite web|url=http://docs.google.com/support/bin/answer.py?answer=50092&hl=en |title=Uploading and exporting : Uploading files&nbsp;— Google Docs Help |publisher=Docs.google.com |date= |accessdate=2009-09-16}}</ref> have products with support for OOXML.
;
;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''.
*The ] 2007 applications (], ] and ]) target Office Open XML (in its Ecma 376 1st edition variant) as their default file format.<ref name="arstechnica" /><ref>{{cite web|url=http://www.linux-watch.com/news/NS6047809291.html |title=WordPerfect to support both ODF and Open XML |publisher=Linux-watch.com |date=2006-11-29 |accessdate=2009-09-16}}</ref><ref>http://office.microsoft.com/en-us/products/ha102058151033.aspx</ref><ref>{{cite web|url=http://www.zdnetasia.com/news/software/0,39044164,62044341,00.htm |title=Microsoft: Developer interest fueling OOXML : News : Software |publisher=ZDNet Asia |date=2008-07-30 |accessdate=2009-09-16}}</ref>


===Compatibility between versions===
*The non-profit organization ] Malaysia announced the release of a business-to-business standard called RosettaNet Automated Enablement standard (RAE) using the Office Open XML document standard.<ref>{{cite web|url=http://www.zdnetasia.com/news/business/0,39044229,62033726,00.htm |title=RosettaNet targets standard at SMEs : News : Business |publisher=ZDNet Asia |date=2007-10-24 |accessdate=2009-05-19}}</ref>
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>


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>
=== Support ===
Several governments, companies, organizations have expressed support for either the standardization of the Office Open XML document format, or for expanding the use of the Office Open XML document format.


==Application support==
* Several of those organizations implementing the format also participated directly in the development of the Office Open XML formats,<ref>{{cite web|url=http://www.openxmlcommunity.org/applications.aspx |title=Applications |publisher=Open XML Community |date= |accessdate=2009-09-16}}</ref> as well as other companies like ] and ] all working together inside the Ecma International Office Open XML technical committee (TC45).<ref>{{cite web|url=http://www.openxmlcommunity.org/quotes.aspx |title=Community Quotes |publisher=Open XML Community |date= |accessdate=2009-09-16}}</ref><ref name="ecma-international.org">{{cite web|url=http://www.ecma-international.org/memento/TC45-M.htm |title=TC 45 Office Open XML formats committee (includes participation list) |publisher=Ecma-international.org |date= |accessdate=2009-09-16}}</ref><ref>{{cite web|url=http://www.netvalley.com/top100am_vendors.html |title=Computer Companies: Top 100 Computer & Software Companies, Largest Computer Companies |publisher=Netvalley.com |date=2006-05-30 |accessdate=2009-09-16}}</ref>
{{Main|List of software that supports Office Open XML}}
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>
* The launched in May 2007, with 327 inaugural members. The community has now grown to over 3,100 members.<ref>{{cite web|url=http://www.openxmlcommunity.org/momentum.aspx |title=Global Momentum |publisher=Open XML Community |date=2007-05-08 |accessdate=2009-05-19}}</ref><ref>{{cite web|url=http://blogs.msdn.com/nzisv/archive/2007/06/19/open-xml-community-site.aspx |title=Open XML Community Site |publisher=Blogs.msdn.com |date=2007-06-19 |accessdate=2009-09-16}}</ref><ref>{{cite web|last=Lai |first=Eric |url=http://www.infoworld.com/t/platforms/microsoft-says-support-open-xml-growing-036 |title=Microsoft says support for Open XML is growing |publisher=Infoworld.com |date=2007-05-09 |accessdate=2009-09-16}}</ref> The website for the Open XML Community is hosted by Microsoft.<ref>{{cite web|url=http://www.openxmlcommunity.org/ |title=Ecma International Open Standard for Office Applications |publisher=Open XML Community |date= |accessdate=2009-09-16}}</ref>
* The was initially founded by 40 organizations.<ref>{{cite web|url=http://xml.sys-con.com/node/200135 |title=Document Sciences Joins XML Developer Group as Founding Member &#124; XML Journal |publisher=Xml.sys-con.com |date= |accessdate=2009-09-16}}</ref> The groups stated intention is to constitute “a community for developers to exchange information with each other regarding the usage of the Ecma-developed Office Open XML file formats.”<ref>{{cite web|last=Montalbano |first=Elizabeth |url=http://www.infoworld.com/%5Bprimary-term-alias-prefix%5D/%5Bprimary-term%5D/microsoft-escalates-odf-fight-openxml-group-483 |title=Microsoft escalates ODF fight with OpenXML group |publisher=InfoWorld |date=2006-03-21 |accessdate=2009-09-16}}</ref><ref>{{cite web|url=http://openxmldeveloper.org/about.aspx |title=Open XML Formats Developer Group mission Statement |publisher=Openxmldeveloper.org |date=2006-03-21 |accessdate=2009-09-16}}</ref><ref>{{cite web|last=Weiss |first=David |url=http://unweary.com/2006/03/apple-an-openxml-developer.html |title=Apple an OpenXML developer |publisher=Unweary.com |date= |accessdate=2009-09-16}}</ref> Notable founding members of the organization include ], ], ], ], ], ], ] and the ].<ref>{{cite web|last=Darrow |first=Barbara |url=http://www.informationweek.com/news/software/development/showArticle.jhtml?articleID=183701603 |title=Microsoft Touts SharePoint As Development Platform&nbsp;— Collaborative Applications |publisher=InformationWeek |date=2006-03-21 |accessdate=2009-09-16}}</ref><ref>{{cite web|url=http://openxmldeveloper.org/archive/2006/03/18/OpenXmlDeveloperGroup.aspx |title=Announcing the Open XML Formats Developer Group |publisher=OpenXML Developer |date= |accessdate=2009-09-16}}</ref> As of December 2006, over 750 developers had joined the Open XML Formats Developer Group.<ref>{{cite web|url=http://www.macworld.co.uk/procreative/news/index.cfm?newsid=16697&pagtype=allchandate |title=Microsoft's Mac promise on Open XML standard&nbsp;— ProCreative&nbsp;— Macworld UK |publisher=Macworld.co.uk |date=2006-12-08 |accessdate=2009-09-16}}</ref> The website of the Open XML Formats Developer Group is hosted by Microsoft.<ref>{{cite web|url=http://openxmldeveloper.org/ |title=OpenXML Developer |publisher=OpenXML Developer |date= |accessdate=2009-09-16}}</ref>
* The ] and the United States ] have participated in the work of Ecma TC45 and support the Office Open XML standard.<ref name="ecma-international.org">{{cite web|url=http://www.ecma-international.org/memento/TC45-M.htm |title=TC 45 Office Open XML formats committee (includes participation list) |publisher=Ecma-international.org |date= |accessdate=2009-09-16}}</ref><ref>{{cite web|url=http://www.xmlopen.org/ooxml-wiki/resources/BSI_OOXML_2007_05.pdf |title=Microsoft PowerPoint&nbsp;— BSI OOXML v1b.ppt |format=PDF |date= |accessdate=2009-09-16}}</ref><ref>{{cite web|url=http://news.cnet.com/Microsoft-to-standardize-Office-formats/2100-1012_3-5965443.html |title=Microsoft to standardize Office formats&nbsp;— CNET News |publisher=News.cnet.com |date=2005-11-22 |accessdate=2009-09-16}}</ref><ref>{{cite web|url=http://www.digitalpreservation.gov/library/challenge/formats_challenge.html |title=Meeting the Challenge: Office Open XML and PDF/A&nbsp;— Digital Preservation (Library of Congress) |publisher=Digitalpreservation.gov |date=2008-04-02 |accessdate=2009-09-16}}</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&nbsp;— 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>
*Former ] board member ], who started the ] and ] projects, showed support for the Office Open XML document format, stating “OOXML is a superb standard and yet, it has been ]ed so badly by its competitors that serious people believe that there is something fundamentally wrong with it.”<ref>{{cite web|url=http://slashdot.org/article.pl?sid=07/10/28/175215 |title=GNOME Foundation Helping OOXML? |publisher=Slashdot |date= |accessdate=2009-05-19}}</ref><ref>{{cite web|url=http://linux.slashdot.org/article.pl?sid=07/09/10/2343256&tid=109 |title=Slashdot &#124; de Icaza calls OOXML a "Superb Standard" |publisher=Linux.slashdot.org |date= |accessdate=2009-05-19}}</ref>
] 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
|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
}}</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:
* According to ], Office Open XML gained a number of supporters including some who are directly affiliated with the OpenDocument format.<ref name="arstechnica">{{cite web|last=Paul |first=Ryan |url=http://arstechnica.com/microsoft/news/2008/04/microsofts-office-open-xml-now-an-official-iso-standard.ars |title=Microsoft's Office Open XML now an official ISO standard |publisher=Ars Technica |date=2008-04-01 |accessdate=2009-09-16}}</ref>
* ] 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:
* Patrick Durusau, the editor of the OpenDocument standard, has been an advocate of the standardization of Office Open XML.<ref name="arstechnica" /><ref>{{cite web|url=http://www.durusau.net/publications/OpenXMLPosterChild.pdf |title=OpenXML: A Poster Child for Open Standards Development? |format=PDF |date= |accessdate=2009-09-16}}</ref>
* ] (included with ])

* ]

* ]
=== Criticism of ECMA-376 1<sup>st</sup> edition ===
* ]

* ]
The ] UK Action Group has stated that with OpenDocument an ISO standard for Office files already exists.<ref name="FSMcriticism">{{cite web
* ]
| url=http://www.freesoftwaremagazine.com/articles/odf_ooxml_technical_white_paper
* ]
| title= ODF/OOXML technical white paper
* ]
| publisher=Free Software Magazine
* ]
|date=2 Mai 2007}}</ref>
Further, they argue that the Office Open XML file-format is heavily based on Microsoft's own ] and is thus not vendor-neutral, and that it has inconsistencies with existing ISO standards such as ] and ] and ]s.<ref name="FSMcriticism" />

In August 2007, the ] published a blog post calling upon ISO National Bodies to vote “No, with comments” on OOXML. It said, ”OOXML is a direct port of a single vendor’s binary document formats. It avoids the re-use of relevant existing international standards (e.g. several cryptographic algorithms, VML, etc.). It lists a large number of “Compatibility Settings” for legacy applications (e.g. ''footnoteLayoutLikeWW8'', ''autoSpaceLikeWord95'', ''useWord97LineBreakRules'', etc.) which would be difficult for other developers to implement and hardly what one would find in an aspirational, consolidated best practices document. There are literally hundreds of technical flaws that should be addressed before standardizing OOXML including continued use of binary code tied to platform specific features, propagating bugs in MS-Office into the standard, proprietary units, references to proprietary/confidential tags, unclear ] and patent rights, and much more.”<ref>{{cite web
| url=http://www.linux-foundation.org/weblogs/cherry/2007/08/29/ooxml-vote-no-with-comments/
| title=OOXML&nbsp;— vote “No, with comments”
| author=John Cherry
| date=14 March 2008}}</ref>

==== Specific criticism ====

* ECMA-376 1<sup>st</sup> edition does not conform to ISO 8601:2004 "Representation of Dates and Times." It requires that implementations replicate a ] <ref>{{cite web | url = http://www.exceluser.com/explore/earlydates.htm | title = How to Work With Dates Before 1900 in Excel | first = Charley | last = Kyd | date = October 2006 | work = ExcelUser | accessdate = 2009-09-16 }}</ref> bug that dictates that 1900 is a leap year, which in fact it isn't. Products complying with ECMA-376 would be required to use the WEEKDAY() spreadsheet function, and therefore assign incorrect dates to some days of the week, and also miscalculate the number of days between certain dates.<ref name="The Contradictory Nature of OOXML">{{cite web
| url=http://www.consortiuminfo.org/standardsblog/article.php?story=20070117145745854
| title=The Contradictory Nature of OOXML
| publisher=ConsortiumInfo.org}}</ref> ECMA-376 2nd edition (ISO/IEC 29500) does use 8601:2004 "Representation of Dates and Times".<ref>{{cite web|url=http://www.ecma-international.org/publications/standards/Ecma-376.htm |title=ECMA-376 2nd edition Part 1 (3. Normative references) |publisher=Ecma-international.org |date= |accessdate=2009-09-16}}</ref><ref>{{cite web|url=http://www.ecma-international.org/news/TC45_current_work/New%20set%20of%20proposed%20dispositions%20posted.htm |title=New set of proposed dispositions posted, including more positive changes to the Ecma Office Open XML formats&nbsp;– Dispositions now proposed for more than half of National Bodies’ comments |publisher=Ecma-international.org |date=2007-12-11 |accessdate=2009-09-16}}</ref>
* ECMA-376 1<sup>st</sup> edition "Embedded Object Alternate Image Requests Types" and "Clipboard Format Types" in the standard refer back to ]s or ]s&nbsp;– each of which are proprietary formats that have hard-coded dependencies on the Windows itself. It should instead have referenced the platform neutral standard ISO/IEC 8632 "Computer Graphics Metafile".<ref name="The Contradictory Nature of OOXML"/>
* Office Open XML (ISO/IEC 29500:2008 Part 4 - Transitional Migration Features) contains specific compatibility settings used when converting existing office documents to Office Open XML, most notably: ''autoSpaceLikeWord95'', ''footnoteLayoutLikeWW8'', ''lineWrapLikeWord6'', ''mwSmallCaps'', ''shapeLayoutLikeWW8'', ''suppressTopSpacingWP'', ''truncateFontHeightsLikeWP6'', ''uiCompat97To2003'', ''useWord2002TableStyleRules'', ''useWord97LineBreakRules'', ''wpJustification'' and ''wpSpaceWidth''.<ref>{{cite web
| url=http://www.freesoftwaremagazine.com/articles/odf_ooxml_technical_white_paper?page=0%2C9
| title=ODF/OOXML technical white paper&nbsp;— A white paper based on a technical comparison between the ODF and OOXML formats
| publisher=Free Software Magazine}}</ref> The compatibility settings are fully documented in the ISO/IEC 29500 / Ecma 2nd edition specifications.<ref>{{cite web|url=http://www.ecma-international.org/publications/standards/Ecma-376.htm |title=ECMA-376 2nd edition Part 4 (paragraph 9.7.3) |publisher=Ecma-international.org |date= |accessdate=2009-09-16}}</ref>
* Office Open XML uses unique tag for each compatibility setting. Currently, the only application’s compatibility settings are the applications that the standard’s authors have decided to include. For other application’s compatibility settings to be added, further tag names would need to be defined in the specification, potentially creating thousands of them, each having nothing to do with interoperability.<ref>{{cite web
| quote="... OOXML chose this route. Rather than create an application-definable configuration tag there is a unique tag for each setting ... Currently, the only application’s unique settings that are catered for are the applications that the standard’s authors have decided to include, ... For other applications to be added, further tag names would need to be defined in the specification, potentially creating thousands of them, each having nothing to do with interoperability ..."
| url=http://www.freesoftwaremagazine.com/articles/odf_ooxml_technical_white_paper?page=0%2C7
| title=ODF/OOXML technical white paper&nbsp;— A white paper based on a technical comparison between the ODF and OOXML formats
| publisher=Free Software Magazine}}</ref>
* Use of ] and the transitional-use-only ] instead of ] recommendation ].<ref>{{cite web
| url=http://reddevnews.com/features/article.aspx?editorialsid=2356
| title= The X Factor
| publisher=reddevnews.com
|month=October | year=2007}}</ref> VML did not become a W3C recommendation.<ref>{{cite web|url=http://www.w3.org/TR/NOTE-VML |title=VML&nbsp;— the Vector Markup Language |publisher=W3.org |date=1998-05-13 |accessdate=2009-05-19}}</ref>
* Use of ] instead of ] recommendation ].<ref>{{cite web
| url=http://www.zdnet.com.au/news/software/soa/Microsoft-Office-dumped-by-Science-and-Nature/0,130061733,339278690,00.htm
| title=Microsoft Office dumped by Science and Nature
| publisher=ZDNet Australia
| date=18 June 2007}}</ref> MathML<ref>{{cite web
| url=http://www.w3.org/Math/
| title=MathML W3C standard
| publisher=W3}}</ref> is a ] recommendation for the "inclusion of mathematical expressions in Web pages" and "machine to machine communication" that has been around since about 1999. However, most mathematicians continue to use the much older ] format as their main method for typesetting complex mathematical formulae. TeX is not an ISO standard, but is fully documented and is the '']'' standard for typesetting mathematical expressions.
* Office Open XML does not define a ], leaving this aspect to be application-defined.{{Citation needed|date=July 2009}}
* The standard is long, with the version submitted to ISO comprising 6,546 pages. The need and appropriateness of such length has been questioned. For example, ] remarks that the OpenDocument specification is 867 pages in length and achieves the same goals.<ref name="GooglesPositiononOOXML">{{cite web
|url=http://www.odfalliance.org/resources/Google%20OOXML%20Q%20%20A.pdf
|title=Google's Position on OOXML as a Proposed ISO Standard
|date=2007-08
|publisher=ODF alliance}}</ref>

== Adoption ==

Several countries have formally announced either adoption, or the evaluation of adoption of OOXML. What this means varies from case to case; in some cases, it means that the OOXML standard has a national standard identifier; in some cases, it means that the OOXML standard is permitted to be used where national regulation says that non-proprietary formats must be used, and in still other cases, it means that some government body has actually decided that OOXML will be used in some specific context.

;Belgium : ]'s Federal Public Service for Information and Communication Technology in 2006 was evaluating the adoption of the Office Open XML format. It already then confirmed that it would consider all ISO standards to be open standards, specifically mentioning Office Open XML as such a possible future ISO standard.<ref>{{cite web|url=http://www.fedict.belgium.be/nl/binaries/Open_Standaarden_NL_V1_tcm167-16667.pdf |title=FED13321-docsPeterStrickx.indd |format=PDF |date= |accessdate=2009-09-16}}</ref>

;Denmark : In June 2007, the ] ] recommended that beginning with January 1, 2008 public authorities must support at least one of the two word processing document formats Office Open XML and ODF in all new IT solutions, where appropriate.<ref>{{cite web|url=http://vtu.dk/nyheder/aktuelle-temaer/2007/aabne-standarder/bilag/bilag-8.html/ |title=Bilag 8&nbsp;– Sammenligning af rapporten om ”Estimering af omkostningerne ved indførelse af Office Open XML (OOXML) og Open Document Format (ODF) i centraladministrationen” i forhold til de spørgsmål, der skal belyses i de økonomiske konsekvensvurderinger, jf. rapporten om ”Anvendelse af åbne standarder i det offentlige” |publisher=Vtu.dk |date= |accessdate=2009-05-19}}</ref>

;Germany : In ] the Office Open XML standard is currently under observation by the governmental office for standards in public IT („Koordinierungs- und Beratungsstelle der Bundesregierung für Informationstechnik in der Bundesverwaltung“ (KBSt). The latest release of „SAGA“ (Standards and Architectures for E-Government-Applications) includes Office Open XML file formats. The standard may be used to exchange complex documents when further processing is required.<ref>{{cite web|url=http://gsb.download.bva.bund.de/KBSt/SAGA/SAGA_v4.0.pdf |title=SAGA 4.0 |format=PDF |date= |accessdate=2009-09-16}}</ref>

;Japan : On ], ], the government of ] published a new interoperability framework which gives preference to the procurement of products that follow open standards.<ref>{{cite news
|url=http://www.informationweek.com/news/showArticle.jhtml?articleID=201000546
|publisher=Information Week
|title=Office Software Formats Battle Moves To Asia
|first=David
|last=Gardner
|date=2007-07-10
|accessdate=2007-07-27
}}</ref><ref>{{cite news
|url=http://www.meti.go.jp/press/20070629014/20070629014.html
|publisher=Ministry of Economy, Trade and Industry, Japan
|title=Interoperability framework for information systems (in Japanese)
|date=2007-06-29
|accessdate=2007-07-27
}}</ref> On ] the government declared that they hold the view that formats like Office Open XML which organizations such as ] and ISO had also approved was, according to them, an open standard {{Citation needed|date=June 2009}}. Also, they said that it was one of the preferences, whether the format is open, to choose which software the government shall deploy.

;Lithuania : Lithuanian Standards Board has adopted the ISO/IEC 29500:2008 Office Open XML format standard as ]n National standard. The decision was made by Technical Committee 4 Information Technology on March 5, 2009. The proposal to adopt the Office Open XML format standard was submitted by Lithuanian Archives Department under the ].<ref>{{cite web|url=http://www.openxmlcommunity.com/latestnews.aspx |title=Latest News |publisher=Open XML Community |date= |accessdate=2009-05-19}}</ref>

;Norway : ]'s ] is evaluating the adoption of the Office Open XML format. The ministry put the document standard under observation in December 2007.<ref>{{cite web|url=http://www.regjeringen.no/en/dep/fad/Documents/Rundskriv/2007/Referansekatalog-for-IT-standarder-i-off.html?id=494951 |title=Referansekatalog for IT-standarder i offentlig sektor |publisher=regjeringen.no |date= |accessdate=2009-05-19}}</ref>

;Sweden : ] has adopted Office Open XML as a 4 part Swedish National Standard ''SS-ISO/IEC 29500:2009''.<ref>{{cite web|url=http://www.sis.se/DesktopDefault.aspx?tabName=@DocType_1&Doc_ID=68693&PresID=2&Desc=SS-ISO/IEC%2029500-1:2009 |title=SS-ISO/IEC 29500-1:2009 |publisher=Sis.se |date=2009-01-19 |accessdate=2009-09-16}}</ref><ref>{{cite web|url=http://www.sis.se/DesktopDefault.aspx?tabName=@DocType_1&Doc_ID=68694&PresID=1&Desc=SS-ISO/IEC%2029500-2:2009 |title=SS-ISO/IEC 29500-2:2009 |publisher=Sis.se |date= |accessdate=2009-09-16}}</ref><ref>{{cite web|url=http://www.sis.se/DesktopDefault.aspx?tabName=@DocType_1&Doc_ID=68695&PresID=2&Desc=SS-ISO/IEC%2029500-3:2009 |title=SS-ISO/IEC 29500-3:2009 |publisher=Sis.se |date= |accessdate=2009-09-16}}</ref><ref>{{cite web|url=http://www.sis.se/DesktopDefault.aspx?tabName=@DocType_1&Doc_ID=68696&PresID=1&Desc=SS-ISO/IEC%2029500-4:2009 |title=SS-ISO/IEC 29500-4:2009 |publisher=Sis.se |date= |accessdate=2009-09-16}}</ref>

;Switzerland : In July 2007, the ] announced adherence SAGA.ch ] standards mandatory for its departments as well as for cantons, cities and municipalities. The latest version of SAGA.ch includes Office Open XML file formats.<ref>{{cite web|url=http://www.ech.ch/index.php?option=com_docman&task=cat_view&gid=92&lang=en |title=eCH&nbsp;— Downloads &#124; Standards/Normes &#124; eCH-0014 d SAGA.ch |publisher=Ech.ch |date= |accessdate=2009-05-19}}</ref>

;United States of America : On April 15, 2009, the ]-accredited ] organisation voted to adopt ISO/IEC 29500:2008 as an American National Standard.<ref>{{cite web
| url=http://ballot.itic.org/itic/archive.taf?function=detail&ballot_id=3025&_UserReference=9B6726AA59D4BAC249E6E82E
| title=INCITS Letter Ballot 3025
| publisher=INCITS
| date=2009-04-15}}</ref>

:The ] of ] has been examining its options for implementing ]-based document processing. In early 2005, ], Secretary of Administration and Finance in Massachusetts, was the first ] official in the ] to publicly connect open formats to a public policy purpose: "It is an overriding imperative of the American ] system that we cannot have our public documents locked up in some kind of proprietary format, perhaps unreadable in the future, or subject to a proprietary system license that restricts access."<ref>{{cite web|url=http://web.archive.org/web/20061013201242/http://www.mass.gov/eoaf/open_formats_comments.html |title=Informal comments on Open Formats |publisher=Web.archive.org |date= |accessdate=2009-09-16}}</ref> Since 2007 Massachusetts classifies Office Open XML as "Open Format" and has its approved technical standards list&nbsp;— the Enterprise Technical Reference Model (ETRM)&nbsp;— to include Office Open XML. Massachusetts now formally endorses Office Open XML formats for its public records.<ref>{{cite web|url=http://xml.coverpages.org/ni2007-07-03-a.html |title=Cover Pages: Major Revision of Massachusetts Enterprise Technical Reference Model (ETRM) |publisher=Xml.coverpages.org |date= |accessdate=2009-05-19}}</ref>

== Application support ==
{{Main|Office Open XML software}}

The Office Open XML format is used in ] and in ].
This includes ]s (both traditional and web-based) and individual applications such as word-processors, spreadsheets, presentation, and data management applications.

The latest version of Office Open XML is formally known as either ISO/IEC 29500:2008 or as ECMA-376 2nd edition (December 2008). IS 29500 is subject to an active maintenance program through the committee ISO/IEC SC34 WG4, which is working on a revision for minor edits (a Corrigendum) and a revision for substantive technical issues (an Amendment)<ref>{{cite web
| url = http://idippedut.dk/post/2009/03/27/The-actual-work-we-did-in-Prague.aspx
| title = The actual work we did in Prague }}</ref>

Microsoft, whose products currently only support the version of Office Open XML originally submitted as an ECMA standard, has committed to using the ISO/IEC 29500 standard in their products<ref>{{cite web
| url = http://www.microsoft.com/interop/letters/ChrisCapOpenLetter.mspx
| title = An Open Letter from Chris Capossela, Senior Vice President, Microsoft Office
| accessdate = 2008-05-26
| quote = ... we are committed to supporting the Open XML specification that is approved by ISO/IEC in our products. ... We are committed to the healthy maintenance of the standard once ratification takes place so that it will continue to be useful and relevant to the rapidly growing number of implementers and users around the world.}}</ref> and has also committed to participate in the maintenance of this standard.

Microsoft has stated that ] will be the first version of Microsoft Office to support ISO/IEC 29500, though no release date has been announced.<ref name="SupportedFormats">{{ cite web | url = http://www.microsoft.com/Presspass/press/2008/may08/05-21ExpandedFormatsPR.mspx | title = Microsoft Expands List of Formats Supported in Microsoft Office | publisher = Microsoft.com | date = 2008-05-21 | accessdate = 2009-05-19 }}</ref>

On July 28, 2008 Murray Sargent, a software development engineer in the Microsoft Office team confirmed that Word 2007 will have a service pack release that enables it to read and write ISO standard Office Open XML files.<ref>{{cite web|url=http://blogs.msdn.com/murrays/archive/2008/07/28/improved-mathml-support-in-word-2007.aspx |title=Murray Sargent: Math in Office : Improved MathML support in Word 2007 |publisher=Blogs.msdn.com |date=2008-07-28 |accessdate=2009-05-19}}</ref> However, the 2009 Service Pack 2 release did not expose any IS 29500 features in its user interface.

In a ] article Alex Brown, leader of the ISO/IEC group in charge of deciding maintenance processes for any ISO/IEC 29500 Standard, stated
<blockquote>"I am hoping that Microsoft Office will shortly be brought into line with the 29500 specification, and will stay that way".<ref>{{cite web
|url=http://news.zdnet.co.uk/software/0,1000000121,39388229,00.htm
|title=Microsoft Office 2007 fails OOXML conformance test}}</ref></blockquote>

On March 13, 2008 Doug Mahugh, a Senior Product Manager at Microsoft specializing in Office client interoperability and the Open XML file formats confirmed that version 1.0 of the Open XML Format SDK
<blockquote>"will definitely be 100% compliant with the final ISO/IEC 29500 spec, including the changes accepted at the BRM".<ref>{{cite web|author=by dmahugh |url=http://blogs.msdn.com/dmahugh/archive/2008/03/13/open-xml-sdk-roadmap.aspx |title=Open XML SDK roadmap |publisher=Blogs.msdn.com |date= |accessdate=2009-05-19}}</ref></blockquote>

In a ComputerWorld interview from 2008, Doug Mahugh said that
<blockquote>"Microsoft would continue to update the SDK to make sure that applications built with it remained compliant with an Open XML standard as changes were made in the future".<ref>{{cite web|last=Lai |first=Eric |url=http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9068198 |title=Microsoft releasing OOXML SDK |publisher=Computerworld.com |date=2008-03-12 |accessdate=2009-05-19}}</ref></blockquote>

Microsoft Open XML Format ]<ref>{{cite web
| url=http://go.microsoft.com/fwlink/?LinkId=120908
| title=Open XML Format SDK
| date=2008-06-10
| author=Microsoft
|publisher=Microsoft}}</ref> contains a set of ] libraries to create and manipulate Office Open XML files programmatically. Version 1.0 was released on June 10, 2008<ref>{{cite web
| url=http://blogs.msdn.com/erikaehrli/archive/2008/06/10/announcing-the-open-xml-format-sdk-1-0.aspx
| title=Announcing the Open XML Format SDK 1.0
| date=2008-06-10
| author=Erika Ehrli
|publisher=Computerworld}}</ref> and incorporates the changes made to the Office Open XML specification made during the current ISO/IEC standardization process.<ref name="ooxmlsdkroadmap">{{cite web
| url = http://blogs.msdn.com/dmahugh/archive/2008/03/13/open-xml-sdk-roadmap.aspx
| author = Doug Mahugh
| publisher = MSDN Blogs
| title = Open XML SDK roadmap
| accessdate = 2008-03-23}}</ref><ref>{{cite web
| url=http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9068198
| title=Microsoft releasing OOXML SDK
| date=2008-03-12
| author=Eric Lai
|publisher=Microsoft}}</ref> Version 2 of the Open XML SDK supports validating Office Open XML documents against the Office Open XML schema, as well as searching in Office Open XML documents.<ref name="ooxmlsdkroadmap" />

, a set of free ] cmdlets for ] to create and manipulate Office Open XML files at the ] or using ]s.<ref>{{cite web|url=http://blogs.msdn.com/ericwhite/archive/2008/06/11/processing-open-xml-documents-server-side-using-powershell.aspx |title=PowerTools for Open XML |publisher=Blogs.msdn.com |date= |accessdate=2009-05-19}}</ref><ref>{{cite web|url=http://www.codeplex.com/PowerTools/license |title=PowerTools license |publisher=Codeplex.com |date= |accessdate=2009-05-19}}</ref><ref>{{cite web|url=http://www.opensource.org/licenses/ms-pl.html |title=Microsoft Public License (Ms-PL) |publisher=Opensource.org |date=2007-10-15 |accessdate=2009-05-19}}</ref>


== See also == == See also ==
* ]
{{Commons category|OOXML}}

* ] * ]
* ]
* ]
* ] * ]
* ]


== References == ==References==
{{Reflist|colwidth=30em}}


==Further reading==
{{reflist|colwidth=30em}}
{{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}}
*
* *
* , Microsoft's site for developers
* Microsoft's site for customers and partners
* {{PDFlink||1.22&nbsp;MB}}
* , How do I open Microsoft Office 2007 files? Article by OpenOffice.org
* , ISO Standards, ] Information technology, SC 34
* , ISO's FAQ site on ISO/IEC 29500
* , contains a file with fairly complex formatting and can be used to quickly check compatibility of an implementation
* , contains resources, articles and tools for Office Open XML
* showing an indication of the percentage of support for Office Open XML by several different office suite implementations in aug-2008


{{Ecma International Standards}}
{{ISO standards}} {{ISO standards}}
{{Ecma International Standards}}
{{Microsoft Office}}
{{Office document file formats}}
{{Document markup languages}}
{{Authority control}}


{{DEFAULTSORT:Office Open Xml}} ]
] ]
]
] ]
]
]
] ]
]
]
] ]
] ]
] ]
]

]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]
]

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 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 byMicrosoft, Ecma, ISO, IEC
Initial release7 December 2006; 18 years ago (2006-12-07)
Latest release4th edition
26 October 2016; 8 years ago (2016-10-26)
Type of formatDocument file format
Extended fromXML, DOC, WordProcessingML
StandardECMA-376, ISO/IEC 29500
Open format?Yes
WebsiteECMA-376, ISO/IEC 29500-1:2016
Office Open XML Presentation
Filename extension .pptx, .pptm
Internet media type application/vnd.
openxmlformats-officedocument.
presentationml.
presentation
Developed byMicrosoft, Ecma, ISO, IEC
Initial release7 December 2006; 18 years ago (2006-12-07)
Latest release3rd edition
29 June 2011; 13 years ago (2011-06-29)
Type of formatPresentation
Extended fromXML, PPT
StandardECMA-376, ISO/IEC 29500
Open format?Yes
WebsiteECMA-376, ISO/IEC 29500:2016
Office Open XML Workbook
Filename extension .xlsx, .xlsm
Internet media type application/vnd.
openxmlformats-officedocument.
spreadsheetml.
sheet
Developed byMicrosoft, Ecma, ISO, IEC
Initial release7 December 2006; 18 years ago (2006-12-07) (as Microsoft Open XML)
Latest release3rd edition
29 June 2011; 13 years ago (2011-06-29)
Type of formatSpreadsheet
Extended fromXML, XLS, SpreadsheetML
StandardECMA-376, ISO/IEC 29500
Open format?Yes
WebsiteECMA-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:

See also

References

  1. "application/vnd.openxmlformats-officedocument.wordprocessingml.document". www.iana.org. IANA. 2011-02-25. Retrieved 2024-11-03.
  2. Klaus-Peter Eckert; Jan Henrik Ziesing; Ucheoma Ishionwu. "Document Interoperability: Open Document Format and Office Open XML" (PDF). Fraunhofer Verlag. p. 90.
  3. "application/vnd.openxmlformats-officedocument.presentationml.presentation". www.iana.org. IANA. 2011-03-14. Retrieved 2024-11-03.
  4. "vnd.openxmlformats-officedocument.spreadsheetml.sheet". www.iana.org. IANA. 2011-03-16. Retrieved 2024-11-03.
  5. "The Document Foundation, LibreOffice and OOXML". The Document Foundation. Retrieved 2016-03-22.
  6. "Overview of the XML file formats in Office 2010". Office 2010 Resource Kit. Microsoft. 5 August 2011.
  7. ^ "XML file name extension reference for Office 2013". Office 2013 Resource Kit. Microsoft. 26 December 2016.
  8. ^ "XLSX Strict (Office Open XML), ISO 29500-1:2008-2016". Library of Congress. Retrieved 2018-09-09.
  9. Brian Jones (2007-01-25). "History of office XML formats (1998–2006)". MSDN blogs. Retrieved 2020-12-31.
  10. "Microsoft Co-Sponsors Submission of Office Open XML Document Formats to Ecma International for Standardization". Microsoft. 2005-11-21.
  11. Casson and Ryan, Open Standards, Open Source Adoption in the Public Sector, and Their Relationship to Microsoft’s Market Dominance
  12. Microsoft hands over Office XML specs to Ecma
  13. "Slides presented by the TC45 committee to Ecma International". Archived from the original on 2011-10-21. Retrieved 2011-06-08.
  14. "Ecma International approves Office Open XML standard". Ecma International. 2006-12-07.
  15. "ISO/IEC DIS 29500 receives necessary votes for approval as an International Standard". ISO. 2008-04-02.
  16. 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.
  17. "Freely Available Standards". ITTF (ISO/IEC). 2008-11-18. Retrieved 2023-09-26.
  18. ^ "Standard ECMA-376". Ecma-international.org. Retrieved 2009-05-19.
  19. ^ Kirk, Jeremy (19 November 2008). "ISO publishes Office Open XML specification". InfoWorld. Retrieved 12 June 2010.
  20. "Norwegian standards body implodes over OOXML controversy". Ars Technica. 3 October 2008.
  21. "Code of Conduct in Patent Matters". Ecma International.
  22. "ISO/IEC/ITU common patent policy".
  23. "Microsoft's Open Specification Promise Eases Web Services Patent Concerns". September 12, 2006. Retrieved 2015-04-18.
  24. "2 Escape Hatches in MS's Covenant Not to Sue". Groklaw. December 4, 2005.
  25. Berlind, David (November 28, 2005). "Top open source lawyer blesses new terms on Microsoft's XML file format". ZDNet. Retrieved 2007-01-27.
  26. "Microsoft Open Specification Promise". Microsoft. 2007-02-15. Retrieved 2015-04-18.
  27. "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
  28. "Microsoft Open Specification Promise". Microsoft.com.
  29. "Licensing conditions that Microsoft offers for Office Open XML". Jtc1sc34.org. 2006-12-20. Retrieved 2009-05-19.
  30. "Microsoft Word — Responses to Comments and Perceived Contradictions.doc" (PDF). Retrieved 2009-09-16.
  31. "ISO search for "29500"". International Organization for Standardization. 2009-06-05.
  32. "Re-introducing on/off-values to ST-OnOff in OOXML Part 4". Archived from the original on 2009-06-26. Retrieved 2009-09-29.
  33. "OOXML and Office 2007 Conformance: a Smoke Test". Archived from the original on 2010-04-28. Retrieved 2009-09-29.
  34. "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
  35. "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.
  36. "Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats (Version 3)". Microsoft. 2007-06-18. Retrieved 2018-06-23.
  37. Open a Word 2007 document in an earlier version of Word - Word - Office.com. Office.microsoft.com. Retrieved on 2013-07-17.
  38. "Microsoft Expands List of Formats Supported in Microsoft Office". Microsoft. Retrieved 2008-05-21.
  39. "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.
  40. "Rivals Set Their Sights on Microsoft Office: Can They Topple the Giant? - Knowledge@Wharton". Knowledge.wharton.upenn.edu. Retrieved 2009-05-19.
  41. 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.
  42. "ISO OOXML convener: Microsoft's format "heading for failure"". Ars Technica. 2 April 2010.
  43. ^ Brown, Alex (31 March 2010). "Microsoft Fails the Standards Test". Where is an end of it?. Alex Brown's weblog. Retrieved 23 June 2018.
  44. "Collabora Online 6.4.0-released". 2 November 2020.
  45. "LibreOffice OOXML". Retrieved 22 March 2012.
  46. "OpenOffice.org 3.0 New Features". 2008-10-13. Retrieved 2009-10-24.
  47. "OpenOffice.org 3.2 New Features". 2010. Retrieved 2010-11-13.
  48. 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
  49. "3.2.0 (build OOO320_m12) - Release Notes". Retrieved 18 Feb 2013. Import of password protected Microsoft Office XML files

Further reading

External links

ISO standards by standard number
List of ISO standards – ISO romanizations – IEC standards
1–9999
10000–19999
20000–29999
30000+
Standards of Ecma International
Application interfaces
File systems (tape)
File systems (disk)
Graphics
Programming languages
Radio link interfaces
Other
List of Ecma standards (1961 – present)
Microsoft 365
Microsoft Office
Windows
Mac
Applications
(list)
Desktop
Server
Mobile
Web
Discontinued
Technologies
Related
Multi-purpose office document file formats
Editable document formats
Fixed document formats
Related topics
Document markup languages
Office suite
Well-known
Lesser-known
List of document markup languages
Categories:
Office Open XML: Difference between revisions Add topic