Opendocument 问与答 (FAQ)

翻译 2006年06月09日 17:38:00
        What is the Open Document Format for Office Applications (OpenDocument) OASIS Standard?
  1. The OpenDocument OASIS Standard is an XML-based file format suitable for office applications. It covers the features required by text, spreadsheets, charts, and graphical documents.

  2. Who benefits from this work and how?

    A vendor- and application-independent open document format for office applications protects content--whether it is an 800-page airplane specification or a legal contract--from being locked into an application- or vendor-specific file format. Additionally, it lets application users participate in the benefits of XML file formats without having to change their habits and without requiring additional knowledge or education.

  3. There is a TC 45 with a similar charter existing at ECMA. Is this a competitive effort?

    No. Although the OASIS OpenDocument Technical Committee and the ECMA TC 45 both define standardized file formats for office applications, there are differences in the charters of both groups.

    The purpose of ECMA TC45 is "to produce a formal standard for office productivity applications that is fully compatible with the Office Open XML Formats, submitted by Microsoft".

    The purpose of the OASIS OpenDocument Committee is to "create an open, XML-based file format specification for office applications." This means, the file format is not specialized for a certain application, but it provides a formal standard for arbitrary office applications. This includes Microsoft Office, but is not limited to it.

  4. How large is the OASIS OpenDocument Technical Committee?

    The OASIS OpenDocument TC has 17 founding members (full list). An up-to-date list of TC members is available here.

  5. Isn't OpenDocument only the file format of the application that has been standardized?

    OpenDocument has been developed as an application-independent format by a vendor-neutral OASIS Technical Committee with the participation of multiple office application vendors. The basis for the OASIS OpenDocument TC's work indeed was the XML file format, but even the XML file format was developed as an application-independent file format that is not usable by the application only.

    The XML specification went through a one-year review phase within OASIS. This review resulted in more than 100 changes to the schema, and additional specification and editorial work. After its approval by the Committee members, OpenDocument also went through a one-month public review phase, and a final approval process by the full OASIS membership, which represents over 600 organizations.

  6. Did the OASIS OpenDocument TC take the requirements of Microsoft Office users into account?

    Absolutely. Several companies that are members in the OASIS OpenDocument TC are very much committed to delivering office products that are highly interoperable with Microsoft Office, especially on the file format level. Some of these companies deliver products that have included MS office document filters for more than a decade. The membership of these companies in the OASIS OpenDocument Technical Committee actually ensures that the requirements of MS Office users are considered within OpenDocument.

  7. Is OpenDocument backward compatible with Microsoft Office binary documents?

    No. Backward compatibility with binary documents is technical impossible for an XML file format. However, applications may support legacy binary format as well as OpenDocument, and in this way may provide backward compatibility with binary formats for office application users.

  8. Does OpenDocument support "custom schemas"?

    There are several usages of the term "custom schema". The term "custom schema support" frequently is used to describe the possibility to interleave an office application schema with XML tags from some other schema. Because this is a feature of XML and XML Namespaces in general, this is supported by OpenDocument. But it is important to distinguish between the OpenDocument format and applications that implement it. No applications at this point exploit this feature, but this is inherently supported by the OpenDocument OASIS Standard.

    Another definition of "custom schema" support is the possibility to include an instance of a non-office-schema into an office document. This feature is provided by OpenDocument, due to its partial inclusion of the W3C XForms Recommendation.

  9. Was performance listed as a requirement for the OpenDocument OASIS Standard?

    Although performance is not explicitly listed as a requirement in the OASIS OpenDocument TC charter, the ability to provide performance implementations of a file format seems to be self-evident for an open standard.

    In comformant applications, there are no performance issues known that have their root cause in the OpenDocument OASIS Standard. If any such issues would be brought to the attention of the TC, the Committee members would work on a resolution.

  10. Has OpenDocument been tested?

    OpenDocument has been well tested. The OASIS Standard is already implemented by several office applications, and some of these applications use it as native file format. Furthermore, OpenDocument is based on the XML file format, which has been the default file format of the application since 2001. This includes the word processor, the spreadsheet, and the presentation applications of

  11. Who owns OpenDocument?

    The OpenDocument format is owned by OASIS, a non-profit consortium dedicated to the open development of public XML standards. The standard is maintained by the OASIS OpenDocument Technical Committee, which is made up of XML, document management, and office application experts.

  12. Is the OpenDocument effort still open?

    Yes. The OASIS OpenDocument Technical Committee will extend OpenDocument 1.0 to encompass additional areas of applications or users, and also will adapt the specification to recent developments in office applications. The team has also formed the OASIS OpenDocument Accessibility Subcommittee , which gathers feedback from the disability community and from developers and users of accessible applications that implement OpenDocument. All those interested in participating in the further development of OpenDocument through the Technical Committee and/or Subcommittee are encouraged to join this effort. Non-OASIS members are welcome to join the consortium at any time.

  13. What is the current state of OpenDocument?

    OpenDocument version 1.0 is an approved OASIS Standard. This represents the highest level of ratification within the consortium.

    OASIS has submitted the OpenDocument Format to the ISO/IEC JTC1 (International Organization for Standardization International Electrotechnical Commission's Joint Technical Committee) for further approval as a de jure standard.

  14. Where did OpenDocument originate?

    OpenDocument has its roots in the XML file format. In December 2003, Arbortext, Boeing, Corel, CSW Informatics, Drake Certivo, National Archive of Australia, New York State Office of the Attorney General, Society of Biblical Literature, Sony, Stellent and Sun Microsystems founded the OASIS Open Office XML Format Technical Committee to develop a standardized XML-based file format for office applications. The basis for the TC's work was the XML file format that had proven its value in real life. The first OpenDocument Committee Draft was approved in March 2003; a second was approved in December 2004. In January 2005, the group was renamed the "OASIS Open Document Format for Office Applications (OpenDocument) Technical Committee" to emphasize that the resulting specification is not only suitable for, but for arbitrary office applications. A third Committee Draft was approved in March 2005. OpenDocument was approved as an OASIS Standard in May 2005.

  15. How much will it cost to use OpenDocument?

    OpenDocument is royalty-free. It can be used without charge by anyone.

  16. Where do I find the OpenDocument specification and schemas?

    The OpenDocument v1.0 specification is available in PDF format at

    and in XML format at

    The OpenDocument v1.0 Relax-NG schemas are available here:

    1. OpenDocument v1.0 Relax-NG Schema (extracted from chapter 1 to 16 of the specification):

    2. OpenDocument v1.0 Manifest Relax-NG Schema (extracted from chapter 17 of the specification):

    3. OpenDocument v1.0 Strict Relax-NG Schema (extracted from appendix A of the specification):

  17. How does this work compare to existing standards at other standards organizations?

    There are some standards that cover single features of office applications, like SVG for graphic content or HTML and XSL-FO for text content, but none of these standards covers all features of office applications. The OpenDocument OASIS Standard covers the features required by text, spreadsheets, charts, and graphical documents, but also 'borrow' from similar, existing standards wherever possible and permitted.

  18. How does this work compare to other office applications schemas?

    • OpenDocument was developed in a completely open, publicly visible, vendor-neutral, royalty-free standards process that allows input from the entire user community

    • OpenDocument is one schema for text, spreadsheets, charts, and graphical documents. There are no distinct schemas for the different kind of office applications.

    • OpenDocument is highly interoperable by making use of existing standards like HTML , SVG , XSL , SMIL , XLink , XForms , MathML or Dublin Core wherever possible.

    • OpenDocument has a package concept and can be used as default file format for office applications without disadvantages in file size or integrity.

  19. What kind of applications are covered by the specification?

    The OpenDocument Format v1.0 is suitable for text, spreadsheets, charts, and graphical documents. Later versions of the specification will encompass additional areas of applications and users.

在 Power BI 问答中提问的提示

  “问答”识别的单词和术语 此关键字的列表并不详尽。 查看 Power BI 是否识别某个关键字的最佳方法是通过在问题框中键入此关键字来进行试验。如果字词或术语灰显,则 Power...
  • Xiao_Li_Fei_Dao
  • Xiao_Li_Fei_Dao
  • 2018年01月04日 15:03
  • 55


遇到的看见的,长期更新~~~ 1.linux乱码问题     [root@vps software]# vi  /etc/sysconfig/i18n     LANG='zh_...
  • u010718976
  • u010718976
  • 2017年01月10日 11:00
  • 184

EGit /用户指南

EGit /用户指南 EGit 内容 1 开始 1.1 概述1.2 基本教程:项目添加到版本控制中 1.2.1 " 配置 1...
  • jibaole
  • jibaole
  • 2016年01月23日 19:33
  • 2052


数据库学习FAQ 简述数据、数据库、数据库管理系统、数据库系统的含义及其联系?数据:数据是信息的符号记录。数据是数据库处理和研究的对象 数据库:长期存储在计算机内,有组织、可共享的数据集合。数据按一定...
  • pupilxmk
  • pupilxmk
  • 2016年05月25日 08:59
  • 471


本文目的:在linux里装Skyeye,用Skyeye模拟ARM7DTMI,运行uClinnux-2.4.x SkyEye可以做什么事情? 1. 通过SkyEye可以帮助促进嵌入式系统的学习,在不...
  • benjaminwan
  • benjaminwan
  • 2013年06月18日 18:15
  • 1474

Spark调研笔记第6篇 - Spark编程实战FAQ

本文主要记录我使用Spark以来遇到的一些典型问题及其解决办法,希望对遇到同样问题的同学们有所帮助。 1. Spark环境或配置相关 Q: Spark客户端配置文件spark-defaults.c...
  • slvher
  • slvher
  • 2015年06月10日 11:16
  • 1735


首先在故事板中拖入一个UIViewController,设计你的UI。我们以下面的例子为例: 在这个ViewController中,上半部分我们将设置为透明(通过代码设置),而下半部分是3个U...
  • kmyhy
  • kmyhy
  • 2015年11月02日 13:44
  • 1669

Linux 常用到的功能及命令-FAQ

如何查看某个进程启动多长时间了? ps -p pid -o etime= 具体参数参考 man 手册top命令 在top交互界面上,输入字母 E 可以调整总内存的显示单位,使用字...
  • It_way
  • It_way
  • 2016年06月18日 23:13
  • 237


  • qq_38125123
  • qq_38125123
  • 2017年04月21日 15:02
  • 266


Spring框架是一个JAVA框架,提供了开发JAVA应用程序时所需的全面的基础架构。Spring负责基础结构所以你可以把注意力放到程序实现上。            Spring 可以使你从“简单...
  • z1049186181
  • z1049186181
  • 2016年05月18日 19:06
  • 2950
您举报文章:Opendocument 问与答 (FAQ)