Office Open XML

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by HAl (talk | contribs) at 11:48, 7 August 2007 (References for support arguments.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Office Open XML (commonly referred to as OOXML or Open XML) is an XML-based file format specification for electronic documents such as memos, reports, books, spreadsheets, charts, presentations and word processing documents. The specification was originally developed by Microsoft for its Microsoft Office 2007 product suite and was published by Ecma International as the Ecma 376 standard in December 2006.[1] Office Open XML is currently undergoing a 'fast track' standardization process within the International Organization for Standardization (ISO).

Office Open XML uses a number of dedicated XML markup languages in fileparts that are placed in an Open Packaging Convention file container.

Background

Microsoft has long been using binary file formats for office data which are based upon an internal format used within their Office suite. These formats have become (and still are) the most used file formats for Office related documents. Microsoft used to limit licensing to these file formats only for governments and noncommercial use. Currently Microsoft offers the binary format specifications to everyone under a royalty free covenant not to sue [2]. Because of this the formats were fairly difficult to interpret by other commercial or free software developers and never fully interoperable although current level of support for these formats by third-party software is very good. In 2002 Microsoft released its first XML version of their Office file format for Word, WordProcessingML [3] and in 2003 it released the full Office 2003 XML formats and made them available under royalty-free licensing.

The 2003 formats did not use a package file format but still used a single file format with embedded items like pictures as binary encoded within the XML. A new version of WordprocessingML currently still is one of the main markup languages used in Office Open XML.

In 2004 governments and mainly the European Union asked both OASIS and Microsoft to standardize their XML office file formats through an official Standardisations organization. [4] OASIS then decided to submit OpenDocument Format for ISO standardization (approved as ISO/IEC 26300). Following this in December 2005 Microsoft decided to standardize the new versions of their MS Office XML formats under development for MS Office 12 through Ecma (renamed as Ecma Office Open XML).

The development and standardization of Office Open XML took place against a groundswell of interest in open, standards-based technologies by commercial and government organizations.

File format and structure

The Office Open XML file is an Open Packaging Convention package containing the individual files that form the basis of the document. In addition to XML files with Office markup data, the ZIP package can also include embedded (binary) files in formats such as PNG, BMP, AVI or PDF.

According to Microsoft, Office Open XML is backward compatible with Microsoft Office versions 2000, XP and 2003 using Microsoft Office Compatibility Pack.[5]

Document markup languages

Office Open XML is a container format with several specialized XML-based document markup languages, corresponding to individual 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
  • SpreadsheetML
  • PresentationML

For graphics support:

  • DrawingML
  • VML (Obsolescent, DrawingML should be used preferably)

and shims for incorporating DrawingML in each of the primary languages.

Shared markup language materials include:

  • OMML (Office Math Markup Language)
  • Extended properties
  • Custom properties
  • Variant Types
  • Custom XML data properties
  • Bibliography

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

The XML Schema of OOXML can be characterized as being highly generic, highly systematic and with an emphasis on reducing load time and improving parsing speed. In an a test with current implementations XML based office documents still were to be a lot slower than binary formats.[6]. For speed, OOXML uses very short element names for common elements and spreadsheets save dates as index numbers (starting from 1899 or from 1904). In order to be systematic and generic, OOXML typically uses separate child elements for data and metadata (element names ending in Pr for properties) rather than using multiple attributes, which allows structured properties. OOXML does not use mixed content but uses elements to put a series of text runs (element name r) into paragraphs (element name p). The result is terse and highly nested in contrast to HTML, for example, which is fairly flat, designed for humans to write in text editors and is more or less congenial for humans to read.

OMML

Included with Office Open XML is Office Math ML (OMML). This is a mathematical markup language which can integrate with the WordprocessingML markup. This means that the math zones can also include word processing markup like revision markings, footnotes, comments, images and elaborate formatting and styles. [7] The format is different from the W3C MathML recommendation but compatible through relatively simple XSL Transformations. For example Microsoft Office 2007 ships with such XSL transformation files allowing MathML to by copied from a clipboard with XSL transformation into OMML. During XSL transformation from OMML to MathML any WordprocessingML related markup should be lost because MathML does not allow for other markup in math zones.

Container structure

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

Office Open XML format uses a ZIP container for packaging XML and other data files.[8]

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

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

Relationships

Relationship files in Office Open XML

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

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<Relationships
  xmlns="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>

Relationship files allow navigation of the package without having to open up each part. For example, images that are referenced in a Word document can be found in the relationship file by looking for all relationships that are of type http://schemas.microsoft.com/office/2006/relationships/image. To point to a different image, you just edit the relationship.

Hyperlink relations

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

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

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

Embedded or linked media file relations

Pictures can be embedded or linked in the XML files using a tag: 

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

This is the reference to the image file. In Office Open XML, all references are done via relationships. For example a document.xml part has a relationship to the image part. The actual URI is located by the corresponding "rId1" item in the accompanying relationships file. There is a _rels folder in the ZIP package, in the same directory as document.xml. Inside _rels is a file called document.xml.rels. In this file there will be a relationship definition that contains a type, an ID and a location. The ID is the referenced ID used in the XML document. The type will be a reference schema definition for the media type and the location will be an internal location within the ZIP package or an external location defined with an URL.

Standardization

Creation of Ecma 376

Microsoft stated that Office Open XML would be an open standard, and submitted it to the Ecma standardization process. On 2005-12-08 Ecma created technical committee 45 (TC45); the press release issued by Ecma the following day stated that TC45 was formed to "produce a formal standard for office productivity applications that is fully compatible with the Office Open XML Formats, submitted by Microsoft". The proposal was co-sponsored by Apple Inc., Barclays Capital, BP, the British Library, Essilor, Intel, Microsoft, NextPage, Statoil ASA and Toshiba.[9]

The TC45 committee is co-chaired by two Microsoft employees;[10] it also includes members from Apple, Canon, Intel, NextPage, Novell, Pioneer, Statoil ASA, Toshiba and The United States Library of Congress.[1]

At the General Assembly meeting on 2006-12-07, Ecma International approved Office Open XML as an Ecma standard (Ecma 376).[1] The General Assembly also approved submission of the text to the Fast Track mechanism of ISO/IEC JTC 1, which — if successful — would result in it becoming an ISO standard.

A full copy of Ecma 376 or a copy in bits can be downloaded from Ecma international.

Submission to ISO

As an ISO external Category A liaison, Ecma have submitted Ecma 376 to the ISO Fast Track process, the same process available to National Standard Organizations. To meet the requirements of this process, [11] Ecma have submitted the documents "Explanatory report on Office Open XML Standard (Ecma-376) submitted to JTC 1 for fast-track"[12] and "Licensing conditions that Microsoft offers for Office Open XML".[13]

Contradiction Phase

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

Contradiction Phase Voting

The following table attempts to summarise the positions of the ISO member countries that voted in the contradiction phase. It should be noted that a lot of countries (such as the USA represented by ANSI) did not respond in the contradictions phase as it is not required if no percieved contradictions are found.

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

Ecma responded to the issues raised during the contradiction period with a document reviewing the national bodies' comments.[14] This document cites the objections raised by the national bodies, and shows the comments overlap considerably with material on the Web created by opponents of Office Open XML, particularly from the Grokdoc[15] site. There have been suggestions by Microsoft employees and others that the national bodies' documents were not written by them, but by Microsoft competitors,[16] referring to the author metadata of the PDF submission by Kenya that contain the names of an IBM Germany employee, and a Malaysian ODF supporter.[17] However, national bodies are permitted to source technical skills as required.

Five-Month Ballot

The JTC 1 directives[11] state that regardless of whether or not resolution is reached on the question of contradiction, a five-month ballot commences immediately. So, on 2007-04-02 the ISO JTC 1 Secretariat duly informed Ecma International that the five-month DIS 29500 (Office Open XML) ballot period had started and would close on 2007-09-02.[18]

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

Response to the Ballot

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

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

Ballot Resolution Process

During the 6 month period of one month contradictions and 5-month ballot the national bodies are able to cast a vote of approval, disapproval or abstention. P-members are required to vote. In the last stage of this Fast Track standardisation process there can be a Ballot Resolution Meeting (BRM) if needed in which submitted comments with the submitted DIS can be resolved. The BRM will have been called at the discretion of the SC34 secretariat at the end of the 5 Month Ballot. The outcome of this meeting effectively decides whether DIS 29500 succeeds or fails in its bid to become a full International Standard. The DIS29500 BRM is provisionally scheduled for February 2008.

Who Attends the BRM?

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

The national bodies who attend this meeting are:

  • SC34 members (who have to send representatives);
  • those that voted "disapprove" during the five-month ballot, who have a duty to send a delegation to this meeting. (JTC 1 Directives[11] clause 13.7);
  • optionally, those who voted to "approve" DIS 29500.

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

Meeting Process

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

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

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

Voting Procedures

JTC 1 states that decisions at the BRM should be reached preferably by consensus, but that any unavoidable votes should be taken according to normal JTC 1 procedures (JTC 1 Directives[11] clause 13.8). According to these procedures a vote at the meeting is passed if:

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

Votes are taken only of those present at the meeting; votes from the 5 Month Ballot are not carried forward to the BRM. [citation needed].

Abstentions are excluded from the count. (JTC 1 Directives[11] clause 9.6)

Eligibility to Vote

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

The Arithmetic of the Votes

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

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

Final Outcome

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

ISO Maintenance Regime

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

National Body Activity

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

  • The American National Standards Institute (ANSI) is publishing comments they receive on DIS 29500 here. An archive of email exchanged between members of INCITS V1 (who provide recommendations on the U.S. position) is available here. When voting on a position, the INCITS V1 committee divided, with Microsoft and Ecma TC45 members Nextpage and BP voting for "approve with comments" on the one hand, and a group including IBM, Sun and Red Hat voting for "disapprove with comments" on the other hand. The committee thus failed to reach agreement on a recommendation to its parent committee.[19]. Subsequently the INCITS Executive Board has decided to hold a ballot for a position of "Approval with comments" and to include all comments processed or non-processed by the V1 committee [20].
  • The British Standards Institute (BSI) used an open Wiki (read-only to the public; read/write for BSI technical committee members) to help coordinate the UK's input into the ballot. While active, the site gathered 630 comments on the text. The main page of the wiki is here, and specific comments on DIS 29500 are here. Beyond this, the deliberations and voting of BSI are confidential.
  • The Standards Council of Canada (SCC) is seeking comments on a proposal to adopt Office Open XML (Open XML) as an international open standard. The forum soliciting comments from Canadians only is here.

Licensing

The Office Open XML format was initially made available under a free and perpetual license.[21]

As there was concern that free and open source software (FOSS) could not use the format under the proposed license,[22] Microsoft provided a covenant not to sue[23]. The covenant received a mixed reception, with some like Groklaw identifying problems[24] and others (such as Lawrence Rosen) endorsing it.[25]

Microsoft also added the Office Open XML format to their Microsoft Open Specification Promise in which Microsoft irrevocably promises not to assert any Microsoft Necessary Claims against you for making, using, selling, offering for sale, importing or distributing any implementation to the extent it conforms to a Covered Specification ("Covered Implementation"). The Office Open XML 1.0 - Ecma 376 and its predecessor Office 2003 XML format are among the covered specifications.[26]

The Office Open XML format therefore can be used under the Covenant not to Sue or the Open Specification Promise.

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

The Microsoft Open Specification Promise was included in documents submitted to ISO in support of the Ecma 376 fast track submission.[13]

EU Definition of an open standard

With Ecma International providing and publishing the standard for free and maintaining the format specifications and Microsofts patent licensing made irrevocably available on the standard format, Office Open XML qualifies as an Open standard according to the European Union's definition of an open standard.

  • The standard is adopted and will be maintained by a not-for-profit organisation, and its ongoing development occurs on the basis of an open decision-making procedure available to all interested parties (consensus or majority decision etc.). [28]
  • The standard has been published and the standard specification document is available either freely or at a nominal charge. It must be permissible to all to copy, distribute and use it for no fee or at a nominal fee. [28]
  • The intellectual property - i.e. patents possibly present - of (parts of) the standard is made irrevocably available on a royalty-free basis. [28]
  • There are no constraints on the re-use of the standard.

More details or information on the EU's definition can be found in European Interoperability Framework for Pan-European eGovernment Services, Version 1.0 [28] .

Adoption

Office Open XML is the default Office 2007 format if macros are not enabled. Microsoft has also released a compatibility pack for older versions.[29] Using the compatibility pack users can create and edit Office Open XML files from within Office 2000, Office XP and Office 2003. The compatibility pack can also be used as a stand alone converter in combination with Office 97.

On May 10 2007, Microsoft's Macintosh Business Unit released a beta version of a converter to allow document format conversion. An updated convertor was released on July 31 2007.[30] Mac OS BU developers had previously advised users of Office 2007 to save their files in the old Office binary format[31] until a file converter is released. Beta testing has started on Microsoft Office 2008 for Mac, which will support Office Open XML. The final version is scheduled to release in the mid-January 2008.[32]

  • Corel has announced that by mid-2007 its WordPerfect Office suite will support Office Open XML as well as OpenDocument.[33]
  • Gnumeric has limited SpreadsheetML markup language support.[34]
  • Panergy Ltd. has developed a converter from WordprocessingML markup language to Rich Text Format (RTF). The converter, called docXConverter, allows Word versions that are not supported by Microsoft's compatibility pack, e.g. Word 97, to open OOXML files containing WordprocessingML markup language. DocXConverter can be used to transfer WordprocessingML data to other applications that read RTF data.[37]
  • Datavis' DocumentsToGo for PalmOS supports Office Open XML documents.[40]
  • Datawatch supports Office Open XML spreadsheets in its report mining tool Monarch v9.0[41]

Arguments in Support and Criticism of OOXML Standard

Arguments in Support

Organisations supporting the Office Open XML format provide a lot of the following features of Office Open XML as support for using the format:

  • The most widely used document formats have previously relied on proprietary binary file formats. For users of the binary formats there is an advantage to migrating to a new open XML standard that is backward compatible with the features of previous binary file formats.
  • The use of the Open Packaging specification which allows for Indirection, Chunking and Relative indirection. [42]
  • The Office Open XML format specifies the ZIP format in an open format (See format spec part II The Open Packaging Conventions)
  • Due to ZIP compression Office Open XML files are smaller than the currently widely used binary formats [43]
  • Office Open XML support custom data elements for integration of data specific to an application or an organisation that wants to use the format.
  • Office Open XML is currently the only open document standard to define spreadsheet formulae.
  • Office Open XML contains alternate representations for the XML schemas and extensibility mechanisms using RELAX NG (ISO/IEC 19757-2) and NVDL (ISO/IEC 19757-4) [43]
  • OpenXML contains no restriction on image, audio or video types. For example, images can be in GIF, PNG, TIFF, PICT, JPEG or any other image type (§1:14.2.12).
  • Embedded controls can be of any type, such as Java or ActiveX (§1:15.2.8).
  • WordprocessingML font specifications can include font metrics and PANOSE information to assist in finding a substitution font if the original is not available (§3:2.10.5). [43]
  • Alternate Content Block (§3:2.18.4) A solution to define alternate content (like an image) which can be used in various situations where a consuming application might not be capable of interpreting what a producing application wrote. [43]
  • Internationalization supporting all kind of features needed for support by multiple nations. For example date representation: In WordprocessingML (§4:2.18.7) and SpreadsheetML (§4:3.18.5), calendar dates can be written using Gregorian (three variants), Hebrew, Hijri, Japanese (Emperor Era), Korean (Tangun Era), Saka, Taiwanese, and Thai formats and for example several internationalization related spreadsheet conversion functions. [43]
  • Custom XML schema extensibility allowing implementations to extend Office Open XML with custom features that can for instance facilite conversion from other formats and future features that are (not yet) in the official specification. [43]

Criticism

The Office Open XML standard has been the subject of wide and varied debate in the computing industry. The parties contributing in this debate include members of the free software movement, organisations supporting OpenDocument [44] and companies including IBM. These parties are generally in favour of the OpenDocument standard. Sun Microsystems, on the other hand, is on record as supporting OOXML becoming an ISO Standard.[45]

In addition to several specific issues noted below, an overall premise behind some of the adverse criticism of OOXML by ODF proponents, is that OOXML is inherently closed in many respects and thus a poor candidate for a global standard.[46]

Specific criticisms include:

  • Duplication of, overlap with, and inability to merge with the OpenDocument Format. Objectors complain that user confusion regarding the two standards would be even greater because of the similarity of the "Office Open XML" name to both "OpenDocument" and "OpenOffice".[15]
  • At 6000 pages long, the specification is too large to evaluate in the 30-day contradiction-only review and the five-month ballot period.[47]
  • Reliance on application-defined behaviors to support important functionality that should be documented or supported via existing standards. For example, book 4 section 6.1.2.19 defines the "equationxml" attribute of "shape" elements, "used to rehydrate an equation using the Office Open XML Math syntax"; however, the "actual format of the contents of this attribute are application-defined".[15]
  • Decimal time, a serial date format, is used in SpreadsheetML. The format incorrectly treats 1900 as a leap year in order to remain backward compatible with previous versions of Microsoft Excel and in Lotus 1-2-3. The criticism is two-fold; dates before 1/3/1900 cannot be used and the ISO 8601 standard for the representation of time and date should have been used instead of the serial date format. [48]
  • Use of DrawingML and VML instead of SVG, and of a new mathematical format instead of MathML. MathML and SVG are W3C recommendations. VML is deprecated and should only occur in uncommon files converted from the MS Office WordprocessingML 2003 format.
  • Internal inconsistencies and omissions. For example, book 4 section 2.18.4 lists styles such as "apples", "scaredCat", and "heebieJeebies", but does not fully define these styles. Missing properties include height, width, color depth, and orientation.[15]
  • Inconsistent notations for percentage units. In book 4, section 2.18.85 uses predefined symbols (like "pct15" for 15%) in 5 or 2.5 percent increments, section 2.15.1.95 uses a decimal number giving the percentage, section 2.18.97 uses a number in fiftieths of a percent, and section 5.1.12.41 uses a number in thousandths of a percent.[15]
  • Inflexible numbering format. For example, book 4 section 2.18.66 describes a numbering format that is fixed to a few countries and contradicts both the W3C XSLT recommendation and Unicode ISO 10646 standard.[15]
  • Non-standard, inflexible paper size naming. For example, book 4 sections 3.3.1.61 define a "paperSize" attribute for which values 1 through 68 are predefined standard paper sizes such as A4 paper.[15]
  • Non-standard language codes and color names.[15]
  • Non-extensible bitmasks, some elements attributes are defined as bitmasks. For example, book 4 section 2.8.2.16 "sig (Supported Unicode Subranges and Code Pages)" describes the <w:sig> element, the attributes of which are all bitmasks.[15]
  • Legacy document rendering compatibility is identified using (deprecated) tags. For example, book 4 section 2.15.3.6, "autoSpaceLikeWord95", “useWord97LineBreakRules”, “useWord2002TableStyleRules", and book 4 section 2.15.3.31, "lineWrapLikeWord6", and "suppressTopSpacingWP" for a 16-year-old version of WordPerfect.[15]. These items should only occur in OOXML documents that were coverted from predecessor Microsoft Office documents.
  • Errors in the spreadsheet formula specifications confirmed by MS [49]

OpenOffice.org in Denmark have submitted objections to ECMA 376 to the Danish National Body (Dansk Standard) [50]. The 22 page submission goes into some detail.

Many members of the Free Software and Open Source Software communities and some civil society organizations have lobbied heavily against the standardization of OOXML in its current form due to technical and legal issues in the format.

References

  1. ^ a b c "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)
  2. ^ "How to extract information from Office files by using Office file formats and schemas". Microsoft. 2007-03-27. Retrieved 2007-07-10.
  3. ^ Brian Jones (2007-01-25). "History of office XML formats (1998-2006)". {{cite web}}: Unknown parameter |Publisher= ignored (|publisher= suggested) (help)
  4. ^ 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. {{cite web}}: Unknown parameter |accesdate= ignored (|access-date= suggested) (help)
  5. ^ "How to use earlier versions of Excel, PowerPoint, and Word to open and save files from 2007 Office programs". Microsoft. Retrieved 2007-02-09.
  6. ^ George Ou (2007-04-27). "MS Office 2007 versus Open Office 2.2 shootout". ZDnet.com. Retrieved 2007-04-27.
  7. ^ Murray Sargent (2007-06-05). "Science and Nature have difficulties with Word 2007 mathematics". MSDN blogs. Retrieved 2007-07-31.
  8. ^ 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)
  9. ^ "The new open standard safeguards the continued use of billions of existing documents". Ecma International. Retrieved 2007-01-28.
  10. ^ "TC45 - Office Open XML Formats". Ecma International. Retrieved 2007-02-08.
  11. ^ a b c d e f "ISO/IEC JTC 1 Directives, 5th Edition, Version 2.0". iso. Retrieved 2007-01-28.
  12. ^ Explanatory report on Office Open XML Standard (Ecma-376) submitted to JTC 1 for fast-track
  13. ^ a b Licensing conditions that Microsoft offers for Office Open XML
  14. ^ "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"" (PDF). Ecma International. 2007-02-28. Retrieved 2007-04-03.
  15. ^ a b c d e f g h i j "EOOXML objections". grokdoc. Retrieved 2007-01-02.
  16. ^ Brian Jones. "A few updates on the OpenXML formats". Retrieved 2007-05-04.
  17. ^ Stephen McGibbon. ""There is no reason to be browbeaten into thinking that there should only be one document format."". Retrieved 2007-06-22.
  18. ^ "Office Open XML reaches next step in ISO/IEC process". Ecma International. 2007-04-02. Retrieved 2007-04-03.
  19. ^ "Email with appended notes from INCITS/V1 meeting on 2007-07-13".
  20. ^ Doug Mahugh (2007-07-19). "INCITS Executive Board to vote on "approve with comments". MSDN blogs.
  21. ^ Paoli, Jean. "Clarification of License Terms for Office XML Schema". Microsoft. Retrieved 2007-01-23.
  22. ^ "Open XML Incompatible With GPL". eweek. Retrieved 2007-01-29.
  23. ^ "Microsoft Covenant Regarding Office 2003 XML Reference Schemas". Microsoft. Retrieved 2006-07-11.
  24. ^ "2 Escape Hatches in MS's Covenant Not to Sue". Groklaw. Retrieved 2007-01-29.
  25. ^ 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)
  26. ^ "Microsoft Open Specification Promise". Microsoft. 2006-09-12. Retrieved 2007-04-22. {{cite web}}: Cite has empty unknown parameter: |1= (help)
  27. ^ 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)
  28. ^ a b c d IDABC - European eGovernment Services (2004). "European Interoperability Framework for pan-European eGovernment Services". Retrieved 2007-07-30.
  29. ^ "Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats". Microsoft. 2006-11-06. Retrieved 2007-11-18.
  30. ^ "Microsoft Office Open XML File Format Converter for Mac 0.2 (Beta)". Microsoft. July 31 2007. {{cite web}}: Check date values in: |date= (help)
  31. ^ sherjo (2006-12-6). "Converters Coming! Free and (Fairly) Fast". The Office for Mac Team Blog. Retrieved 2007-03-18. {{cite web}}: Check date values in: |date= (help)
  32. ^ Forbes (August 2, 2007). "Microsoft Delays Office for Mac Release".
  33. ^ "Corel WordPerfect Office To Support Open Document Format and Microsoft Office Open XML". corel. Retrieved 2007-01-30.
  34. ^ "GNOME Office / Gnumeric". GNOME.org. Retrieved 2006-07-28.
  35. ^ "Download OpenOffice.org–OpenXML translator". Novell. Retrieved 2007-03-02.
  36. ^ "Issue 79123 - Integrate a first version of the import filter for ooxml wordprocessing documents". OpenOffice.org. Retrieved 2007-07-09.
  37. ^ "docXConverter - Features". panergy. Retrieved 2007-01-31.
  38. ^ "OS X leopard Text Edit to Support Office 2007?". uneasysilence. {{cite web}}: Unknown parameter |acessdate= ignored (|access-date= suggested) (help)
  39. ^ ""iPhone User's Guide"" (PDF). Apple, Inc.
  40. ^ ""DocumentsToGo for PalmOS Premium Edition"". Datavis.
  41. ^ "Datawatch Announces Availability of Monarch V.9.0; Supports Microsoft® Windows Vista™ and Extends Excel Capabilities". 2007-02-27. {{cite web}}: Unknown parameter |Author= ignored (|author= suggested) (help); Unknown parameter |Publisher= ignored (|publisher= suggested) (help)
  42. ^ Rick Jeliffe (2007-07-29). "(comment on) Can a file be ODF and Open XML at the same time ?". O'Reilly XML.com. Retrieved 2007-08-06.
  43. ^ a b c d e f Cite error: The named reference ecma_tc45_white paper was invoked but never defined (see the help page).
  44. ^ ODF Alliance. "Office Open XML factsheet" (PDF). {{cite web}}: Unknown parameter |accesdate= ignored (|access-date= suggested) (help)
  45. ^ Jon Bosak (2007-07-16). "Email from Jon Bosak of Sun Microsystems to the INCITS-V1 committee". Retrieved 2007-08-02.
  46. ^ Sam Hiser (June 14 2007). "Achieving Openness: A Closer Look at ODF and OOXML" (HTML). ONLamp.com. p. 1. Retrieved 2007-07-12. {{cite web}}: Check date values in: |date= (help)
  47. ^ "Six thousand pages, one month, no chance..." Retrieved 2007-02-03.
  48. ^ Spolsky, Joel (2006-06-16). "My First BillG Review". Joel on Software. Retrieved 2007-01-31.
  49. ^ Brian Jones (2007-07-12). "Spreadsheet formula bugs". MSDN blogs. {{cite web}}: Unknown parameter |accesdate= ignored (|access-date= suggested) (help)
  50. ^ "Objections to Ecma 376 from OpenOffice.org in Denmark" (pdf). OpenOffice.org in Denmark. 2007-06-25. Retrieved 2007-07-03. {{cite journal}}: Cite journal requires |journal= (help)

See also

External links

General Office Open XML

OOXML criticism

Commentary on OOXML criticism

Converters and Tools

Retrieved from "https://en.wikipedia.org/w/index.php?title=Office_Open_XML&oldid=149752972"