Content deleted Content added
→Encryption: dash created confusion that rest of text was an explanation of text before it. Semicolon clearer that they are two separate statements. |
Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.5 |
||
| (16 intermediate revisions by 11 users not shown) | |||
Line 8:
* As a '''single XML document''' – also known as ''Flat XML'' or ''Uncompressed XML Files''. Single OpenDocument XML files are not widely used,{{citation needed|date=December 2014}} they are also unsupported on some office software which claims to support ODF (Microsoft Office applications version 2007 to 2013 do not recognize them). Filename extensions for a single OpenDocument XML documents are not defined in the OpenDocument technical specification, but commonly used are <code>.xml</code>, <code>.fodt</code>,<ref>{{cite web |url=http://www.ensode.net:80/roller/dheffelfinger/entry/openoffice_documents_version_control_with |archive-url=https://web.archive.org/web/20171125144435/http://www.ensode.net/roller/dheffelfinger/entry/openoffice_documents_version_control_with |url-status=dead |archive-date=2017-11-25 |title=OpenOffice.org Document Version Control With Mercurial |accessdate=2010-06-07 }}</ref> <code>.fods</code>, ... etc.
The recommended filename extensions and [[MIME]] types are included in the official standard (OASIS, May 1, 2005, and its later revisions or versions). The MIME types and extensions contained in the ODF specification are applicable only to office documents that are contained in a package. Office documents that conform to the OpenDocument specification but are not contained in a package should use the MIME type text/xml.
The MIME type is also used in the <code>office:mimetype</code> attribute. It is very important to use this attribute in flat XML files/single XML documents, where this is the only way the type of the document can be detected (in a package, the MIME type is also present in a separate file ''mimetype''). Its values are the MIME types that are used for the packaged variant of office documents.
Line 17:
{| class="wikitable"
! File type
! Extension
Line 63 ⟶ 62:
|1.0
|-
|rowspan=3|Database
|rowspan=3|.odb
|application/vnd.sun.xml.base<ref>{{citation |url=http://dlc.sun.com/osol/jds/downloads/sources/defaults.list |title=MIME types - OpenSolaris Default Applications |accessdate=2010-06-06 |url-status=dead |archiveurl=https://web.archive.org/web/20110716163416/http://dlc.sun.com/osol/jds/downloads/sources/defaults.list |archivedate=2011-07-16 }}</ref><ref>{{citation |url=http://extension.nirsoft.net/odb |title=.odb Extension - List of programs that can open .odb files |accessdate=2010-06-06}}</ref>
|not defined in ODF 1.0/1.1 specifications;<br>used in OpenOffice.org 2.x
|-
|application/vnd.oasis.opendocument.base
|ODF 1.2;<br>used in OpenOffice.org 3.x
|-
|application/vnd.oasis.opendocument.database
|defined in [https://www.iana.org/assignments/media-types/application/vnd.oasis.opendocument.database IANA registration]
Line 89 ⟶ 84:
{| class="wikitable"
! File type
! Extension
Line 173 ⟶ 167:
The OpenDocument format implements spreadsheets as sets of tables. Thus it features extensive capabilities for formatting the display of tables and spreadsheets. OpenDocument also supports database ranges, filters, and "data pilots" (known in Microsoft Excel contexts as "[[pivot table]]s"). Change tracking is available for spreadsheets as well.
The graphics format supports a vector graphic representation, in which a set of layers and the contents [https://web.archive.org/web/20051212150956/http://www.auton.nl/software/apps/adms/en/adms.html] of each layer is defined. Available drawing shapes include Rectangle, Line, Polyline, Polygon, Regular Polygon, Path, Circle, Ellipse, and Connector. 3D Shapes are also available; the format includes information about the Scene, Light, Cube, Sphere, Extrude, and Rotate (it is intended for use as for office data exchange, and not sufficient to represent videos or other extensive 3D scenes). Custom shapes can also be defined.
Presentations are supported. Users can include animations in presentations, with control over the sound, showing a shape or text, hiding a shape or text, or dimming something, and these can be grouped. In OpenDocument, much of the format capabilities are reused from the text format, simplifying implementations. However, tables are not supported within OpenDocument as drawing objects, so may only be included in presentations as embedded tables.
Line 191 ⟶ 185:
** Drawings
** Presentations
* Objects that do not have an XML representation
Use of Microsoft Object Linking and Embedding (OLE) objects limits the interoperability, because these objects are not widely supported in programs for viewing or editing files (e.g. embedding of other files inside the file, such as tables or charts from a spreadsheet application in a text document or presentation file).<ref>{{cite web |url=https://www.linux.com/news/foss-word-processors-compared-ooo-writer-abiword-and-kword/ |title=FOSS word processors compared: OOo Writer, AbiWord, and KWord |author=Bruce Byfield |date=2005-08-23 |accessdate=2010-04-06}}
===Formatting===
Line 211 ⟶ 205:
===Encryption===
When an OpenDocument file is password protected the file structure of the bundle remains the same, but contents of XML files in the package are encrypted using the following algorithm:
# The file contents are compressed with the [[DEFLATE]] algorithm.
# A checksum of a portion of the compressed file is computed (SHA-1 of the file contents, or SHA-1 of the first 1024 bytes of the file, or SHA-256 of the first 1024 bytes of the file) and stored, so password correctness can be verified when decrypting.
# A digest (hash) of the user
# This digest is used to produce a derived key by undergoing [[key stretching]] with [[PBKDF2]] using HMAC-SHA-1 with a salt of arbitrary length (in ODF 1.2; it's 16 bytes in ODF 1.1 and below) generated by the random number generator for an arbitrary iteration count (1024 by default in ODF 1.2).
# The random number generator is used to generate a random initialization vector for each file.
Line 221 ⟶ 215:
==Format internals==
An OpenDocument file commonly consists of a standard [[ZIP (file format)|ZIP]] archive ([[JAR (file format)|JAR]] archive<ref>{{cite web |last=Sobhi |first=Ali |date=2007-08-14 |orig-date=August 2006 |title=Introduction to OpenDocument Format |publication-place=Armonk, New York, United States |publisher=[[IBM]] |url=http://www-03.ibm.com/able/resources/odfintro.html |archive-url=https://web.archive.org/web/20080602152400/http://www-03.ibm.com/able/resources/odfintro.html |url-status=dead |archive-date=2008-06-02
According to the OpenDocument 1.0 specification, the ZIP file specification is defined in ''Info-ZIP Application Note 970311, 1997''.<ref>{{cite web |url=http://tools.oasis-open.org/issues/browse/OFFICE-2205 |title=NEEDS-DISCUSSION: ZIP reference - N 1309 |
The simple compression mechanism used for a package normally makes OpenDocument files significantly smaller than equivalent Microsoft "<code>.doc</code>" or "<code>.ppt</code>" files. This smaller size is important for organizations who store a vast number of documents for long periods of time, and to those organizations who must exchange documents over low bandwidth connections. Once uncompressed, most data is contained in simple text-based XML files, so the uncompressed data contents have the typical ease of modification and processing of XML files. The standard also allows for the creation of a single XML document, which uses ''<office:document>'' as the root element, for use in document processing.
Line 291 ⟶ 285:
===mimetype (file)===
'''mimetype''' is just a one-line file with the mimetype of the document. One implication of this is that the file extension is actually immaterial to the format. The file extension is only there for the benefit of the user. It is important to note that this special file is always the first file entry in the ZIP archive and it is uncompressed. Because the ZIP header uses fields with fixed lengths, this allows the direct identification of the different OpenDocument formats without decompression of the content (e. g. with magic bytes).
===Thumbnails (directory)===
'''Thumbnails''' is a separate folder for a document thumbnail. The thumbnail must be saved as “thumbnail.png”. A thumbnail representation of a document should be generated by default when the file is saved. It should be a representation of the first page, first sheet, etc. of the document. The required size for the thumbnails is 128x128 pixel. In order to conform to the [
===META-INF (directory)===
Line 312 ⟶ 306:
==History==
* Version 1.0 became an OASIS Standard on 2005-05-01;<ref>
{{cite web
| url
| title
| work
| publisher
| accessdate
| quote = Open Document
}}
</ref>
* Version 1.1 became an OASIS Standard on 2007-02-07;<ref>
{{cite web
| url
| title = OASIS Open Document Format for Office Applications (OpenDocument) TC
| work
| publisher
| accessdate
| quote = Open Document
}}
</ref>
* Version 1.2 became an OASIS Standard on 2011-09-29;<ref name="odf12">
{{cite web
| url = http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
| title = OASIS Open Document Format for Office Applications (OpenDocument) TC
| work = OASIS website
| publisher = OASIS
| accessdate = 2024-11-26
| quote = Open Document Format v1.2 was approved as a OASIS Standard on 29 September 2011.
}}
</ref>
* Version 1.3 became an OASIS Standard on 2021-04-27.<ref>
{{cite web
| url = http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
| title = OASIS Open Document Format for Office Applications (OpenDocument) TC
| work = OASIS website
| publisher = OASIS
| accessdate = 2024-11-26
| quote = Open Document Format for Office Applications (OpenDocument) Version 1.3 OASIS Standard was approved by the members of OASIS on 27 April 2021.
}}
</ref>
==Versions detection==
To indicate which version of the OpenDocument specification a file complies with, all root elements take an <code>office:version</code> attribute
===ODF 1.0/1.1===
It is not mandatory to use <code>office:version</code> attribute in ODF 1.0 and ODF 1.1 files, so when an element has office:version omitted, the element is based on ODF 1.0 or 1.1. If the file has a version known to an XML processor, it may validate the document. Otherwise, it is optional to validate the document, but the document must be well formed
===ODF 1.2===▼
The <code>office:version</code> attribute shall be present in each and every <office:document>, <office:document-content>, <office:document-styles>, <office:document-meta>, and <office:document-settings> element in the XML documents that comprise an OpenDocument 1.2 document. The value of the office:version attribute shall be "1.2".▼
▲===ODF 1.2 and newer===
▲The <code>office:version</code> attribute shall be present in each and every <office:document>, <office:document-content>, <office:document-styles>, <office:document-meta>, and <office:document-settings> element in the XML documents that comprise an OpenDocument 1.2 or newer document. The value of the office:version attribute shall
==Conformance==
Line 367 ⟶ 378:
==References==
{{Refbegin}}
* [https://docs.oasis-open.org/office/OpenDocument/v1.4/ OpenDocument 1.4 specification] in ODT, HTML and PDF formats
* [https://docs.oasis-open.org/office/OpenDocument/v1.3/ OpenDocument 1.3 specification] in ODT, HTML and PDF formats
* [https://docs.oasis-open.org/office/v1.2/ OpenDocument 1.2 specification] in ODT, HTML and PDF formats
| |||