ODF 1.1 Interoperability Profile v1.0

Committee Draft 03

29 June 2010

Specification URIs:

This Version:

http://docs.oasis-open.org/oic/odf1.1i/v1.0/CD03/ODF1.1-InteropProfile-v1.0-cd03.odt (Authoritative)

http://docs.oasis-open.org/oic/odf1.1i/v1.0/CD03/ODF1.1-InteropProfile-v1.0-cd03.html

http://docs.oasis-open.org/oic/odf1.1i/v1.0/CD03/ODF1.1-InteropProfile-v1.0-cd03.pdf

Previous Version:

N/A

Latest Version:

http://docs.oasis-open.org/oic/odf1.1i/v1.0/ODF1.1-InteropProfile-v1.0.odt

http://docs.oasis-open.org/oic/odf1.1i/v1.0/ODF1.1-InteropProfile-v1.0.html

http://docs.oasis-open.org/oic/odf1.1i/v1.0/ODF1.1-InteropProfile-v1.0.pdf

Technical Committee:

OASIS Open Document Format Interoperability and Conformance TC

Chair(s):

Bart Hanssens, Fedict

Editor(s):

Bart Hanssens, Fedict

Related Work:

This specification is related to:

OASIS ODF v1.1

OASIS ODF v1.2 part 1 CD04

Declared XML Namespace(s):

N/A

Abstract:

This specifications describes an interoperability profile on top of ODF 1.1.

Status:

This document was  last revised or approved by the OASIS OIC TC on the above date. The level of approval is also listed above. Check the "Latest Version" or "Latest Approved Version" location noted above for possible later revisions of this document.

Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at http://www.oasis-open.org/committees/oic/.

For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (http://www.oasis-open.org/committees/oic/ipr.php).

The non-normative errata page for this specification is located at http://www.oasis-open.org/committees/oic/.

Notices

Copyright © OASIS® 2009-2010. All Rights Reserved.

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.

OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.

OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.

The names "OASIS", "ODF", "Open Document Format", "OIC TC", "ODF Interoperability and Conformance TC" are trademarks of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/who/trademark.php for above guidance.

 

Table of Contents

1 Introduction

1.1 Terminology

1.2 Normative References

1.3 Non-normative References

2 Interoperability Profile for ODF 1.1

2.1 Conformance and interoperability

2.2 Versions of the Interoperability Profile

2.3 Versions of Interoperability Profile and ODF specifications

2.4 Conformance clauses

3 Conformance

3.1 General clauses

3.2 Specific clauses

3.2.1 Document Processing and Conformance (Section 1.5)

3.2.2 MIME Types and File Name Extensions (Section 1.7)

3.2.3 Document Roots (Section 2.1)

3.2.4 Document Root Attributes – Version (Section 2.1.2)

3.2.5 Pre-Defined vs Custom Metadata (Section 2.2.1)

3.2.6 Pre-Defined Metadata Elements (Section 3.1)

3.2.7 Generator (Section 3.1.1)

3.2.8 Keywords (Section 3.1.5)

3.2.9 Initial Creator (Section 3.1.6)

3.2.10 Editing Duration (Section 3.1.17)

3.2.11 Change tracking (Section 4.6)

3.2.12 Table Cell – Formula (Section 8.1.3)

3.2.13 Objects - Object Data (Section 9.3.3)

3.2.14 Plot Area (Section 10.5)

3.2.15 Series (Section 10.9)

3.2.16 Control Implementation (Section 11.4.2)

3.2.17 Annotations (Section 12.1)

3.2.18 Creation Date and Time String (Section 12.1.3)

3.2.19 Line-Through Type (Section 15.4.6)

3.2.20 Line-Through Style (Section 15.4.7)

3.2.21 Encryption (Section 17.3)

3.2.22 MIME Type Stream (Section 17.4)

Appendix A. Acknowledgments

Appendix B. Non-Normative Text

Implementation specific defaults

Appendix C. Revision History

 

1 Introduction

ODF 1.1 is widely implemented, but there are areas where the specification is not clear or not complete. As a result of this ambiguity, interoperability issues arise when exchanging documents between different implementations.

ODF is also very flexible, leaving a great degree of freedom for implementing - or not implementing - certain features and using supplementary objects of various types. However, from an interoperability point of view, this flexibility calls for a common denominator. This document aims to clarify and formalize interpretations of the ODF 1.1 specification, by creating an Interoperability Profile.

This Interoperability Profile does not add new features to ODF 1.1 (although some implicit features may be clarified), nor does it remove existing conformance clauses. It does, however, add more conformance constraints.

 

1.1 Terminology

Within this specification, the key words "shall", "shall not", "should", "should not" and "may" are to be interpreted as described in Annex H of [ISO/IEC Directives] if they appear in bold letters.

Application in this context does not refer to a software product like an office suite. In this context, the broader term implementation is used instead of software product.

 

ODF Implementation: implementation using ODF as (a) storage format. This may be a general office suite or a specialist application and can be installed as part of a network service (like - but not limited to - a webbased editor) or as a stand-alone application on a computing device (like - but not limited to - a PC, netbook, PDA, cell phone...)

ODF Document (ODF-Doc): Conforming [ODF] document that may or may not conform to the Interoperability Profile outlined in this document

ODF 1.1 Interoperability Profile Conformant Document (ODF1.1i-Doc): Conforming [ODF 1.1] document that also conforms to the Interoperability Profile outlined in this document

ODF 1.1 Interoperability Profile Conformant Producer (ODF1.1i-Prod): ODF Implementation capable of producing ODF1.1i-Doc files and conforming to the Producer Conformance Clauses outlined in this specification.

ODF 1.1 Interoperability Profile Conformant Consumer (ODF1.1i-Cons): ODF Implementation capable of consuming ODF 1.1 files and conforming to the Consumer Conformance Clauses outlined in this specification.

ODF 1.1 Interoperability Profile Conformant Implementation (ODF1.1i-Impl): a ODF1.1i-Cons or ODF1.1i-Prod or a combination of both.

User: a human who or system that interacts with an ODF1.1i-Impl

 

1.2 Normative References

[ISO/IEC Directives] ISO/IEC Directives, Part 2 Rules for the structure and drafting of International Standards, International Organization for Standardization, 2004

[ODF 1.1] OASIS Standard, "OpenDocument Format for Office Applications (ODF) Version 1.1", February 2007. http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1-html/OpenDocument-v1.1.html

[ODF 1.2] OASIS Committee Draft 04, "OpenDocument Format for Office Applications (ODF) Version 1.2, Part 1: Introduction and OpenDocument Schema", December 2009. http://docs.oasis-open.org/office/v1.2/part1/cd04/OpenDocument-v1.2-part1-cd04.html

[OFF] OASIS Committee Draft 01, "OpenDocument Format for Office Applications (ODF) Version 1.2, Part 2: Recalculated Formula (OpenFormula) Format", March 2009. http://www.oasis-open.org/committees/download.php/36769/OpenDocument-v1.2-part2-cd01.zip

 

1.3 Non-normative References

N/A

 

2 Interoperability Profile for ODF 1.1  

2.1 Conformance and interoperability

Conformance and interoperability are two distinct (but related) topics.  It is assumed that increasing the  number of strict conformance clauses improves interoperability by reducing the number of interpretations.

Therefore, this ODF 1.1 Interoperability Profile does not replace or remove any of the existing conformance clauses listed in [ODF 1.1]

 

2.2 Versions of the Interoperability Profile

Note that this document starts out rather small, but is expected to be updated frequently. Using this approach, one does not have to wait until the next version of the ODF specification arrives (a process that can take several years) to clear out the details of implementing [ODF 1.1].

This also means that, when referring to the Interoperability Profile as a normative reference, one should always mention the version number and date of approval of the Interoperability Profile.

 

Example (non-normative):

OASIS Specification, "ODF 1.1 Interoperability Profile v1.23",  May 2010

 

2.3 Versions of Interoperability Profile and ODF specifications

Care shall be taken that new versions of this document do not contradict earlier versions of the Interoperability Profile and/or the [ODF 1.1] itself.

Whenever feasible, the Interoperability Profile shall make use of clarifications and/or additional conformance clauses within [ODF 1.2]. That is, if they can be applied to [ODF 1.1] without violating requirements of [ODF 1.1] or the Interoperability Profile.

 

2.4 Conformance clauses

The rest of this document consists of conformance clauses.

3 Conformance

3.1 General clauses

Conformance:

 

Conformance when using / converting ODF-Doc:

 

3.2 Specific clauses

The numbering (between parentheses) of the following specific clauses matches the numbering of the [ODF 1.1] specification.

3.2.1 Document Processing and Conformance (Section 1.5)

Conformance:

3.2.2 MIME Types and File Name Extensions (Section 1.7)

Conformance:

 

3.2.3 Document Roots (Section 2.1)

Conformance:

3.2.4 Document Root Attributes – Version (Section 2.1.2)

Conformance:

3.2.5 Pre-Defined vs Custom Metadata (Section 2.2.1)

Conformance:

3.2.6 Pre-Defined Metadata Elements (Section 3.1)

Conformance:

 

Conversion conformance (ODF-Doc to ODF1.1i-Doc):

3.2.7 Generator (Section 3.1.1)

Conformance:

 

Conversion conformance (ODF-Doc to ODF1.1i-Doc):

3.2.8 Keywords (Section 3.1.5)

Conformance:

3.2.9 Initial Creator (Section 3.1.6)

Conformance:

3.2.10 Editing Duration (Section 3.1.17)

Conformance:

3.2.11 Change tracking (Section 4.6)

Conformance:

 

3.2.12 Table Cell – Formula (Section 8.1.3)

Conformance:

 

Conversion conformance (ODF-Doc to ODF1.1i-Doc):

 

 

[

 

 Conformance once [OFF] is approved:

]

 

 

 

3.2.13 Objects - Object Data (Section 9.3.3)

Conformance:

 

Conversion conformance (ODF-Doc to ODF1.1i-Doc):

 

3.2.14 Plot Area (Section 10.5)

Conformance:

3.2.15 Series (Section 10.9)

Conformance:

3.2.16 Control Implementation (Section 11.4.2)

Conformance:

3.2.17 Annotations (Section 12.1)

Conformance:

3.2.18 Creation Date and Time String (Section 12.1.3)

Conformance:

3.2.19 Line-Through Type (Section 15.4.6)

Conformance:

3.2.20 Line-Through Style (Section 15.4.7)

Conformance:

This is in line with [ODF 1.2] 19.364

 

3.2.21 Encryption (Section 17.3)

Conformance:

 

3.2.22 MIME Type Stream (Section 17.4)

Conformance:

Appendix A. Acknowledgments

The following individuals have participated in the creation of this specification and are gratefully acknowledged

Participants:

 

Appendix B. Non-Normative Text

Implementation specific defaults

(Note that this is not about the default attribute values in the XML schema, nor about the elements within <office:settings>)

 

ODF Implementations like office suites may use implementation specific defaults, especially for layout purposes.

For example:

The user may or may not be pleased with this result. However, without a user-specific action it is not possible to determine if one merely wants to save the data into an ODF-Doc and let the consuming ODF Implementation use its own defaults, or one wants to preserve some or all of these implicit settings.

 

For maximum interoperability and flexibility:

Appendix C. Revision History

Changes marked with "OIC": see http://tools.oasis-open.org/issues/browse/OIC-<number>