Office document formats: OpenDocument, Office Open XML and public records

A document format describes how information is stored. An office application creates, reads or changes documents using that format. A public authority's format policy can therefore concern access to records and exchange between systems without determining every feature of the office application. Wikipedia’s open-file-format overview notes that both proprietary and open-source software can implement an open format.

For public records, the distinction connects purchasing decisions with the ability to use information later. A file can outlast the software in which it was created. A format specification, an implementation and a policy on accepting documents address different parts of that problem. The interoperability page explains the broader relationship among standards, implementation rights and systems that work together.

OpenDocument and its standards setting

Wikipedia’s OpenDocument article describes ODF as an XML-based format for word-processing documents, spreadsheets, presentations and graphics. The same article identifies an OASIS technical committee as the body developing and maintaining the standard, and records its publication as ISO/IEC 26300. These descriptions identify the format's scope and standards setting rather than prescribing a particular office suite.

Nextgov’s report of May 9, 2006 recorded the announcement that ODF had received international standard status from ISO. It also reported Massachusetts seeking information on a plug-in that would allow existing office software to save in ODF. Standardization and the availability of a practical conversion route were separate developments in that account.

Wikipedia’s OpenOffice.org article describes OpenDocument as the suite's default file format and records the relationship between its earlier XML format and the ODF specification. The LibreOffice article describes a suite developed by The Document Foundation as a fork of OpenOffice.org, with support for OpenDocument. These are examples of implementations and development relationships, rather than recommendations to adopt either suite.

Office Open XML

Wikipedia’s Office Open XML article describes OOXML as an XML-based document format developed by Microsoft for spreadsheets, charts, presentations and word processing. The article records the initial Ecma standard as ECMA-376 and later ISO and IEC versions as ISO/IEC 29500. A standard identifier names a specification; it does not establish that every application's behavior or supported features are identical.

Ecma International’s ECMA-376 page states that the standard defines document vocabularies, representation and packaging, together with requirements for consumers and producers of OOXML. That separates the structure of a stored document from the responsibilities of software reading or writing it. The page is the standards body's account of the specification's scope.

Wikipedia’s standardization account places the process between December 2006 and November 2008, beginning with Ecma and proceeding through ISO and IEC. It describes the process as contentious. Its procedural account records an initial ballot that did not meet the approval requirements, followed by comment resolution and a later amended specification. The description of controversy belongs to that reference, rather than a verdict on the format.

The distinction between a proposal, a draft and a published standard matters when reading that chronology. A failed intermediate ballot was part of a continuing standards procedure; it was not the final outcome of the entire process. Wikipedia’s OOXML overview records approval of an amended version in April 2008 and publication of the resulting international standard in November 2008.

Massachusetts: policy and implementation

Wikipedia’s OpenDocument-adoption article states that Massachusetts endorsed ODF for public records in September 2005 and later included OOXML in its approved technical standards list in 2007. The change in the list and the work of equipping agencies were different parts of the episode. A policy could specify acceptable records while implementation still depended on usable applications or converters.

CIO’s coverage of the Massachusetts dispute described a hearing on the ODF plan and disagreements about the process used to establish the standard. It also reported concerns about accessibility in products implementing ODF. Those were questions about authority and implementation, alongside the policy's concern with public documents. They did not make a format synonymous with an application or its license.

Computerworld’s report on the rollout described adoption proceeding more slowly than planned. It linked the delay to working plug-ins and described accessibility testing. The account illustrates the difference between defining a policy and carrying it into everyday use. It does not establish that implementation difficulties necessarily follow from every open-format policy.

Other adoptions and long-term records

The adoption article also describes Belgium's federal requirement to accept and read ODF documents and Norway's requirement for ODF when publishing documents intended to be changed after downloading. These were different uses of a format rule, as the government-adoption reference records. Accepting a submitted document, editing a working file and maintaining a record over time are distinct administrative tasks.

Wikipedia’s digital-preservation article describes keeping information accessible and usable over time through policies, resources and preservation methods. It identifies media failure, changing technology and unavailable presentation tools as challenges. Preserving a file's bytes and retaining the ability to render its significant properties are consequently related but separate concerns.

The procurement page connects formats to requirements and switching costs. The Europe policy page covers wider standards frameworks. These relationships explain why formats recur in software policy without implying that a single specification settles every purchasing or record-keeping question.