Jump to content

OpenDocument: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
→Application support: removed POV instructions to readers on how they must interpret the text; indicated that this is a paraphrase from a blog, not a direct quote. Giving the actual text.
Rfvuhbtg (talk | contribs)
15 edits
added info relevant to last edit
Line 270: Line 270:
|date=[[2006-05-19]]
|date=[[2006-05-19]]
|accessdate=2009-05-21
|accessdate=2009-05-21
|publisher=zdnet}}</ref> Critics say that with this conflict of standards Microsoft actually managed to reduce interoperability between office productivity software.<ref name="JeremyAllison" /><ref> {{cite web|url=http://www.odfalliance.org/blog/index.php/site/microsofts_odf_support_falls_short/ |title=Microsoft’s ODF Support Falls Short |accessdate=2009-05-22 |date=2009-05-19 |work=Open Document Alliance |publisher=[[ODF Alliance]] }}</ref><ref> {{cite web|url=http://www.robweir.com/blog/2009/05/update-on-odf-spreadsheet.html |title=Update on ODF Spreadsheet Interoperability |accessdate=2009-05-22 |last=Weir |first=Rob |date=2009-05-03 }}</ref> The company had previously reportedly stated that "where ODF 1.1 is ambiguous or incomplete, the Office implementation can be guided by current practice in OpenOffice.org, mainly, and other implementations including KOffice and AbiWord. Peter Amstein and the Microsoft Office team are reluctant to make liberal use of extension mechanisms, even though provided in ODF 1.1. They want to avoid all appearance of an embrace-extend attempt." <ref name="mwork">http://orcmid.com/blog/2008/08/microsoft-odf-interoperability-workshop.asp</ref>
|publisher=zdnet}}</ref> Critics say that with this conflict of standards Microsoft actually managed to reduce interoperability between office productivity software.<ref name="JeremyAllison" /><ref> {{cite web|url=http://www.odfalliance.org/blog/index.php/site/microsofts_odf_support_falls_short/ |title=Microsoft’s ODF Support Falls Short |accessdate=2009-05-22 |date=2009-05-19 |work=Open Document Alliance |publisher=[[ODF Alliance]] }}</ref><ref> {{cite web|url=http://www.robweir.com/blog/2009/05/update-on-odf-spreadsheet.html |title=Update on ODF Spreadsheet Interoperability |accessdate=2009-05-22 |last=Weir |first=Rob |date=2009-05-03 }}</ref> The company had previously reportedly stated that "where ODF 1.1 is ambiguous or incomplete, the Office implementation can be guided by current practice in OpenOffice.org, mainly, and other implementations including KOffice and AbiWord. Peter Amstein and the Microsoft Office team are reluctant to make liberal use of extension mechanisms, even though provided in ODF 1.1. They want to avoid all appearance of an embrace-extend attempt." <ref name="mwork">http://orcmid.com/blog/2008/08/microsoft-odf-interoperability-workshop.asp</ref> However, according to the [[ODF Alliance]], "ODF spreadsheets created in Excel 2007 SP2 do not in fact conform to ODF 1.1 because Excel 2007 incorrectly encodes formulas with cell addresses. Section 8.3.1 of ODF 1.1 says that addresses in formulas "start with a "[" and end with a "]"." In Excel 2007 cell addresses were not enclosed with the necessary square brackets, which could be easily corrected."
<ref name="sp2-fact-sheet">{{cite web
|url=http://www.odfalliance.org/resources/fact-sheet-Microsoft-ODF-support.pdf
|title=Fact-sheet Microsoft ODF support
|accessdate=2009-05-24
|quote=''ODF spreadsheets created in Excel 2007 SP2 do not in fact conform to ODF 1.1 because Excel 2007 incorrectly encodes formulas with cell addresses. Section 8.3.1 of ODF 1.1 says that addresses in formulas “start with a "[" and end with a "]"." In Excel 2007 cell addresses were not enclosed with the necessary square brackets, which could be easily corrected.''
|publisher=odfalliance}}</ref>


Before SP2, Microsoft had sponsored the creation of the Open XML translator<ref>{{cite web
Before SP2, Microsoft had sponsored the creation of the Open XML translator<ref>{{cite web

Revision as of 01:25, 4 June 2009

Template:Distinguish2

"ODF" redirects here. For other uses, see ODF (disambiguation).
OpenDocument Format
OpenDocument Text
Filename extension
.odt
Internet media type
application/vnd.
oasis.opendocument.
text
Uniform Type Identifier (UTI)org.oasis.
opendocument.text[1]
Developed bySun Microsystems, OASIS
Type of formatDocument file format
Extended fromXML
OpenDocument Presentation
Filename extension
.odp
Internet media type
application/vnd.
oasis.opendocument.
presentation
Uniform Type Identifier (UTI)org.oasis.
opendocument.presentation[1]
Developed bySun Microsystems, OASIS
Type of formatPresentation
Extended fromXML
OpenDocument Spreadsheet
Filename extension
.ods
Internet media type
application/vnd.
oasis.opendocument.
spreadsheet
Uniform Type Identifier (UTI)org.oasis.
opendocument.spreadsheet[1]
Developed bySun Microsystems, OASIS
Type of formatSpreadsheet
Extended fromXML
OpenDocument Graphics
Filename extension
.odg
Internet media type
application/vnd.
oasis.opendocument.
graphics
Uniform Type Identifier (UTI)org.oasis.
opendocument.graphics[1]
Developed bySun Microsystems, OASIS
Type of formatGraphics file format
Extended fromXML
OpenDocument Database
Filename extension
.odb
Internet media type
application/vnd.
oasis.opendocument.
database
Uniform Type Identifier (UTI)org.oasis.
opendocument.database[1]
Developed bySun Microsystems, OASIS
Type of formatDatabase
Extended fromXML

The OpenDocument format (ODF) is a file format for electronic office documents such as spreadsheets, charts, presentations and word processing documents. While the specifications were originally developed by Sun, the standard was developed by the OASIS Open Document Format for Office Applications (OpenDocument) TC - OASIS ODF TC [2], committee of the Organization for the Advancement of Structured Information Standards (OASIS) consortium and based on the XML format originally created and implemented by the OpenOffice.org office suite (see OpenOffice.org XML). In addition to being a free and open OASIS standard, it is published (in one of its version 1.0 manifestations) as an ISO/IEC international standard, ISO/IEC 26300:2006 Open Document Format for Office Applications (OpenDocument) v1.0.[3] Published ODF standards meet the common definitions of an open standard, meaning they are freely available and implementable.

Specifications

Main article: OpenDocument technical specification

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

A basic OpenDocument file 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 sample documents in OpenDocument Format available.[5] The whole test suite is available under the Creative Commons Attribution 2.5 license.

Standardization

Main article: OpenDocument standardization

The OpenDocument standard was developed by a Technical Committee (TC) under the 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.[6] 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 December 16, 2002; OASIS approved OpenDocument as an OASIS Standard on May 1, 2005. OASIS submitted the ODF specification to ISO/IEC Joint Technical Committee 1 (JTC1) on November 16, 2005, under Publicly Available Specification (PAS) rules.

After a six-month review period, on May 3, 2006 OpenDocument unanimously passed its six-month DIS ballot in JTC1, with broad participation,[7] after which the OpenDocument specification was "approved for release as an ISO and IEC International Standard" under the name ISO/IEC 26300:2006.[8]

After responding to all written ballot comments, and a 30-day default ballot, the OpenDocument International standard went to publication in ISO, officially published November 30, 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. 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.[9] It was approved as an OASIS Standard on 2007-02-01 following a call for vote issued on 2007-01-16.[10] The public announcement was made on 2007-02-13.[11]
  • OpenDocument 1.2 is currently being written by the ODF TC. It is likely to include additional accessibility features, metadata enhancements, a spreadsheet formula specification based on OpenFormula, support for digital signatures and some features suggested by the public. Originally OpenDocument 1.2 was expected to become an OASIS standard by October 2007 but later it was predicted to become a final draft in May 2008 and an OASIS standard in 2009 and a new ISO/IEC version some months later.[12] However currently there is no final draft of ODF v1.2 yet.

Application support

Software

Main article: OpenDocument software

The OpenDocument format is used in free software and in proprietary software. This includes office suites (both traditional 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:

Originally most implementations used the ODF 1.0/1.1 versions of the format. Some newer office suites like OpenOffice.org 3.x base their default format on drafts of ODF 1.2.

For spreadsheet formulas most implementations use dialects of the proprietary OpenOffice.org 1.x/2.x spreadsheet formula format. Newer implementations like OpenOffice.org 3.x Calc use the draft OpenFormula specification. OpenFormula is expected to be included in ODF 1.2.

The OpenDocument Fellowship[22] maintains a list of software and services that support the OpenDocument format. The list also provides information on the status of support for the format.[23]

Third parties have announced development of conversion software (including plugins and filters) to support OpenDocument on Microsoft's products.[24][25] Currently there are nine packages of conversion software.[23]

Microsoft Office 2007 SP2 supports the OpenDocument format. The current implementation faces criticism for not supporting encrypted documents and formula format in the same way as other OpenDocument-compatible software, as well as for stripping out formulas in imported spreadsheets created by other OpenDocument-compatible software. [20] [26] Critics say that with this conflict of standards Microsoft actually managed to reduce interoperability between office productivity software.[26][27][28] The company had previously reportedly stated that "where ODF 1.1 is ambiguous or incomplete, the Office implementation can be guided by current practice in OpenOffice.org, mainly, and other implementations including KOffice and AbiWord. Peter Amstein and the Microsoft Office team are reluctant to make liberal use of extension mechanisms, even though provided in ODF 1.1. They want to avoid all appearance of an embrace-extend attempt." [29] However, according to the ODF Alliance, "ODF spreadsheets created in Excel 2007 SP2 do not in fact conform to ODF 1.1 because Excel 2007 incorrectly encodes formulas with cell addresses. Section 8.3.1 of ODF 1.1 says that addresses in formulas "start with a "[" and end with a "]"." In Excel 2007 cell addresses were not enclosed with the necessary square brackets, which could be easily corrected." [20]

Before SP2, Microsoft had sponsored the creation of the Open XML translator[30] project to allow the conversion of documents between Office Open XML and OpenDocument. As a result of this project, Microsoft financed the ODF add-in for Word project on SourceForge. This project is an effort by several of Microsoft's partners to create a plugin for Microsoft Office that will be freely available under a BSD license. The project released version 1.0 for Microsoft Word of this software in January 2007 followed by versions for Microsoft Excel and Microsoft PowerPoint in December of the same year. Sun Microsystems has created the competing OpenDocument plugin for Microsoft Office 2007 (Service Pack 1 or higher), 2000, XP, and 2003 that supports Word, Excel, and Powerpoint documents.[31] The ODF Alliance has claimed that third-party plug-ins “provide better support for ODF than the recently released Microsoft Office 2007 SP2”. [20]

Mac OS X 10.5 offers both a new TextEdit version and QuickLook feature supporting the OpenDocument Text format (albeit with some formatting loss).

Accessibility

Further information: [[:OpenDocument software - Accessibility]]

The specification of OpenDocument has undergone an extensive 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.

Licensing

The OpenDocument specification, as initially approved by OASIS, is available for free download and use.[32] The International (ISO/IEC) Standard is available from ISO as a freely available download.

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.[33] This Statement is not an assurance that an OpenDocument Implementation would not infringe patents or other intellectual property rights of any third party.[34] The covenant is limited to versions of the OpenDocument specification on which Sun has participated to the point of incurring an obligation. Sun's patent promise only applies to a future version of the format if Sun Microsystems still participates in development of that subsequent standard version.

A second contributor to ODF development, IBM which for instance has contributed Lotus spreadsheet documentation[35] 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.[36] IBM's ISP licensing for OpenDocument is limited to existing listed versions (currently v1.0 and v1.1) and do not to future versions, similar to Microsoft's Open Specification Promise on Office Open XML however a Microsoft lawyer has claimed a difference relating to the coverage of partial and imperfect implementations[37] IBM grants their patent licensing only to fully compliant implementations of OpenDocument.[36]

"Covered Implementations" are those specific portions of a product (…) that implement and comply with a Covered Specification AND are included in a fully compliant implementation of that Covered Specification

Obligated members of the OASIS ODF TC have agreed to make certain licences available to implementors under the OASIS RF with Limited Terms IPR policy.

Response

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

  • Information technology companies like Apple, Adobe, Google, IBM, Intel, Microsoft, Nokia, Novell, Sun Microsystems as well as other companies who may on may not be working inside the OASIS OpenDocument Adoption Technical Committee.
  • Over 600 companies and organizations promote OpenDocument format through The OpenDocument Format Alliance. [38]
  • NATO with its 26 members uses ODF as a mandatory standard for all members.
  • The OpenOffice.org Suite and the KOffice Suite promote the OpenDocument Format, as it is used as their default file format.
  • The OpenDocument Fellowship was founded to support and promote OpenDocument.
  • In December 2007, the Wikimedia Foundation announced that by mid 2008 MediaWiki, which powers Wikipedia and a number of other Internet wiki-based sites, will provide OpenDocument export of wiki content.[39]
  • In November 2008, DocuVerse was created. It is a system for unified access to all Internet resources, based on ODF.

On November 4, 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, November 10, 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.

Criticism

Various criticisms have been levelled at the approved ODF standard.

  • Use of MathML for mathematical typesetting in the ODF specification. MathML[40] is a W3C recommendation for the "inclusion of mathematical expressions in Web pages" and "machine to machine communication" that has been around since about 1999. However, most mathematicians continue to use the much older TeX format as their main method for typesetting complex mathematical formulae. TeX is not an ISO standard, but is fully documented and is the de facto standard for typesetting mathematical expressions. There exists a converter from (La)TeX to ODT, including mathematical formulas.[41] OpenDocument is also criticized for not using the ISO 12083:1994 standard for mathematical formulae, which is not used within MathML either. MathML has a few issues with displaying mathematical formulae well, compared to other methods like TeX.[42] A major downside of TeX is that Tex is a presentation-only markup: unlike MathML, it does not offer a semantic markup model. This means it is impossible for a computer algebra system to reliably understand the meaning of TeX markup. TeX is useful only for typesetting.
  • OASIS ODF 1.0, OASIS ODF 1.1 and ISO/IEC ODF do not define a definite spreadsheet formula language, syntax or function libraries.[43] This means that standard conforming files may not necessarily be compatible. OASIS is working on creating a standard formula language (OpenFormula) for OpenDocument v1.2.
  • The OpenDocument ISO specification does not require that an application supports tables in presentations.[44] OpenDocument 1.1 allows tables to appear inside a draw:text-box element, which can appear inside draw:frame in a presentation.
  • 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.[45]
  • Even though OpenOffice.org allows digital signatures and stores them in ODF files according to XML-DSig, the OpenDocument Format 1.0-1.1 itself has no reference to the digital signature. Digital signature is application-specific feature in the OpenDocument v1.1 standard. However, OpenDocument v1.2 will incorporate XML-DSig in the same fashion as in OpenOffice.org. Thus OpenDocument v1.2 will have interoperable digital signatures with KOffice 2.0.[46]
  • The OpenDocument Format 1.0-1.1 specifications refer to 'zip' files but do not reference a standard which describes the zip file format. However, a specification (as opposed to a "standard") for the Zip format was distributed with PKZIP in the file APPNOTE.TXT and this continues to be maintained.[47]
  • ODF format has limited support for tracking changes [48]
  • The OpenDocument Foundation, Inc. participated in developing ODF within the OASIS TC and in developing the closed‐source daVinci plug-in for Microsoft Office. Before closing, the Foundation shifted its attention from supporting OpenDocument to supporting the W3C Compound Document Format (CDF). The reason stated was: “it is important to recognize that ODF does not adequately respect existing standards and does not address the market's requirements for a single Universal Document Format with which any and all applications can work on an equal basis”.[49]

Worldwide adoption

Main article: OpenDocument adoption

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. OpenDocument is intended to be an alternative to proprietary formats, including the commonly used DOC, XLS, and PPT formats used by Microsoft Office and other applications.

Since July 2008, NATO has added ISO/IEC 26300:2006 (ODF 1.0) to its list of mandatory standards for all members.[50]

National level

Belgium – 2007 [51][52][53][54][55][56]

Government agencies are required to:

  • Be able to access documents in ODF format by September 2007 (completed 9 months early in December 2006)
  • Use ODF for intra- and inter agency exchange of word processing documents, slideshow-style presentations, and spreadsheets by September 2008 (completed in December 2007)

Government agencies are permitted to:

  • Use other formats when creating and distributing documents internally

Brazil – 2006, 2008 [57]

Under e-PING Standards of Interoperability for Electronic Government v 4.0 (16 Dec 2008), ODF was upgraded from “recommended” under v 2.0 (17 Dec 2006) to “adopted”, meaning ODF compliance is now mandatory . Government agencies are required to incorporate “adopted” file formats like ODF into new information systems and upgrades to existing systems.

Croatia – 2007 [58]

Government agencies are required to:

  • Make each government form posted on a public Web site “accessible in a way that makes it legible in accessible freeware applications”
  • Options for meeting this requirement:
    • ODF
    • PDF
    • HTML

Denmark – 2007 [59]

Government agencies are required to:

  • Accept ODF and OOXML “data-processing documents” created by the public, businesses, and other governmental units

Government entities are permitted to:

  • Refrain from implementing the new OOXML and ODF standard if doing so would incur “additional costs or inconveniences” or raise “IT security concerns”

France – 2006[60][61][62][63]

Government agencies are required to:

  • Accept documents submitted in ODF format
  • Use PDF/A to preserve text documents

Government agencies are encouraged to:

  • Install OpenOffice.org (an open-source, ODF-based productivity suite)
  • Use ODF to create text documents, spreadsheets, and slideshow-style presentations

Government agencies are prohibited from:

  • Migrating to any productivity suite formats other than ODF

Germany – 2008[64]

Federal agencies will be able to receive, read, send and edit ODF documents beginning no later than 2010.

Under Germany's Standards and Architectures for eGovernment Applications 4.0 (SAGA 4.0), ODF recommended for editable text documents, a multi-stakeholder initiative that recommends and mandates standards to be used by the German federal government.

Italy – 2007

The Italian standardization organization UNI adopted ISO/IEC 26300 (ODF 1.0) on January 26, 2007.[65]

Japan – 2007, 2008[66]

Government ministries and agencies are required to:

  • Solicit bids from software vendors whose products support internationally-recognized open standards

Open formats:

  • Are to be preferred, and
  • Must be used to promote exchange of information between ministries

Japan's Diet passed an open standards software incentive as part of its omnibus Special Taxation Measures law:

  • Provides tax reductions for companies which buy open-standard based software
  • Went into effect April 2008 and expires in March 2011.

Malaysia – 2008[67][68]

Roadmap announced for:

  • Implementing ODF in Malaysia's public sector

Malaysian Administrative Modernization and Management Planning Unit (MAMPU) adopting ODF for all new documents created from April 1, 2008 onwards.

Netherlands – 2007[69][70]

Government agencies are required to:

  • Migrate new systems to Open Standards and Open Source
  • "Support ODF alongside existing file formats for reading, writing and exchange of documents"
  • Create open source implementation strategies;
  • Share with each other knowledge gained from agency pilots, migrations, and test cases;
  • Work collaboratively with stakeholders on openness plans.

ODF-based procurement now mandatory. For government bodies in the public and semi-public sectors:

  • Instructions published 24 Nov 2008 making open-standards based procurement the default for public purchases of IT worth more than 50,000 euro
  • Use of open standards such as ODF – official listed as one of the approved open standards - is now mandatory ("comply or explain” why not).

Norway – 2007[71]

Government agencies are required to:

  • Make government documents posted on the Web accessible to the public in three (3) mandatory formats:
    • HTML (presentation)
    • PDF (presentation)
    • ODF (editable)
  • Develop ability to RECEIVE documents from the public in these formats.

Government agencies are permitted to:

  • Use other formats, but only if they also produce the documents in PDF or ODF format.

Russia – 2007[72]

Government-wide action plan envisions:

  • Legislative requirements to mandate the procurement of software based on how well it adheres to widely-used standards.
  • Support of ODF in e-gov framework

South Africa – 2007[73]

Government agencies are required to:

  • Comply with MIOS standards ("Minimum Interoperability Standards (MIOS) for Information Systems in Government")
  • Migrate new systems and major upgrades to MIOS standards
  • Make their IS systems Internet-centered, with access to public services and documents preferably via web browser
  • Consider open source based solutions before proprietary ones
  • Use ONLY the following formats:
    • For working office suite documents (word-processing, spreadsheet, presentation): ASCII, CSV, or ODF
    • For office suite documents provided in presentation view: XHTML or PDF
  • Work collaboratively with stakeholders on openness plans

Switzerland – 2007[74]

Government agencies are required to:

  • Use the following formats when exchanging documents with citizens or other agencies:
    • PDF/A (“urgently recommended”)
    • PDF/X (“recommended”)
    • ODF (“recommended under observation”)
    • OOXML (“recommended under observation”)

Uruguay – 2008[75]

AGESIC (Agency for the Development of Government Electronic Management and Information and Knowledge Society), which is responsible for proposing IT standards for the federal government, has officially recommended the use of:

  • ODF for editable documents
  • PDF for documents in final, published form

Venezuela – 2009[76]

All organizations of the Federal Government of Venezuela must:

  • Use ODF 1.0 (ISO/IEC 26300) for editable documents
  • Use PDF for non-editable documents

United Kingdom – 2008[77]

Under the “Open Source, Open Standards and Re–Use: Government Action Plan” the UK government will specify requirements by reference to open standards and require compliance with open standards in solutions where feasible. The government indicated it will support the use of ODF 1.0 (ISO/IEC 26300:2006).

Regional, province, and state levels

Andalusia (Spain) – 2007 [78]

Government agencies are required to:

  • Use open standards to interchange documents with citizens, non-governmental organizations, and other government bodies”
    • ODF
    • PDF
    • PDF/A
    • HTML
    • XHTML
    • ASCII
    • UNICODE
    • ASCII (open)
    • RTF (acceptable)

Assam (India) – 2007 [79][80]

Government agencies are required to:

  • Use ODF
  • Transition to open-source operating systems

Extremadura (Spain) – 2007 [81][82]

Government agencies are required to:

  • Create and save in ODF (manipulable) or PDF/A (static) format all documents that will be exchanged with other government entities or with citizens.

Hong Kong (China) – 2007 [83]

Government agencies are required to:

  • Exchange text documents in ODF, HTML, RTF or a mutually agreed-upon legacy format
  • Exchange spreadsheets in ODF, or a mutually agreed-upon legacy format
  • Exchange slideshow-type presentations in ODF, or a mutually-agreed-upon legacy format

Kerala (India) – 2007 [84]

Open standards to be followed in e-governance projects to avoid total dependence on select vendors. Specific standards cited in policy include:

  • ODF
  • Unicode

Massachusetts (United States) – 2007 [85]

Government agencies are required to:

  • Create and save “official records” in one of six (6) “open” or “acceptable” formats:
    • ODF (open)
    • OOXML (open)
    • HTML (open)
    • ASCII (open)
    • RTF (acceptable)
    • PDF (acceptable)

Misiones (Argentina) – 2007 [86]

Government agencies are required to:

  • Create and save in ODF (manipulable) or PDF/A (static) format all documents that will be exchanged with other government entities or with citizens

Paraná (Brazil) – 2007 [87][88]

Government agencies and state-owned companies are required to:

  • Use ODF for the creation, storage, and display of all electronic documents

See also

References

  1. ^ a b c d e Huw Alexander Ogilvie. "Filetypes". Retrieved 2008-06-20.
  2. ^ "OASIS Open Document Format for Office Applications (OpenDocument) TC". Organization for the Advancement of Structured Information Standards.
  3. ^ "ISO/IEC 26300:2006 Information technology -- Open Document Format for Office Applications (OpenDocument) v1.0". International Organization for Standardization.
  4. ^ http://www.ua.es/en/rua/formatos.html
  5. ^ sample documents in OpenDocument Format
  6. ^ "OpenDocument TC's publicly-visible membership roster". Retrieved 2007-11-03.
  7. ^ ISO/IEC SC34 Secretariat (2006-06-13). "Summary of Voting on DIS ISO/IEC 26300 - Open Document Format for Office Applications (OpenDocument) v1.0". ISO/IEC JTC 1/SC 34 Document Repository. Retrieved 2006-08-24.{{cite web}}: CS1 maint: numeric names: authors list (link)
  8. ^ "ISO and IEC approve OpenDocument OASIS standard for data interoperability of office applications". ISO Press Releases. ISO. 2006-05-08. Retrieved 2006-08-24.
  9. ^ "OpenDocument 1.1 Specifications". OASIS. 2006. Retrieved 2006-10-31.
  10. ^ "Approval of OpenDocument v1.1 as OASIS Standard". OASIS. Retrieved 2007-02-06.
  11. ^ "Members Approve OpenDocument Version 1.1 as OASIS Standard". OASIS. Retrieved 2007-02-15.
  12. ^ Weir, Rob (2006-05-04). "TC coordination call draft minutes 2008-02-11". Oasis' list archives. OASIS. Retrieved 2008-02-19.
  13. ^ "Adobe Buzzword online word processor from Acrobat.com". Labs.adobe.com. Retrieved 2009-05-19.
  14. ^ http://www.abisource.com/wiki/OpenDocument
  15. ^ Abiword 2.4.2 Release Notes. Retrieved 2009-03-03
  16. ^ http://www.google.com/support/forum/p/Google+Docs/thread?tid=014457aa446500fa&hl=en
  17. ^ http://blogs.msdn.com/dmahugh/archive/2009/05/09/1-2-1.aspx
  18. ^ http://symphony.lotus.com/software/lotus/symphony/help.nsf/ReleaseNotes
  19. ^ http://koffice.org/filters/1.6/
  20. ^ a b c d "Fact-sheet Microsoft ODF support" (PDF). odfalliance. Retrieved 2009-05-24. Cite error: The named reference "sp2-fact-sheet" was defined multiple times with different content (see the help page).
  21. ^ "Corel WordPerfect Office X4 - Standard Edition - Compatible". Retrieved 2008-05-03.
  22. ^ "OpenDocument Fellowship". OpenDocument Fellowship. Retrieved 2007-07-27.
  23. ^ a b "Application support for the OpenDocument format". OpenDocument Fellowship. Retrieved 2007-07-27.
  24. ^ "OpenDocument Foundation to MA: We Have a Plugin". Groklaw. 2006-05-04. Retrieved 2006-08-23.
  25. ^ "Microsoft Office to get a dose of OpenDocument". CNet. 2006-05-05. Retrieved 2006-12-06.
  26. ^ a b "In Office SP2, Microsoft manages to reduce interoperability". zdnet. 2006-05-19. Retrieved 2009-05-21. Yet Microsoft Office SP2 claims to have a fully compliant version of ODF, and that's probably true, as defined by the specification. It's just completely useless at interoperating with other vendors' products. This is not interoperability, it's an attack on the very concept. {{cite news}}: Check date values in: |date= (help)
  27. ^ "Microsoft's ODF Support Falls Short". Open Document Alliance. ODF Alliance. 2009-05-19. Retrieved 2009-05-22.
  28. ^ Weir, Rob (2009-05-03). "Update on ODF Spreadsheet Interoperability". Retrieved 2009-05-22.
  29. ^ http://orcmid.com/blog/2008/08/microsoft-odf-interoperability-workshop.asp
  30. ^ "Microsoft Expands Document Interoperability". Microsoft. 2006-07-05. Retrieved 2007-01-28.
  31. ^ "Sun's OpenDocument filter for MS Office is finished". Heise Online. 2006-07-04. Retrieved 2007-07-06.
  32. ^ OASIS Open Document Format for Office Applications (OpenDocument) TC
  33. ^ Sun OpenDocument Patent Statement
  34. ^ Sun Microsystems, Inc. "Sun OpenDocument Patent Statement". OASIS Open Document Format for Office Applications (OpenDocument) TC. OASIS foundation.
  35. ^ http://lists.oasis-open.org/archives/office/200607/msg00076.html
  36. ^ a b Interoperability Specifications Pledge
  37. ^ Richard Wilder (Associate General Counsel for Intellectual Property Policy at Microsoft) (2008-07-25). "The OSP and You". Port 25 (Microsoft's open source portal). Retrieved 2008-07-25. {{cite web}}: |author= has generic name (help)
  38. ^ "ODF Alliance members". ODF Alliance. Retrieved 2009-05-24.
  39. ^ "Wikis Go Printable". Wikimedia Foundation. 13 December 2007. Retrieved 2007-12-31. {{cite web}}: Check date values in: |date= (help)
  40. ^ "MathML W3C standard". W3.
  41. ^ TeX4ht: LaTeX and TeX for Hypertext
  42. ^ Ian Hutchinson (2006). "Web Publishing Mathematics With HTML and MathML from TeX" (PDF). Retrieved 2007-12-16. {{cite web}}: Unknown parameter |month= ignored (help)
  43. ^ Marco Fioretti. "OpenDocument office suites lack formula compatibility". Retrieved 2008-05-11.
  44. ^ Brian Jones. "Quick question for ODF experts". Retrieved 2007-01-24.
  45. ^ Marco Fioretti. "Macros an obstacle to office suite compatibility". Retrieved 2008-05-11.
  46. ^ "Initial proposal for digital signatures in ODF". Michael Brauer - Sun Germany. 2007-02-16. Retrieved 2007-03-29.
  47. ^ APPNOTE.TXT - .ZIP File Format Specification
  48. ^ http://blogs.msdn.com/dmahugh/archive/2009/05/13/tracked-changes.aspx
  49. ^ Sam Hiser (2007-10-16). "CDF: Disrupting the Disruption". Retrieved 2007-10-25.
  50. ^ 3.4. NNEC Core Enterprise Services
  51. ^ "Open Standards: Belgium's Federal Council of Ministers Approves ODF (Open Document Format)". Ministry of Employment and Computerization. 2006-06-23. Retrieved 2009-04-23.
  52. ^ "Belgian Government Chooses Open Document". CNET News. 2006-06-23. Retrieved 2009-04-23.
  53. ^ "Belgian Government Adopts Open Document". Techworld. 2006-06-29. Retrieved 2009-04-23.
  54. ^ "File Types and Document Formats". Belgian Government Interoperability Framework. 2007-09-18. Retrieved 2009-04-23.
  55. ^ "Open Standards and ODF in Belgium" (PDF). Presentation of Chief Information Officer, FEDICT, at the 1st International ODF User Workshop. 2007-10-29. Retrieved 2009-04-23.
  56. ^ "Implementing ODF In Belgium: No Country for Old Men" (PDF). Presentation of Chief Information Officer, FEDICT, at the 2nd International ODF User Workshop. 2008-10-09. Retrieved 2009-04-23.
  57. ^ "e-PING Standards of Interoperability for Electronic Government". Brazilian Government Executive Committee on Electronic Government. 2008-12-16. Retrieved 2009-04-23.
  58. ^ "Interoperability". Central State Administrative Office for e-Croatia. Retrieved 2009-04-23.
  59. ^ "Agreement on the Use of Open Standards for Software in the Public Sector". Ministry of Science Technology and Information. 2007-10-01.
  60. ^ "Référentiel Général d'Interopéabilité Volet Technique version 0.90" (PDF). General Directorate for the State’s Modernization. 2006-11-14. Retrieved 2009-04-23.
  61. ^ "Les Postes Micro-informatiques des Députés Seront Dotés de Logiciels Libres à Compter de la Prochaine Legislature". National Assembly, France. 2006-11-22. {{cite news}}: line feed character in |title= at position 69 (help)
  62. ^ "Mise á Disposition d'un Kit d'Installation Open Office.Org". General Directorate for the State’s Modernization. 2006-06-20. Retrieved 2009-04-23.
  63. ^ "Rationalisations des Moyens Mutualisations des Méthodes". General Directorate for the State’s Modernization. 2007-08-13. Retrieved 2009-04-23.
  64. ^ "Standards und Architekturen für E-Government-Anwendungen – SAGA 4.0" (PDF). General Directorate for the State’s Modernization. 2008-03-01. Retrieved 2009-04-23.
  65. ^ Documenti elettronici: pubblicata la norma UNI CEI ISO/IEC 26300 sul formato OpenDocument
  66. ^ "Announcement of Japan's Interoperability Framework". Ministry of Economy, Trade and Industry. 2007-06-27. Retrieved 2009-04-23.
  67. ^ Lynn, Tan (2007-08-13). "Malaysia formally embraces Open Document Format". Zdnet Asia. Retrieved 2009-04-23.
  68. ^ "OpenOffice.org Migration in the Malaysian Public Sector" (PDF). Tan King Ing, Malaysian Administrative Modernization and Management Planning Unit (MAMPU), Malaysia, speaking at the 2nd Int'l ODF User Workshop. 2008-10-09. Retrieved 2009-04-23.
  69. ^ "The Netherlands in Open Connection: An Action Plan for the Use of Open Standards and Open Source Software in the Public and Semi-public" (PDF). Netherlands Ministry of Economic Affairs. 2007-11-01. Retrieved 2009-04-23.
  70. ^ "NL: Dutch government instructs itself to use open standards". Open Source Observatory. 2008-11-26. Retrieved 2009-04-23.
  71. ^ "Reference Catalogue of IT Standards in the Public Sector". Ministry of Government Administration and Reform. 2007-12-21. Retrieved 2009-04-23.
  72. ^ "Action Plan on Open Source Software Development and Usage in the Russian Government Program".
  73. ^ "Minimum Interoperability Standards (MIOS) for Information Systems in Government (v.4.1)" (PDF). South Africa Department of Public Service and Administration. 2007-10-01. Retrieved 2009-04-23. {{cite news}}: line feed character in |publisher= at position 46 (help)
  74. ^ "SAGA.ch, standard no. eCH-0014, version 4.01". eCH. 2007-07-24. Retrieved 2009-04-23.
  75. ^ "Estándares de formatos de archivo en ofimática, Recomendación para adopción en el Estado" (PDF). Agencia para el Desarrollo del Gobierno de Gestión Electrónica y la Sociedad de la Información y del Conocimiento, AGESIC. 2008-06-24. Retrieved 2009-04-23.
  76. ^ "Gaceta Oficial de la República Bolivariana de Venezuela N° 39.109". Tribunal Supremo de Justícia. 2009-01-29. Retrieved 2009-04-23.
  77. ^ "Open Source, Open Standards and Re–Use: Government Action Plan". Chief Information Officer Council. 2009-03-27. Retrieved 2009-04-23.
  78. ^ "Junta de Andalucía's Digital Interoperability Framework" (PDF). Junta de Andalucía, Council of Innovation, Science, and Business. 2007-10-01. Retrieved 2009-04-23.
  79. ^ "Achieving Impeccable Openness in Translation with Open Document Format" (PDF). Assam Electronics Development Corporation. 2007-10-01. Retrieved 2009-04-23.
  80. ^ "German Foreign Office Comes Out in Favor of Open Document Format" (PDF). Heise Online. 2007-10-30. Retrieved 2009-04-23.
  81. ^ "Extremadura completely switches to Linux and OpenDocument". Heise Online. 2007-08-01. Retrieved 2009-04-23.
  82. ^ "Standard Open Formats and Libre Software in the Extremadura Public Administration" (PDF). Upgrade. 2006-12-01. Retrieved 2009-04-23.
  83. ^ "The HKSARG Interoperability Framework version 6.0" (PDF). Government Chief Information Officer. 2007-12-01. Retrieved 2009-04-23.
  84. ^ "Information Technology Policy: Towards an inclusive knowledge society" (PDF). Department of Information Technology - Government of Kerala. 2007-01-01. Retrieved 2009-04-23.
  85. ^ "Enterprise Technical Reference Manual—Version4.0—Domain: Information". Information Technology Department. 2007-08-01. Retrieved 2009-04-23.
  86. ^ "Resolución DGCC No. 175/06—Boletín Oficial No. 11928". Computer Center of the Province of Misiones. 2006-12-21. Retrieved 2009-04-23.
  87. ^ "Diáro Oficial Paraná," digital edition no. 7621". Imprensa Oficial do Estado do Paraná. 2007-12-18. Retrieved 2009-04-23.
  88. ^ "Lei No. 15742". Casa Civil do Governo do Estado do Paraná. 2007-12-18. Retrieved 2009-04-23.
  • OpenDocument Fellowship Volunteer organization with members around the world to promote the adoption, use and development of the OpenDocument format.
  • OpenDocument Format Alliance The alliance works globally to educate policymakers, IT administrators and the public on the benefits and opportunities of the OpenDocument Format, to help ensure that government information, records and documents are accessible across platforms and applications, even as technologies change today and in the future.
  • OpenDocument XML.org The official community gathering place and information resource for the OpenDocument OASIS Standard (ISO/IEC 26300).
  • OASIS OpenDocument Technical Committee coordinates the OpenDocument development and is the official source for specifications, schemas, etc.
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=OpenDocument&oldid=294293792"