ISO/IEC 26300:2006/Amd 1:2012

INTERNATIONAL ISO/IEC
STANDARD 26300
First edition
2006-12-01
AMENDMENT 1
2012-03-15
Information technology — Open
Document Format for Office Applications
(OpenDocument) v1.0
AMENDMENT 1: Open Document Format
for Office Applications (OpenDocument) v1.1
Technologies de l'information — Format de document ouvert pour
applications de bureau (OpenDocument) v1.0
AMENDEMENT 1: Format de document ouvert pour applications de
bureau (OpenDocument) v1.1
Reference number
ISO/IEC 26300:2006/Amd.1:2012(E)
©
ISO/IEC 2012
ISO/IEC 26300:2006/Amd.1:2012(E)

©  ISO/IEC 2012
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2012 – All rights reserved

ISO/IEC 26300:2006/Amd.1:2012(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
Amendment 1 to ISO/IEC 26300:2006 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 34, Document description and processing languages.
This Amendment should be read in conjunction with ISO/IEC 26300:2006 and the associated Technical
Corrigenda 1 and 2. The current edition of ISO/IEC 26300 should be understood by first applying the change
specified in the Technical Corrigenda, then applying the changes specified in this Amendment.

© ISO/IEC 2012 – All rights reserved iii

ISO/IEC 26300:2006/Amd.1:2012
Notation conventions
The title of each change is the complete reference to the section or sub-section being modified. In all cases
(except for an amendment inserting two new Appendices) the title begins with the section or sub-section
number, the section or sub-section name, and the page number. In most cases the location of the
amendment is more precisely indicated by a paragraph number or other indicator. Paragraph numbers are
determined by counting the number of paragraphs from the beginning of the section or sub-section in
question, ignoring lists, tables and examples.
In the case of amendments to the normative Relax-NG schema, the lines of the schema that are amended
are indicated in italics below the heading. Schema line numbers refer to the amended schema. Other
guidance on the intended application of an amendment may be given in italics below the heading.
A change can contain any one or more of the following kinds of edits:
Addition of text: New text is displayed in blue and is underlined, as demonstrated here.
Deletion of text: Deleted text is displayed in red and is struck-through, as demonstrated here.
An ellipsis '…' is occasionally used to indicate deliberate omission of fragments of the original text that are
unchanged by this Amendment and would unreasonably extend the text of this Amendment.
© ISO/IEC 2012 – All rights reserved iv

ISO/IEC 26300:2006/Amd.1:2012(E)
Front matter, p. 1
Open Document Format for Office
Applications (OpenDocument) v1.10
(Second Edition)
Committee Specification1, 19 Jul 2006OASIS Standard, 1 Feb
Document identifier:
OpenDocument-v1.1ed2-.odt
Location:
This Version: http://www.oasis-open.org/committees/office
Previous Version: http://docs.oasis-open.org/office/v1.0
Specification URIs
This Version:
http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.odt
http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.pdf
http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.html.zip
Previous Version:
http://www.oasis-open.org/committees/download.php/19275/OpenDocument-v1.0ed2-cs1.odt
http://www.oasis-open.org/committees/download.php/19274/OpenDocument-v1.0ed2-cs1.pdf
Latest Version:
http://docs.oasis-open.org/office/v1.1/OpenDocument-v1.1.odt
http://docs.oasis-open.org/office/v1.1/OpenDocument-v1.1.pdf
http://docs.oasis-open.org/office/v1.1/OpenDocument-v1.1.html.zip
Latest Approved Version:
http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.odt
http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.pdf
http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.html.zip
Technical Committee:
OASIS Open Document Format for Office Applications (OpenDocument) TC
Chair:
Michael Brauer, Sun Microsystems, Inc.
Editors:
Patrick Durusau, Individual
Michael Brauer, Sun Microsystems, Inc.
Lars Oppermann, Sun Microsystems, Inc.
Related Work:
This specification supersedes OASIS OpenDocument v1.0.
Declared XML Namespaces:
A list of XML namespaces declared by this specification is available in section 1.3.
Abstract:
This is the specification of the Open Document Format for Office Applications (OpenDocument)
format, an open, XML-based file format for office applications, based on OpenOffice.org XML [OOo].
© ISO/IEC 2012 – All rights reserved 1

ISO/IEC 26300:2006/Amd.1:2012(E)
Status:
This document was last revised or approved by the membership of OASISOASIS Open Document
Format for Office Applications (OpenDocument) Technical Committee on the above date. The level
of approval is also listed above. Check the current location noted above for possible later revisions
of this document. This document is updated periodically on no particular schedule.
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
www.oasis-open.org/committees/office.
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
(www.oasis-open.org/committees/office/ipr.php.
The non-normative errata page for this specification is located at
www.oasisopen.org/committees/office.
§ 1.4, “Relax-NG Schema”, schema fragment, p. 32
{The following text amends lines 3-4 and 9-10 of the normative Relax-NG schema, as reproduced in this
section.}
1
2
§ 1.5, “Document Processing and Conformance”, paragraph 7,
p. 34
There are no rules regarding the elements and attributes that actually have to be supported by conforming
applications, except that applications should not use foreign elements and attributes for features defined inby
the OpenDocument schema. See also appendix D.
§ 2.1.1, “Document Root Element Content Models”,
paragraph 1, p. 37
{The following text corrects an editorial error in ISO/IEC 26300:2006/Cor 1, in which part of the text of the
sentence inserted at the end of the paragraph is missing.}
The content models of the five root elements is summarized in the following table. Note that
may contain all supported top-level elements. All four subdocument root elements
together contain the same information as an element that contains the same
subdocument root elements.
2 © ISO/IEC 2012 – All rights reserved

ISO/IEC 26300:2006/Amd.1:2012(E)
§ 2.1.1, table following paragraph 1, p. 37
{The following text amends the heading of the second column of the table.}
meta-
data
§ 2.3.1, “Text Documents”, sub-section “Text Document
Content Model”, schema fragment, p. 42
{The following text inserts a new line (line 179 of the amended schema) in the definition of pattern “text-
content” in the normative Relax-NG schema, as reproduced in this section.}
170
171
172
173
174
175
176
177
178
179     
180
181
182
183
184
185
186
187
188
189
190
§ 2.3.1, “Text Documents”, following sub-section “Global Text
Documents”, p. 42
{The following text inserts a new sub-section, including reproduction of a new pattern definition “office-text-
attlist” inserted into the normative Relax-NG schema (lines 201-207 of the amended schema).}
Use Soft Page Breaks
The  text:use-soft-page-breaks  attribute specifies whether the document contains soft page breaks.
A soft page break is a page break that has been included by a page oriented processor at a position where
the document itself does not include a page break (e.g. by using the  fo:break-before  and  fo:break-
after  formatting properties described in section 15.5.2) .
Soft page breaks are specified by the    elements described in sections 4.7 and
5.1.1:Soft Page breaks.
The use of the    elements is always optional. An application generating the
format  may  include the element if it has computed a paginated layout. A consuming ap plication may  handle
the element while computing the layout, but it  shall not  depend on its existence. Soft page breaks are only
supported within text documents.
A generating application that stores soft page breaks  shal l indicate this by setting the  text:use-page-
breaks  attribute to  true . A generating application that does not store soft page breaks  sha ll indicate that b y
omitting this attribute, or by setting it to  false  .
© ISO/IEC 2012 – All rights reserved 3

ISO/IEC 26300:2006/Amd.1:2012(E)
An application that does not support pagination and soft page-breaks, that modifies an OpenDocument file,
which includes soft page-breaks,  shal l at least set the  text:use-page-breaks  attribute to  false  (or
remove it). It  should  also remove the    elements from the document but is not
required to do so.
An application that computes a paginated layout of a document  should  provide a facility to turn on export of
soft page breaks for the purposes of consistent page breaks and for proper conversion to digital talking book
formats (such as  [DAISY ] ) .
For    elements that appear within table rows, the maximum number of
  elements that appear within the single table cells determines the number o f
page breaks that appear within the table row. The     elements contained in each
cell determine the positions where these page breaks appear within the cell content.
Similarly,    elements that appear within text boxes and other content displayed
outside the text flow, do not start a new page, but only indicate where the text-box's content breaks between
two pages.
201
202   
203     
204        
205     
206   
207
§ 2.5, “Scripts”, paragraph 2, p. 50
Scripts do not imply a scripting language or an object model. A script can for instance operate on the
Document Object Model (DOM) composed from the XML representation of a document in OpenDocument
format (see [DOM2]), operate on the Document Object Model (DOM) of a document in OpenDocument format
or on an application specific API.
§ 3, “Meta Data Elements”, section title, p. 56
{The section title is revised as follows.}
3 Metad Data Elements
§ 3.1.18, “Document Statistics”, schema fragment, pp. 62–63
{The following text moves five lines of the definition of the pattern “office-meta-data” to a new position (lines
771-775 of the amended schema) in the normative Relax-NG schema, as reproduced in this section.}

745
...
766
767

769
770
771     
772        

774        
775     
4 © ISO/IEC 2012 – All rights reserved

ISO/IEC 26300:2006/Amd.1:2012(E)
776
777
778
779
780
...
816
817
818
819
820 ...