Wikipedia

Office Open XML

This is an old revision of this page, as edited by Yesudeep (talk | contribs) at 14:31, 15 April 2008. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Template:Distinguish2

Office Open XML Document
Filename extension
.docx
Internet media type
application/vnd.
openxmlformats-officedocument.
wordprocessingml.document[1]
Developed byMicrosoft, Ecma International
Type of formatDocument file format
Extended fromXML, DOC, WordProcessingML
WebsiteEcma 376, ISO/IEC 29500
Office Open XML Presentation
Filename extension
.pptx
Internet media type
application/vnd.
openxmlformats-officedocument.
presentationml.presentation[1]
Developed byMicrosoft, Ecma International
Type of formatPresentation
Extended fromXML, PPT
WebsiteEcma 376, ISO/IEC 29500
Office Open XML Workbook
Filename extension
.xlsx
Internet media type
application/vnd.
openxmlformats-officedocument.
spreadsheetml.sheet[1]
Developed byMicrosoft, Ecma International
Type of formatSpreadsheet
Extended fromXML, XLS, SpreadsheetML
WebsiteEcma 376, ISO/IEC 29500

Office Open XML (ISO/IEC 29500 also referred to as OOXML or OpenXML) is a pseudo-open international "standard" for representing electronic documents such as spreadsheets, charts, presentations and word processing documents which can only be opened properly with Microsoft products. Your peers will not be able to open these documents because some parts of the specification for this standard are shady with keys guarded tightly by Microsoft.

Microsoft originally developed the specification as a successor to its binary Microsoft Office 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[2] and can be freely downloaded from Ecma international.[3]. The Microsoft Office Open XML 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. [4] Subject to there being no formal appeals from ISO/IEC national bodies in the next two months[5], the text of the standard will be published as ISO/IEC 29500.

Background

Prior to the 2007 edition of Microsoft Office, its component applications (such as the word-processor Word and spreadsheet Excel) used binary file formats for storing data by default. Historically, these formats have been difficult for developers to work with natively, because of a lack of publicly available information on, and royalty-free access to, the format specifications. (Microsoft does offer these binary format specifications under a royalty-free covenant not to sue as part of its Open Specification Promise[6][7]) While a level of support for the binary formats had been achieved by various applications, full interoperability remained elusive.

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

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

File format and structure

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

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
  • DrawingML used for vector drawing, charts, and for example, text art. (additionally, though deprecated, VML is supported for drawing).

Shared markup language materials include:

  • Office Math Markup Language (OMML)
  • 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 OOXML 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.[11] To enhance performance, OOXML uses very short element names for common elements and spreadsheets save dates as index numbers (starting from 1899 or from 1904). In order to be systematic and generic, OOXML typically uses separate child elements for data and metadata (element names ending in Pr for properties) rather than using multiple attributes, which allows structured properties. OOXML does not use mixed content but uses elements to put a series of text runs (element name r) into paragraphs (element name p). The result is terse and highly nested in contrast to HTML, for example, which is fairly flat, designed for humans to write in text editors 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 [12] , footnotes, comments, images and elaborate formatting and styles.[13] 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[14] through relatively simple XSL Transformations.

DrawingML
File:DrawingML text effect.png
Example of DrawingML text effects

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

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.

Container structure

Main article: Open Packaging Convention

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.[16] 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.
word/document.xml
This file is the main part for any Word document.

Relationships

Relationship files in Office Open XML

An example relationship file (from word/_rels/document.xml.rels) 

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

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

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

In this example, the URL is represented by "rId2". The actual URL is 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: 

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

Licensing

Reasonable and Non Discriminatory

Ecma International provides specifications that "can be freely copied by all interested parties without restrictions"[17]. 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[18] for its patent licensing. The covenant received a mixed reception, with some (like the Groklaw blog) identifying problems[19] and others (such as Lawrence Rosen, an attorney and lecturer at Stanford Law School) endorsing it.[20]

Open Specification Promise

Main article: Open Specification Promise

Microsoft also added the format to their Open Specification Promise[21] 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.[22] Ecma International asserted that, "The OSP enables both open source and commercial software to implement [the specification]."[23]

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

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

In 2006 [26] , 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."[27]

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

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 OOXML and the GPL[29]. In a published analysis of the promise it states that[30]

  • "Because of this narrow definition of the covered specifications, no future versions of any of the specifications are guaranteed to be covered under the OSP."[31]
  • "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."[31]
  • "...it permits implementation under free software licenses so long as the resulting code isn't used freely."[31]
  • "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." [31]

With Ecma International publishing the specification for free and patents made irrevocably available on a royalty-free basis trough the Open Specification Promise, Office Open XML conforms to all characteristics of the European Union's definition of an open standard.[32]

Standardization

Main article: Standardization of Office Open XML

Microsoft's Office Open XML is currently an Ecma standard (Ecma-376, approved on 7 December 2006). The specification entered fast-track standardization within ISO/IEC as DIS 29500 (Draft International Standard 29500).[33] In a round of voting by ISO/IEC national body members in September 2007, the draft text, which at that time was approximately 6000 pages, was not approved as an international standard. A ballot resolution process has amended the text, and a final decision has been reached on its approval at the end of March 2008, based on the 6000-page text + approximately 2000 pages of proposed amendments, and a promise to add 1400 more pages of XML-format documentation.

On April 2nd, 2008, ISO officially published that the DIS 29500 has been approved for acceptance as an ISO/IEC Standard following a JTC 1 fast tracking standardization process [34]. In accordance with the JTC 1 directives the Project Editor will now create the final text for scrutiny by ITTF and when this is complete the text will be published as ISO/IEC 29500; by ISO directives, this is supposed to happen within a month of final approval. There have been allegations that the ISO ballot process for OOXML was marred with voting irregularities and heavy-handed tactics by some stakeholders.[35][36]

Application support

The list here is not exhaustive. A More exhaustive list of supporting/partial implementations of Office Open XML can be found on Microsoft's office open XML Community website.

Implementation

Office Open XML (as specified by Ecma 376) is the default Microsoft Office 2007 format. For older versions of Office (2000, XP and 2003) a compatibility pack is provided.[37] It is available for Windows 2000 Service Pack 4 and newer operating systems.[38]. 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.[39]

  • Microsoft Office 2008 for Mac supports the Office Open XML format.[40] For older versions of Office on the Mac, a beta release of the Microsoft Office Open XML File Format Converter is available.[41] Microsoft had previously advised users of Office 2007 to save their files in the old Office binary format.[42]
  • Microsoft Office Mobile 6.1 supports Office Open XML on Mobile devices.[43]
  • 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).[44][45][46]
  • Apple Inc.'s TextEdit supports Office Open XML in OS X Leopard.[47]
  • Apple Inc.'s iPhone has read-only support for Office Open XML attachments to email.[48]
  • The online Thinkfree Office supports Office Open XML word processing files, and will support spreadsheets and presentation files in the future.[49]
  • Gnumeric has limited SpreadsheetML support.[50]
  • QuickOffice, a mobile office suite for Symbian and Palm OS, supports Office Open XML. [51]
  • Dataviz' DocumentsToGo for PalmOS supports Office Open XML documents.[52]
  • Datawatch supports Office Open XML spreadsheets in its report mining tool Monarch v9.0.[53]
  • Intergen has released a Silverlight plugin that allows Office Open XML word processing files to be viewed within a web browser.[54]
  • OpenOffice.org supports Office Open XML when used with the OpenXML/ODF Translator for OpenOffice.[55] The translator works with SuSe Linux, some versions of (K)ubuntu and Novell OpenOffice.org 2.3 for Microsoft Windows. It can be used from the command line.[56]
  • The Mac OS X-based NeoOffice office suite has supported Office Open XML since version 2.1.[57]
  • Online word processor Zoho Writer has added support for Office Open XML Wordprocessing files.[58]
  • Xpertdoc Studio is a document merge and assembly product which generates Office Open XML Wordprocessing files from any platform supporting DotNet or the Java language.[59]

Filters and Converters

  • 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[60]. This filter however is only for importing OOXML 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.[61]
  • Google search supports direct HTML view of Office Open XML files. Found files can be viewed directly in a converted HTML view. [62]

Planned and beta software

Template:Future software

  • Apache POI will support Office Open XML in the forthcoming 3.5 release, currently in alpha, which is aiming for a summer release.[63]
  • Corel has released beta version of their Corel Wordperfect Office X3 edition that includes support for Office Open XML.[64]
  • Office Open XML SDK, containing a set of managed code libraries to create and manipulate OOXML files programmatically, will be shipped by Microsoft. Currently available in a CTP release, version 1.0 will be released in May 2008.[65] The shipping version of the SDK will incorporate the changes made to the OOXML specification made during the current ISO/SEC standardization process.[66] Version 2 of the OOXML SDK will support validating OOXML documents against the OOXML schema, as well as searching in OOXML documents.[65]
  • OpenOffice.org 3.0 alpha supports Office Open XML.[67]

Criticism

It has often been criticized that with OpenDocument there exists already an ISO-standard for Office files and that two competing standards are against the very concept of a standard.[68] Further, critics 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 (time and date format, color codes, etc.)[69]

Specific criticism

  • Use of DrawingML and the transitional-use-only VML instead of W3C recommendation SVG.[70] VML did not become a W3C recommendation.[71]
  • Use of Office Math ML instead of W3C recommendation MathML.[72]
  • Office Open XML does not define a macro language, leaving this aspect to be application-defined.[73]
  • 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.[74]. That coupled with the fast track standardization process, Google claims, reduces the review time per page ratio.[74]

See also

References

  1. ^ a b c Microsoft. "Register file extensions on third party servers". microsoft.com. Retrieved 2008-04-09.
  2. ^ "Ecma International approves Office Open XML standard" (Press release). Ecma International. December 7 2006. Retrieved 2006-12-08. {{cite press release}}: Check date values in: |date= (help)
  3. ^ Standard ECMA-376
  4. ^ "ISO/IEC DIS 29500 receives necessary votes for approval as an International Standard". ISO. 2008-04-02.
  5. ^ ISO/IEC DIS 29500 receives necessary votes for approval as an International Standard
  6. ^ "How to extract information from Office files by using Office file formats and schemas". Microsoft. 2007-03-27. Retrieved 2007-07-10.
  7. ^ "Microsoft Office Binary (doc, xls, ppt) File Formats". Microsoft. 2008-02-15. Retrieved 2008-04-05.
  8. ^ Brian Jones (2007-01-25). "History of office XML formats (1998-2006)". {{cite web}}: Unknown parameter |Publisher= ignored (|publisher= suggested) (help)
  9. ^ 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. Retrieved 2007-07-30.
  10. ^ "Microsoft Co-Sponsors Submission of Office Open XML Document Formats to Ecma International for Standardization". Microsoft. 2005-11-21.
  11. ^ George Ou (2007-04-27). "MS Office 2007 versus Open Office 2.2 shootout". ZDnet.com. Retrieved 2007-04-27.
  12. ^ Jesper Lund Stocholm (2008-01-29). "Do your math - OOXML and OMML". A Mooh Point blog. Retrieved 2008-02-12.
  13. ^ Murray Sargent (2007-06-05). "Science and Nature have difficulties with Word 2007 mathematics". MSDN blogs. Retrieved 2007-07-31.
  14. ^ David Carlisle (2007-05-09). "XHTML and MathML from Office 2007". David Carlisle. Retrieved 2007-09-20.
  15. ^ Wouter Van Vugt (2007-08-13). "Open XML Explained e-book". Openxmldeveloper.org. Retrieved 2007-09-14.
  16. ^ Tom Ngo (December 11 2006). "Office Open XML Overview" (PDF). Ecma International. p. 6. Retrieved 2007-01-23. {{cite web}}: Check date values in: |date= (help)
  17. ^ "What is Ecma International". {{cite web}}: Unknown parameter |Publisher= ignored (|publisher= suggested) (help)
  18. ^ "Microsoft Covenant Regarding Office 2003 XML Reference Schemas". Microsoft. Retrieved 2006-07-11.
  19. ^ "2 Escape Hatches in MS's Covenant Not to Sue". Groklaw. Retrieved 2007-01-29.
  20. ^ Berlind, David (November 28 2005). "Top open source lawyer blesses new terms on Microsoft's XML file format". ZDNet. Retrieved 2007-01-27. {{cite web}}: Check date values in: |date= (help)
  21. ^ "Microsoft Open Specification Promise". Microsoft. 2006-09-12. Retrieved 2007-04-22. {{cite web}}: Cite has empty unknown parameter: |1= (help)
  22. ^ Licensing conditions that Microsoft offers for Office Open XML
  23. ^ -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
  24. ^ Baker & McKenzie (2006). "Standardization and Licensing of Microsoft's Office Open XML Reference Schema" (PDF). Baker & Mckenzie. Retrieved 2007-02-01. {{cite web}}: Unknown parameter |month= ignored (help)
  25. ^ "Microsoft's Open Specification Promise Eases Web Services Patent Concerns". xml.coverpages.org. 2006-09-12.
  26. ^ "Microsoft promises to hang patent fire over web services". 2006-09-12.
  27. ^ "Microsoft Open Specification Promise".
  28. ^ Peter Galli (2006-09-12). "Microsoft Promises Not to Sue over Web Services Specs".
  29. ^ "Software Freedom Law Center Publishes Analysis of Microsoft's Open Specification Promise new article". Software Freedom Law Center. March 12, 2008.
  30. ^ "Software Freedom Law Center Publishes Analysis of Microsoft's Open Specification Promise". Business Wire. March 12, 2008.
  31. ^ a b c d "Microsoft's Open Specification Promise: No Assurance for GPL". Software Freedom Law Center. March 12, 2008.
  32. ^ IDABC - European eGovernment Services (2004). "European Interoperability Framework for pan-European eGovernment Services". Retrieved 2007-07-30.
  33. ^ ISO/IEC DIS 29500, Information technology -- Office Open XML file formats
  34. ^ "ISO/IEC DIS 29500 receives necessary votes for approval as an International Standard". ISO. 2008-04-02.
  35. ^ Fiveash, Kelly (2008-03-31). "OOXML approved as international standard?". The Register. Retrieved 2008-04-01. {{cite news}}: Italic or bold markup not allowed in: |publisher= (help)
  36. ^ Eric, Lai. "Microsoft admits Swedish employee promised incentives for Open XML support". computerworld.com. Retrieved 2008-04-06. {{cite news}}: Italic or bold markup not allowed in: |publisher= (help)
  37. ^ "Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats (Version 3)". Microsoft. 2007-06-18. Retrieved 2007-09-04.
  38. ^ Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats
  39. ^ "Office Compatibility Pack Review". OpenOffice.org Ninja. 2008-02-06. Retrieved 2008-02-26.
  40. ^ Amazon. "Microsoft Office 2008 for Mac".
  41. ^ "Microsoft Office Open XML File Format Converter for Mac 0.21 (Beta)". Microsoft. 2008-03-06.
  42. ^ sherjo (2006-12-06). "Converters Coming! Free and (Fairly) Fast". The Office for Mac Team Blog. Retrieved 2007-03-18. {{cite web}}: Check date values in: |date= (help)
  43. ^ "Microsoft Office Mobile 6.1: Upgrade for Microsoft Office 2007 file formats". Microsoft. 2007-11-28. Retrieved 2007-11-29. {{cite web}}: Check date values in: |date= (help)
  44. ^ "Apple - iWork - Pages". Retrieved 2007-07-08.
  45. ^ "Apple - iWork - Numbers". Retrieved 2007-07-08.
  46. ^ "Apple - iWork - Keynote". Retrieved 2007-07-08.
  47. ^ "OS X leopard Text Edit to Support Office 2007?". uneasysilence. Retrieved 2007-02-14.
  48. ^ ""iPhone User's Guide"" (PDF). Apple, Inc.
  49. ^ "Power Edit MS Word 2007 (DOCX) Support". Retrieved 2007-10-09.
  50. ^ "Gnumeric 1.8 is Here!". www.gnome.org. Retrieved 2008-01-28.
  51. ^ "QuickOffice".
  52. ^ ""DocumentsToGo for PalmOS Premium Edition"". Dataviz.
  53. ^ "Datawatch Announces Availability of Monarch V.9.0; Supports Microsoft® Windows Vista™ and Extends Excel Capabilities". 2007-02-27. {{cite web}}: Check date values in: |date= (help); Unknown parameter |Author= ignored (|author= suggested) (help); Unknown parameter |Publisher= ignored (|publisher= suggested) (help)
  54. ^ http://www.textglow.net
  55. ^ andrew z (2008-01-31). "odf-converter 1.1 released". OpenOffice.org Ninja. {{cite web}}: Check date values in: |date= (help)
  56. ^ Convert OpenXML (.docx, etc.) in Linux using command line
  57. ^ "NeoOffice 2.2.1 for Mac OS X Released". trinity.neooffice.org. 2007-08-26. Retrieved 2007-10-09. {{cite web}}: Check date values in: |date= (help)
  58. ^ Raju Vegesna (2008-02-27). "Zoho Writer Update: DocX Support, Thesaurus, Group Sharing & More". {{cite web}}: Check date values in: |date= (help)
  59. ^ Francis Dion (2008-04-01). "Xpertdoc support for OpenXML". {{cite web}}: Check date values in: |date= (help)
  60. ^ "OxygenOffice as a Word 2007 (.docx) converter". OpenOffice.org Ninja. 2008-02-25. Retrieved 2008-02-26.
  61. ^ "docXConverter - Features". panergy. Retrieved 2007-01-31.
  62. ^ Brian Jones (2008-01-17). "Google support for Open XML formats".
  63. ^ "Office Open XML Support". Apache POI. Retrieved 2008-04-14.
  64. ^ "OOXML/ODF beta for WordPerfect® Office now available". Corel. Retrieved 2007-10-04.
  65. ^ a b Doug Mahugh. "Open XML SDK roadmap". MSDN Blogs. Retrieved 2008-03-23.
  66. ^ Eric Lai (2008-03-12). "Microsoft releasing OOXML SDK". {{cite web}}: Unknown parameter |Publisher= ignored (|publisher= suggested) (help)
  67. ^ Andrew Z (2008-03-19). "OpenOffice.org 3.0's new features, an early look".
  68. ^ "ODF/OOXML technical white paper". Free Software Magazine. 2 Mai 2007. {{cite web}}: Check date values in: |date= (help)
  69. ^ "ODF/OOXML technical white paper". Free Software Magazine. 2 Mai 2007. {{cite web}}: Check date values in: |date= (help)
  70. ^ "The X Factor". reddevnews.com. October 2007.
  71. ^ VML - the Vector Markup Language
  72. ^ "Microsoft Office dumped by Science and Nature". ZDNet Asia. 18 June 2007.
  73. ^ "Microsoft New Zealand's director of innovation puts the case for a new standard". Computerworld.
  74. ^ a b "Googles position on OOXML" (PDF).
Retrieved from "https://en.wikipedia.org/w/index.php?title=Office_Open_XML&oldid=205791956"