Section

 Section Refinement

Correction

1.3

Namespaces

Replace in first table “Prefix” column:

“drawing” with “draw”.

1.6

White-Space Processing and EOL Handling

Replace:

“In conformance with the W3C XML specification [XML1.0], optional white-space characters that are contained in elements that have element content (in other words that must contain elements only but not text) are ignored.”

with

“In conformance with the W3C XML specification [XML1.0], white-space characters that are contained in elements that have element-only content (in other words that must contain elements only but not text) are ignored.”

and replace:

“For some elements, different white-space processing may take place, for example the paragraph element.”

with

“For some elements (see 5.1.1 White-space Characters) different white-space processing may take place, for example the paragraph element.”

2.1.2

Document Root Attributes

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.”

3.1.15

Language

Delete the sentence:

“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.”

6.3

Variable Fields

Delete:

"In the OpenDocument file format, a variable must be declared at the beginning of a document".

6.3

Variable Fields

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.”

6.7.2

Fixed

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 in all future edits of the document.  

• •false: value of the field element where this attribute appears is not preserved in future edits of the document.  

7.3.1

Use Index Marks

Delete the sentence:

“See section 7.1 for more information on index marks.”

7.3.1

Index Scope

Delete 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.”

and insert the sentence:

“The text:index-scope attribute specifies whether index entries from an entire document or from a chapter are used to construct a table of contents.”

7.3.2

Table of Content Entry Template

Delete the sentence:

“(See below.)”

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.” 

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.” 

7.8.2

Auto Mark File

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.”

7.12

Index Template Entries

Replace:

“There are eight types of index entries, ....”

with

“There are seven types of index entries,....”

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.”

8.1.2

Visibility

Replace:

“Filtered rows are invisible, because a filter is applied to the table that does not select the table row. ”

with

“Filtered rows are invisible because they were not selected by a filter applied to a table. ”

8.1.2

Visibility

Replace:

“Collapsed rows have been made invisible by invisible in the UI directly.”

with

“Collapsed rows have been made invisible by the UI directly.”

8.1.3

Cell Current Currency

Replace:

“This attribute is only evaluated for cells whose data type is currency.”

with

“This attribute is only evaluated for cells whose value type is currency.”

8.1.3

Cell Current Date Value

Replace:

“This attribute is only evaluated for cells whose data type is date.”

with

“This attribute is only evaluated for cells whose value type is date.”

8.1.3

Cell Current Time Value

Replace:

“This attribute is only evaluated for cells whose data type is time.”

with

“This attribute is only evaluated for cells whose value type is time.”

8.1.3

Cell Current Boolean Value

Replace:

“This attribute is only evaluated for cells whose data type is boolean.”

with

“This attribute is only evaluated for cells whose value type is boolean.”

8.1.3

Cell Current String Value

Replace:

“This attribute is only evaluated for cells whose data type is string.”

with

“This attribute is only evaluated for cells whose value type is string.”

8.1.3

Table Cell Protection

Replace:

“The table:protected attribute....”

with

“The table:protect attribute....”

8.3.4

Shapes

Replace:

“The <table:shapes> element contains all graphic shapes with an anchor on the table this element is a child of. ”

with

“The <table:shape> element contains all the elements that represent graphic shapes that are anchored on a table where this element occurs.”

8.4.3

Detective

Delete:

“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.”

and insert:

“The <table:detective> element contains information that is used by an UI to determine the highlighting of relationships between cells or cells that are highlighted due to error conditions.”

8.4.4

Detective Operation

Delete:

“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:”

and insert:

“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:”

8.4.4

Name

Delete:

“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.”

and insert:

“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.”

8.5

Search Criteria Must Apply to Whole Cell

Delete:

“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.”

and insert:

“The table:search-criteria-must-apply-to-whole-cell attribute specifies the matching criteria for search patterns against cell content.

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 used on a <table:filter-condition> element if the table:data-type attribute on that <table:filter-condition> element has a table:data-type attribute with the value of "text" and a table:operator attribute with a value of either:

• •>“match” (i.e. matches) 

• •>“!match” (i.e. does not match)  

• •>“=” (i.e. equal to)  

• •>“!=” (i.e. not equal to).” 

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”

with:

“The value of this attribute should be a namespace prefix, followed by an implementation-dependent Boolean expression.”

8.7.1

Condition Source Range Address

Replace in the example “F G G I" with “F G H I”.

8.8

Data Pilot Tables

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.”

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.”

9.4.5

Extrude

Replace:

“The <dr3d:extrude> element represents a three-dimensional extrude based on a polygon.”

with:

“The <dr3d:extrude> element represents a three-dimensional extrude object based on the given polygon. The 3D geometry is formed by extruding the polygon perpendicular to the polygon by a depth (see <dr3d:depth>, 15.22.6), thus creating a front plane, a back plane and side planes. The side planes are formed by connecting all corresponding single edges of the front and back plane. When no depth is given, the polygon forms a plane without depth. The existence of a front plane depends on <dr3d:close-front> (15.22.9). The existence of a back plane depends on <dr3d:close-back> (15.22.9). The size of the back plane can be relative to the size of the front plane when <dr3d:back-scale> is used. “

9.4.6

Rotate

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 formed by rotating the polygon around it's Y-Axis by a number of steps (see <dr3d:horizontal-segments> 15.22.1). The side planes are formed by connecting all corresponding single edges of a neighbored pair 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 plane or back plane is created. If the rotation is different, a front plane is created using the first, unrotated polygon and a back plane is created using the last rotated polygon. The existence of a front plane also depends on <dr3d:close-front> (15.22.9) and back plane on <dr3d:close-back> (15.22.9). The size of the back plane can be relative to the size of the front plane when <dr3d:back-scale> is used.”

15.4.38

Text Combine

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.” 

15.14.12

Fill Image Tile Translation

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.”

15.22.8

End Angle

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.”

15.22.9

Close Front

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 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 3D extrude objects and 3D rotation objects.”

15.22.10

Close Back

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 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 3D extrude objects and 3D rotation objects.”

15.24.4

Mode

Replace “dr3d:normals-direction” with “dr3d:texture-mode.”

15.24.4

Mode

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. “ 

15.31.4

Tick Marks

Replace“chart:axis-interval-major” with “chart:interval-major”

and

replace “chart:axis-interval-minor” with “chart:interval-minor.”  

17.5

Usage of IRIs Within Packages

Delete:

“A relative-path reference (as described in §6.5 of [RFC3987]) 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 IRI for resolving relative-path references is the one that has to be used to retrieve the (unzipped) file that contains the relative-path reference.”

Delete:

“All other kinds of IRI references, namely the ones that start with a protocol (like http:), an authority (i.e., //) or an absolute-path (i.e., /) 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. IRI references inside a package may leave the package, but once they have left the package, they never can return into the package or another one.”

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], except that it may contain the additional characters that are allowed in IRI references [RFC3987]) 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/IRI for resolving relative-path references is the one that has to be used to retrieve the (unzipped) file that contains the relative-path reference.”

Insert after the final paragraph, the following note:

“Note: URI/IRI 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.”

17.7.4

Encryption Data

Replace <encryption-data> with <manifest:encryption-data>.

Appendix B

References

Replace:

“http://www.info-zip.org/doc/appnote-19970311-iz.zip”

with

“ftp://ftp.uu.net/pub/archiving/zip/doc/appnote-970311-iz.zip”.