OpenDocument Overview

The OpenDocument Format (ODF) is an open XML-based document file format for office applications to be used for documents containing text, spreadsheets, charts, and graphical elements. The file format makes transformations to other formats simple by leveraging and reusing existing standards wherever possible.

As an open standard under the stewardship of OASIS, ODF also creates the possibility for new types of applications and solutions to be developed other than traditional office productivity applications. ODF is defined via an open and transparent process at OASIS and has been approved unanimously by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) as an international standard in May 2006. It is available for implementation and use free of any licensing, royalty payments, or other restrictions.

From a technical point of view, ODF is a ZIP archive that contains a collection of different XML files as well as binary files like embedded images. The use of XML makes accessing the document content simple because content can be opened and changed with simple text editors if necessary. In contrast, the previously used binary file formats were cryptic and difficult to process. The ZIP compression guarantees relatively small file sizes, in order to reduce file storage and transmission bandwidth requirements. ODF was the first broadly used document file format that used the concept of a ZIP package containing different XML files.

ODF uses the same set of XML files for different application types. In addition, definitions for elements like tables are consistent across application types as well. The OpenDocument format has a long tradition of openness. The first work on the file format started as early as 1999. Right from the beginning ODF was designed as an open and implementation neutral file format. The open specification process started in 2000 with the foundation of the OpenOffice.org open source project and the community efforts within its XML development project. An even higher level of openness was established in 2002 with the creation of the OASIS Open Office Technical Committee (TC).

Many organizations and companies are participating the ODF specification process. In addition, a growing number of applications implement the OpenDocument file format.

The OpenDocument Format was designed to be vendor neutral and implementation agnostic. In order to simplify transformations and to maximiz interoperability, the format reuses established standards like HTML, SVG, XSL, SMIL, XLink, XForms, MathML, and Dublin Core. ODF files of different application types (e.g. word processor, spredsheet) include the same set of XML files within the ZIP packages.

Features and benefits

Why an open file format matters

In a world where paper documents increasingly get replaced by electronic records, long term access to the data becomes critical. This is especially the case for legal contracts and government documents which stay valid and relevant over decades, or even centuries.

Like paper and pens have been available from multiple vendors, and not just one single source, document file formats and the applications creating these file formats need to be supported by and available from multiple vendors. This guarantees long-term access to data, even if companies disappear, change their strategies or dramatically raise their prices. 

Open standards that are equally accessible and do not favor one particular vendor, help maintain a diverse ecosystem of vendors. This as well causes competitive pricing, thus ensuring the best use of money from investors or tax payers.

Open standards also lower the barrier of entry, allowing new companies to join the ecosystem. For example, the SQL standard for relational databases allowed the emergence of various implementations including free open source and very specialized high-end database management systems. As long as only standard SQL features are used, database management systems can be exchanged without much effort. Vendor lock-in only happens based on special features not included in the SQL standard. Thus, vendor lock-in becomes a voluntary choice, not a mandatory one.

In the case of public documents provided by governments to their citizens, it is also important that no citizens, or at least as few as possible, get excluded from data access. For example, nobody should be forced to buy software from one specific vendor or for one specific operating system platform. Public data should be accessible to citizens independent off their income and their physical abilities.

Assistive Technologies

• Orca (Screen Reader)
• GOK (On-screen Keyboard)

See also:

- OpenDocument Accessibility FAQ
- OASIS OpenDocument Accessibility Subcommittee.

List of organizations using ODF

OpenDocument is being deployed worldwide. Review and contribute to this growing list of deployments in the following categories. (See Case studies for detailed descriptions of representative implementations.)

Specification

The complete OpenDocument v1.0 OASIS Standard specification document is available in ODT and PDF formats.

The specification defines three Relax-NG schemas, which are also available separately:

1. OpenDocument v1.0 Relax-NG Schema, the schema for office documents defined in chapters 1 to 16;
2. OpenDocument v1.0 Manifest Relax-NG Schema, the normative schema for the manifest file defined in chapter 17; and
3. OpenDocument v1.0 Strict Relax-NG Schema, the strict schema for office documents that permits only meta information and formatting properties contained in this specification itself, as defined in appendix A.

The complete OpenDocument v1.1 OASIS Standard is available in OpenDocument, PDF and XHTML (zipped) formats.  It  was approved as an OASIS Standard on 2 February 2007.

The three schemas defined by the OpenDocument v1.1 specification are also available separately:

1. OpenDocument v1.1 Relax-NG Schema (extracted from chapter 1 to 16 of the specification)
2. OpenDocument v1.1 Manifest Relax-NG Schema (extracted from chapter 17 of the specification)
3. OpenDocument v1.1 Strict Relax-NG Schema (extracted from appendix A of the specification)

• Dublin Core
• XSL:FO
• SVG
• MathML
• SMIL
• XForms
• XLink

History of OpenDocument

The OpenDocument format has a long tradition of openness. The first work on the file format started as early as 1999. Right from the beginning ODF was designed as an open and implementation neutral file format.

The open specification process started in 2000 with the foundation of the OpenOffice.org open source project and the community efforts within its XML development project. An even higher level of openness was established in 2002 with the creation of the OASIS Open Office Technical Committee (TC).

Committees

OpenDocument is advanced by three Committees within OASIS:

• The OASIS Open Document Format for Office Applications (OpenDocument) Technical Committee defines the specification as an open, XML-based file format for office applications. For more information, see the Committee charter and member list.

• The OASIS OpenDocument Format (ODF) Adoption Committee members collaborate to provide expertise and resources to educate the marketplace on the value of OpenDocument. By raising awareness of the benefits offered by OpenDocument, the Committee increases the demand for and availability of OpenDocument-conforming products, resulting in a greater choice of tools and platforms and expanding the OpenDocument community of users, suppliers, and developers. For more information, see the Committee charter and member list.

• The OASIS Open Document Format Interoperability and Conformance (OIC) Committee helps implementors create applications that conform to ODF. The OIC TC works to ensure that the growing number of ODF-compliant applications are able to interoperate. For more information, see the Committee charter and member list.

• Adobe Systems
• Google
• IBM
• Intel
• Microsoft
• Novell
• Oracle
  
• Sun Microsystems
• U.S. Department of Defense

All Committees invite participation from new members. See Join OASIS for details.