OpenDocument

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Lua error in package.lua at line 80: module 'strict' not found.

OpenDocument Text
OpenDocument Text icon
Filename extensions
.odt  .fodt
Internet media type
application/vnd.oasis.
opendocument.text
Uniform Type Identifier (UTI)
org.oasis.opendocument.text[1]
UTI conformation
org.oasis-open.opendocument
public.composite-content
Developed by OASIS
Initial release 1 May 2005; 18 years ago (2005-05-01)
Latest release
1.2
(29 September 2011; 12 years ago (2011-09-29))
Type of format Document
Extended from XML
Standard ISO/IEC 26300[2][3][4][5]
(OASIS OpenDocument Format)
Open format? Yes
Website
OpenDocument Presentation
OpenDocument Presentation icon
Filename extensions
.odp  .fodp
Internet media type
application/vnd.oasis.
opendocument.presentation
Uniform Type Identifier (UTI)
org.oasis.opendocument.presentation[1]
UTI conformation
org.oasis-open.opendocument
public.composite-content
Developed by OASIS
Initial release 1 May 2005; 18 years ago (2005-05-01)
Latest release
1.2
(29 September 2011; 12 years ago (2011-09-29))
Type of format Presentation
Extended from XML
Standard ISO/IEC 26300[2][3][4][5]
(OASIS OpenDocument Format)
Open format? Yes
OpenDocument Spreadsheet
OpenDocument Spreadsheet icon
Filename extensions
.ods  .fods
Internet media type
application/vnd.oasis.
opendocument.spreadsheet
Uniform Type Identifier (UTI)
org.oasis.opendocument.spreadsheet[1]
UTI conformation
org.oasis-open.opendocument
public.composite-content
Developed by OASIS
Initial release 1 May 2005; 18 years ago (2005-05-01)
Latest release
1.2
(29 September 2011; 12 years ago (2011-09-29))
Type of format Spreadsheet
Extended from XML
Standard ISO/IEC 26300[2][3][4][5]
(OASIS OpenDocument Format)
Open format? Yes
OpenDocument Graphics
OpenDocument Spreadsheet icon
Filename extensions
.odg  .fodg
Internet media type
application/vnd.oasis.
opendocument.graphics
Uniform Type Identifier (UTI)
org.oasis.opendocument.graphics[1]
UTI conformation
org.oasis-open.opendocument
public.composite-content
Developed by OASIS
Initial release 1 May 2005; 18 years ago (2005-05-01)
Latest release
1.2
(29 September 2011; 12 years ago (2011-09-29))
Type of format Graphics
Extended from XML
Standard ISO/IEC 26300[2][3][4][5]
(OASIS OpenDocument Format)
Open format? Yes

The Open Document Format for Office Applications (ODF), also known as OpenDocument, is an XML-based file format for spreadsheets, charts, presentations and word processing documents. It was developed with the aim of providing an open, XML-based file format specification for office applications.[6]

The standard was developed by a technical committee in the Organization for the Advancement of Structured Information Standards (OASIS) consortium.[7] It was based on the Sun Microsystems specification for OpenOffice.org XML, the default format for OpenOffice.org, which had been specifically intended "to provide an open standard for office documents."[8]

In addition to being an OASIS standard, it was published as an ISO/IEC international standard ISO/IEC 26300 — Open Document Format for Office Applications (OpenDocument).[2][3][4][5][9][10]

Specifications

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The most common filename extensions used for OpenDocument documents are:[11][12]

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.[13] The whole test suite is available under the Creative Commons Attribution 2.5 license.

Standardization

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The OpenDocument standard was developed by a Technical Committee (TC) under the Organization for the Advancement of Structured Information Standards 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.[14] 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 the 28th August 2001.[15]

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 JTC1/SC34), with broad participation,[16] after which the OpenDocument specification was "approved for release as an ISO and IEC International Standard" under the name ISO/IEC 26300:2006.[17]

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.

Further standardization work with OpenDocument includes:

  • The OASIS Committee Specification OpenDocument 1.0 (second edition) corresponds to the published ISO/IEC 26300:2006 standard. The content of ISO/IEC 26300 and OASIS OpenDocument v1.0 2nd ed. is identical.[5] It includes the editorial changes made to address JTC1 ballot comments. It is available in ODF, HTML and PDF formats.
  • OpenDocument 1.1 includes additional features to address accessibility concerns.[18] It was approved as an OASIS Standard on 2007-02-01 following a call for vote issued on 2007-01-16.[19] The public announcement was made on 2007-02-13.[20] This version was not initially submitted to ISO/IEC, because it is considered to be a minor update to ODF 1.0 only, and OASIS were working already on ODF 1.2 at the time ODF 1.1 was approved.[21] However it was later submitted to ISO/IEC (as of March 2011, it was in "enquiry stage" as Draft Amendment 1 - ISO/IEC 26300:2006/DAM 1) and published in March 2012 as "ISO/IEC 26300:2006/Amd 1:2012 — Open Document Format for Office Applications (OpenDocument) v1.1".[9][10]
  • OpenDocument 1.2 includes additional accessibility features, RDF-based metadata,[22] a spreadsheet formula specification based on OpenFormula,[22] support for digital signatures and some features suggested by the public. It consists of three parts: Part 1: OpenDocument Schema, Part 2: Recalculated Formula (OpenFormula) Format and Part 3: Packages. Version 1.2 of the specification was approved as an OASIS Standard on 29 September 2011.[23] It was submitted to the relevant ISO committee under the Publicly Available Specification (PAS) procedure in March 2014.[24] As of October 2014, it has been unanimously approved as a Draft International Standard, some comments have been raised in process that need to be addressed before OpenDocument 1.2 can proceed to become an International Standard.[25] OpenDocument 1.2 was published as ISO/IEC standard on 17 June 2015.[2][3][4]

Future

  • OpenDocument 1.3 (a.k.a. "ODF-Next") As of January, 2014, the current state of a possible future version of OpenDocument specification is a working draft (a preliminary unapproved sketch, outline, or version of the specification). The OASIS Advanced Document Collaboration subcommittee (created in December, 2010) is working on an update of OpenDocument change-tracking that will not only enhance the existing change-tracking feature set, but also lay the foundation for the standardization of real-time collaboration by making change tracking compatible with real-time collaboration.[26][27][28]

Application support

Software

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The OpenDocument format is used in free software and in proprietary software. This includes office suites (both stand-alone and web-based) and individual applications such as word-processors, spreadsheets, presentation, and data management applications. Prominent office suites supporting OpenDocument fully or partially include:

Various organizations have announced development of conversion software (including plugins and filters) to support OpenDocument on Microsoft's products.[42][43] As of July 2007, there are nine packages of conversion software. Microsoft first released support for the OpenDocument Format in Office 2007 SP2.[44] However, the implementation faced substantial criticism and the ODF Alliance and others claimed that the third party plugins provided better support.[45] Microsoft Office 2010 can open and save OpenDocument Format documents natively, although not all features are supported.[46]

Starting with Mac OS X 10.5, the TextEdit application and Quick Look preview feature support the OpenDocument Text format.

Accessibility

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The specification of OpenDocument has undergone an accessibility review, and a few additions were made to version 1.1 of the specification to improve accessibility. Many of the components it is built on, such as Synchronized Multimedia Integration Language and Scalable Vector Graphics, have already gone through the World Wide Web Consortium's Web Accessibility Initiative processes.[citation needed]

Licensing

Public access to the standard

Versions of the OpenDocument Format approved by OASIS are available for free download and use.[47] The ITTF has added ISO/IEC 26300 to its "list of freely available standards"; anyone may download and use this standard free-of-charge under the terms of a click-through license.[48]

Additional royalty-free licensing

Obligated members of the OASIS ODF TC have agreed to make deliverables available to implementors under the OASIS Royalty Free with Limited Terms policy.

Key contributor Sun Microsystems made an irrevocable intellectual property covenant, providing all implementers with the guarantee that Sun will not seek to enforce any of its enforceable U.S. or foreign patents against any implementation of the OpenDocument specification in which development Sun participates to the point of incurring an obligation.[49]

A second contributor to ODF development, IBM – which, for instance, has contributed Lotus spreadsheet documentation[50] – has made their patent rights available through their Interoperability Specifications Pledge in which "IBM irrevocably covenants to you that it will not assert any Necessary Claims against you for your making, using, importing, selling, or offering for sale Covered Implementations."[51]

The Software Freedom Law Center has examined whether there are any legal barriers to the use of the OpenDocument Format (ODF) in free and open source software arising from the standardization process. In their opinion ODF is free of legal encumbrances that would prevent its use in free and open source software, as distributed under licenses authored by Apache and the FSF.

Response

Support for OpenDocument

Several governments, companies, organizations and software products support the OpenDocument format. For example:

  • The OpenDoc Society run frequent Plugfests in association with industry groups and Public Sector organisations. The 10th Plugfest [52] was hosted by the UK Government Digital Service in conjunction with industry associations including the OpenForum Europe and the Open Source Consortium.
    • An output of the 10th Plugfest was an ODF toolkit [53] which includes "Open Document Format principles for Government Technology" that has the purpose of simply explaining the case for ODF directed at the "average civil servant" and includes an extract form the UK Government policy relating to Open Document Format.
    • The toolkit also includes a single page graphical image [54]designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated in to more than 10 languages.
  • Information technology companies like Apple Inc., Adobe Systems, Google, IBM, Intel, Microsoft, Nokia, Novell, Red Hat, Oracle as well as other companies who may or may not be working inside the OASIS OpenDocument Adoption Technical Committee.
  • Over 600 companies and organizations promote OpenDocument format through The OpenDocument Format Alliance.[55]
  • NATO with its 26 members uses ODF as a mandatory standard for all members.[56]
  • The TAC (Telematics between Administrations Committee), composed of e-government policy-makers from the 25 European Union Member States, endorsed a set of recommendations for promoting the use of open document formats in the public sector.[57]
  • The free office suites Apache OpenOffice, Calligra, KOffice, NeoOffice and LibreOffice all use OpenDocument as their default file format.
  • Several organisations, such as the OpenDocument Fellowship and OpenDoc Society were founded to support and promote OpenDocument.
  • The UK government has adopted ODF as the standard for all documents in the UK civil service [58]
  • The Wikimedia Foundation supports ODF export from MediaWiki, which powers Wikipedia and a number of other Internet wiki-based sites.[59]
  • The default text processing applications in Windows 10 (WordPad) and Mac OS 10.9 (TextEdit) support OpenDocument Text.

On 4 November 2005, IBM and Sun Microsystems convened the "OpenDocument (ODF) Summit" in Armonk, New York, to discuss how to boost OpenDocument adoption. The ODF Summit brought together representatives from several industry groups and technology companies, including Oracle, Google, Adobe, Novell, Red Hat, Computer Associates, Corel, Nokia, Intel, and Linux e-mail company Scalix (LaMonica, 10 November 2005). The providers committed resources to technically improve OpenDocument through existing standards bodies and to promote its usage in the marketplace, possibly through a stand-alone foundation.[60] Scholars have suggested that the "OpenDocument standard is the wedge that can hold open the door for competition, particularly with regard to the specific concerns of the public sector."[61] Indeed, adoption by the public sector has risen considerably since the promulgation of the OpenDocument format initiated the 2005/2006 time period.[61]

  • Different applications using ODF as a standard document format have different methods of providing macro/scripting capabilities. There is no macro language specified in ODF. Users and developers differ on whether inclusion of a standard scripting language would be desirable.[62]
  • The ODF specification for tracked changes is limited and does not fully specify all cases, resulting in implementation-specific behaviors.[63] In addition, OpenDocument does not support change tracking in elements like tables or MathML.[64]
  • It is not permitted to use generic ODF formatting style elements (like font information) for the MathML elements.[64]

Adoption

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

One objective of open formats like OpenDocument is to guarantee long-term access to data without legal or technical barriers, and some governments have come to view open formats as a public policy issue. Several governments around the world have introduced policies of partial or complete adoption.[61] What this means varies from case to case; in some cases, it means that the ODF standard has a national standard identifier; in some cases, it means that the ODF standard is permitted to be used where national regulation says that non-proprietary formats must be used, and in still other cases, it means that some government body has actually decided that ODF will be used in some specific context. The following is an incomplete list:

International
National Africa
Asia
Europe
S America
Subnational

See also

References

  1. 1.0 1.1 1.2 1.3 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 2.3 2.4 2.5 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 3.2 3.3 3.4 3.5 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 4.2 4.3 4.4 4.5 Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 5.2 5.3 5.4 5.5 Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. 22.0 22.1 22.2 22.3 22.4 Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. 10th Plugfest hosted by the UK Cabinet Office December 2014
  53. http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/
  54. http://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. 57.0 57.1 Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. 61.0 61.1 61.2 Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. 64.0 64.1 Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. https://joinup.ec.europa.eu/community/osor/news/ec-recommends-supporting-open-document-format
  67. Lua error in package.lua at line 80: module 'strict' not found.
  68. Lua error in package.lua at line 80: module 'strict' not found.
  69. Lua error in package.lua at line 80: module 'strict' not found.
  70. Lua error in package.lua at line 80: module 'strict' not found.
  71. Lua error in package.lua at line 80: module 'strict' not found.
  72. Lua error in package.lua at line 80: module 'strict' not found.
  73. Lua error in package.lua at line 80: module 'strict' not found.
  74. Lua error in package.lua at line 80: module 'strict' not found.

External links