1. Standardization within Ecma International

2. International standardization
     Interim ballot result    Response to ballot comments    Ballot resolution process   Ballot result  Appeals  Publication   Maintenance regime  

3. Reactions to standardization
     Complaints about the national bodies process   Other complaints  Examination of fast track process  Investigation of Microsoft by the European Commission   Microsoft complaints about competitors  

4. Arguments in support and criticism of Office Open XML standard
    Support  User base  Policy arguments  Technical arguments  Criticism  Technical  Process manipulation  Post-adoption quotes 

5. See also

6. References

The Office Open XML file formats were standardised between December 2006 and November 2008, first by the Ecma International consortium (where they became ECMA-376), and subsequently, after a contentious standardization process, by the ISO/IEC's Joint Technical Committee 1 (where they became ISO/IEC 29500:2008).

Standardization within Ecma International

More than a year after being asked by the European Union to standardize their Office 2003 XML formats,^[1] Microsoft submitted 2,000 pages of documentation for a new file format to the Ecma International consortium for it to be made into an open standard.^[2] Ecma formed a technical committee (TC45) in December 2005,^[3] in order to produce and maintain a "formal standard for office productivity applications that is fully compatible with the Office Open XML Formats, submitted by Microsoft".^[4] The technical committee was chaired by two Microsoft employees^[5] and included members drawn from Apple, Canon, Intel, NextPage, Novell, Pioneer, Statoil ASA, Toshiba, The United States Library of Congress, The British Library and the Gnome Foundation.^[6]

During standardisation within Ecma the specification grew to approximately 6,000 pages. It was approved as an Ecma standard (ECMA-376) on December 7, 2006.^[7] The standard can be downloaded from Ecma free of charge.^[8]

International standardization

Using their entitlement as an ISO/IEC JTC 1 external Category A liaison, Ecma International submitted ECMA-376 to the JTC 1 fast track standardization process. To meet the requirements of this process,^[9]

they submitted the documents "Explanatory report on Office Open XML Standard (Ecma-376) submitted to JTC 1 for fast-track"^[10] and "Licensing conditions that Microsoft offers for Office Open XML".^[11] ISO and IEC classified the specification as DIS 29500 (Draft International Standard 29500) Information technology – Office Open XML file formats.^[12]

The fast track process consists of a contradictions phase, a ballot phase, and a ballot resolution phase.

During the contradictions phase, ISO and IEC members submitted perceived contradictions to JTC 1. During the ballot phase the members voted on the specification as it was submitted by Ecma and submitted editorial and technical comments with their vote. In the ballot resolution phase the submitted comments were addressed and members were invited to reconsider their vote.

Interim ballot result

During the standardization of Office Open XML, Ecma International submitted its Office Open XML File Formats standard (ECMA-376) to the ISO Fast Track process. After a comment period, the ISO held a ballot that closed September 2007. This has been observed to be perhaps the most controversial and unusual ISO ballot ever convened, both in the number of comments in opposition, and in unusual actions during the voting process. Various factions have strongly supported and opposed this fast track process. On the supporting side were primarily Microsoft affiliated companies; on the opposing side were free- or open-source software organizations, IBM and affiliates, Sun Microsystems, and Google.

There have been reports of attempted vote buying,^{[13][14][15][16]} heated verbal confrontations, refusal to come to consensus and other very unusual behavior in national standards bodies.^{[17][18][19][20]}

This is said to be unprecedented for standards bodies, which usually act together and have generally worked to resolve concerns amicably.

87 ISO member countries responded to the five-month ballot. There were 51 votes of "approval", 18 votes of "disapproval" and 18 abstentions.^[21] For the measure to pass, {{2/3}} of "P" members (participating, as opposed to "O" members: observing) must approve and less than {{1/4}} of all voting national members (excluding members that abstain from voting) must disapprove. The ballot shows 53% approval by "P" members and 26% disapproval from the total votes.

The following table shows the results by member of the balloting that ended 2 September 2007:^[22]

 ! Country    ! Standards Body    ! Membership    ! Vote   

On 25–29 February 2008, a Ballot Resolution Meeting was held in Geneva, Switzerland, to consider revisions to the OOXML proposal. Under ISO rules, national standards bodies have thirty days following the Ballot Resolution Meeting to reconsider and possibly change their votes.

Belgium

The Belgian Bureau de Normalisation considered the revisions, but failed to reach a consensus on the proposal. Belgium's initial abstention therefore stood.^[23]

Czech Republic

The Český Normalizační Institut considered the revisions and changed its initial vote against the proposal to a vote in favour.^[24]

Germany

The Normenausschuss Informationstechnik und Anwendungen considered the revisions and reaffirmed Germany's initial vote for the proposal.^[25]

India

The Bureau of Indian Standards considered the revisions and reaffirmed India's initial vote against the proposal.^[26]

Netherlands

The Netherlands Standardization Institute (NEN) considered the revisions and reaffirmed the Netherlands' initial abstention.^[27]

Trinidad and Tobago

The Trinidad and Tobago Bureau of Standards announced that it will change its initial abstention to a vote for the revised proposal.^[28]

United States

The International Committee on Information Technology Standards (INCITS) considered the revisions and reaffirmed the U.S.'s initial vote for the proposal.^[29]

In September 2007 eighty-seven ISO and IEC member countries had responded to the ballot.^[30] There were 51 votes of "approval", 18 votes of "disapproval" and 18 abstentions. "P-members", who were required to vote, had to approve by 66.67% for the text to be approved. The P-members voted 17 in favour out of 32, below the required threshold for approval. Also, no more than 25% of the total member votes may be negative for the text to be approved, and this requirement was also not met since 26% of the total votes were negative. The standardization process then entered its ballot resolution phase, described below.

Response to ballot comments

Ecma produced a draft "Disposition of Comments" document that addresses the 1,027 distinct "NB comments" (that is, comments by national bodies) that had been submitted in the letter ballot phase. This document comprised 1,600 pages of commentary and proposed changes. The ISO and IEC members had 6 weeks to review this draft, and had an opportunity to participate in several informal conference call sessions with the Ecma TC45 to discuss it before the BRM.^[31]

Ballot resolution process

A Ballot Resolution Meeting (BRM) is an integral part of the ballot resolution phase. The outcome of, and period following, this meeting decided whether DIS 29500 succeeded or failed in its bid to become an International Standard. The DIS 29500 BRM took place in late February 2008.

At the BRM, 873 proposed changes to the specification were submitted by Ecma (of their 1,027 responses, 154 proposed no change). Of these only 20% were discussed and modified in meeting sessions, given the 5 day time limit of the meeting. The remaining 80% were not discussed and were subject to a voting mechanism approved by the meeting (see Resolution 37 of the meeting resolutions cited below). Using this voting mechanism NBs could approve, disapprove or abstain on each and every one of these proposed changes. This allowed a set of approved changes to be decided upon without discussion.^[32][33]

With the original submitted draft used as the base, all the agreed-upon changes were applied by the Project Editor to create a new set of documents incorporating the changes agreed during the BRM. In parallel with this, NBs had 30 days after the BRM in which to decide whether to amend their votes of September 2, 2007.

Ballot result

A number of JTC 1 members took the opportunity to amend their votes, predominantly in favour of approval of DIS 29500. Thus, 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. They stated that "75% of the JTC 1 participating member votes cast positive and 14% of the total of national member body votes cast negative"^[34] In accordance with the JTC 1 directives the Project Editor had created a new version of the final text within a month of the BRM. After review, corrections and the resolution of appeals, this text was distributed to the members of SC34.^[35]

Appeals

Four JTC 1 members appealed the standardisation: the bodies of South Africa,^[36][37] Brazil, India^[38] and Venezuela.^[39]

Since the appeals system is designed to find a solution by consensus, it was unlikely that the process would have resulted in ISO/IEC abandoning progress of DIS 29500.^[39] The CEOs of ISO and IEC advised the management board that these appeals should no longer be processed any further: the Secretary General of ISO is reported as stating: "[t]he processing of the ISO/IEC DIS 29500 project has been conducted in conformity with the ISO/IEC JTC 1 Directives, with decisions determined by the votes expressed by the relevant ISO and IEC national bodies under their own responsibility, and consequently, for the reasons mentioned above, the appeals should not be processed further".^[40]

The main issue in the appeals was the BRM procedures{{Citation needed|date=June 2009}}. The 3 appealing countries did not appeal during the BRM and even all voted approval on the resolution that allowed for voting on each of the resolutions that had not been discussed in the plenary meeting through means of a form.^[41] The three countries appealing used that form vote for a disapproval vote of most of the responses (in total only 4 countries did that) but failed to have a significant number of responses disapproved{{Citation needed|date=June 2009}}.

The appeals did not get sufficient support of the National Bodies voting on the ISO and IEC management boards, and consequently the go-ahead was given to publish ISO/IEC DIS 29500, Information technology – Office Open XML formats, as an ISO/IEC International Standard on August 15, 2008.^[42]

Publication

The International Standard ISO/IEC 29500:2008 was published in November 2008.^[43]

Maintenance regime

Following the standardization of ISO/IEC 29500, ISO/IEC JTC1/SC34, as the designated maintenance group for the standard, established two ad hoc groups for deciding how the Standard would be maintained:^[44] a group to collect comments on the newly approved standard, and a group to decide what structures should be used for long-term maintenance. The resulting recommendation^[45] was that ISO/IEC JTC1/SC34 should assume full control of the maintenance work on ISO/IEC 29500. This decision was duly ratified^[46] at SC 34's September 2008 meeting on Jeju Island, Korea. Ecma were invited as a liaison to provide individual experts to contribute to the maintenance activity. This decision superseded an earlier proposal from Ecma, in which Ecma itself proposed it was responsible for maintenance.^[47]

On May 21, 2008, Microsoft announced that it would be "an active participant in the future evolution of ODF, Open XML, XPS and PDF standards".^[48]

ISO/IEC 29500 is maintained within Working Group 4 ("WG 4") of ISO/IEC JTC1/SC34 under the convenorship of MURATA Makoto of Japan.

Under this maintenance regime the JTC 1 Directives apply, and these stipulate that:

• Proposals to amend the text, and acceptance of any such amendments, are subject to normal JTC 1 voting processes (JTC 1 Directives^[9] clause 15.5)
• The standard cannot be "stabilised" (no longer subject to periodic maintenance) except through approval in a JTC 1 ballot (JTC 1 Directives,^[9] clause 15.6.2).
• For the standard to be stabilised it must have passed through one review cycle (JTC 1 Directives,^[9] clause 15.6.1). In this review cycle, the text would have to have been re-written to comply with ISO's formatting and verbal requirements (JTC 1 Directives,^[9] clause 13.4).

WG 4 has a web site and open document register.^[49] Defect logs and statistics from WG 4 are available online.^[50]

At the WG4 meeting in Copenhagen, June 22–24, 2009, there were 16 people listed as present; 5 of these were employed by Microsoft, 4 by universities.^[51]

Reactions to standardization

Complaints about the national bodies process

There have been allegations that the ISO ballot process for Office Open XML was marred with voting irregularities and heavy-handed tactics by some stakeholders.^[52][53][54]

• An Ars Technica article sources Groklaw stating that at Portugal's national body TC meeting, "representatives from Microsoft attempted to argue that Sun Microsystems, the creators and supporters of the competing OpenDocument format (ODF), could not be given a seat at the conference table because there was a lack of chairs."^[55]
• In Sweden, Microsoft notified the Swedish Standards Institute (SIS) that an employee sent a memo to two of its partners, requesting them to join the SIS committee and vote in favor of Office Open XML in return for "marketing contributions".^[56] Jason Matusow, a Director in the Corporate Standards Strategy Team at Microsoft, stated that the memo was the action of an individual employee acting outside company policy, and that the memo was retracted as soon as it was discovered.^[57][58] SIS have since changed its voting procedure so that a member has to actually participate before being allowed to vote.^[59]
• Sweden invalidated its vote (80% was for approval) as one company cast more than one vote, which is against SIS policy.^[60]
• Finnish IT journalists described that meeting as raising strong differences in opinions.^[61][62]
• In Switzerland, SNV registered a vote of "approval with comments," and there was some criticism about a "conflict of interest" regarding the chairman of the UK 14 sub-committee, who did not allow discussion of licensing, economic and political arguments.^[63][64] In addition, the chairman of the relevant SNV parent committee is also the secretary general of Ecma International{{Citation needed|date=June 2009}}, which approved OOXML as a standard. Further complaints regarded "committee stuffing", which is however allowed by present SNV rules, and non-adherence to SNV rules by the UK 14 chairman, which resulted in a re-vote with the same result.{{Citation needed|date=June 2009}}
• Australia's national standards body, Standards Australia, was criticized for its handling of the OOXML process by the New Zealand Open Source Society,^[65] the open source advisory firm Waugh Partners, Australian National University Professor Roger Clarke,^[66] OASIS lawyer Andrew Updegrove,^[66] IBM{{Citation needed|date=June 2009}} and Google{{Citation needed|date=June 2009}}. Standards Australia sent ISO SC 34 expert and XML and Schematron specialist Rick Jelliffe to the BRM, despite critics^[67] alleging that Jelliffe would not represent the views of those opposing the standardization. Jelliffe had previously been in the news after being offered payment by Microsoft to improve incorrect Wikipedia articles about Office Open XML.^[68] Microsoft had bought a schema conversion tool from his company and he had performed the initial conversion of the Office Open XML schemas from XML Schemas to RELAX NG{{Citation needed|date=June 2009}}, both schema languages he had been involved in standardizing. It was alleged that Standards Australia had broken a previous public pledge to send two internal employees to the BRM.^[69][70] However Standards Australia issued a press release denying this and stating that the Computerworld article was "riddled with inaccuracies and misrepresentations."^[71]
• Norway's vote was decided by Standard Norge; the mostly opposing viewpoints of the technical committee resulted in a disapproval vote in the 2007 ballot. However, the administration of Standard Norge changed Norway's vote to "approval" in 2008 even if the majority of the committee argued in favor of keeping its "disapproval" vote. Membership in the technical committee had risen from 6–7 to 30 members; all of the pre-OOXML members argued in favour of a "no" vote.^{[72][73][74][75]} In October 2008, 13 of the 23 members, 12 of which are associated with the open-source movement,^[76] resigned^[77] after OOXML was ratified by ISO and all appeals were rejected.
• The IDABC community programme (which is managed by the European Commission) runs the "Open Source Observatory" which is "dedicated to Free/Libre/Open Source Software."^[78] Via its "Open Source News", it has reported on reports which criticize the standardization process.
  • It states that the German IT news site Heise reports that in Germany, two opponents of Office Open XML, Deutsche Telekom and Google, were not allowed to vote^[79] because they tried to join the committee last-minute.^[80] Open Source News says, "Participants described the process as ludicrous."
  • It relays a report from Michiel Leenaars (director of the Internet Society Netherlands) that in the Netherlands, "the chair of the national standardization committee deciding on OOXML, protested that the almost unanimous conditional approval was blocked by Microsoft."^[79]
  • It reports on a report from Borys Musielak, a member of Poland's Linux community, who wrote on the PolishLinux website that Poland's technical committee KT 171 rejected Office Open XML.^[81] The vote was invalidated and assigned to KT 182. A member of Poland's Linux community believes this was due to "reorganisation in the Polish standardisation body." KT 182 voted to approve Office Open XML.^[82]
  • It reports that in Andalucía, the director of Andalucía's Department for Innovation complained that Microsoft submitted misinformation to the Spanish National Body stating that it (Andalucía) supported the company's Office Open XML-proposal.^[83]
  • It reports that in Portugal, eleven companies (including IBM) and open source advocacy groups requested that Portugal's Ministry of Economy and Innovation investigate Portugal's vote on Office Open XML.^[84]
• In June 2008, the High Court of Justice in the United Kingdom rejected a complaint by the UK Unix and Open Systems User Group (UKUUG), requesting a review of the British Standard Institution's decision to vote in favour of DIS 29500. The judge commented that "this application does not disclose any arguable breach of the procedures of BSI or of rules of procedural fairness".^[85]

Other complaints

A further letter of protest was filed by Open Source Leverandørforeningen, a Danish open source vendor association ^[86]

although no appeal has been filed directly by Dansk Standard itself.

In September 2008, a joint letter known as the Consegi declaration was issued and signed by 3 representatives for free software of the countries that issued appeals (South Africa, Brazil and Venezuela) as well as Ecuador, Cuba and Paraguay.

After the specification was officially accepted as an ISO standard, Red Hat{{Citation needed|date=June 2009}} and IBM{{Citation needed|date=June 2009}} claimed the ISO is losing credibility, and

Ubuntu founder Mark Shuttleworth commented "We're not going to invest in trying to implement a standard that is poorly defined."^[87][88] IBM issued a press release stating: "IBM will continue to be an active supporter of ODF. We look forward to being part of the community that works to harmonize ODF and OOXML for the sake of consumers, companies and governments, when OOXML control and maintenance is fully transferred to JTC1."^[89]

Examination of fast track process

At the plenary meeting of JTC 1 in Nara, Japan that took place in November 2008, a resolution was passed which related to concerns express during the standardisation of ISO/IEC 29500.^[91] Resolution 49 was entitled "Clarification on Consistency of Standards vs Competing Specifications" and contained the following text:

JTC 1 recognizes its commitment to ISO's and IEC's "one standard" principle; however, it recognizes that neither it nor its SCs are in a position to mandate either the creation or the use of a single standard, and that there are times when multiple standards make the most sense in order to respond to the needs of the marketplace and of society at large. It is not practical to define, a priori, criteria for making these decisions. Therefore each standard must be judged by the National Bodies, based on their markets, on its own merits.

At a companion meeting of the Special Working Group on Directives (SWG-Directives) in Osaka a recommendation was made^[92] describing series of "concepts" that would in future be applied to the Ballot Resolution process of future Fast Tracked standards. These mirrored the process that had taken place for ISO/IEC 29500:

1. The purpose is to review and address ballot comments
2. The meeting must have a separate agenda and be convened as a separate meeting even if it is in conjunction with/co-located with an SC/WG meeting
3. The comments must be discussed within a single meeting and NOT distributed over a series of meetings
4. The meeting is open to the Fast track Submitter and to all National Bodies regardless of whether or not the National Body has voted on the document under review – no limitation on which National Body can participate
5. The meeting participants represent their National Body and their National Body positions
6. All National Bodies have an equal say in any decisions made during the meeting
7. The Project Editor must prepare an Editor's proposed disposition of ballot comments in sufficient time prior to the BRM to allow consideration by National Bodies. This editor's proposed disposition of comments document will be reviewed during the ballot resolution meeting
8. A disposition of ballot comments approved during the meeting must be circulated following the meeting for the information of all National Bodies
9. When all comments have been addressed and a disposition of comments has been approved by the meeting, the BRM meeting criteria have been met

Standards lawyer Andy Updegrove (whose firm represents OASIS) commented that he was "startled and dismayed" at these concepts, since they "basically add up to a ratification of the conduct of the Geneva BRM."^[93]

Investigation of Microsoft by the European Commission

In January 2008, the European Commission started an antitrust investigation into the interoperability of the Office Open XML format on the request of European Committee for Interoperable Systems, described as "a coalition of Microsoft's largest competitors".^[94] Anonymous source(s) of the Wall Street Journal claim that this investigation also includes an investigation into whether Microsoft violated antitrust laws in the course of the standardization process.^[95] The Financial Times reports that European ISO members have confirmed receipt of a letter by the European Commission "asking how they prepared for votes [...] on acceptance of Microsoft's OOXML document format as a worldwide standard."^[96]

Microsoft complaints about competitors

On February 14, 2007, Microsoft attacked IBM's opposition to the Office Open XML standardization process in an open letter, saying

On December 7, Ecma approved the adoption of Open XML as an international open standard. The vote was nearly unanimous; of the 21 members, IBM's was the sole dissenting vote. IBM again was the lone dissenter when Ecma also agreed to submit Open XML as a standard for ratification by ISO/IEC JTC1.^[97]

IBM led a global campaign urging national bodies to demand that ISO/IEC JTC1 not even consider Open XML, because ODF had made it through ISO/IEC JTC1 first.

Nicos Tsilas, Microsoft's senior director of interoperability and intellectual property policy, downplaying Microsoft's American and EU conviction as abusers of monopoly power, expressed concern that IBM and the Free Software Foundation have been lobbying governments to mandate the use of the rival OpenDocument format (ODF) to the exclusion of other formats. In his opinion, they are "using government intervention as a way to compete" as they "couldn't compete technically."^[98][99]

IBM have asked governments to have an open-source, exclusive purchasing policy.

Arguments in support and criticism of Office Open XML standard

Support

Microsoft believes its own format should be adopted. It has presented this argument on its "community web site", a site owned and operated by Microsoft.^[100]

In December 2007 Ecma International announced that many of reported issues will be taken into account in next edition of the standardisation proposal to ISO.^[103]

• The British Library and the United States Library of Congress have participated in the work of Ecma TC45 and support the Office Open XML standard.^{[104][105][106][107]}
• Former Gnome Foundation board member Miguel de Icaza, who started the GNOME and Mono projects, showed support for the Office Open XML document format, stating "OOXML is a superb standard and yet, it has been FUDed so badly by its competitors that serious people believe that there is something fundamentally wrong with it."^[108][109]
• Patrick Durusau, the editor of the OpenDocument standard, has characterized OOXML as a "poster child for the open standards development process"^[110][111]

User base

The most widely used office productivity packages currently rely on various proprietary and reverse engineered binary file formats such as those created by successive releases of Microsoft Word, PowerPoint and Excel. However, OOXML is a new format which is not backwards or forwards compatible with any of the old Microsoft Office formats.^[112]

Policy arguments

With regards to the alleged overlap in scope with the OpenDocument format, Ecma has provided the following policy arguments in favor of standardization: overlap in scope of ISO/IEC standards is common and can serve a practical purpose; Office Open XML addresses distinct user requirements; The OpenDocument format and Office Open XML are structured to meet different user requirements; and Office Open XML and Opendocument can serve as duo-standards.^[113]

Technical arguments

A study comparing IS 29500:2008 and IS 26300:2006 (ODF 1.0) by the German Fraunhofer Institute found

It may be concluded that many of the functionalities, especially those found in simpler documents, can be translated between the standards, while the translation of other functionalities can prove complex or even impossible.^[114]

• The use of the Open Packaging Convention which allows for Indirection, Chunking and Relative indirection.^[122]
• Uses the ZIP format, making ZIP part of the standard. Due to compression, files are smaller than current binary formats.^[122]
• It supports custom data elements for integration of data specific to an application or an organisation that wants to use the format.^[122]
• It defines spreadsheet formulas.^[115]
• 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.)^[122]
• No restriction on image, audio or video types, Book 1 §14.2.12.^[122]
• Embedded controls can be of any type, such as Java or ActiveX, Book 1 §15.2.8.^[122]
• WordprocessingML font specifications can include font metrics and PANOSE information to assist in finding a substitution font if the original is not available, Book 3 §2.10.5.^[122]
• In the situation where a consuming application might not be capable of interpreting what a producing application wrote, Office Open XML defines an Alternate Content Block which can represent said data in an alternate format, such as an image. Book 3 §2.18.4.^[122]
• Internationalization support. For example, date representation: In WordprocessingML (Book 4 §2.18.7) and SpreadsheetML (Book 4 §3.18.5), calendar dates after 1900 CE can be written using Gregorian (three variants), Hebrew, Hijri, Japanese (Emperor Era), Korean (Tangun Era), Saka, Taiwanese, and Thai formats. Also, there are several internationalization related spreadsheet conversion functions.^[116]
• Custom XML schema extensibility allows the addition of features to the format. This can, for instance, facilitate conversion from other formats and future features that are not part of the official specification.^[116]

Criticism

Technical

The standard has been the subject of debate within the software industry. At over 6,000 pages, the specification is difficult to evaluate quickly.^[117] Objectors also claim that there could be user confusion regarding the two standards because of the similarity of the "Office Open XML" name to both "OpenDocument" and "OpenOffice". Objectors also argued that an ISO standard for documents already exists and there is no need for a second standard.^[118]

Google stated that "the ODF standard, which achieves the same goal, is only 867 pages" and that

If ISO were to give OOXML with its 6546 pages the same level of review that other standards have seen, it would take 18 years (6576 days for 6546 pages) to achieve comparable levels of review to the existing ODF standard (871 days for 867 pages) which achieves the same purpose and is thus a good comparison.

Considering that OOXML has only received about 5.5% of the review that comparable standards have undergone, reports about inconsistencies, contradictions and missing information are hardly surprising.^[119]

Those who support the ODF standard include the FFII, ODF Alliance^[120] IBM,^[121] as well as South Africa, and other nations that voiced strong opposition to OOXML during standardization.

The ODF Alliance UK Action Group has stated that with OpenDocument an ISO standard for Office files already exists.^[122]

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.^[122]

Process manipulation

In addition, the standardization process itself has been questioned,^[118][123] including claims of balloting irregularities by some technical committees, Microsoft representatives and Microsoft partners in trying to get Office Open XML approved.^[118][123] "The editorial group who actually produce the spec is referred to as "ECMA", but in fact the work is mostly done by Microsoft people."^[123]

Post-adoption quotes

During a panel discussion on Red Hat Summit in Boston in June 2008 Microsoft's national technology officer Stuart McKee said that "ODF has clearly won". He also made the following statement:^[124][125]

We found ourselves so far down the path of the standardisation process with no knowledge. We don't have a standards office. We didn't have a standards department in the company. I think the one thing that we would acknowledge and that we were frustrated with is that, by the time we realised what was going on and the competitive environment that was underway, we were late and there was a lot of catch-up. It was very difficult to enter into conversations around the world where the debate had already been framed.

On June 25, 2008, Gray Knowlton, a Group Product Manager for the Microsoft Office system made the following statements regarding the future of Open XML:^[126]

Microsoft will continue to support the development of the specification and the adoption of the Open XML formats, in addition to the other work we are driving around document formats in Office. [...] In the end, Open XML is still the better choice for the compatibility and line-of-business interoperability scenarios we have discussed throughout its history. [...] while we are working on ODF moving forward, we will remain committed to Open XML and believe that it will be the format of choice for large parts of the global community.

In an interview Richard Stallman, head of the Free Software Foundation, said:^[127]

Microsoft corrupted many members of ISO in order to win approval for its phony 'open' document format, OOXML. This was so governments that keep their documents in a Microsoft-only format can pretend that they are using 'open standards.' The government of South Africa has filed an appeal against the decision, citing the irregularities in the process.

On March 31, 2010, Dr Alex Brown, who had been the Convener of the February 2008 Ballot Resolution Meeting, posted an entry on his personal blog^[128] in which he complained of Microsoft's lack of progress in adapting current and future versions of Microsoft Office to produce files in the Strict (as opposed to the Transitional) ISO 29500 format:

On this count Microsoft seems set for failure. In its pre-release form Office 2010 supports not the approved Strict variant of OOXML, but the very format the global community rejected in September 2007, and subsequently marked as not for use in new documents — the Transitional variant. Microsoft are behaving as if the JTC 1 standardisation process never happened...

Microsoft responded that the next release of Microsoft Office (version 15) would fully support ISO/IEC 29500 Strict.^[129]

See also

• OpenDocument standardization
• Comparison of Office Open XML and OpenDocument
• Comparison of document markup languages
• Non-standard extensions used by Microsoft's applications

References

• Ashtray Rock
• Ash-tree
• Ash Tree
• Ashtree
• Ash Tree Press
• Ash-Tree Press
• Ash trees
• Ashtānga Hridayam
• Ashuelot Pond
• Ashuelot Railroad
• Ashug
• Ashuganj
• Ashugi Qaribi
• Ashugs
• Ashu Kasim
• Ashu Kasim Rabo
• Ashulia
• Ash United
• Ash United F.C.
• Ashura Blaster
• Ashuradeh
• Ashurah
• Ashuraman
• Ashura massacre
• Ashura the Hedgehog