Office Open XML

From Wikipedia, the free encyclopedia

Jump to: navigation, search
Not to be confused with OpenDocument (another XML document format), OpenOffice.org XML (a deprecated format used by earlier versions of OpenOffice.org), or Microsoft Office XML formats (a deprecated format used by earlier versions of Microsoft Office).
Office Open XML
Office Open XML Document
Image:X-office-document.svg
Filename extension .docx or .docm
Internet media type application/vnd.
openxmlformats-officedocument.
wordprocessingml.
document[1]
Developed by Microsoft, Ecma, ISO/IEC
Type of format Document file format
Extended from XML, DOC, WordProcessingML
Standard(s) ECMA-376, ISO/IEC 29500
Website ECMA-376,
ISO/IEC 29500:2008
Office Open XML Presentation
Image:X-office-presentation.svg
Filename extension .pptx
Internet media type application/vnd.
openxmlformats-officedocument.
presentationml.
presentation[1]
Developed by Microsoft, Ecma, ISO/IEC
Type of format Presentation
Extended from XML, PPT
Standard(s) ECMA-376, ISO/IEC 29500
Website ECMA-376,
ISO/IEC 29500:2008
Office Open XML Workbook
Image:X-office-spreadsheet.svg
Filename extension .xlsx
Internet media type application/vnd.
openxmlformats-officedocument.
spreadsheetml.
sheet[1]
Developed by Microsoft, Ecma, ISO/IEC
Type of format Spreadsheet
Extended from XML, XLS, SpreadsheetML
Standard(s) ECMA-376, ISO/IEC 29500
Website ECMA-376,
ISO/IEC 29500:2008

Office Open XML (also referred to as OOXML, OpenXML, or Open XML) is a file format for representing spreadsheets, charts, presentations and word processing documents. An Office Open XML document file contains mainly XML-based files compressed within a zip package.

The Office Open XML format specification in 2006 became a free and open Ecma International standard.[2][3][4][5][6][7][8] In November 2008, after incorporating some of the proposed changes from ISO/IEC members during standardization process of Office Open XML a revised version of the specification was published as a multi-part International Standard ISO/IEC 29500:2008, Information technology – Office Open XML formats,[9] and as ECMA-376 Office Open XML File Formats - 2nd edition (December 2008). ISO/IEC 29500:2008 is a 4 part standard specification that can be freely downloaded.[10]

Microsoft originally developed the specification as a successor to its earlier binary and Office 2003 XML file formats. The specification was later handed over to Ecma International to be developed as the ECMA-376 standard, under the stewardship of Ecma International Technical Committee TC45. ECMA-376 was published in December 2006[11] and can be freely downloaded from Ecma International.[12]

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.[13]

Starting with Microsoft Office 2007, the Office Open XML file formats (ECMA-376) have become the default file format of Microsoft Office, the currently market-leading office suite.[14][15] Microsoft Office 14 will be the first version to implement the ISO/IEC IS 29500 compliant version of Office Open XML.[16][17][18]

Contents

[edit] Background

Prior to the 2007 edition, the core applications of the Microsoft Office software suite (primarily Word, Excel, and PowerPoint) by default stored their data in binary files. Historically, these files were difficult for other applications to interoperate with, due to the lack of publicly available information. Before 2007 Microsoft 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 Open Specification Promise.[19][20] Due to Microsoft keeping their prior 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 XML-based format for Microsoft Excel, which was incorporated in Office XP. In 2002, a new file format for Microsoft Word followed.[21] The Excel and Word formats – known as the Office 2003 XML formats – were later incorporated into the 2003 release of Microsoft Office.

In May 2004, governments and the European Union recommended to Microsoft that they publish and standardize their XML Office formats through a standardization organization.[21][22] Microsoft announced in November 2005 that it would standardize the new version of their XML-based formats through Ecma International, as "Ecma Office Open XML".[23]

[edit] File format and structure

Office Open XML main components

Office Open XML uses a file package conforming to the Open Packaging Convention. This format uses mechanisms from the ZIP file format 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.

[edit] Document markup languages

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

The primary markup languages are:

  • WordprocessingML for word-processing
  • SpreadsheetML for spreadsheets
  • PresentationML for presentations

Shared markup language materials include:

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

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

The XML Schema of Office Open XML emphasizes reducing load time and improving parsing speed. In a test with applications current in April 2007, XML-based office documents were slower to load than binary formats.[24] 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 HTML, for example, which is fairly flat, designed for humans to write in text editors and is more congenial for humans to read.

[edit] 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,[25] footnotes, comments, images and elaborate formatting and styles.[26] The OMML format is different from the World Wide Web Consortium (W3C) MathML recommendation that does not support those office features, but is partially compatible[27] through relatively simple XSL Transformations.

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

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

[edit] DrawingML
Example of DrawingML charts

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

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

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

A DrawingML graphic's dimensions are specified in English Metric Units (EMUs). This unit is defined as 1/360,000 of a centimeter and thus there are 914,400 EMUs per inch, and 12,700 EMUs per point. This unit was chosen so that integers can be used to accurately represent most dimensions encountered in a document. Floating point cannot accurately represent a fraction that is not a sum of powers of two and the error is magnified when the fractions are added together many times, resulting in misalignment. As an inch is 2.54 centimeters, or 127/50, the inch must be divided by 127 so that both 1 inch and 1 centimeter are an integer. To accurately represent decimal to 2 digits, a divisor of 100 is needed. To accurately represent a point a divisor of 72 is needed, which also allows divisions of 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 (the least common multiple would work as well which would have been 228,600 per inch and 90,000 per centimeter). According to Rick Jelliffe, programmer and standards activist (ISO, W3C, IETF), EMUs are a rational solution to a particular set of design criteria.[29]

[edit] Container structure

Main article: Open Packaging Convention
Container structure of Part 2 of the Ecma Office Open XML standard, ECMA-376

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

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

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

[edit] Relationships

[edit] Relationship files in Office Open XML

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

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

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

[edit] Hyperlink relations

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

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

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

[edit] Embedded or linked media file relations

Pictures can be embedded or linked using a tag:

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

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

[edit] Document properties

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

[edit] Core properties

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

<?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>Wikipedia</dc:creator>
  <cp:keywords>Office Open XML, Metadata, Dublin Core</cp:keywords>
  <dc:description>Office Open XML uses ISO 15836:2003</dc:description>
  <cp:lastModifiedBy>Wikipedia</cp:lastModifiedBy>
  <cp:revision>1</cp:revision>
  <dcterms:created xsi:type="dcterms:W3CDTF">2008-06-19T20:00:00Z</dcterms:created>
  <dcterms:modified xsi:type="dcterms:W3CDTF">2008-06-19T20:42:00Z</dcterms:modified>
  <cp:category>Document file format</cp:category>
  <cp:contentStatus>Final</cp:contentStatus>
</cp:coreProperties>

[edit] Structure of the standard

To aid the reader's understanding, the Office Open XML specification contains both normative material and informative material.

[edit] ISO/IEC 29500:2008

The ISO/IEC standard is structured into four parts, each of which are independent standards.[31][citation needed]

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, thumbnails and digital signatures
XML schemas for the OPC are declared as XML Schema Definitions (XSD) and (non-normatively) using RELAX NG (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 NVDL (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 and ISO/IEC 29500:2008

The standard specifies six 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.

[edit] ECMA-376 1st edition (2006)

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

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
Defines the Open Packaging Conventions (package model, physical package)
Defines core properties, thumbnails and digital signatures
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 and attributes by which applications with different extensions can interoperate
Extensibility rules are expressed using NVDL (ISO/IEC 19757-4)

[edit] Licensing

[edit] Reasonable and Non Discriminatory

Ecma International provides specifications that "can be freely copied by all interested parties without restrictions".[32] Under the Ecma code of conduct in patent matters, participating and approving member organisations are required to make available their patent rights on a Reasonable and Non Discriminatory (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. That is why Microsoft, a main contributor to the standard, provided a Covenant Not to Sue[33] for its patent licensing. The covenant received a mixed reception, with some (like the Groklaw blog) identifying problems[34] and others (such as Lawrence Rosen, an attorney and lecturer at Stanford Law School) endorsing it.[35]

[edit] Open Specification Promise

Main article: Open Specification Promise

Microsoft also added the format to their Open Specification Promise[36] 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 […]"

subject to certain restrictions. Office Open XML can therefore be used under the Covenant Not to Sue or the Open Specification Promise.

The Open Specification Promise was included in documents submitted to ISO in support of the ECMA-376 fast track submission.[37] Ecma International asserted that, "The OSP enables both open source and commercial software to implement [the specification]."[38]

In support of the licensing arrangements Microsoft commissioned an analysis from the London legal firm Baker & McKenzie.[39]

Several standards and OSS licensing experts expressed support in 2006 of the OSP. A 2006 article in Cover Pages quotes Lawrence Rosen, an attorney and lecturer at Stanford Law School, as saying,

"I'm pleased that this OSP is compatible with free and open source licenses."[40]

In 2006[41], Mark Webbink; a lawyer and member of the board of the Software Freedom Law Center, and former employee of Linux vendor Red Hat; has said,

"Red Hat believes that the text of the OSP gives sufficient flexibility to implement the listed specifications in software licensed under free and open source licenses. We commend Microsoft’s efforts to reach out to representatives from the open source community and solicit their feedback on this text, and Microsoft's willingness to make modifications in response to our comments."[42]

Standards lawyer Andy Updegrove said in 2006 the Open Specification Promise was

"[…] what I consider to be a highly desirable tool for facilitating the implementation of open standards, in particular where those standards are of interest to the open source community."[43]

On March 12, 2008 the Software Freedom Law Center, which provides services to protect and advance free software and open source software, has warned of problems with the Open Specification Promise as it relates to Office Open XML and the GNU General Public License (GPL).[44] In a published analysis of the promise it states that[45]

  • "Any code that implements the specification may also do other things in other contexts, so in effect the OSP does not cover any actual code, only some uses of code."[46]
  • "...it permits implementation under free software licenses so long as the resulting code isn't used freely."[46]
  • "The OSP cannot be relied upon by GPL developers for their implementations not because its provisions conflict with GPL, but because it does not provide the freedom that the GPL requires."[46]

Microsoft amended the OSP FAQ to specifically assure GPL license users that the open licensing of its covered formats through the Open Specification Promise applies to users of the GPL license when implementing covered implementations:

"The OSP provides the assurance that Microsoft will not assert its Necessary Claims against anyone who make, use, sell, offer for sale, import, or distribute any Covered Implementation under any type of development or distribution model, including the GPL."[47]

Legal experts and academics[who?] have confirmed that the licensing is similar to the licensing terms offered by IBM, and to a lesser extent Sun and Adobe Systems on their Office formats but warned that ambiguous legal jargon contained in Microsoft's Open Specification Promise, although understood in the terminology of the specialist patent and intellectual property law community, makes it hard for small developers to determine with certainty that Microsoft will not be entitled to sue them for using OOXML. They[who?] criticize Microsoft for not explicitly defining which parts of the specification contains intellectual property.[citation needed] The OSP has never been tested in a court of law regarding intellectual property rights, and the OSP does not name which court or jurisdiction a dispute will be heard in. David Vaile, executive director of the Cyberspace Law and Policy Centre at the University of New South Wales, acknowledges that the Microsoft approach to its Open Specification Promise is similar although not identical to other approaches used by IBM, and to a lesser extent Adobe and Sun, and that these represent a substantial advance on the past practice of negotiating long case-by-case agreements.[48]

[edit] Standardization

Main article: Standardization of Office Open XML

Office Open XML is an Ecma standard (Ecma-376, approved on 7 December 2006). ECMA-376 was created using as a basis a new version of the Microsoft Office 2003 XML file format, donated by Microsoft, which was being created for Microsoft Office 12.

The specification entered fast-track standardization within ISO/IEC as DIS 29500 (Draft International Standard 29500).[49] In a September 2007 vote by ISO/IEC member bodies, the draft text was not approved as an international standard. A ballot resolution process in March 2008 amended the text.

On April 2, 2008, ISO and IEC officially stated that the DIS 29500 had been approved for acceptance as an ISO/IEC Standard, pending any appeals.[13] In accordance with the JTC 1 directives the Project Editor created a new version with the final text within a month after the BRM, to be published as ISO/IEC 29500. After review and corrections this text has been distributed to the members of SC34.[50]

On May 21, 2008, Microsoft announced that it will be an active participant in the future evolution of the Office Open XML standard.[16]

In October 2008, ISO/IEC committee JTC1/SC34 (Document Description and Processing Languages) created a working group for maintenance of the ISO/IEC 29500 standard within ISO/IEC.[51]

In November 2008, the new international standard was published as ISO/IEC 29500:2008, Information technology – Office Open XML formats.

In December 2008, Ecma International published ECMA-376 Office Open XML File Formats - 2nd edition, an updated version of ECMA-376 that is identical to ISO/IEC 29500:2008.

[edit] Response

 Please help improve this article or section by expanding it. Further information might be found on the talk page. (January 2009)

The Microsoft Office applications Word, Excel and PowerPoint 2007 and later promote the Office Open XML format, as it is used as their default file format. Several groups and companies support the Office Open XML document format. For example:

  • The Open XML Community site launched in May 2007, with 327 inaugural members. The community has now grown to over 3,100 members.[52]
  • The non-profit organization RosettaNet Malyasia announced the release of a business-to-business standard called RosettaNet Automated Enablement standard (RAE) using the Office Open XML document standard.[55]
  • Members and partners of the Interop Vendor Alliance (IVA) test and promote interoperability of Office Open XML files across a wide range of applications on mixed platforms.[56]
  • The Open XML Developer site was launched to promote these formats and to support developers impementing the specification.

[edit] Criticism of ECMA-376 1st edition

The ODF Alliance UK Action Group has stated that with OpenDocument an ISO-standard for Office files already exists.[57] Further, they argue that the Office Open XML file-format is heavily based on Microsoft's own Office applications and is thus not vendor-neutral, and that it has inconsistencies with existing ISO standards such as time and date formats and color codes.[57]

[edit] Specific criticism

  • Use of DrawingML and the transitional-use-only VML instead of W3C recommendation SVG.[58] VML did not become a W3C recommendation.[59]
  • Use of Office MathML instead of W3C recommendation MathML.[60]
  • Office Open XML does not define a macro language, leaving this aspect to be application-defined.[61]
  • The standard is long, with the version submitted to ISO comprising 6546 pages. Google alleges that this length is unnecessary, saying that the OpenDocument specification is 867 pages in length and achieves the same goals.[62] That coupled with the fast track standardization process, Google notes, reduces the review time per page ratio.[62]
  • A comparison of some specific items in the format specification documents of Office Open XML and OpenDocument formats is used to claim disharmony within the Office Open XML format. For example, OOXML implements three different methods for specifying the color and alignment of text depending on whether the document is a text, spreadsheet, or presentation whereas ODF uses the same method for all three.[63]

[edit] Worldwide adoption

 Please help improve this article or section by expanding it. Further information might be found on the talk page. (November 2008)

[edit] Belgium

Belgium's Federal Public Service for Information and Communication Technology is evaluating the adoption of the Office Open XML format. Federal administrations may use the file format for creating, saving and exchanging office documents.[64]

[edit] Commonwealth of Massachusetts

The US state of Massachusetts has been examining its options for implementing XML-based document processing. In early 2005, Eric Kriss, Secretary of Administration and Finance in Massachusetts, was the first government official in the United States to publicly connect open formats to a public policy purpose: "It is an overriding imperative of the American democratic 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."[65] Since 2007 Massachusetts classifies Office Open XML as "Open Format" and has amended its approved technical standards list — the Enterprise Technical Reference Model (ETRM) — to include Office Open XML. Massachusetts now formally endorses Office Open XML formats for its public records.[66]

[edit] Denmark

In June 2007, the Danish Ministry of Science, Technology and Innovation 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.[67]

[edit] Germany

In Germany 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), see SAGA 4.0[68]). It may be used to exchange complex documents when further processing is required.

[edit] Lithuania

Lithuanian Standards Board has adopted the ISO/IEC 29500:2008 Office Open XML format standard as Lithuanian 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 Government of the Republic of Lithuania.[69]

[edit] Norway

Norway's Ministry of Government Administration and Reform is evaluating the adoption of the Office Open XML format. The ministry put the document standard under observation in December 2007.[70]

[edit] Switzerland

In July 2007, the Swiss Federal Council announced adherence SAGA.ch e-Government 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.[71]

[edit] Application support

Main article: Office Open XML software
The list here is not exhaustive. Another list of supporting/partial implementations of Office Open XML can be found on Microsoft's office open XML Community website, but it is also not exhaustive.

[edit] ECMA-376 implementations

The ECMA-376 1st edition (December 2006) standard is supported in several office suites from various vendors.

[edit] Office applications

  • AbiWord includes an input filter for Office Open XML text documents beginning with version 2.6.0.[72] Export of Office Open XML text documents is supported beginning with version 2.6.5.[73]
  • Adobe Buzzword, the online word processor by Adobe Systems, imports and exports Microsoft Word (DOC), Office Open XML (DOCX), OpenDocument (ODT) and Word 2003 XML files.[74]
  • Apple Inc.'s iWork '08 suite has read-only support for Office Open XML word processing, spreadsheet and presentation file formats in Pages, Numbers and Keynote (respectively).[75][76][77]
  • Apple Inc.'s iPhone has read-only support for Office Open XML attachments to email.[78]
  • Apple Inc.'s TextEdit, the built-in word processing program of Mac OS X, has read and write support for Office Open XML files starting with Mac OS X v10.5.[79]
  • Butler Office Pro X 2.2.0+ is NeoOffice variant and has built-in support for Office Open XML files. It is available for Mac OS X.[80]
  • Corel WordPerfect Office X4 includes import-only support for Office Open XML.[81]
  • DataViz' Documents To Go for PalmOS, Windows Mobile and Symbian OS (UIQ, S80) supports Office Open XML documents.[82]
  • Gnumeric has limited SpreadsheetML support.[83]
  • Go-oo (OpenOffice.org variant) has built-in support for opening Office Open XML files. Version 3.x is available for Windows 2000/XP/Vista and for most of Linux distributions. Go-oo Version 2.4.1 is available also for Windows 98/ME.[84]
  • JustSystems' Ichitaro 2008 word processor has built-in support for Office Open XML files. It is available for Windows and Linux.[85]
  • Kingsoft Office 2009 for Windows has import-only support for Office Open XML text documents and spreadsheets. This support is marked as "beta" in program's file browser.[86]
  • Microsoft Office 2007 for Windows uses the Office Open XML format as the default.
  • Older versions of Microsoft Office (2000, XP and 2003) require a free compatibility pack provided by Microsoft.[87] It is available for Windows 2000 Service Pack 4 and newer operating systems. The compatibility pack does not require Microsoft Office, but does require Microsoft Windows. It can be used as a standalone converter with products that read Office's older binary formats, such as OpenOffice.org.[88]
  • Microsoft Office 2008 for Mac supports the Office Open XML format.[89] For older versions of Office on the Mac, a converter is available.
  • Microsoft Office Mobile 6.1 supports Office Open XML on Mobile devices.[90]
  • Microsoft Works 9.0 Word Processor supports Office Open XML documents.[91]
  • The Mac OS X-based NeoOffice office suite supports opening, editing, and saving of most Office Open XML documents since version 2.1.[92]
  • Nisus Writer Pro 1.2 for Mac OS X v10.4 or later supports Office Open XML documents.[93]
  • OpenOffice.org has built-in support for opening Office Open XML text documents, spreadsheets and presentations beginning with OpenOffice.org version 3.0 (October 2008). It is available for Windows 2000/XP/Vista, Mac OS X (Intel/PowerPC), Linux, Solaris, FreeBSD (*BSD)[94]
  • OpenXML Writer is an open source text editor for creating WordprocessingML files.[95]
  • The online Thinkfree Office supports Office Open XML word processing files, and will support spreadsheets and presentation files in the future.[96]
  • Online word processor Zoho Writer supports exporting to the Office Open XML WordprocessingML format.[97]

[edit] Viewers, filters and converters

  • Microsoft has created Office Open XML Converter for Mac OS X that can convert Office Open XML files to the former binary file formats used in older versions of Microsoft Office.[98]
  • OxygenOffice includes xmlfilter which is the code that OpenOffice.org 3 will use to process Office Open XML files, and xmlfilter is completely different than OdfConverter.[99] This filter however is only for importing Office Open XML files not for exporting them.
  • docXConverter by Panergy Ltd. converts from WordprocessingML to Rich Text Format (RTF) and from SpreadsheetML to Comma-separated values (CSV). docXConverter can be used to transfer WordprocessingML data to other applications that read RTF data such as Word 97.[100]
  • Microsoft and Sonata Software created a plugin to convert Office Open XML text documents to DAISY XML, an open standard format used for creating spoken document for disabled people.[101]
  • Google search supports direct HTML view of Office Open XML files. Found files can be viewed directly in a converted HTML view.[102]
  • OpenXML Document Viewer is an open source command line utility that provides Office Open XML to HTML transformation to display WordprocessingML files in web browsers.[103]
  • DataViz MacLinkPlus Deluxe 16 supports Office Open XML file formats.[104]

[edit] Other products

  • Altova DiffDog supports detailed differencing for Office Open XML and ZIP archive file pairs.[105]
  • Altova MapForce includes support for data integration based on the Office Open XML spreadsheet data format.[105]
  • Altova StyleVision adds Word 2007 (Office Open XML) wordprocessing capabilities to its graphical stylesheet design tool.[106]
  • Altova XMLSpy, an XML editor for modeling, editing, transforming, and debugging XML technologies supports Office Open XML file formats.[107]
  • Aspose.Words supports loading, generating, saving and converting OOXML documents.
  • IBM DB2 Content Manager V8.4 clients support Office Open XML file formats.[108]
  • IBM Lotus Domino 8.0.2 server and IBM Lotus Notes 8.0.2 client KeyView (10.4.0.0) filter supports Office Open XML formats for viewing files.[109]
  • IBM Lotus Quickr V8.0 includes support for Office Open XML documents.[110]
  • Nuance OmniPage Professional 16, an OCR and Document Conversion Software, was the first desktop OCR application to provide native support for the Office Open XML standard.[111]
  • Oxygen XML Editor provides ready to use validation, editing and processing support for Office Open XML files. These capabilities allow developers to use data from office documents together with validation and transformations (using XSLT or XQuery) to other file formats. Validation is done using the latest ECMA-376 XML Schemas.[112]
  • RIM BlackBerry Enterprise Server software version 4.1 SP4 (4.1.4) supports Office Open XML file formats.[113]
  • Softinterface 'Diff Doc' supports fast and accurate file comparison for Office Open XML file pairs.[114]

[edit] Planned and beta software

[edit] Implementations of new 2008 version

 This article or section contains information about scheduled or expected future software.
The content may change as the software release approaches and more information becomes available.

The newest version of Office Open XML is formally known as either ISO/IEC 29500:2008 or as ECMA-376 2nd edition (December 2008). Microsoft has stated that Microsoft Office 14 will be the first version of Microsoft Office to support ISO/IEC 29500, though no release date has been announced.[16]

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 OOXML files.[120]

Microsoft, whose products currently only support the ECMA-376 standard version of Office Open XML, has committed to using the ISO/IEC 29500 standard in their products[121] and has also committed to participate in the maintenance of this standard.

In a ZDNet article Alex Brown, leader of the ISO/IEC group in charge of deciding maintenance processes for any ISO/IEC 29500 Standard, stated

"I am hoping that Microsoft Office will shortly be brought into line with the [ISO/IEC] 29500 specification, and will stay that way".[122]

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

"will definitely be 100% compliant with the final ISO/IEC 29500 spec, including the changes accepted at the BRM".[123]

In a ComputerWorld interview from 2008, Doug Mahugh said that

"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".[124]

[edit] Implementations

[edit] See also

Sister project Wikimedia Commons has media related to: OOXML

[edit] References

  1. ^ a b c Microsoft. "Register file extensions on third party servers". microsoft.com. http://technet2.microsoft.com/Office/ja-JP/library/f88d06fb-c9a4-413c-a1d3-40c97e340c5a1041.mspx?mfr=true. Retrieved on 2008-04-09. 
  2. ^ http://www.ecma-international.org/activities/General/presentingecma.ppt
  3. ^ Ecma formal publications
  4. ^ Microsoft PowerPoint - BSI OOXML v1b.ppt
  5. ^ http://www.mass.gov/Aitd/docs/policies_standards/etrmv4dot0/etrmv4dot0information.rtf
  6. ^ http://www.itscj.ipsj.or.jp/sc34/open/1026.pdf
  7. ^ "Office Open XML wird als weltweiter ISO/IEC-Standard anerkannt". ntz Fachzeitschrift für Informations- und Kommunikationstechnik (Berlin: VDE-Verlag) (3-4): 10. 2008. ISSN 0948-728X. http://www.vde-verlag.de/ntz.html. 
  8. ^ Techtree.com India > News > Software > ISO puts Microsoft's OOXML Standard on Hold
  9. ^ ISO/IEC (2008-11-18). "Publication of ISO/IEC 29500:2008, Information technology - Office Open XML formats". ISO. http://www.iso.org/iso/pressrelease.htm?refid=Ref1181. Retrieved on 2008-11-19. 
  10. ^ "Freely Available Standards". ITTF (ISO). 2008-11-18. http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html. 
  11. ^ Ecma International (December 7, 2006). Ecma International approves Office Open XML standard. Press release. http://www.ecma-international.org/news/PressReleases/PR_TC45_Dec2006.htm. Retrieved on 2006-12-08. 
  12. ^ a b Standard ECMA-376
  13. ^ a b "ISO/IEC DIS 29500 receives necessary votes for approval as an International Standard". ISO. 2008-04-02. http://www.iso.org/iso/pressrelease.htm?refid=Ref1123. 
  14. ^ http://www.courierpress.com/news/2008/oct/24/microsofts-future-lies-somewhere-beyond-the/
  15. ^ http://knowledge.wharton.upenn.edu/article.cfm?articleid=1795
  16. ^ a b c Microsoft Expands List of Formats Supported in Microsoft Office
  17. ^ http://www.computerworld.com/action/article.do?command=viewArticleBasic&taxonomyName=Protocols+and+Standards&articleId=9089258&taxonomyId=141&pageNumber=1
  18. ^ http://consortiuminfo.org/standardsblog/article.php?story=20080521092930864
  19. ^ "How to extract information from Office files by using Office file formats and schemas". Microsoft. 2007-03-27. http://support.microsoft.com/kb/840817/en-us#. Retrieved on 2007-07-10. 
  20. ^ "Microsoft Office Binary (doc, xls, ppt) File Formats". Microsoft. 2008-02-15. http://www.microsoft.com/interop/docs/officebinaryformats.mspx. Retrieved on 2008-04-05. 
  21. ^ a b Brian Jones (2007-01-25). "History of office XML formats (1998–2006)". http://blogs.msdn.com/brian_jones/archive/2007/01/25/office-xml-formats-1998-2006.aspx. 
  22. ^ Telematics between Administrations Committee based on IDA expert group on open document formats (2004-05-25). "TAC approval on conclusions and recommendations on open document formats". IDABC - European eGovernment Services. http://ec.europa.eu/idabc/en/document/2592/5588. Retrieved on 2007-07-30. 
  23. ^ "Microsoft Co-Sponsors Submission of Office Open XML Document Formats to Ecma International for Standardization". Microsoft. 2005-11-21. http://www.microsoft.com/presspass/features/2005/nov05/11-21Ecma.mspx. 
  24. ^ George Ou (2007-04-27). "MS Office 2007 versus Open Office 2.2 shootout". ZDnet.com. http://blogs.zdnet.com/Ou/?p=480. Retrieved on 2007-04-27. 
  25. ^ Jesper Lund Stocholm (2008-01-29). "Do your math - OOXML and OMML". A Mooh Point blog. http://idippedut.dk/post/2008/01/Do-your-math---OOXML-and-OMML.aspx. Retrieved on 2008-02-12. 
  26. ^ Murray Sargent (2007-06-05). "Science and Nature have difficulties with Word 2007 mathematics". MSDN blogs. http://blogs.msdn.com/murrays/archive/2007/06/05/science-and-nature-have-difficulties-with-word-2007-mathematics.aspx. Retrieved on 2007-07-31. 
  27. ^ David Carlisle (2007-05-09). "XHTML and MathML from Office 2007". David Carlisle. http://dpcarlisle.blogspot.com/2007/04/xhtml-and-mathml-from-office-20007.html. Retrieved on 2007-09-20. 
  28. ^ Wouter Van Vugt (2008-11-01). "Open XML Explained e-book". Openxmldeveloper.org. http://openxmldeveloper.org/articles/1970.aspx. Retrieved on 2007-09-14. 
  29. ^ http://www.oreillynet.com/xml/blog/2007/04/what_is_an_emu.html
  30. ^ Tom Ngo (December 11, 2006). "Office Open XML Overview" (PDF). Ecma International. 6. http://www.ecma-international.org/news/TC45_current_work/OpenXML%20White%20Paper.pdf. Retrieved on 2007-01-23. 
  31. ^ Rex Jaeshke - project editor (2008-09-26). "N1080 Final Text for ISO/IEC 29500-1, Information technology -- Document description and processing languages -- Office Open XML File Formats -- Part 1: Fundamentals and Markup Language Reference". http://lucia.itscj.ipsj.or.jp/itscj/servlets/ScmDoc10?Com_Id=34. 
  32. ^ "What is Ecma International". http://www.ecma-international.org/memento/index.html. 
  33. ^ "Microsoft Covenant Regarding Office 2003 XML Reference Schemas". Microsoft. http://www.microsoft.com/office/xml/covenant.mspx. Retrieved on 2006-07-11. 
  34. ^ "2 Escape Hatches in MS's Covenant Not to Sue". Groklaw. http://www.groklaw.net/articlebasic.php?story=20051202135844482. Retrieved on 2007-01-29. 
  35. ^ Berlind, David (November 28, 2005). "Top open source lawyer blesses new terms on Microsoft’s XML file format". ZDNet. http://blogs.zdnet.com/BTL/?p=2192. Retrieved on 2007-01-27. 
  36. ^ "Microsoft Open Specification Promise". Microsoft. 2006-09-12. http://www.microsoft.com/interop/osp/default.mspx. Retrieved on 2007-04-22. 
  37. ^ Licensing conditions that Microsoft offers for Office Open XML
  38. ^ -Response Document- National Body Comments from 30-Day Review of the Fast Track Ballot for ISO/IEC DIS 29500 (ECMA-376) Office Open XML File Formats
  39. ^ Baker & McKenzie (June 2006). "Standardization and Licensing of Microsoft’s Office Open XML Reference Schema" (PDF). Baker & McKenzie. http://www.bakernet.com/NR/rdonlyres/CC54A6B6-79E8-4E0D-B290-C836D5F70867/0/OpenXML.pdf. Retrieved on 2007-02-01. 
  40. ^ "Microsoft's Open Specification Promise Eases Web Services Patent Concerns.". xml.coverpages.org. 2006-09-12. http://xml.coverpages.org/ni2006-09-12-a.html. 
  41. ^ "Microsoft promises to hang patent fire over web services". 2006-09-12. http://www.computerbuyer.co.uk/buyer/news/93789/microsoft-promises-to-hang-patent-fire-over-web-services.html. 
  42. ^ "Microsoft Open Specification Promise". http://www.microsoft.com/interop/osp/default.mspx#EOHAC. 
  43. ^ Peter Galli (2006-09-12). "Microsoft Promises Not to Sue over Web Services Specs". http://www.devsource.com/c/a/Architecture/Microsoft-Promises-Not-to-Sue-over-Web-Services-Specs/. 
  44. ^ "Software Freedom Law Center Publishes Analysis of Microsoft's Open Specification Promise new article". Software Freedom Law Center. March 12, 2008. http://www.softwarefreedom.org/news/2008/mar/12/osp-gpl/. 
  45. ^ "Software Freedom Law Center Publishes Analysis of Microsoft's Open Specification Promise". Business Wire. March 12, 2008. http://www.smartmoney.com/news/pr/index.cfm?story=PR-20080312-002366-1529. 
  46. ^ a b c "Microsoft's Open Specification Promise: No Assurance for GPL". Software Freedom Law Center. March 12, 2008. http://www.softwarefreedom.org/resources/2008/osp-gpl.html. 
  47. ^ "Microsoft Open Specification Promise". http://www.microsoft.com/interop/osp/default.mspx#ELPAC. Retrieved on 2008-07-28. 
  48. ^ Winterford, Brett (2008-02-14). "Can Microsoft be trusted on OOXML covenants?". Australia: ZDNet. http://www.zdnet.com.au/insight/software/soa/Can-Microsoft-be-trusted-on-OOXML-covenants-/0,139023769,339285929,00.htm. Retrieved on 2008-07-07. 
  49. ^ ISO/IEC DIS 29500, Information technology -- Office Open XML file formats
  50. ^ IS 29500 has been sent to ITTF for publication (Jesper Lund Stocholm, personal blog - "This will finally make it possible for the NBs of ISO to verify that the editorial instructions from the BRM has made it into the final text")
  51. ^ "Resolutions of ISO/IEC JTC 1/SC 34 Plenary Meeting, 2008-10-01, Jeju, Republic of Korea". ISO/IEC JTC1/SC34 Document Description and Processing Languages. 2008-10-01. http://www.itscj.ipsj.or.jp/sc34/open/1099.htm. Retrieved on 2008-10-09. 
  52. ^ http://www.openxmlcommunity.org/momentum.aspx
  53. ^ http://slashdot.org/article.pl?sid=07/10/28/175215
  54. ^ http://linux.slashdot.org/article.pl?sid=07/09/10/2343256&tid=109
  55. ^ http://www.zdnetasia.com/news/business/0,39044229,62033726,00.htm
  56. ^ http://interopvendoralliance.org/labs/
  57. ^ a b "ODF/OOXML technical white paper". Free Software Magazine. 2 Mai 2007. http://www.freesoftwaremagazine.com/articles/odf_ooxml_technical_white_paper. 
  58. ^ "The X Factor". reddevnews.com. October 2007. http://reddevnews.com/features/article.aspx?editorialsid=2356. 
  59. ^ VML - the Vector Markup Language
  60. ^ "Microsoft Office dumped by Science and Nature". ZDNet Australia. 18 June 2007. http://www.zdnet.com.au/news/software/soa/Microsoft-Office-dumped-by-Science-and-Nature/0,130061733,339278690,00.htm. 
  61. ^ "Microsoft New Zealand’s director of innovation puts the case for a new standard". Computerworld. 13 March 2008. http://computerworld.co.nz/news.nsf/news/14110D406CB0AB11CC2574050004FA06. 
  62. ^ a b "Googles position on OOXML" (PDF). http://www.odfalliance.org/resources/Google%20XML%20Q%20%20A%20(2).pdf. 
  63. ^ Rob Weir (14 March 2008). "Disharmony of OOXML". http://www.robweir.com/blog/2008/03/disharmony-of-ooxml.html. 
  64. ^ http://www.fedict.belgium.be/nl/binaries/Open_Standaarden_NL_V1_tcm167-16667.pdf
  65. ^ Administration and Finance
  66. ^ http://xml.coverpages.org/ni2007-07-03-a.html
  67. ^ http://vtu.dk/nyheder/aktuelle-temaer/2007/aabne-standarder/bilag/bilag-8.html/
  68. ^ http://gsb.download.bva.bund.de/KBSt/SAGA/SAGA_v4.0.pdf PDF
  69. ^ http://www.openxmlcommunity.com/latestnews.aspx
  70. ^ http://www.regjeringen.no/en/dep/fad/Documents/Rundskriv/2007/Referansekatalog-for-IT-standarder-i-off.html?id=494951
  71. ^ http://www.ech.ch/index.php?option=com_docman&task=cat_view&gid=92&lang=en
  72. ^ "AbiWord v2.6.0 Released". www.abisource.com. http://abisource.com/release-notes/2.6.0.phtml. Retrieved on 2008-03-24. 
  73. ^ "AbiWord v2.6.5 Changelog". www.abisource.com. http://www.abisource.com/changelogs/2.6.5.phtml. Retrieved on 2008-12-19. 
  74. ^ http://labs.adobe.com/technologies/buzzword/
  75. ^ "Apple - iWork - Pages". http://www.apple.com/iwork/pages/#compatible. Retrieved on 2007-07-08. 
  76. ^ "Apple - iWork - Numbers". http://www.apple.com/iwork/numbers/#compatibility. Retrieved on 2007-07-08. 
  77. ^ "Apple - iWork - Keynote". http://www.apple.com/iwork/keynote/#share. Retrieved on 2007-07-08. 
  78. ^ ""iPhone User's Guide"" (PDF). Apple, Inc.. http://manuals.info.apple.com/en/iPhone_User_Guide.pdf#page=48. 
  79. ^ "Apple - Pro - Tips - Editing Word Files — Without Word". http://www.apple.com/pro/tips/word_files.html?sr=hotnews. Retrieved on 2008-07-12. 
  80. ^ "Mac office alternative for text, spreadsheet and other Mac office applications". Butler Software Solutions. 2008-09-20. http://www.butlerofficepro.com/news.html. Retrieved on 2008-12-13. 
  81. ^ "WordPerfect Office X4, Do more with words, numbers and ideas". Corel. http://www.corel.com/servlet/Satellite/us/en/Product/1151523326841. Retrieved on 2008-04-18. 
  82. ^ ""DocumentsToGo for PalmOS Premium Edition"". Dataviz. http://www.dataviz.com/products/documentstogo/premium/index.html. 
  83. ^ "Gnumeric 1.8 is Here!". www.gnome.org. http://www.gnome.org/projects/gnumeric/announcements/1.8/gnumeric-1.8.shtml. Retrieved on 2008-01-28. 
  84. ^ "Go-OO features". http://go-oo.org/. 
  85. ^ "日本語ワードプロセッサ 一太郎2009". JustSystems. http://www.justsystems.com/jp/products/ichitaro/. Retrieved on 2008-12-13. 
  86. ^ "Kingsoft Research, The home of Kingsoft Office 2009". Kingsoft Research Corporation. http://www.kingsoftresearch.com/index.aspx. Retrieved on 2008-12-13. 
  87. ^ "Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats (Version 3)". Microsoft. 2007-06-18. http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=941B3470-3AE9-4AEE-8F43-C6BB74CD1466. Retrieved on 2007-09-04. 
  88. ^ "Office Compatibility Pack Review". OpenOffice.org Ninja. 2008-02-06. http://www.oooninja.com/2008/02/office-compatibility-pack-review.html. Retrieved on 2008-02-26. 
  89. ^ Amazon. "Microsoft Office 2008 for Mac". http://www.amazon.com/Microsoft-Office-2008-for-Mac/dp/B000WR2F2M/ref=pd_bbs_sr_4?ie=UTF8&s=software&qid=1199396007&sr=8-4. 
  90. ^ "Microsoft Office Mobile 6.1: Upgrade for Microsoft Office 2007 file formats". Microsoft. 2007-11-28. http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=4b106c1f-51e2-42f0-ba32-69bb7e9a3814. Retrieved on 2007-11-29. 
  91. ^ "Microsoft Works 9 - Works 9: Features". Microsoft Corporation. http://www.microsoft.com/products/works/ProductDetails.aspx?pid=003&active_tab=Features. Retrieved on 2008-12-13. 
  92. ^ "NeoOffice 2.2.1 for Mac OS X Released". trinity.neooffice.org. 2007-08-26. http://trinity.neooffice.org/index.php. Retrieved on 2007-10-09. 
  93. ^ "Nisus Writer Pro - Powerful Word Processor for Mac OS X". Nisus Software, Inc.. http://nisus.com/pro/. Retrieved on 2008-12-13. 
  94. ^ "OpenOffice.org 3.0 New Features". 2008-10-13. http://www.openoffice.org/dev_docs/features/3.0/#Microsoft_Office_2007_Import_Filters. 
  95. ^ OpenXML.biz (2008-06-30). "OpenXML Writer - An opensource editor for generating .docx files". http://www.openxml.biz/OpenXMLWriter.html. 
  96. ^ "Power Edit MS Word 2007 (DOCX) Support". http://product.thinkfree.com/Docxsupport.html. Retrieved on 2007-10-09. 
  97. ^ Raju Vegesna (2008-02-27). "Zoho Writer Update: DocX Support, Thesaurus, Group Sharing & More". http://blogs.zoho.com/writer/zoho-writer-update-docx-support-thesaurus-group-sharing-more/. 
  98. ^ "Conversieprogramma voor de Open XML-bestandsindeling voor Mac 1.0". 2008-06-24. http://www.microsoft.com/downloads/details.aspx?displaylang=nl&FamilyID=6b9238e1-cf69-48c4-bf2d-c4a8aceee520. 
  99. ^ "OxygenOffice as a Word 2007 (.docx) converter". OpenOffice.org Ninja. 2008-02-25. http://www.oooninja.com/2008/02/word-2007-docx-converter-oxygenoffice.html. Retrieved on 2008-02-26. 
  100. ^ "docXConverter - Features". panergy. http://www.panergy-software.com/products/docxconverter/features.html. Retrieved on 2007-01-31. 
  101. ^ "Easily Translate Open XML to DAISY XML Standards". openxmlcommunity.org. http://www.openxmlcommunity.org/daisy/. Retrieved on 2008-05-15. 
  102. ^ Brian Jones (2008-01-17). "Google support for Open XML formats". http://blogs.msdn.com/brian_jones/archive/2008/01/17/google-support-for-open-xml-formats.aspx. 
  103. ^ Microsoft (2008-06-30). "Microsoft Takes Additional Steps in Implementing Interoperability Principles". http://www.microsoft.com/presspass/press/2008/jun08/06-30InteropUpdatePR.mspx. 
  104. ^ http://www.dataviz.com/news/press/pressreleases/Detail.html?id=170
  105. ^ a b "Altova Announces Version 2008 Release 2 of its Software Product Line". http://www.altova.com/Version2008R2_042908.html. Retrieved on 2008-04-29. 
  106. ^ "Altova Adds Word 2007 (OOXML) Capabilities to its Graphical Stylesheet Design Tool and Cuts the Price to Ease Adoption". http://www.altova.com/StyleVisionOOXML_v2008r2_050108.html. 
  107. ^ "Altova XMLSpy Now Supports New ECMA Office Open XML File Formats". Altova. http://www.altova.com/OOXML_060407.html. Retrieved on 2008-04-15. 
  108. ^ "DB2 Content Manager V8.4 Clients Support for Office Open XML File Formats". IBM. http://www-1.ibm.com/support/docview.wss?uid=swg21288972. Retrieved on 2008-07-09. 
  109. ^ http://publibfp.boulder.ibm.com/epubs/pdf/c2359762.pdf
  110. ^ http://publib.boulder.ibm.com/infocenter/lqkrhelp/v8r0/index.jsp?topic=/com.ibm.lotus.quickr.user.dom.doc/h_AdminSecurityAdd_CreatorHelp.html
  111. ^ "Nuance Unveils OmniPage Professional 16". Nuance Communications. http://www.nuance.com/news/pressreleases/2007/20070731_op16.asp. Retrieved on 2008-04-15. 
  112. ^ "oXygen XML editor - Microsoft® Office 2007 - Office Open XML (OOXML)". SyncRO Soft Ltd.. http://www.oxygenxml.com/ooxml_office_2007.html. Retrieved on 2008-07-04. 
  113. ^ "Supported Microsoft Office (2007) Open XML file formats". Research In Motion Limited. http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB13306. Retrieved on 2008-06-30. 
  114. ^ "Softinterface releases Open XML friendly version of 'Diff Doc'". http://www.softinterface.com/MD/Document-Comparison-Software-Target.htm. Retrieved on 2009-03-2. 
  115. ^ "Office Open XML Support". Apache POI. http://poi.apache.org/. Retrieved on 2008-04-14. 
  116. ^ "ExtenXLS Office Open XML Support". Extentech Inc.. http://extentech.sheetster.com/knowledgebase/docs_home.jsp?meme_id=1741&showall=true. Retrieved on 2008-06-30. 
  117. ^ http://www-01.ibm.com/support/docview.wss?uid=swg21317706
  118. ^ http://www.softmaker.com/forum/viewtopic.php?f=118&t=6026&p=24525&sid=8e5bf6df7d35f9f91bd9eaba7f2d6e38#p24525
  119. ^ "UOF OpenXML Translator". 2008-04-15. http://uof-translator.sourceforge.net/. 
  120. ^ http://blogs.msdn.com/murrays/archive/2008/07/28/improved-mathml-support-in-word-2007.aspx
  121. ^ "An Open Letter from Chris Capossela, Senior Vice President, Microsoft Office". http://www.microsoft.com/interop/letters/ChrisCapOpenLetter.mspx. Retrieved on 2008-05-26. "... 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." 
  122. ^ "Microsoft Office 2007 fails OOXML conformance test". http://news.zdnet.co.uk/software/0,1000000121,39388229,00.htm. 
  123. ^ Open XML SDK roadmap
  124. ^ Microsoft releasing OOXML SDK
  125. ^ Microsoft (2008-06-10). "Open XML Format SDK". http://go.microsoft.com/fwlink/?LinkId=120908. 
  126. ^ Erika Ehrli (2008-06-10). "Announcing the Open XML Format SDK 1.0". http://blogs.msdn.com/erikaehrli/archive/2008/06/10/announcing-the-open-xml-format-sdk-1-0.aspx. 
  127. ^ a b Doug Mahugh. "Open XML SDK roadmap". MSDN Blogs. http://blogs.msdn.com/dmahugh/archive/2008/03/13/open-xml-sdk-roadmap.aspx. Retrieved on 2008-03-23. 
  128. ^ Eric Lai (2008-03-12). "Microsoft releasing OOXML SDK". http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9068198. 
  129. ^ PowerTools for Open XML
  130. ^ PowerTools license
  131. ^ Microsoft Public License (Ms-PL)

[edit] External links

v • d • e
Multi-purpose office document file formats
Editable document formats
Fixed document formats
v • d • e
Standards of Ecma International
ANSI escape code · C++/CLI · C# · CD-ROM · CLI · DDS · E4X · ECMAScript · Eiffel · FAT · FD · HVD · Office Open XML · U3D · UDF · UDO · UMD · UWB
List of Ecma standards
Retrieved from "http://en.wikipedia.org/wiki/Office_Open_XML"
Personal tools