OASIS Open Document Format for Office Applications (OpenDocument) TC
Developing an XML-based file format specification for office applications
Table of Contents
- TC Liaisons
- TC Tools and Approved Publications
- Technical Work Produced by the Committee
- External Resources
- Mailing Lists and Comments
- Additional Information
- 11 January 2012 ODF 1.2 has been published
- 29 September 2011 ODF 1.2 has been approved as an OASIS Standard. Also, the press release.
- 22 September 2011 The ODF 1.2 Candidate OASIS Standard has been submitted for balloting to approve as an OASIS Standard
- 26 March 2011 The ODF TC has approved OpenDocument v1.2 as a Committee Specification
- 01 December 2010 The ODF TC has voted to create a new subcommittee to look at advanced document collaboration. Interested parties are invited to join this new effort.
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, OpenDocument also creates the possibility for new types of applications and solutions to be developed other than traditional office productivity applications.
The OpenDocument TC works closely together with the OASIS ODF Adoption Technical Committee which provide expertise and resources to educate the marketplace on the value of the OpenDocument OASIS Standard.
- OpenDocument - Accessibility
- OpenDocument - Formula
- OpenDocument - Metadata
- OpenDocument - Requirements
- OpenDocument - Advanced Document Collaboration
- OASIS Open Document Format Interoperability and Conformance (OIC) TC: Rob Weir (IBM)
- ISO/IEC JTC1/SC34: Patrick Durusau (Individual)
- ISO/IEC JTC1/SC34 WG1:
- Dennis Hamilton (Individual)
- ISO/IEC JTC1/SC34 WG5:
- Dennis Hamilton (Individual)
- ISO/IEC JTC1/SC34 WG6:
Open Document Format v1.0 has been approved by ISO/IEC JTC1 as an International Standard ISO/IEC 26300:2006.
The specification defines three Relax-NG schemas:
- The schema for office documents (defined in chapters 1 to 16),
- the normative schema for the manifest file used by the OpenDocument package format (defined in chapter 17), and
- the strict schema for office documents that permits only meta information and formatting properties contained in this specification itself (defined in appendix A).
These three schemas are also available separately:
- OpenDocument v1.0 Relax-NG Schema (extracted from chapter 1 to 16 of the specification)
- OpenDocument v1.0 Manifest Relax-NG Schema (extracted from chapter 17 of the specification)
- OpenDocument v1.0 Strict Relax-NG Schema (extracted from appendix A of the specification)
The three schemas defined by the Open Document Format v1.1 specification are also available separately:
- OpenDocument v1.1 Relax-NG Schema (extracted from chapter 1 to 16 of the specification)
- OpenDocument v1.1 Manifest Relax-NG Schema (extracted from chapter 17 of the specification)
- OpenDocument v1.1 Strict Relax-NG Schema (extracted from appendix A of the specification)
Open Document Format v1.2 was approved as a OASIS Standard on 29 September 2011
- Open Document Format v1.2, Relax NG Schema
- Open Format Document v1.2, Manifest Schema
- Open Document Format v1.2, Digital Signature Schema
- Open Document Format v1.2, Metadata Manifest Ontology
- Open Document Format v1.2, Package Metadata Manifest Ontology
Accessibility Evaluation of the OpenDocument v1.0 specification
The Open Document Format v1.1 Accessibility Guidelines Version 1.0 have been created by the Accessibility Subcommittee and after public review have been approved by the OpenDocument TC as a Committee Specification. They are available in OpenDocument, PDF and HTML formats.
Although not produced by the OASIS OpenDocument TC, the following information offers useful insights into its work.
OpenDocument XML.org is a community-driven site hosted by OASIS that provides reliable background information on the standard. The site also serves as a community bulletin board and directory where readers post news, ideas, opinions, and recommendations. It incorporates wiki functionality to let users edit and add new pages to the site. The public is encouraged to contribute content.
opendocument-users: an unmoderated, public mail list that provides an open forum for developers to exchange ideas and information on implementing the office OASIS Standard. Subscribe or view archives.*
*To minimize spam, you must subscribe to this list before posting.
Belorussian translation of this page, produced by Paul Bukhovko as a voluntary service to the community
The TC has approved the following standing rule on 28 February 2011:
- Any substantive additions, deletions or changes to the ODF specification must be initiated by a TC member by submitting a Proposal. For all proposals, a JIRA issue must exist. For all proposals, TC members should follow the Proposal Instructions.
- A TC member wishing to make a Proposal (the Proposer) should first announce their intention to make a Proposal as defined by the Proposal Instructions or on the ODF TC's mailing list. Detail is not needed at this point, but such notification is recommended in order to let other interested TC members know that someone is working in this area and to prevent duplication of effort.
- The Proposer controls the content of the Proposal and the pace at which the Proposal advances towards approval. As it is discussed, TC members may propose changes to the Proposal. However, the control of the proposal remains at the proposer.
- When the Proposal is ready for broader discussion within the TC, the Proposer must notify the TC as defined by the Proposal Instructions, or post a link to it to the TC's mailing list to solicit feedback.
- When the Proposer wishes for the Proposal to be discussed in a TC meeting, he or she must notify the TC as defined by the Proposal Instructions, or on the TC's mailing list.
- When the completion of a proposal has been announced, when the proposal is detailed enough to be integrated into the specification, when no objections are raised in the issue within one week, and if the TC's schedule for Committee Specification Drafts permits this, the TC editors may integrate the proposal. Already integrated proposals may be revised or amended by subsequent proposals. No proposal shall be voted on unless it formally meets the definition of "contribution" as defined by OASIS IPR Policy. A proposal shall be considered detailed enough if it contains the exact text to be added top the specification and the exact changes to the schema (where required), or instructions to the TC editor how the exact text and schema changes can be derived.
- When above conditions are met but objections are raised to a proposal, the Proposer may request a vote to accept his or her Proposal.
The TC has approved the following standing rule on 12 October 2009
In accordance with OASIS Technical Committee Process 2.13, the OASIS ODF TC will allow motions to open electronic ballots to be made, seconded and discussed on the TC's mailing list
For technical assistance regarding this OASIS TC web page, contact firstname.lastname@example.org.
Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.