|Introduction | Sustainability Factors | Content Categories | Format Descriptions | Contact|
|Full name||OpenDocument Presentation Document Format (ODP), Version 1.2. Part of OASIS Open Document Format for Office Applications, Version 1.2 and the equivalent ISO 26300-1:2015.|
The OpenDocument Presentation Document Format (ODP), Version 1.2 (given the short name ODF_presentation_1_2 here) is a format for editable documents that are presentations based on sequences of "slides." Designed to be a native format for applications for assembling slide-show presentations, the format is sometimes called ODP after its usual file extension. The term ODP will be used here to refer to ODF_presentation_1_2 and other chronological versions of the OpenDocument Presentation format. It is one of several subtypes in the ODF family for particular content categories. This description relates to part 1 of the ODF 1.2 specification as published by OASIS and the equivalent ISO/IEC 26300-1:2015 specification. The standard specifies markup for presentations using the ODF presentation:, draw:, and text: namespaces in particular. Other namespaces used in many presentations are table:, anim:, smil:.
The primary ODF markup used for presentations is actually in the draw: namespace, with the <draw:page> element as the usual container for a single slide. The content.xml file’s <office:presentation> element typically holds a series of <draw:page> elements, each of which has a unique draw:name attribute, often in the form pagen. The presentation: namespace is used for presentation-specific elements, such as <presentation:notes>, <presentation:animations> and specifications for headers and footers on slides.
The ODF specification covers two physical forms for ODF documents, a flat form as a single XML file and a package form based on the ZIP_6_2_0 format. This description focuses on the more commonly used ZIP-based package format for ODF presentation files, given the .odp file extension. Files using the same markup specification and package but with an extension of .otp are for use as presentation document templates.
An ODF package can be recognized as a presentation document in several ways. Externally, there are file extensions for two ways in which ODF presentation documents may be used in graphics applications, as noted above. The primary internal indication is that the mandatory file named mimetype will contain one of the corresponding strings listed as File type signifiers below. An additional way to recognize an ODF presentation document is that the <office:body> element, a child of the root <office:document-content> element in content.xml has the child element <office:presentation>.
The ZIP-based package for any ODF file contains, at a minimum, five files: a one-line mimetype file containing a single text string; content.xml; styles.xml; meta.xml; and settings.xml. The typical content.xml file for a minimal presentation document has the basic form:
For details of the ZIP-based package for ODF_presentation_1_2, see ODF_package_1_2. The package specification defines the form for the package manifest, and options for digital signatures, encryption, etc.
See Notes in ODF Family for more information about the flat XML-only variant of ODF files. For a flat ODF presentation file, the root <office:document> element has an office:mimetype attribute with one of the values listed below as File signifiers.
Apart from changes to the underlying package format, changes made to the markup for ODF presentations between ODF versions 1.1 and 1.2 were limited to a few enhancements.
|Production phase||Can be used in any production phase: for creating documents (initial state); for editing and review (middle-state); and for final use or distribution.|
|Relationship to other formats|
|Subtype of||ODF_Family, OpenDocument Format (ODF) Family, OASIS and ISO/IEC 26300|
|Contains||ODF_draw_1_2, OpenDocument Drawing Document Format (ODG), Version 1.2, ISO 26300:2015. Presentations typically consist of sequences of "drawings," with each slide represented by a drawing.|
|May contain||Other ODF document categories, such as charts and drawings embedded in individual slides.|
|May contain||Embedded images, sound, or video, in base64 encoding. PNG is recommended for bit-mapped images.|
|Subtype of||ODF_package_1_2, OpenDocument Package Format, ODF 1.2, ISO 26300-3:2015|
|Subtype of||ZIP_6_2_0, ZIP File Format, Version 6.2.0 (PKWARE). Various features of the ZIP File Format are not permitted in ODF.|
|Contains||META-INF/manifest.xml file. This manifest file is mandatory in all ODF packages.|
|Has earlier version||ODP 1.1, not described separately on this site.|
|Defined via||XML_1_0, XML (Extensible Markup Language) 1.0. A normative RELAX NG schema is part of the specification for ODF 1.2, which includes the specification for chart documents.|
|LC experience or existing holdings|
|LC preference||As of December 2015, no format preference has been explicitly expressed by the Library of Congress in relation to acquisition of digital presentations for its collections.|
|Disclosure||International open standard. Developed and maintained by OASIS Open Document Format for Office Applications (OpenDocument) TC as part of the OpenDocument Format (ODF) 1.2 specification published by OASIS in 2011. Also approved as part of the equivalent ISO/IEC 26300-1:2015 by ISO/IEC JTC1/SC34.|
Specifications from OASIS: Open Document Format for Office Applications (OpenDocument) Version 1.2. Markup specification for ODF 1.2 presentation documents are found primarily in chapters 9 and 10 of Part 1 of the specification. The technical specification is through a normative RNG schema for primary component files for ODF documents..
The identical specification is published as ISO/IEC 26300-1:2015, Information technology -- Open Document Format for Office Applications (OpenDocument) v1.2 Part 1: OpenDocument Schema.
The ODF 1.2 specification is divided into three parts, with the bulk of the markup specification in Part 1: OpenDocument Schema. The package specification has been moved into a separate Part 3: Packages.
See ODF_Family for a listing of namespaces that can be incorporated into any ODF 1.1 or ODF 1.2 document and links to associated specifications.
The major office suites using ODF as primary native format family include special applications for developing presentations and can read and write presentation documents as defined in ODF 1.2:
Microsoft Office has supported direct editing of ODF 1.2 presentation documents since Office 2013. PowerPoint features not supported or only partially supported in the .odp format are listed in Supported features in OpenDocument presentation (.odp) format. This list suggests that some types of animation and transition supported in PowerPoint and by PPTX can not be represented in ODP. There are also a number of vector graphic capabilities and design settings available in PowerPoint, that cannot be used in an ODP file. A feature comparison from LibreOffice focuses on the application functionality rather than the format. See Notes in the description of PPTX Transitional (Office Open XML) for a discussion of issues relating to conversion between PPTX and ODP, both issues that have been found in practice, and potential issues based on functionality added recently.
See Adoption among the Sustainability Factors for PPTX Transitional (Office Open XML) for discussion of the market for presentation software. Additional useful references below highlight the crowded market for presentation software, with a recent emphasis on creative ways to leave behind the traditional slide-by-slide flow. Lists of alternatives to PowerPoint often have no mention of any application using ODP as native format. Where LibreOffice is recommended, it is often as a largely compatible free alternative to PowerPoint. Comments welcome.
See ODF-Family for more detail on adoption of ODF in general, and particularly for mandates or recommendations for ODF when exchanging editable documents among government agencies and the individiduals or organizations they serve.
|Licensing and patents||No concerns. See ODF_Family.|
The structure and text of an ODP file are all represented in XML and hence viewable without special tools, although XML-aware tools that can show the element hierarchy make viewing and interpretation more convenient. The most commonly used parts, elements, and attributes have recognizable names. Simple documents can be interpreted with very basic tools. However, interpreting the semantics of some elements and the correspondence of some elements and attributes to charting terminology or functionality will require not only understanding of the schema and the specification text, but familiarity with the associated terminology and functionality.
As for other members of the ODF 1.2 family, ODF_presentation_1_2 added support for metadata based on RDF (W3C's Resource Description Framework). As well as using RDF for metadata for the document package as a whole, RDF can be attached to elements within the document's content. The use of "custom" metadata as specified in ODF 1.1 is deprecated in ODF 1.2.
Pre-defined metadata elements for the document as a whole, stored in an <office:meta> element include:
The pre-defined elements are all optional and repeatable. However, applications are not required to update multiple occurrences in a specific way to reflect modifications to a document.
Also supported in both ODF 1.1 and ODF 1.2 is an XML structure for user-defined metadata, based on triplets of name, data type, and value.
Depends on features used. Presentation documents in ODF_presentation_1_2 format are often self-contained, but may include links to externally stored data.
|Technical protection considerations||Encryption is supported for files within an ODF 1.1 or ODF 1.2 package. In addition, an ODF package file may be encrypted during interchange or as part of DRM controlling distribution.|
No specific set of factors for assessing quality and functionality of a presentation format has been developed. This format description uses selected factors for assessing formats for images and text.
Graphics and text on a slide are structured to scale with monitor size. Raster images can be incorporated in a slide and "may have an arbitrary format" but the ODF standard recommends use of PNG.
|Clarity (high image resolution)||Since slides are intended for display on monitors, support for very high spatial resolution or high-bit-depth is not needed. For vector graphics and text effects, ODF 1.2 uses the notation #rrggbb and the RGB color model (assuming the sRGB colorspace).|
|Color maintenance||There is no support for ICC profiles or other color management mechanisms intended to produce consistent color on different devices. Accuracy of perceived color is not considered crucial for presentations.|
|Support for vector graphics, including graphic effects and typography||Excellent support for typographic effects and vector graphics, using all the capabilities supported for ODF_draw_1_2.|
|Support for multispectral bands||Not relevant for a format aimed at presentations.|
|Functionality beyond normal rendering||
Support for animations, slide transitions, and user interactions during presentations. Selected elements borrowed from the Synchronized Multimedia Integration Language (SMIL) 2.0 specification can be used to animate text on a slide.
|Normal rendering||Editable document. Textual content is conveniently extractable for quotation and for indexing. Full support for Unicode.|
|Integrity of document structure||The ordering of slides and of textual lists on slides is indicated by order of elements. Relationships between slides and embedded content are indicated by nesting of elements.|
|Integrity of layout and display||Excellent support for layout choices. Represents entire layout and formatting as intended by an author who used an application for which ODP is a native format. Differences in detail can occur on display if the original fonts used are not available in the system used for viewing. Bi-directional and vertical display of text can be specified; see Appendix E of the ODF 1.2 specification.|
|Support for mathematics, formulae, etc.||Equations can be represented using MathML, either as independent files or as drawing objects that can be embedded in slides.|
|Functionality beyond normal rendering||
Selected elements borrowed from the Synchronized Multimedia Integration Language (SMIL) 2.0 specification can be used to animate text on a slide.
||.odp is the extension used for an ODF presentation file.|
|Internet Media Type||application/vnd.oasis.opendocument.presentation
||The MIME types for ODF_presentation_1_2 are the same as for earlier versions|
|Magic numbers||See note.||Magic numbers that apply to ODF document category subtypes incorporate the magic number for ZIP_PK, the string mimetype at position 30, and the MIME subtype string value at position 38.|
|Indicator for profile, level, version, etc.||ASCII: office:version="1.2"
||The four root elements used in the primary files in an ODF package all require an attribute that records the ODF version. This is the signifier that distinguishes ODF 1.2 packages from earlier versions. Documents without this attribute are assumed to be from version 1.1 or earlier.|
||The extension .otp is used for a presentation document used as a template.|
|Internet Media Type||application/vnd.oasis.opendocument.presentation-template
See OASIS OpenDocument Essentials: Chapter 7. Presentations for examples of markup for transitions, animations, and interactions. Elements borrowed from the Synchronized Multimedia Integration Language (SMIL) 2.0 specification can be used to animate text on a slide.
See Notes section in description for PPTX Transitional (Office Open XML) for discussion of issues relating to conversion between PPTX and ODP.
See ODF_package_1_2 for discussion of changes to ODF in general between versions 1.1 and 1.2. Changes to the markup for presentations between versions 1.1 and 1.2 were primarily enhancements requested by implementers. Appendix G of the ODF 1.2 schema specification suggests that a functional extension was support for tables in presentations. No elements or attributes were added to the presentation: namespace.
See ODF_family for more on the history ODF in general.