The Open Document Format for Office Applications (OpenDocument) format, is an open, XML-based file format for office applications, based on OpenOffice.org XML [OOo].

This document is the second errata document for OpenDocument v1.0. It includes as first part the OpenDocument Format 1.0 Approved Errata 01, covering the first part the comments of the Japanese National Body (N0942 ) and in the new second part the second comments of the Japanese National Body (N1078 ) and the first of the British National Body (N1309 ).

Status:

This document was last revised or approved by the OASIS 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.oasis-open.org/committees/office .

Notices

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", “OpenDocument”, “Open Document Format” and “ODF” 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.

Errata Part 01

The following part is identical with the OpenDocument Format 1.0 Approved Errata 01 .
It covers the first Japanese Defect Report (N0942 ) and includes references to ODF 1.0, ISO/IEC 26300 and N0942 , the Japanese National Body comments provided for the reader's convenience.

Section	ODF 1.0 Page	ODF 1.0 Line	ISO/IEC 26300 Page	ISO/IEC 26300 Line	N0942 #	Correction

2.1.1	38	24	37	24	41	Replace "None of the four subdocument root elements contain the complete data, but four combined do." with "All four subdocument root elements together contain the same information as an <office:document> element that contains the same subdocument root elements.
6.7.5	141	18	141	34	40	Replace for value " This value displays the value of the field. Some fields do not support this value. In these cases, the text:display attribute only takes the values value or none , and value or formula , respectively. " with: "This value displays the value of the field."
6.7.5	141	22	141	38	40	Replace for formula " This value allows the display of the formula rather than the value of the field. Some fields do not support this value. In these cases, the text:display attribute only takes the values value or none , and value or formula , respectively. " with: "This value allows the display of the formula rather than the value of the field. This value is not supported by all kinds of fields."
8.11.7	254	47	257	47	61	Replace "specified" with "specifies".
8.11.8	256	3	259	5	62	Replace "It" with "it".
8.11.14	261	12	264	22	63	Replace "cells" with "cell".
9.1.4	268	26	271	26	64	Display "borders" in standard font.
9.1.5	270	22	273	27	65	Replace "presentation:notes>" with "<presentation:notes>".
9.2.5	274	41	278	5	66	Replace "In general, if r is the radius of the polygon, and s is the sharpness, the inner corners a located on a ellipse that's radius is r(100-s)/100." with "In general, if r is the radius of a polygon, and s is the sharpness, the inner corners are located on an ellipse whose radius is r(100-s)/100."
9.2.6	275	38	279	4	42	Replace "supports" with "support" after "may".
9.2.7	276	42	280	8	43	Replace the first "are" with "is".
9.2.12	284	7	287	27	44	Delete "attributes".
9.2.18	291	48	295	30	45	Replace "supports" with "support".
9.2.18	292	10	295	40	46	Replace "supports" with "support".
9.2.19	292	39	296	22	47	Replace "specifies" with "specify".
9.2.19	293	8	296	40	48	Replace "The attribute draw:align specifies the alignment behavior of the glue point if the drawing object is resized and the shape edge to which the glue point's position relates." with: "The attribute draw:align defines the horizontal and vertical edges to which a glue point with absolute position aligns."
9.2.19	293	29	297	12	49	Replace the first "the" in "the the" with "that". Replace “horizontal” with “ horizontal ”; replace “ left ” with “left”; replace “ right ” with “right”; replace “vertical” with “ vertical ”.
9.3	294	2	297	34	50	Delete "where".
9.3	295	39	299	21	52	The term “scale” should be replaced with “scale”.
9.3	295	43	299	25	53	Replace "/" with "or".
9.3	296	26	300	5	54	Replace "effect" with "affect".
9.3	296	26	300	5	55	Replace second "This" with "That".
9.3.1	297	26	301	12	56	Replace "or" with "and".
9.3.1	297	27	301	13	57	Replace "or" with "and".
9.3.3	300	11	304	5	58	Replace "," with "." at the end of "representation." Replace “An example for this kind of objects OLE objects (see [OLE]).” with “For example, an OLE object has no XML representation (see [OLE]).”
9.3.3	300	12	304	6	59	Replace “a XML” with “an XML”.
9.3.3	301	2	304	38	60	Replace "The object is contained within this sub page exactly as it would as it is a document of its own." with "For objects that have an XML representation, the representation of the object is the equivalent to a separate document representing that object, except that it is stored in a folder in the document package. The xlink references that folder."
9.3.10	306	35	310	28	1	Remove “.” following where.
9.3.10	307	39	311	32	2	Remove the second occurrence of “the” in the sentence.
9.3.10	307	40	311	33	3	Remove the second occurrence of “the” in the sentence.
9.3.11	311	24	315	15	4	Change "a URI" to "a URL" in ODF 1.0 and change "a IRI" to "an IRI" in ISO 26300.
9.4.1	315	41	319	38	5	Replace “y-axis” with “z-axis.”
9.5	319	23	323	24	61	Remove the last “the” from the sentence.
9.5.3	330	34	334	36	7	Replace “(x4, y4)” with “(x, y)”.
9.5.3	330	35	334	37	8	Replace “a” with “an” preceding “implied.”
9.5.3	330	39	334	41	9	Replace “a” with “an” preceding “implied.”
9.5.3	331	43	336	3	10	Replace the first “a” with “an” and remove the second “a” in the sentence.
9.5.3	332	1	336	5	11	Replace "A" with "An."
9.5.3	332	19	336	23	12	Replace the first "a" with "an" and remove the second "a."
9.5.3	332	21	336	25	13	Replace "A" with "An."
9.5.3	332	36	336	40	14	Replace "a" with "an."
9.5.3	333	5	337	12	15	Remove "to be."
9.5.5	334	37	338	42	16	Insert "be" between "may" and "changed".
9.5.5	335	10	339	18	17	Replace "and or" with "or."
9.5.5	335	38	340	1	18	Replace "identifier" with "Identifier".
9.5.5	335	40	340	3	19	Insert "of" after "position".
9.5.5	335	41	340	4	20	Insert "of" after "position".
9.5.5	335	42	340	5	21	Insert "of" after "position".
9.5.5	336	9	340	14	22	Replace "A" with "An".
9.5.6	337	28	341	34	23	Replace the first "a" with "an" and remove the second "a".
9.7.2	344	30	349	6	24	Replace "our" with "or".
9.8.1	349	25	354	9	25	Replace "and or" with "or".
9.8.2	352	27	357	16	26	Replace "The" with "the".
9.9	356	11	360	35	27	Replace "lunched" with "launched".
9.10	358	25	363	3	28	Insert "in" before "presentations".
9.11.4	360	39	365	19	29	Remove the second "the" in "the the".
11.7.3	432	22	438	16	82	Replace "vale" with "value".
12.4	438	37	445	3	83	Replace “section .” with “section 9.9.”
14.7.9	500	32	508	22	84	Replace "language" with "country".
15.4.7	555	44	565	12	382	Delete “ See §9.2 of [CSS3Text] for details. ”
15.4.8	556	8	565	24	38	Delete “See §9.3 of [CSS3Text] for details. ”
15.4.19	561	12	570	38	33	Replace reference to Subsection 8.8.4 of XSL with 7.8.4.
15.4.29	565	40	575	25	38	Delete “ See §9.2 of [CSS3Text] for details. ”
15.4.30	566	9	575	50	38	Delete “See §9.3 of [CSS3Text] for details. ”
15.4.33	567	39	577	28	38	Delete “ See § 9.5 of [CSS3Text] for details. ”
15.4.34	567	57	577	47	38	Delete “ See § 9.5 of [CSS3Text] for details. ”
15.5.29	589	23	599	43	34 (duplicates 31)	Replace reference to Subsection 7.9.14 of XSL with 7.19.4.
15.5.38	592	25	602	44	67	Replace "Snap To Layout" with "Snap to Layout Grid".
15.10.1	605	5	615	38	97	Replace: "fixed" with "minimum".
15.11.9	609	4	619	44	98	Replace "page" with "cell".
15.11.11	609	17	620	11	35 (duplicates 32)	Replace reference to Subsection 7.5.13 of XSL with 7.15.13.
15.12	613	19	624	19	96	Replace "species" with "specifies".
15.27.21	651	3	662	39	92	Replace "left side" with "the right side".
15.27.22	651	31	663	28	91	Replace "style:wrap-dynamic-treshold" in the schema with "style:wrap-dynamic-threshold".
15.27.31	655	12	667	10	95 (duplicates 90)	Replace "overly" with "overlies".
15.27.31	655	18	667	16	94	Replace “object” with “option”.
15.28.3	656	9	668	8	88	Replace "draw:margin-horizontal" with "draw:frame-margin-horizontal" and "draw:margin-vertical" with "draw:frame-margin-vertical".
15.28.4	656	32	668	31	93	Replace "this section" with “15.28.5 and 15.28.6”.
15.30.4	659	41	671	45	87	Replace "chart:symbol-length" with "chart:symbol-height".
15.30.9	661	46	674	13	86	Replace " The line interpolation is determined by the chart:splines property." with "The line interpolation is determined by the chart:interpolation attribute."
15.31.2	663	7	675	23	85	Replace chart:axis-visible with chart:visible.
15.31.3	663	20	675	36	81	Replace chart:axis-logarithmic with chart:logarithmic.
15.31.3	663	21	675	37	81	Replace chart:axis-logarithmic with chart:logarithmic.
15.31.3	663	34	676	5	80	Replace "chart:interval-minor-divisor" with "chart:interval-minor".
15.31.3	663	37	676	8	80	Replace "chart:interval-minor-divisor" with "chart:interval-minor".
15.31.4	664	19	676	40	79	Replace " Inner marks are drawn towards the inside of the plot area, that is to the right for an axis displayed on the left hand side of the plot area, and to the left for an axis displayed on the right hand side of the plot area. Outer marks point in the opposite direction. If both properties are specified, one tick mark is drawn that crosses the axis. " with: ” The chart:tick-mark-major-inner and chart:tick-mark-major-outer attributes define the marks for a major interval. The chart:tick-mark-minor-inner and chart:tick-mark-minor-outer attributes define the marks for a minor interval. Inner marks are drawn towards the inside of the plot area, that is to the right for an axis displayed on the left hand side of the plot area, and to the left for an axis displayed on the right hand side of the plot area. Outer marks point in the opposite direction. If both inner or outer attributes are specified for one mark, one tick mark is drawn that crosses the axis.”
15.36	670	4	682	28	77	Replace <style:style-drawpage-properties> with <style:drawing-page-properties>.
15.36	670	20	683	3	75	Insert into the list immediately before 15.36.1:  Transition Type or Family  Transition Subtype  Transition Direction  Fade Color
15.36.8	674	28	687	8	76	Replace “presentation:page-duration” with “presentation:duration”.
15.36.10	675	6	687	36	72	Strike: " It must be included in the <style:presentation-properties> element. "
16.1	678	39	691	40	74	Replace “(positive or negative)” with “(positive, zero, or negative).
16.1	679	29	692	29	73	Replace: 'A list of value types supported for certain generic values, such as “string” or “date”.' With: 'A list of supported value types.'
17.6	686	37	699	35	373	Delete "In order to conform to the Thumbnail Managing Standard (TMS) at www.freedesktop.org,".
17.6	686	38	699	36	37	Replace "thumbnails" with "Thumbnails".
17.7.3	688	38	701	35	364	Replace http://www.isi.edu/in-notes/iana/assignments/media-types/media-types with http://www.iana.org/assignments/media-types/ .
17.7.3	688	38	701	35	68	Strike "As an example, all XML streams have the media type "text/xml"."
17.7.6	690	34	703	34	69	Replace second “name” with “encryption key”.
Appen-dix B	695	7	708	9	395	Replace http://www.w3.org/TR/2003/WD-DOM-Level-3-Events-20030331 with http://www.w3.org/TR/2003/NOTE-DOM-Level-3-Events-20031107/
Appen-dix D	701	17	714	15	71	Change 12.2 Title entry to read "Number Format".
Appen-dix D	702	33	715	31	71	Replace "Text Alignment Properties" with "Text and Text Alignment Properties".

Notes of Errata 01:

Line Numbering:

Lines were counted from the top of each page, including blank lines in schema fragments. Where tables were present, the section with the largest number of lines was used for the line count.

N0942:

All of the “defects” from the Japanese errata document filed with JTC 1/SC 34 were included in the foregoing errata, except for the following (see http://www.itscj.ipsj.or.jp/sc34/open/0942rev1.htm ):

N0942:30 “In 15.4.1, subsection 8.8.4 of XSL is referenced, but it should be 7.8.4.”

Rejected, the text is correct.

N0942:51 “Section 9.3, 8th line on page 298 Current description: Like the formatting properties of drawing shapes, frame formatting properties are stored in styles belonging to the graphic family. Proposal: A different font is used for the word "graphic", but it shouldn't.”

Rejected, the text is correct. The term “graphic” here refers to a particular “family” of styles that is defined by OpenDocument.

N0942:70 – Requires further consideration.

N0942:78 “Can style:default-style contain the properties in 15.36 "Presentation Page Attributes"? The beginning of this subsection is: 'The properties described in this section can be contained within style elements <style:style> whose family is drawing-page.' However, can style:default-style whose family is drawing-page contain these properties? The schema appears to say so.”

Rejected, not a defect. The answer to the question is yes. The reference in the text was not exclusive.

N0942:89 “The first para of 15.3.4 is:

If a page contains borders, the border line width attributes

style:border-line-width, style:border-line-width-top,

style:border-line-width-bottom, style:borderline-width-left and

style:border-line-width-right specify the properties of the

border lines of the headers and footers.

However, since 15.3 applies to headers and footers, should "If a page" be replaced with "If a header or footer"?”

Rejected. Borders of pages define the borders of headers and footers and therefore the text is correct as written.

Errata Part 02

The following part is new to the second errata document for OpenDocument v1.0 .
This part covers the second Japanese Defect Report (N1078 ) and the first British Defect Report (N1309 ) and includes references to the comments of the Japanese National Body (N1078 ) and British National Body (N1309 ) for the reader's convenience.

Section	Subsection	Correction	Comment of National Body
1.3		Replace in first table “Prefix” column: “drawing” with “draw”.	N1309:9
1.6		Replace the entire section and title with the following: “1.6 White-Space Processing ODF processing of whitespace characters is in conformance with the provisions of [XML 1.0]. In addition, ODF processors shall ignore all element children ([RNG] section 5, Data Model) of ODF-defined elements that are strings consisting entirely of whitespace characters and which do not satisfy a pattern of the ODF schema definition for the element. Any special treatment of additional occurrences of whitespace characters depends on the specific definitions of individual ODF elements, attributes, and their datatypes. See, in particular, section 5.1.1.”	N1309:10
2.1.2	Version	Delete: “If the file has a version known to an XML processor, it may validate the document. Otherwise, it is optional to validate the document, but the document must be well formed.”	N1309:6
3.1.15		Replace: “The manner in which the language is represented is similar to the language tag described in [RFC3066]. It consists of a two or three letter Language Code taken from the ISO 639 standard optionally followed by a hyphen (-) and a two-letter Country Code taken from the ISO 3166 standard.” with: “The syntax and semantics of the language tag are specified in [RFC3066].”	N1078:1
4.4.1	Protected Sections	After: “To avoid saving the password directly into the XML file, only a hash value of the password is stored.” insert: “The hashing is implementation-dependent.”	N1078:18
6.3		Delete: "In the OpenDocument file format, a variable must be declared at the beginning of a document".	N1309:1
6.3		Replace: “OpenDocument text documents can contain variables, which are processed or displayed using variable fields.” with “OpenDocument documents can contain variables, which are processed or displayed using variable fields.”	N1309:2
6.7.2		Delete the sentences: “If the value of a field is fixed, the value of the field element to which this attribute is attached is preserved in all future edits of the document. If the value of the field is not fixed, the value of the field may be replaced by a new value when the document is edited.” and insert: “The defined values of the text:fixed attribute are: • true: value of the field element where this attribute appears is preserved. • false: value of the field element where this attribute appears may be changed.”	N1078:2
7.3.1	Use Outline	Delete the sentence: “See section 7.1 for more information on index marks.”	N1078:3
7.3.1	Index Scope	Replace the sentence: “The text:index-scope attribute determines whether the table-of-content is generated for the whole document, or only for the current chapter.” with: “The text:index-scope attribute specifies whether index entries from an entire document or from the chapter that contains the <text:table-of-content> element are used to construct a table of contents . The default value and the determination of the chapter are implementation-dependent.”	N1078:5
7.3.2		Delete the sentence: “(See below.)”	N1078:6
7.4.1	Use Caption	Delete the sentences: “Each object contained in a text document has a name. In addition, images also have a caption. The image caption or the image name can be gathered for the index of illustrations.” and insert: “The text:use-caption attribute specifies whether the captions or names of illustrations are used for an index. The defined values of the text:use-caption attribute are: • true: illustration captions are used for an index. • false: illustration names are used for an index.”	N1078:7
7.7.1	Copy Outline Levels	Delete the sentences: “This attribute can have a value of true or false. If the value is true, the entries are gathered at the outline level of the source element to which they refer. If the value is false, all index entries gathered are at the top outline level. For example, if an image appears in section 1.2.3, the entry for the image is located at outline level 3.” and insert: “The text:copy-outline-levels attribute specifies whether index entries are indented according to the outline level of their source. The defined values for the text:copy-outline-levels attribute are:  false: no indentation is added.  true: index entries are indented according to the outline level of their source.”	N1078:8
7.8.2		Insert new a paragraph following the paragraph that ends with: “The declaration element in an Xlink, which points to the resource containing the list of terms.” that reads: “The format of an index mark file is implementation dependent.”	N1078:9
7.12		Replace: “There are eight types of index entries, ....” with “There are seven types of index entries,....”	N1078:10
8.1.1	Protected	Replace: “If a table is protected, all of the table elements and the cell elements with a style:cell-protect attribute set to true are protected.” with “If a table is protected, all of the table's cell elements with a style:cell-protect attribute set a different value than none are protected.”	N1078:11
8.1.1	Protected	After: “To avoid saving the password directly into the XML file, only a hash value of the password is stored within the table:protection-key attribute.” insert: “The hashing is implementation-dependent.”	N1078:18
8.1.2	Visibility	Replace the entire paragraph with the following text: “The table:visibility attribute specifies the conditions under which the table row is visible. The values of the attribute are: • visible : the row is visible • collapse : the row is not visible • filter : the row is not visible as the result of applying a filter (see section 8.7) The default is visible .”	N1078:12 N1078:13
8.1.3	Value Type	Replace: “The table:value-type attribute specifies the type of value that can appear in a cell.” with “The office:value-type attribute specifies the type of value that can appear in a cell.”	N1078:14
8.1.3	Cell Current Numeric Value	Replace: “This attribute is only evaluated for cells that contain the following data types:” with “This attribute is present only whenever there is an office:value-type attribute with one of the following values:”	N1078:14
8.1.3	Cell Current Currency	Replace: “The tableoffice:currency attribute specifies the current currency value of a cell. The value of this attribute is usually currency information such as DEM or EUR. This attribute is only evaluated for cells whose data type is currency.” with “The office:currency attribute specifies the currency system in which the value of the office:value attribute is expressed. The value of this attribute is usually a currency identifier, such as “DEM” or “EUR”. This attribute may be present only when the office:value-type attribute value is “currency”.”	N1078:14
8.1.3	Cell Current Date Value	Replace: “This attribute is only evaluated for cells whose data type is date.” with “This attribute is present only whenever the office:value-type attribute value is “date ” .”	N1078:14
8.1.3	Cell Current Time Value	Replace: “This attribute is only evaluated for cells whose data type is time.” with “This attribute is present only whenever the office:value-type attribute is “time ” .”	N1078:14
8.1.3	Cell Current Boolean Value	Replace: “This attribute is only evaluated for cells whose data type is boolean.” with “This attribute is present only whenever the office:value-type attribute value is “boolean ” .”	N1078:14
8.1.3	Cell Current String Value	Replace: “This attribute is only evaluated for cells whose data type is string.” with “This attribute may be present only whenever the office:value-type attribute value is “string ” .”	N1078:14
8.1.3	Table Cell Protection	Replace: “The table:protected attribute protects the table cells.” with “The table:protect attribute protects the table cells.” Replace in the last sentence of the subsection the word: "table:cell-protect" with: "style:cell-protect"	N1078:15
8.3.4		Replace: “The <table:shapes> element contains all graphic shapes with an anchor on the table this element is a child of.” with “The <table:shapes> element contains all the elements that represent graphic shapes (see section 9.2) that are anchored on a table where this element occurs.”	N1078:16
8.4.3		Replace: “The <table:detective> element has two purposes. One the one hand, it contains information about relations that exist between table cells because of formulas and that should be highlighted in the UI. On the other hand, the element contains information about cells that are highlighted currently in the UI either because of the relations mentioned above or because of error conditions.” with “The <table:detective> element contains information about what relationships between the current cell and other cells are revealed in the presentation of the table.”	N1078:17
8.4.4		Replace: “The <table:operation> element specifies that certain relations that exist between the cell the element is a child of and other cells should be made visible or invisible in the UI. One and the same detective operation can be applied multiple times to the same cell. In this case, the second operation is applied to the resulting cells of the first operation and so on. This means that an operation not necessarily is applied to the cell the operation is defined in, but also to other cells, and that it therefor can interact with operations defined in other cells. This especially applies to operations that make relations invisible. To get a determinate behavior, operations have an index and are applied in the order of that index. The attributes associated with the <table:operation> element are:” with “The <table:operation> element specifies both the type of detective operation that leads to the discovery of relationships between cells (table:name attribute) and the order which those operations are applied (table:index attribute). Once relationships between cells have been discovered, those cells are highlighted to show those relationships. The attributes associated with the <table:operation> element are:”	N1078:17
8.4.4	Name	Replace “The table:name attribute specifies the name of the detective operation. Possible names are trace-dependents , remove-dependents, trace-precedents, remove-precedents and trace-errors. trace-dependents and remove-dependents displays or hides cells that use the value of the current cell in their formula. Trace-precedents and remove-precedents displays or hides cells whose value is used in the formula of the current cell. Trace-errors displays cells that cause an error while calculating the result of the current cell's formula.” with “The table:name attribute specifies the name of a detective operation. The defined values for the table:name attribute are: • remove-dependents: removes highlighting from cells that use the value of the current cell in their formula. • remove-precedents: removes highlighting from cells whose values are use in the formula of the current cell. • trace-dependents: highlights cells that use the value of the current cell in their formula. • trace-errors: highlights cells that cause an error while calculating the result of the current cell's formula. • trace-precedents: highlights cells whose values are use in the formula of the current cell. The nature of the highlighting imposed or removed from cells as the result of detective operations is implementation dependent.”	N1078:17
8.5.1		After: “To avoid saving the password directly into the XML file, only a hash value of the password is stored.” insert: “The hashing is implementation-dependent.”	N1078:18
8.5.2	Search Criteria Must Apply to Whole Cell	Replace: “The table:search-criteria-must-apply-to-whole-cell attribute specifies whether or not the specified search criteria, according to the regular expression used, must apply to the entire cell contents.” with “The table:search-criteria-must-apply-to-whole-cell attribute specifies whether a search pattern from the table:value attribute matches the entire content of a cell. The defined values of the table:search-criteria-must-apply-to-whole-cell are:  false: a search pattern can match any substring at any position in a cell.  true: a search pattern must match the entire content of a cell. The table:search-criteria-must-apply-to-whole-cell attribute is only used with the <table:filter-condition> element when its table:data-type attribute has the value text and its table:operator attribute has one of the values:  match (i.e. matches)  !match (i.e. does not match)  = (i.e. equal to)  != (i.e. not equal to).”	N1078:20
8.5.2	Use Regular Expressions	Insert after the first paragraph: "The syntax and semantics of the regular expressions are implementation-dependent."	N1309:4
8.5.3	Condition	Replace: “The value of this attribute should be a namespace prefix, followed by a Boolean expression. A typical syntax of the expression may be similar to the XPath syntax. The following are valid conditions: • Condition ::= ExtendedTrueCondition \| TrueFunction 'and' TrueCondition • TrueFunction ::= cell-content-is-whole-number() \| cell-content-is-decimal-number() \| cell-content-is-date() \| cell-content-is-time() \| cell-content-is-text() • ExtendedTrueCondition ::= ExtendedGetFunction \| cell-content-text-length() Operator Value • TrueCondition ::= GetFunction \| cell-content() Operator Value • GetFunction ::= cell-content-is-between(Value, Value) \| cell-content-is-not-between(Value, Value) • ExtendedGetFunction ::= cell-content-text-length-is-between(Value, Value) \| cell-content-text-length-is-not-between(Value, Value) \| cell-content-is-in-list(StringList) • Operator ::= '<' \| '>' \| '<=' \| '>=' \| '=' \| '!=' • Value ::= NumberValue \| String \| Formula • StringList ::= StringList ';' String \| String” • A Formula is a formula without an equals (=) sign at the beginning. See section for more information. • A String comprises one or more characters surrounded by quotation marks. • A NumberValue is a whole or decimal number. It must not contain comma separators for number of 1000 or greater.” with: “The value of this attribute should be a namespace prefix, followed by an implementation-dependent Boolean expression.”	N1078:21
8.6.10	Function	Add after the paragraph before the schema: "These functions are implementation-dependent."	N1078:23
8.7.1	Condition Source Range Address	Replace in the example “F G G I" with “F G H I”.	N1078:24
8.8		Replace: “Data pilot tables allow it to analyze and evaluate data contained in spreadsheet tables.” with: “Data pilot tables enable users to analyze and evaluate data extracted from a range of structured data sources, such as spreadsheet tables, database tables, or external service components.”	N1078:22
8.8.4	Function	Add after the paragraph before the schema: "These functions are implementation-dependent."	N1078:23
8.8.4	Used Hierarchy	Replace: “The value means that no hierarchy should be applied at all.” with: “The value -1 means no hierarchy should be applied at all.”	N1078:26
8.8.7	Function	Add after the paragraph before the schema: "These functions are implementation-dependent."	N1078:23
8.9	Function	Add after the paragraph before the schema: "These functions are implementation-dependent."	N1078:23
9.2.9		Replace: “The <draw:connector> element represents a series of lines that are connected to the glue points of two other shapes.” with “The <draw:connector> element represents a connected set of one or more lines, that visually connects a start and an end point. Start and/or end points can be assigned to glue points (see section 9.2.19) or absolute positions.”	N1078:25
9.2.11		Add to end of first paragraph: “The layout of the measure shape is implementation-dependent.”	N1078:27
9.3	Relative Sizes	The term “scale” should be replaced with “scale”. [This corrects an incorrect errata item in Part 1.]	N0942:52
9.4		Immediately below the section title, add the paragraph: "3D shapes are used to define geometry inside coordinate systems. All ODF coordinate systems are right-handed. Geometry is represented by a tree of scenes. Each scene may contain zero or more 3D shapes, with scene being a special case of shape. The root scene defines the world coordinate system. Each 3D shape may define a local coordinate system relative to its parent 3D scene."	N1078:32
9.4.5		Replace: “The <dr3d:extrude> element represents a three-dimensional extrude based on a polygon.” with: “The <dr3d:extrude> element represents a three-dimensional extruded object based on the given polygon. The 3D geometry is formed by extruding the polygon perpendicular to the plane of the polygon by a depth (see dr3d:depth, 15.22.6), thus creating a front face, a back face and side faces. The side faces are formed by connecting all corresponding single edges of the front and back plane. When no depth is given, the polygon forms a shape without depth. The closing of the front face depends on dr3d:close-front (15.22.9). The closing of the back face depends on dr3d:close-back (15.22.10). The size of the back face can be relative to the size of the front face when dr3d:back-scale (15.22.5) is used. The side faces defined by the extrusion of the shape are always closed.“	N1078:32
9.4.6		Replace: “The <dr3d:rotate> element represents a three-dimensional rotation shape based on a polygon.” with: “The <dr3d:rotate> element represents a three-dimensional rotation shape based on the given polygon. The 3D geometry is defined by rotating the XY-Plane with the polygon around the Y-Axis of the local coordinate system. This rotation is linearly interpolated in the given number of steps (see dr3d:horizontal-segments) around the given angle (see dr3d:end-angle). The side faces are formed by connecting all corresponding single edges of neighboring pairs of rotated polygons. By default, the rotation uses a full rotation (360 degrees, see dr3d:end-angle 15.22.8). In that case the 3D geometry is implicitly closed and no front face or back face is created (unless they are of different sizes). If the rotation is different, a front face is created using the first, unrotated polygon and a back face is created using the last rotated polygon. The closing of a front face also depends on dr3d:close-front (15.22.9) and back face on dr3d:close-back (15.22.10). The size of the back face can be different than the size of the front face when dr3d:back-scale (15.22.5) is used.”	N1078:32
9.5.2	Extrusion First Light Harsh	Following the first paragraph add: “When the attribute value is true, the light is harsh. The light is an undiffused point source. When the attribute value is false, the light is not harsh. The means by which the light is softened is implementation-dependent.”	N1309:3
9.5.2	Extrusion Second Light Harsh	Following the first paragraph add: “When the attribute value is true, the light is harsh. The light is an undiffused point source. When the attribute value is false, the light is not harsh. The means by which the light is softened is implementation-dependent.”	N1309:3
15.4.38		Replace: “Use the style:text-combine property to combine characters so that they are displayed within two lines. The value of this attribute can be none, letters or lines. If the value is lines, all characters with this attribute value that immediately follow each other are displayed within two lines of approximately the same length. There can be a line break between any two characters to meet this constraint. If the value of the attribute is letters, up to 5 characters are combined within two lines. Any additional character is displayed as normal text.” with: “The style:text-combine attribute specifies whether to combine characters so that they are displayed within two lines. The defined values for the style:text-combine attribute are: • letters: Display text in Kumimoji. Up to five (5) characters are combined within two lines and are displayed with a reduced size in a single wide-cell character. Additional characters are displayed as normal text. • lines: Displays text in Warichu. All characters with the style:text-combine attribute that immediately follow each other are displayed within two lines of approximately the same length. A line break may occur between any two characters to meet this constraint. • none: characters should not be combined.”	N1309:7
15.14.12		Replace: “This attribute is only interpreted if the value of the current style:repeat attribute is tiled.” with: “This attribute is only interpreted if the value of the current style:repeat attribute is repeat.”	N1078:28
15.19		Add to the end of first paragraph: “The layout of the connector is implementation-dependent.”	N1078:25
15.20		Add to the end of first paragraph: “The layout of the measure drawing objects is implementation-dependent.”	N1078:29
15.22.5		Replace: “The attribute dr3d:back-scale specifies the proportion of the background geometry for lathe and extrude objects.” with “The dr3d:back-scale attribute specifies the proportion of the background geometry for 3D rotation and extrude objects.”	N1078:32
15.22.8		Replace: “The attribute dr3d:end-angle specifies the rotation angle for 3D lathe objects. If it is the default (360°), the lathe object is closed and completely rotated. With smaller values it is possible to define opened lathe objects (segments). The then visible sides are closed and take into account the dr3d:back-scale and dr3d:edge-rounding attributes. With bigger values it is possible to create lathe objects with more than one rotation. This will only have a visible effect when e.g., dr3d:back-scale is used.” with: “The attribute dr3d:end-angle specifies the rotation angle for 3D rotation objects. If it is the default (360°), the 3D rotation object is closed and completely rotated. With values less than 360° it is possible to define opened 3D rotation objects (segments). The then visible sides are closed and take into account the dr3d:back-scale and dr3d:edge-rounding attributes. With values greater than 360° it is possible to create 3D rotation objects with more than one rotation. This will only have a visible effect when e.g., dr3d:back-scale is used.”	N1078:32
15.22.9		Replace: “The dr3d:close-front property specifies whether a front plane shall be generated. E.g., if an ellipse is extruded, and this attribute is set, the ellipse will have an open front. The attribute can be used with extrudes and lathe objects.” with: “The dr3d:close-front property specifies whether a front face is generated. When set to false, generation of a front face may be suppressed. This will only have an effect when the provided geometry is closed and thus would produce a face.”	N1078:32
15.22.10		Replace: “The dr3d:close-back property describes if a back plane shall be generated. E.g., if an ellipse is extruded, and this attribute is set, the ellipse will have an open back. The attribute can be used with extrudes and lathe objects.” with: “The dr3d:close-back property describes if a back face is generated. When set to false, generation of a back face may be suppressed. This will only have an effect when the provided geometry is closed and thus would produce a face.”	N1078:32
15.24.4		Replace “dr3d:normals-direction” with “dr3d:texture-mode”.	N1078:30
15.24.4		Insert after “The attribute dr3d:texture-mode is used to specify how the texture is modulated.” the text: “The values of the dr3d:texture-mode attribute are:  blend: blends the texture color with the object color.  modulate: modulates the object color with the texture color.  replace: replaces the object color with the texture color. “	N1078:31
15.31.4		Replace: “chart:axis-interval-major” with “chart:interval-major” and replace “chart:axis-interval-minor” with “chart:interval-minor”.	N1078:36
17.5		Delete the paragraph starting with: “A relative-path reference” Delete the paragraph starting with: “All other kinds” Insert after the list item that ends “from the file system or another package.” the paragraph: “A relative-path reference (as defined in §4.2 of [RFC3986] that occurs in a file that is contained in a package has to be resolved exactly as it would be resolved if the whole package gets unzipped into a directory at its current location. The base URI for resolving relative-path references is the one that has to be used to retrieve the (unzipped) file that contains the relative-path reference.”	N1078:35
17.5		Insert after the final paragraph, the following note: “Note: URI references that are not a relative-path reference do not need any special processing. This especially means that absolute-paths do not reference files inside the package, but within the hierarchy the package is contained in, for instance the file system.”	N1078:35
17.7.4		Replace <encryption-data> with <manifest:encryption-data>.	N1078:33
Appendix B		Delete the reference entry for [RFC2396] and insert this reference for [RFC3986]: [RFC3986] T. Berners-Lee, R. Fielding, L. Masinter, Uniform Resource Identifier (URI): Generic Syntax, http://www.ietf.org/rfc/rfc3986.txt , IETF, January 2005.	N1078:35
Appendix B		Replace the URL of the ZIP application note with: “http://www.info-zip.org/doc/appnote-19970311-iz.zip ” Delete the text: “PKWARE Inc., 2004.”	N1309:8

Notes of Errata 02:

N1078:

All of the items in the SC34 N 1078 defect report from the National Body for Japan (see http://www.itscj.ipsj.or.jp/sc34/open/1078.htm ) are addressed in the foregoing errata except for the following:

N1078:4 - “Is the attribute "text:use-index-source-styles" orthogonal to the text:use-outline and text:use-index-marks attributes? For example, can text:use-index-marks="true" and text:use-index-source-styles="true" coexist?”
No action:The specification shows no contradiction to the independence of XML attributes, but ODF 1.2 will offer a more detailed explanation of the attributes.

N1078:19 - No comment with number nineteen exists.

N1078:34 - “relative-path reference" in 17.5 is never defined in RFC 3987.”
The defect was covered with amendment for N1078:35 .

N1309:

All of the items in the SC34 N 1309 defect report from the National Body for Great Britain (see http://www.itscj.ipsj.or.jp/sc34/open/1309.htm ) are addressed in the foregoing errata except for the following:

N1309:5 - “The clause 9.3.8 mentions the <draw:contour-polygon> and <draw:contour-path> elements. However the function of purpose elements is not defined except with the words "[t]hese elements describe the contour of an image or object."
No action as 9.3.8 already states: “The elements are similar to the <draw:polygon> (see section 9.2.4) and <draw:path> (see section 9.2.6) elements, except that they specify a contour rather than a drawing shape. The attributes they support are the ones for the size, the viewbox, the points (contour polygon only) and the path (contour path only).”
Given the reference to 9.2.4 and 9.2.6 it should be obvious how the contour is defined.

1Original comment referenced section 9.4.6. That section reference was incorrect. The correct reference was supplied.

2This comment was applied to normative references in 15.4.7, 15.4.8, 15.4.29, 15.4.30, 15.4.33, and 15.4.34.

3Section and page references were not included in the original comment.

4Section and page references were not included in the original comment.

5Section and page references were not included in the original comment.