computer science

OpenDocument

OpenDocument is a computer science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand OpenDocument rather than just read about it. In short: OpenDocument Format (ODF) for Office Applications, also known as OpenDocument, standardized as ISO 26300, is an open file format for word processing documents, spreadsheets, presentations and graphics using ZIP-compressed XML files. It was developed with the aim of providing an open, XML-based file format specification for office applications.

Key takeaways

OpenDocument belongs to computer science; place it in that map before memorising details.
Learn the definition first, then one example that makes the definition concrete.
Connect OpenDocument to a quantity you can measure, compute or draw — that is where exam questions come from.
Reproduce the core statement of OpenDocument from memory before moving on to harder problems.

Reference excerpt

OpenDocument Format (ODF) for Office Applications, also known as OpenDocument, standardized as ISO 26300, is an open file format for word processing documents, spreadsheets, presentations and graphics using ZIP-compressed XML files. It was developed with the aim of providing an open, XML-based file format specification for office applications. The standard is developed and maintained by a technical committee in the Organization for the Advancement of Structured Information Standards (OASIS) consortium. It was based on the Sun Microsystems specification for OpenOffice.org XML, the default format for OpenOffice.org and LibreOffice. It was originally developed for StarOffice "to provide an open standard for office documents." In addition to being an OASIS standard, it is published as an ISO/IEC international standard ISO/IEC 26300 – Open Document Format for Office Applications (OpenDocument). From March 2024, the current version is 1.4. Since March 2026 the German government mandates the ODF and PDF/UA file formats for documents for all levels of government through the Deutschland-Stack project. Implementation is intended to be finalized by 2027.

Specifications

The most common filename extensions used for OpenDocument documents are:

.odt and .fodt for word processing (text) documents .ods and .fods for spreadsheets .odp and .fodp for presentations .odg and .fodg for graphics .odf for formulae, mathematical equations The original OpenDocument format consists of an XML document that has <document> as its root element. OpenDocument files can also take the format of a ZIP compressed archive containing a number of files and directories; these can contain binary content and benefit from ZIP's lossless compression to reduce file size. OpenDocument benefits from separation of concerns by separating the content, styles, metadata, and application settings into four separate XML files. There is a comprehensive set of example documents in OpenDocument format available. The whole test suite is available under the Creative Commons Attribution 2.5 license.

History

Conception The OpenDocument standard was developed by a Technical Committee (TC) under the Organization for the Advancement of Structured Information Standards (OASIS) industry consortium. The ODF-TC has members from a diverse set of companies and individuals. Active TC members have voting rights. Members associated with Sun and IBM have sometimes had a large voting influence. The standardization process involved the developers of many office suites or related document systems. The first official ODF-TC meeting to discuss the standard was 16 December 2002. OASIS approved OpenDocument as an OASIS standard on 1 May 2005. OASIS submitted the ODF specification to ISO/IEC Joint Technical Committee 1 (JTC 1) on 16 November 2005, under Publicly Available Specification (PAS) rules. ISO/IEC standardization for an open document standard including text, spreadsheet and presentation was proposed for the first time in DKUUG 28 August 2001. After a six-month review period, on 3 May 2006, OpenDocument unanimously passed its six-month DIS (Draft International Standard) ballot in JTC 1 (ISO/IEC JTC 1/SC 34), with broad participation, after which the OpenDocument specification was "approved for release as an ISO and IEC International Standard" under the name ISO/IEC 26300:2006. After responding to all written ballot comments, and a 30-day default ballot, the OpenDocument international standard went to publication in ISO, officially published 30 November 2006. In 2006, Garry Edwards, a member of OASIS TC since 2002, along with Sam Hiser and Paul "Marbux" E. Merrell founded the OpenDocument Foundation. The aim of this project was to be an open-source representative of the format in OASIS. The immediate aim of this project was to develop software that would convert legacy Microsoft Office documents to ODF. By October 2007 the project was a failure: Conversion of Microsoft Office documents could not be achieved. By this time, The foundation was convinced that ODF was not moving in a direction that they supported. As a result, it announced the decision to abandon its namesake format in favor of W3C's Compound Document Format (CDF), which was in early stages of its development. The foundation, however, never acted on this decision and was soon dissolved. The CDF was never designed for this purpose either.

Further standardization

Further standardization work with OpenDocument includes:

… excerpt ends here. Continue reading the full article.

Illustrations

Worked examples

Example 1 — a first encounter with OpenDocument

Start with the simplest possible case. Write down what OpenDocument claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In computer science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to OpenDocument before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about OpenDocument ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of OpenDocument

In research: OpenDocument appears in computer science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry: Engineering practice reuses OpenDocument in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom: OpenDocument is common in secondary-school and first-year university syllabi. It links to neighbouring topics Computer file formats, Document-centric XML-based standards, ISO/IEC 26300, so understanding it makes those chapters shorter.
In everyday life: Look for OpenDocument outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study OpenDocument in 20 minutes

Read the reference excerpt below once, without taking notes.
Close the page and write down what OpenDocument means in your own words.
Compare your version with the excerpt and mark what you missed.
Work through the three examples above with pen and paper.
Explain OpenDocument out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is OpenDocument in simple terms?

Why does OpenDocument matter?

Because it connects several computer science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study OpenDocument?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on OpenDocument.