Open Document Format for Office Applications (OpenDocument) Version 1.2

OASIS Standard

29 September 2011

Specification URIs:

This version:

http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os.odt (Authoritative)
http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os.pdf
http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os.html

Previous version:

http://docs.oasis-open.org/office/v1.2/csd06/OpenDocument-v1.2-csd06.odt (Authoritative)
http://docs.oasis-open.org/office/v1.2/csd06/OpenDocument-v1.2-csd06.pdf
http://docs.oasis-open.org/office/v1.2/csd06/OpenDocument-v1.2-csd06.html

Latest version:

http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.odt (Authoritative)
http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.pdf
http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html

Technical Committee:

OASIS Open Document Format for Office Applications (OpenDocument) TC

Chairs:

Rob Weir, IBM
Michael Brauer, Oracle Corporation

Editors:

Patrick Durusau

Michael Brauer, Oracle Corporation

Related work:

This specification supersedes OASIS OpenDocument v1.1 [ODF11].

This specification consists of this document as well as the following documents, schemas and ontologies:

OpenDocument v1.2 part 1: OpenDocument Schema
OpenDocument v1.2 part 2: Recalculated Formula (OpenFormula) Format
OpenDocument v1.2 part 3: Packages
OpenDocument v1.2 Relax NG Schema
OpenDocument v1.2 Manifest Schema
OpenDocument v1.2 Digital Signature Schema
OpenDocument v1.2 Metadata Manifest Ontology
OpenDocument v1.2 Package Metadata Manifest Ontology

Declared XML namespaces:

urn:oasis:names:tc:opendocument:xmlns:animation:1.0
urn:oasis:names:tc:opendocument:xmlns:chart:1.0
urn:oasis:names:tc:opendocument:xmlns:config:1.0
urn:oasis:names:tc:opendocument:xmlns:database:1.0
urn:oasis:names:tc:opendocument:xmlns:dr3d:1.0
urn:oasis:names:tc:opendocument:xmlns:drawing:1.0
urn:oasis:names:tc:opendocument:xmlns:form:1.0
urn:oasis:names:tc:opendocument:xmlns:manifest:1.0
urn:oasis:names:tc:opendocument:xmlns:meta:1.0
urn:oasis:names:tc:opendocument:xmlns:data style:1.0
urn:oasis:names:tc:opendocument:xmlns:office:1.0
urn:oasis:names:tc:opendocument:xmlns:presentation:1.0
urn:oasis:names:tc:opendocument:xmlns:script:1.0
urn:oasis:names:tc:opendocument:xmlns:table:1.0
urn:oasis:names:tc:opendocument:xmlns:text:1.0
urn:oasis:names:tc:opendocument:xmlns:style:1.0
urn:oasis:names:tc:opendocument:xmlns:xsl-fo-compatible:1.0
urn:oasis:names:tc:opendocument:xmlns:svg-compatible:1.0
urn:oasis:names:tc:opendocument:xmlns:smil-compatible:1.0
urn:oasis:names:tc:opendocument:xmlns:of:1.2
http://docs.oasis-open.org/ns/office/1.2/meta/odf#
urn:oasis:names:tc:opendocument:xmlns:manifest:1.0
urn:oasis:names:tc:opendocument:xmlns:digitalsignature:1.0
http://docs.oasis-open.org/ns/office/1.2/meta/pkg#

Abstract:

This specification consists of this document as well as the following three parts:

Part 1 defines an XML schema for office applications and its semantics. The schema is suitable for office documents, including text documents, spreadsheets, charts and graphical documents like drawings or presentations, but is not restricted to these kinds of documents.

Part 2 defines a formula language to be used in OpenDocument documents.

Part 3 defines a package format to be used for OpenDocument documents.

Status:

This document was last revised or approved by the OASIS Open Document Format for Office Applications (OpenDocument) TC on the above date. The level of approval is also listed above. Check the "Latest version" location noted above for possible later revisions of this document.

Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at http://www.oasis-open.org/committees/office/.

For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (http://www.oasis-open.org/committees/office/ipr.php).

Citation format:

When referencing this specification the following citation format should be used:

OpenDocument-v1.2

Open Document Format for Office Applications (OpenDocument) Version 1.2. 29 September 2011. OASIS Standard. http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os.html

Notices

Copyright © OASIS Open 2002–2011. All Rights Reserved.

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.

OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.

OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.

The names "OASIS", “OpenDocument”, “Open Document Format”, and “ODF” are trademarks of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/who/trademark.php for above guidance.

Table of Contents

1 Introduction
1.1 Scope
1.2 Terminology
1.3 Normative References
1.4 Non Normative References
2 Conformance
Appendix A. Changes From Previous Specification Versions (Non Normative)
A.1. Changes from “Open Document Format for Office Applications (OpenDocument) v1.1”
Appendix B. Acknowledgments (Non Normative)

Table of Contents Part 1

Table of Contents Part 2

Table of Contents Part 3

# 1 Introduction

## 1.1 Scope

This standard specifies the characteristics of an XML-based application-independent and platform-independent digital document file format, as well as the characteristics of software applications which read, write and process such documents. This standard is applicable to document authoring, editing, viewing, exchange and archiving, including text documents, spreadsheets, presentation graphics, drawings, charts and similar documents commonly used by personal productivity software applications.

This standard has three parts.

Part 1 defines an XML schema for office documents. Office documents includes text documents, spreadsheets, charts and graphical documents like drawings or presentations, but is not restricted to these kinds of documents.

Part 2 defines a formula language for OpenDocument documents.

Part 3 defines the package format for OpenDocument documents.

This standard, for illustrative purposes, describes functionality using terminology common in desktop computing environments that contain a display terminal, keyboard and mouse, attached to a computer hosting an operating system with a graphical user interface which includes user interface controls such as input controls, command buttons, selection boxes, etc.

However, this standard is not limited to such environments. The standard also supports the use of alternative computing environments, other form factors, non-GUI consumers and producers, and the use of assistive technologies, using analogous user interface operations.

## 1.2 Terminology

All text is normative unless otherwise labeled.

Within the normative text of this specification, the terms "shall", "shall not", "should", "should not", "may" and “need not” are to be interpreted as described in Annex H of [ISO/IEC Directives].

implementation-defined behavior: behavior that depends on the implementation and that each implementation shall document.
implementation-dependent behavior: behavior that depends on the implementation. The implementation is not required to document which behavior occurs.

Note:: Usually, the range of possible behaviors is delineated by the Standard.
undefined behavior: behavior for which the Standard imposes no requirements. Undefined behavior may also be expected when the standard omits the description of any explicit definition of behavior.

## 1.3 Normative References

[ISO/IEC Directives] ISO/IEC Directives, Part 2 (Fifth Edition) Rules for the structure and drafting of International Standards, International Organization for Standardization and International Electrotechnical Commission, 2004.

The individual parts of the OpenDocument specification each defines its own set of normative references.

## 1.4 Non Normative References

[ODF11] OASIS Standard, Open Document Format for Office Applications (OpenDocument) v1.1, February 2007, http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.pdf.

The individual parts of the OpenDocument specification each contains further non normative references.

# 2 Conformance

The OpenDocument specification defines conformance for documents, consumers, producers, packages, package consumer, package producers, formula expressions and formula evaluators, with multiple conformance classes.

1. (C1)A conforming OpenDocument Document shall meet the requirements defined in part 1 section 2.2.1 and chapters 3 to 20 for OpenDocument documents..

2. (C2)A conforming OpenDocument extended Document shall meet the requirements defined in part 1 section 2.2.2 and chapters 3 to 20 for OpenDocument extended documents.

3. (C3)A conforming OpenDocument Text Document shall meet the requirements defined in part 1 section 2.2.3 and chapters 3 to 20 for OpenDocument Text documents.

4. (C4)A conforming OpenDocument Spreadsheet Document shall meet the requirements defined in part 1 section 2.2.4 and chapters 3 to 20 for OpenDocument Spreadsheet documents.

5. (C5)A conforming OpenDocument Drawing Document shall meet the requirements defined in part 1 section 2.2.5 and chapters 3 to 20 for OpenDocument Drawing documents.

6. (C6)A conforming OpenDocument Presentation Document shall meet the requirements defined in part 1 section 2.2.6 and chapters 3 to 20 for OpenDocument Presentation documents.

7. (C7)A conforming OpenDocument Chart Document shall meet the requirements defined in part 1 section 2.2.7 and chapters 3 to 20 for OpenDocument Chart documents.

8. (C8)A conforming OpenDocument Image Document shall meet the requirements defined in part 1 section 2.2.8 and chapters 3 to 20 for OpenDocument Image documents.

9. (C9)A conforming OpenDocument Formula Document shall meet the requirements defined in part 1 section 2.2.9 and chapters 3 to 20 for OpenDocument Formula documents.

10. (C10)A conforming OpenDocument Database Front End Document shall meet the requirements defined in part 1 section 2.2.10 and chapters 3 to 20 for OpenDocument Database Front End documents.

11. (C11)A Conforming OpenDocument Producer shall meet the requirements defined in part 1 section 2.3.1 and chapters 3 to 20 for OpenDocument producers.

12. (C12)A Conforming OpenDocument Extended Producer shall meet the requirements defined in part 1 section 2.3.2 and chapters 3 to 20 for OpenDocument extended producers.

13. (C13)A Conforming OpenDocument Consumer shall meet the requirements defined in part 1 section 2.4 and chapters 3 to 20 for OpenDocument consumers.

14. (C14)A conforming OpenDocument Formula Expression shall meet the requirements defined in part 2 section 2.2 and chapters 3 to 8 for OpenDocument formula expressions.

15. (C15)A Conforming OpenDocument Formula Evaluator shall meet the requirements defined in part 2 section 2.3.1 and chapters 3 to 8 for OpenDocument formula evaluators.

16. (C16)A Conforming OpenDocument Formula Small Group Evaluator shall meet the requirements defined in part 2 section 2.3.2 and chapters 3 to 8 for OpenDocument formula small group evaluators.

17. (C17)A Conforming OpenDocument Formula Medium Group Evaluator shall meet the requirements defined in part 2 section 2.3.3 and chapters 3 to 8 for OpenDocument formula medium group evaluators.

18. (C18)A Conforming OpenDocument Formula Large Group Evaluator shall meet the requirements defined in part 2 section 2.3.4 and chapters 3 to 8 for OpenDocument formula large group evaluators.

19. (C19)A conforming OpenDocument Package shall meet the requirements defined in part 3 section 2.2.1 and chapters 3 to 7 for OpenDocument packages.

20. (C20)A conforming OpenDocument Extended Package shall meet the requirements defined in part 3 section 2.2.2 and chapters 3 to 7 for OpenDocument extended packages.

21. (C21)A Conforming OpenDocument Package Producer shall meet the requirements defined in part 3 section 2.3.1 and chapters 3 to 7 for OpenDocument package producers.

22. (C22)A Conforming OpenDocument Package Extended Producer shall meet the requirements defined in part 3 section 2.3.2 and chapters 3 to 7 for OpenDocument package extended producers.

23. (C23)A Conforming OpenDocument Package Consumer shall meet the requirements defined in part 3 section 2.4 and chapters 3 to 7 for OpenDocument package consumers.

1. Appendix A. Changes From Previous Specification Versions (Non Normative)

   1. A.1.Changes from “Open Document Format for Office Applications (OpenDocument) v1.1”

The OpenDocument specification has been divided into three parts and has been restructured. A more detailed list of changes is included in parts 1 and 3. Part 2 contains content that is new in OpenDocument v1.2.

1. Appendix B. Acknowledgments (Non Normative)

The following individuals have participated in the creation of this specification and are gratefully acknowledged:

Participants:

Chieko Asakawa, IBM

Waldo Bastian, Intel Corporation

Thorsten Behrens, Novell

Nathaniel Borenstein, IBM

Michael Brauer, Oracle Corporation

Pete Brunet, IBM

Manuel Cano
Suresh Chande, Nokia Corporation

Robin Cover, OASIS

Pierre Ducroquet

Jerome Dumonteil, Ars Aperta

Patrick Durusau

Cherie Ekholm, Microsoft Corporation

Ezer Farhi

David Faure

Jean Gouarne, Ars Aperta

Andreas J. Guelzow

Bettina Haberer, Sun Microsystems

Dennis E. Hamilton

Bart Hanssens, Fedict

Donald Harbison, IBM

Mingfei Jia, IBM

Bob Jolliffe

Peter Junge

Kazmer Koleszar, MultiRacio Ltd.

Peter Korn, Oracle Corporation

Jirka Kosek

Robin LaFontaine

Marcus Lange, Sun Microsystems

David LeBlanc, Microsoft

Fong Lin, Novell

Jun Ma, Beijing Redflag Chinese 2000 Software Co., Ltd.

Yue Ma, IBM

John Madden, Duke University

Doug Mahugh, Microsoft Corporation

Ben Martin, KDE e.V.

James Mason, ISO/IEC JTC1/SC34

Tristan Mitchell

Duane Nickull, Adobe Systems

Michael Paciello
Ganesh Paramasivam, KDE e.V.

Eric Patterson, Microsoft Corporation

David Pawson
Steven Pemberton, Stichting Centrum voor Wiskunde & Informatica

Stephen Peront, Microsoft Corporation

Asokan Ramanathan, IBM

Eike Rathke, Oracle Corporation

Florian Reuter, Novell

Janina Sajka

Svante Schubert, Oracle Corporation

Charles Schulz, Ars Aperta

Richard Schwerdtfeger, IBM

Douglas Schepers

Wei Guo Shi, IBM

Michael Stahl, Oracle Corporation

Yan Shi, Beijing Sursen International Information Technology Co., Ltd.

Jomar Silva, OpenDocument Format Alliance

Frank Stecher, Sun Microsystems

Hironobu Takagi, IBM

Malte Timmermann, Oracle Corporation

John Tolbert, The Boeing Company

Elias Torres, IBM

Warren Turkal, Google Inc.

Jos van den Oever, KDE e.V.

Alex Wang, Beijing Sursen International Information Technology Co., Ltd.

Robert Weir, IBM

Oliver-Rainer Wittmann, Oracle Corporation

David A. Wheeler

Cheng XiuZhi, Beijing Redflag Chinese 2000 Software Co., Ltd.

Panrong Yin, IBM

Kohei Yoshida, Novell

Helen Yue, IBM

Jin YouBing, Beijing Redflag Chinese 2000 Software Co., Ltd.

Thorsten Zachmann, Nokia Corporation

Thomas Zander, Nokia Corporation

Pine Zhang, UOML Alliance