Open Document Format for Office Applications (OpenDocument) v1.1 Errata 01

OASIS Approved Errata

22 July 2013

Specification URIs

This version:

http://docs.oasis-open.org/office/v1.1/errata01/os/OpenDocument-v1.1-errata01-os.odt  (Authoritative)

http://docs.oasis-open.org/office/v1.1/errata01/os/OpenDocument-v1.1-errata01-os.html

http://docs.oasis-open.org/office/v1.1/errata01/os/OpenDocument-v1.1-errata01-os.pdf

Previous version:

N/A

Latest version:

http://docs.oasis-open.org/office/v1.1/errata01/OpenDocument-v1.1-errata01.odt (Authoritative)

http://docs.oasis-open.org/office/v1.1/errata01/OpenDocument-v1.1-errata01.html

http://docs.oasis-open.org/office/v1.1/errata01/OpenDocument-v1.1-errata01.pdf

Technical Committee:

OASIS Open Document Format for Office Applications (OpenDocument) TC

Chair:

Rob Weir (robert_weir@us.ibm.com), IBM

Editors:

Dennis E. Hamilton (dennis.hamilton@acm.org), Individual

Patrick Durusau (patrick@durusau.net), Individual

Additional artifacts:

This prose specification is one component of a Work Product which also includes:

  Open Document Format for Office Applications (OpenDocument) v1.1. 22 July 2013. OASIS Standard incorporating Approved Errata 01. http://docs.oasis-open.org/office/v1.1/errata01/os/OpenDocument-v1.1-errata01-os-complete.html.

Related work:

This specification provides errata for:

  Open Document Format for Office Applications (OpenDocument) v1.1. 01 February 2007. OASIS Standard. http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1-html/OpenDocument-v1.1.html.

Abstract:

This specification lists errata for Open Document Format for Office Applications (OpenDocument) v1.1.

 

Status:

This document was last revised or approved by the OASIS Open Document Format for Office Applications (OpenDocument) TC on the above date. The level of approval is also listed above. Check the Latest version location noted above for possible later revisions of this document.

Technical Committee members should send comments on this Work Product to the Technical Committees email list. Others should send comments to the Technical Committee by using the "Send A Comment" button on the Technical Committees web page at http://www.oasis-open.org/committees/office/.

For information on whether any patents have been disclosed that may be essential to implementing this Work Product, 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/office/ipr.php).

Citation format:

When referencing this Work Product the following citation format should be used:

[OpenDocument-v1.1-errata01]

Open Document Format for Office Applications (OpenDocument) v1.1 Errata 01. 22 July 2013. OASIS Approved Errata. http://docs.oasis-open.org/office/v1.1/errata01/os/OpenDocument-v1.1-errata01-os.html.

 

 

Notices

Copyright OASIS Open 2013. 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 name "OASIS" is a trademark 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/policies-guidelines/trademark for above guidance.

 

Table of Contents


1      Introduction.............................................................................................................................. 5

1.1      Terminology...................................................................................................................... 5

1.2      Normative References....................................................................................................... 5

1.3      Non-Normative References................................................................................................ 6

1.4      Errata Tabulation Format.................................................................................................. 7

1.5      Notation Conventions........................................................................................................ 7

1.5.1      Section/Subsection Entries........................................................................................ 7

1.5.2      Issue Identifications.................................................................................................... 7

1.5.3      Issue Sources.............................................................................................................. 7

1.5.4      Amd? Status............................................................................................................... 8

2      Errata Items.............................................................................................................................. 9

3      Conformance.......................................................................................................................... 37

Appendix A    Acknowledgments.................................................................................................... 38

Appendix B    Issues Not Applicable to ODF 1.1............................................................................. 40

Appendix C    IS 26300:2006/Amd1 Reconciliation....................................................................... 41


 

 

1       Introduction

[All text of this document is informative.]

This document provides the first Errata document for Open Document Format for Office Applications (OpenDocument) v1.1 [ODF 1.1].

The errata items have three sources:

  Errata items developed for the earlier [ODF 1.0] that also apply to the text of [ODF 1.1]

  Additional errata based on comments submitted to or originated in the OASIS Open Document Format for Office Applications (OpenDocument) TC

  Errata identified for achieving technical alignment of [ODF 1.1] and International Standard for OpenDocument [IS 26300:2006] as amended for mutual alignment [AMD1]

These errata do not apply to the International Standard.  To facilitate technical-alignment review, these errata entries identify whether an equivalent errata item has already been included in changes that align the International Standard with ODF 1.1.  

Some ODF 1.0 Errata items do not apply to ODF 1.1.  Those are accounted for in ().

Some ODF 1.1 Errata 01 items have arisen since the International Standard corrigenda and amendment were produced.  Those items are identified in the Errata items (section ) and also summarized in a form applicable to the amended International Standard ().

 

1.1                  Terminology

 

Within the ODF 1.1 specification and the extracts presented in errata items, the terms "shall", "shall not", "should", "should not", and may are interpreted as described in Annex H of [ISO/IEC Directives] if they appear in bold letters [ODF 1.1].  Occurrences have their effect in the ODF 1.1 specification.  They do not apply to the interpretation of this document.

1.2                  Normative References

 

This is an informative specification.  There is no introduction of normative conditions and conformance clauses by reference or in any other manner.

1.3                  Non-Normative References

[ISO/IEC Directives]
ISO/IEC Directives, Part 2: Rules for the structure and drafting of International Standards.  Fifth edition, 2004. International Organization for Standardization and International Electrotechnical Commission.  Sixth edition with unchanged Annex H available at http://www.iso.org/directives

[ODF 1.0]
Open Document Format for Office Applications (OpenDocument) v1.0. 01 May 2005. OASIS Standard.  Available at http://docs.oasis-open.org/office/v1.0/OpenDocument-v1.0-os.pdf

[1.0-1] 
Open Document Format for Office Applications (OpenDocument) 1.0 Errata 01. 
24 November 2008.  OASIS Approved Errata.  All formats available at
http://docs.oasis-open.org/office/v1.0/errata/os/

[1.0-2] 
Open Document Format for Office Applications (OpenDocument) 1.0 Errata 02.
20 September 2010.  OASIS Approved Errata.  All formats available at
http://docs.oasis-open.org/office/v1.0/errata/os/

[ODF 1e2]
Open Document Format for Office Applications (OpenDocument) 1.0 (Second Edition).
19 July 2006.  OASIS Committee Specification 01.  Available at
https://www.oasis-open.org/committees/document.php?document_id=19274 (PDF) and https://www.oasis-open.org/committees/document.php?document_id=19275 (ODT)

[ODF 1.1]
Open Document Format for Office Applications (OpenDocument) v1.1. 01 February 2007. OASIS standard. All formats available at
http://docs.oasis-open.org/office/v1.1/OS/

[IS 26300:2006]
Information Technology – Open Document Format for Office Applications (OpenDocument) v1.0.  Available at
http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html (entry for Standard ISO/IEC 26300:2006)

[COR1]
Information Technology – Open Document Format for Office Applications (OpenDocument) v1.0, Technical Corrigendum 1.  2010-12-15.  Available at 
http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html (entry for Standard ISO/IEC 26300:2006/Cor.1:2010)

[COR2]
Information Technology – Open Document Format for Office Applications (OpenDocument) v1.0, Technical Corrigendum 2.  2011-12-01.  Available at 
http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html (entry for Standard ISO/IEC 26300:2006/Cor.2:2011)

[AMD1]
Information Technology – Open Document Format for Office Applications (OpenDocument) v1.0 – Amendment 1: Open Document Format for Office Applications (OpenDocument) v1.1. 
2012-03-15.  Available at 
http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html (entry for Standard ISO/IEC 26300:2006/Amd.1:2012)

 

 

1.4                  Errata Tabulation Format

 

Section/
Subsection

Instruction

Issue

Source

Amd?

2.1.1

Instructions and other notations that are not the texts themselves are included in these brackets.

Removed text is shown in light red strike-through.Inserted text is shown in light blue underlined.  Other text is shown without change and to provide sufficient context for the changes ...

N1078:10
3798

COR2
WG6

-
Y

2.1.2/
Version

Style changes are shown in magenta, double-underlined.  The text is shown in the desired resulting style.

N0942:50

1.0-1

N

1.5                  Notation Conventions

1.5.1          Section/Subsection Entries

When instructions apply to a numbered section outside of any subsection, the section number is used alone.  For example, 2.1.1 refers to ODF 1.1 section 2.1.1 Document Root Element Content Models.

When the instructions apply in a named subsection, the subsection name follows the numbered section identification.  For example, 2.1.2/Version refers to the Version subsection of section 2.1.2 Document Root Attributes.

1.5.2          Issue Identifications

Issue identifications beginning with N, such as N0942:50 and N1078:10, refer to numbered issues in defect reports on [IS 26300:2006] received from ISO/IEC JTC1/SC34.  Further details on those defect items and their disposition in [ODF 1.0] are found in ODF 1.0 Errata 02 [1.0-2].

Issues identified by numerals, nnnn, such as 3798, refer to an issue identified OFFICE-nnnn (e.g., OFFICE-3798) in the  issue database of the OASIS Open Document Format for Office Applications (OpenDocument) TC.

Whenever an issue identification has a link, there is (also) discussion of the issue in the issue database.  The link is to the corresponding issue entry (e.g., N1078:10 linked to associated issue OFFICE-1802, 3798 linked to associated issue OFFICE-3798).

1.5.3          Issue Sources

All errata items originate in ODF 1.0 Errata and/or ODF 1.1-specific issues captured in the OpenDocument TC issue database.  The Source indicates additional information that is pertinent to the alignment of ODF 1.1 and IS 26300:2006:

  1.0-1 indicates an ODF 1.0 Errata 01 item [1.0-1]

  COR1 indicates an ODF 1.0 Errata 01 item that was also applied in IS 26300:2006 [COR1]

  1.0-2 indicates an ODF 1.0 Errata 02 item [1.0-2]

  COR2 indicates an ODF 1.0 Errata 02 item that was also applied in IS 26300:2006 [COR2]

  TC indicates an ODF 1.1 item that originated in the OpenDocument TC

  WG6 indicates an ODF 1.1 item that originated in ISO/IEC JTC1/SC34 WG6 as part of creating the [AMD1] alignment for ODF 1.1.

1.5.4          Amd? Status

This column indicates whether or not there is an issue that is or is not reflected in [AMD1]:

1.     Entry - signifies that [AMD1] coverage was unnecessary.  This is usually an item that was covered with [COR1] or [COR2].

2.     Entry Y signifies that [AMD1] also covered the errata item.

3.     Entry N signifies that [AMD1] did not cover the errata item and any coverage depends on subsequent work by ISO/IEC JTC1/SC34 WG6.  These items are also accounted for in .

 

2       Errata Items

Section/
Subsection

Instruction

Issue

Source

Amd?

1.3

Change, in the Prefix column of Table 1

drawing

N1309:9

COR2

-

1.6

Change the entire section

1.6 White-Space Processing and EOL Handling

ODF processing of whitespace characters is in conformance with the provisions of In conformance with the W3C XML specification [XML1.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 white-space characters depend on the specific definition of individual ODF elements, attributes, and their datatypes. See, in particular, section 5.1.1. 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.  This applies to the following white-space and end-of-line (EOL)[UNICODE] characters:

 . . .  deleting the remainder of the section〛. . .

As a consequence of the white-space and EOL processing rules, any CARRIAGE RETURN characters that are contained either in the text content of an element or in an attribute value must be encoded by the character entity

.  The same applies to the HORIZONTAL TABULATION and LINE FEED characters if they are contained in an attribute value.

N1309:10

COR2

-

2.1.1

Change the first paragraph of the section

The content models of the five root elements is summarized in the following table.  Note that
<office:document> may contain all supported top-level elements.  AllNone of the four subdocument root elements contain the complete data, but four combined dotogether contain the same information as an <office:document> element that contains the same subdocument root elements.

N0942:41

1.0-01

Y

2.1.2/
Version

Change the first paragraph of the subsection

All root elements take an
office:version attribute, which indicates which version of this specification it complies with.  The version number is in the format revision.version.  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

COR2

-

2.3.1/
Use Soft Page Breaks

Change the fifth and sixth paragraphs of the subsection

A generating application that stores soft page breaks shall indicate this by setting the
text:use-page-breaks attribute to true.  A generating application that does not store soft page breaks shall indicate that by omitting this attribute, or by setting it to false.

An application that does not support pagination and soft page-breaks, that modifies an OpenDocument file, which includes soft page-breaks, shall at least set the
text:use-page-breaks attribute to false (or remove it).  It should also remove the <text:soft-page-break> elements from the document but is not required to do so.

3694

WG6

Y

3.1.15

Change, in the last paragraph

 

The manner in which the language is represented is similar toThe syntax and semantics of the language tag are specifieddescribed 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.

N1078:1

COR2

-

3.1.18

Change, in the schema

 

<optional>

    <attribute name="meta:frame-count">

        <ref name="nonNegativeInteger"/>

    </attribute>

</optional>

<optional>

    <attribute name="meta:sentence-count">

        <ref name="nonNegativeInteger"/>

    </attribute>

</optional>

<optional>

    <attribute name="meta:syllable-count">

        <ref name="nonNegativeInteger"/>

    </attribute>

</optional>

<optional>

    <attribute name="meta:non-whitespace-character-count">

        <ref name="nonNegativeInteger"/>

    </attribute>

</optional>

3743

 TC

N

4.4.1/
Protected Sections

Change, at the end of the last paragraph

 

〛To avoid saving the password directly into the XML file, only a hash value of the password is stored.  The hashing is implementation-dependent.

N1078:18

COR2

-

4.7

〚In some forms of the ODF 1.1 specification, there may need to be some or all of these changes to have the correct form of the last sentence.  Change, in the last sentence of the section

 

See section 2.3.1:2.3.1 Use Soft Page BreaksUse Soft Page Breaks for details regarding soft page breaks.

2712

WG6

Y

5.1.1

Change, in the last line preceding the start of the Space Character Subsection

 

, in other words they are processed in the same way that [HTML4] processes them.

2713

TC

-

5.1.4

Change, in the beginning of the list

 

  Name

  Title

 

3797

 

WG6

Y

6.3

Change the first paragraph

 

OpenDocument text documents can contain〚 〛Most variable fields support different value types, such as numbers, dates, strings, and so on. In the OpenDocument file format, a variable must be declared at the beginning of a document.

N1309:1
N1309:2

COR2

-

6.7.2

Change the first paragraph

 

The text:fixed attribute specifies whether or not the value of a field element is fixed. 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. The defined values of the text:fixed attribute are:

  true: value of the field element where this attribrute appears is preserved.

  false: value of the field element where this attribute appears may be changed.

N1078:2

COR2

-

6.7.5

Change the text of the first list item

 

  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.

N0942:40

COR1

-

6.7.5

Change the text of the second list item

 

  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.  This value is not supported by all kinds of fields.

N0942:40

COR1

-

7.3.1/
Use Outline

Change at the end of the only paragraph

 

See section 7.1 for more information on index marks.

N1078:3

COR2

-

7.3.1/
Index Scope

Change the only paragraph

 

The text:index-scope attribute determines whether the table-of-content is generated for the whole document, or only for the current chapter.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

COR2

-

7.3.2

Change the end of first paragraph

 

〛for any outline level. (See below.)

N1078:6

COR2

-

7.4.1/
Use Caption

Change the only paragraph

 

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

COR2

-

7.7.1/
Copy Outline Levels

Change the entire text

 

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.

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

1.0-02

N

7.8.2

Insert a new paragraph after the only one

 

an XLink, which points to the resource containing the list of terms.

 

The format of an index mark file is implementation-dependent.

N1078:9

COR2

-

7.12

Change the first sentence

 

There are seveneight types of index entryies, as follows:

N1078:10
3798

COR2
WG6

-

8.1.1/
Protected

Change, at the end of the first paragraph

 

〛If a table is protected, all of the table's cell elements and the cell elements with a style:cell-protect attribute set to true a different value than none are protected.

N1078:11

COR2

-

8.1.1/
Protected

Change, at the end of the second paragraph

 

〛only a hash value of the password is stored within the table:protection-key attribute. The hashing is implementation-dependent.

N1078:18

COR2

-

8.1.2/
Default Cell Style

Change, in the first paragraph

 

〛Cells contained in the row that don't have a table:style-namestyle name attribute use this default cell style.

3799

WG6

Y

8.1.2/
Visibility

Change, in the only paragraph

 

The table:visibility attribute specifies whether the row is visible, filtered, or collapsed. Filtered and collapsed rows are not visible. Filtered rows are invisible, because a filter is applied to the table that does not select the table row. Collapsed rows have been made invisible by invisible in the UI directly.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

COR2

-

8.1.3/
Cell Content Validation

Change, in the last paragraph, following the schema fragment

 

See section 8.5.3 for more information on cell content validation and the <table:cell-content-validation> element.

3800

WG6

Y

8.1.3/
Value Type

Change, in the first sentence

 

The tableoffice:value-type attribute specifies the type of value that can appear in a cell.

N1078:14

COR2

-

8.1.3/
Cell Current Numeric Value

Change, in the first paragraph

 

The office:value attribute specifies the current numeric value of a cell. This attribute is only evaluated for cells that contain the following data typespresent only whenever there is an office:value-type attribute with one of the following values:

N1078:14

COR2

-

8.1.3/
Cell Current Currency

Change, in the first paragraph

 

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 currencythe 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

1.0-2

N

8.1.3/

Cell Current Date Value

Change, in the first paragraph

 

〛This attribute is present only evaluated for cells whose data typewhenever the office:value-type attribute is date.

N1078:14

COR2

-

8.1.3/
Cell Current Time Value

Change, in the first paragraph

 

〛This attribute is present only evaluated for cells whose data typewhenever the office:value-type attribute is time.

N1078:14

COR2

-

8.1.3/
Cell Current Boolean Value

Change, in the first paragraph

 

〛This attribute is present only evaluated for cells whose data typewhenever the office:value-type attribute is boolean.

N1078:14

COR2

-

8.1.3/
Cell Current String Value

Change, in the first paragraph

 

〛This attribute ismay be present only evaluated for cells whose data typewhenever the office:value-type attribute is string.

N1078:14

COR2

-

8.1.3/
Table Cell Protection

Change, in the first paragraph

 

The table:protected attribute protects the table cells. 〚

Change, in the last paragraph

 

〛 the tablestyle:cell-protect attribute for table cell styles 〚

N1078:15

COR2

-

8.2.1/
Default Cell Style

Change, in the first paragraph

 

〛cells that don't have a table:style-namestyle name attribute use this style when there is no default cell style specified for the cell's row as well.

3801

WG6

Y

8.3.4

Change, in the first paragraph

 

The <table:shapes> element contains all graphic shapes with an anchor on the table this element is a child ofthe elements that represent graphic shapes (see section 9.2) that are anchored on a table where this element occurs.〚

N1078:16

COR2

-

8.4.3

Change, in the first paragraph

 

The <table:detective> element contains information about what relationships between the current cell and other cells are revealed in the presentation of the table.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.

N1078:17

COR2

-

8.4.4

Change, in the first paragraph

 

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 in which those operations are applied (table:index attribute).  Once relationships between cells have been discovered, those cells are highlighted to show those relationships.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:

N1078:17

COR2

-

8.4.4/
Name

Change, in the only paragraph

 

The table:name attribute specifies the name of athe 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.

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

COR2

-

8.5.1

Change, at the end of the only paragraph

 

〛a hash value of the password is stored. The hashing is implementation-dependent.

N1078:18

COR2

-

8.5.2/

Search Criteria Must Apply to Whole Cell

Change the only paragraph

 

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 cellor not the specified search criteria, according to the regular expression used, must apply to the entire cell contents. 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

COR2

-

8.5.2/
Use Regular Expressions

Insert after the only paragraph

 

〛enabled for character string comparisons and when searching.

 

The syntax and semantics of the regular expressions are implementation-dependent.

N1309:4

COR2

-

8.5.3/
Condition

Change the entire text

 

The table:condition attribute specifies the condition that must evaluate to true for all cells the validation rule is applied to. The value of this attribute should be a namespace prefix, followed by an implementation-dependent 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 8.1.3 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 numbers of 1000 or greater.

N1078:21

COR2

-

8.6.10/
Function

Insert after the only paragraph

 

stdevp, sum, var and varp.

 

These functions are implementation-dependent.

N1078:23

COR2

-

8.7.1/
Condition Source Range Address

Change in the top row of the Example table

 

     G | GH | I

N1078:24

COR2

-

8.8

Change in the only paragraph

 

Data pilot tables allow it to analyze and evaluate data contained in spreadsheet tablesenable users to analyze and evaluate data extracted from a range of structured data sources, such as spreadsheet tables, database tables, or external service components. The data pilot tables element 〚

N1078:22

COR2

-

8.8.4/
Function

Insert after the only paragraph

 

〛that no function is applied at all.

 

These functions are implementation-dependent.

N1078:23

COR2

-

8.8.4/
Used Hierarchy

Change in the last sentence of the text

 

〛The value -1 means that no hierarchy should be applied at all.

N1078:26

COR2

-

8.8.7/
Function

Insert after the only paragraph

 

sum, var and varp.

 

These functions are implementation-dependent.

N1078:23

COR2

-

8.9/
Function

Insert after the only paragraph

 

sum, var and varp.

 

These functions are implementation-dependent.

N1078:23

COR2

-

8.11.7

Change the text

 

The <table:change-deletion> element specifiesd the id of a previously tracked change that gets deleted by the current change.

N0942:61

COR1

-

8.11.8/

Position

Change the text

 

The table:position attribute specifies the position where the deletion was made in the table.  Depending on the deletion type, Iit is either the number of a row, a column or a table.

N0942:62

COR1

-

8.11.14/

Formulas and Values

Change, in the first line

 

The change track table cells additionally supports 〚

N0942:63

COR1

-

9.1.3

Change, in the sentence immediately after the schema fragment

 

The <draw:layer> element> may contain the following elements:

3359

WG6

Y

9.1.4/

Master Page

Change, in the first list item

 

  Defines properties such as the size and borders of the drawing page

N0942:64

COR1

-

9.1.5

Change, near the bottom of the example

 

       <presentation:notes>

           <draw:text ...>This is a note</draw:text>

       </presentation:notes>

   </draw:page>

</office:body>

N0942:65

COR1

-

9.2.5

Change, in the sentence immediately after the schema fragment

 

The attributes that may be associated with the <draw:regular-polygon> element are:

3364

WG6

Y

9.2.5/

Sharpness

Change, in the last sentence

 

In general, if r is the radius of the polygon, and s is the sharpness, the inner corners are located on an ellipse whosethat's radius is r(100-s)/100.

N0942:65

COR1

-

9.2.6/

Path Data

Change, in the last sentence

 

Some implementations may only supports a subset 〚

N0942:42

COR1

-

9.2.7/

Radius

Change, in the last sentence

 

If this optional attribute isare not set, the position and 〚

N0942:43

COR1

-

9.2.9

Change, in the first paragraph

 

The <draw:connector> element represents a series of lines that are connected to the glue points of two other shapesconnected 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

COR2

-

9.2.11

Change, in the first paragraph

 

The <draw:measure> element represents a shape that is used to measure distances in drawings. The layout of the measure shape is implementation-dependent.

N1078:27

COR2

-

9.2.12/

Control

Change, in the first line

 

The attributes draw:control attribute specifies the control

N0942:44

COR1

-

9.2.15/
Caption-ID

Change, in the entire text

 

The draw:caption-id attribute establishes a relationship between a drawing objects and its caption. It takes a value of type IDREF. The value forof the draw:caption-id attribute is the target ID assigned to the <draw:text-box> (see section 9.3.1) used to represent the corresponding caption.

When a caption is assigned by a user agent, an id must be assigned to the element containing the text used to caption a drawing element. The drawing element being captioned must then be assigned the draw:caption-id attribute with an IDREF equivalent to the id <draw:text-box> containing the captioning text, thus establishing a relationship between the captioned text and the object captioned as needed for accessibility. Removing the caption should result in removing the draw:caption-id attribute of the object that was being captioned.

If the user agent supports a platform which provides a draw:caption-id relationship in its accessibility API, this relationship for captions should be used to fulfill the relationship.

See appendix E for guidelines how to use this attributeon the use of this provision to support accessibility.

3365

3366
3367

TC

N

9.2.18

Change, in the first sentence

 

The following defined attributes are common for all shapes that supports styles and no text.

N0942:45

COR1

-

9.2.18

Change, in the last sentence

 

The following defined attributes are common for all shapes that supports styles and text.

N0942:46

COR1

-

9.2.19/

Position

Change, in the first sentence

 

The svg:x and svg:y attributes specifyies the position

N0942:47

COR1

-

9.2.19/

Align

Change, in the first sentence

 

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 relatesdefines the horizontal and vertical edges to which a glue point with absolute position aligns.

N0942:48

COR1

-

9.2.19/

Escape Direction

Change, in the second sentence

 

The value horizontal means thatthe the connection line may escape to the left or to the right, the value vertical means that the connection may escape up or down.

N0942:49

COR1

-

9.2.20

Change the last sentence of the section

 

It is further supported byThe <svg:title> and <svg:desc> elements are also usable with layers (see section 9.1.3) and client side image maps (see section 9.3.10).

3368

TC

N

9.3

Change, in the first sentence

 

A frame is a rectangular container where that contains

 

N0942:50

COR1

-

9.3

Change, in the third list item after the schema fragment, by inserting a section and subsection reference

 

  Presentation class – see section 9.6.1 Class

3802

WG6

Y

9.3/

Relative Sizes

Change, in the fifth paragraph

 

The value scale-min equals the value scale, except that the

N0942:52

COR2

-

9.3/

Relative Sizes

Change, at the end of the last paragraph

 

〛real width and heights in the svg:width and svg:height or /fo:min-height attributes.

N0942:53

COR1

-

9.3/

Copy Frames

Change, in the last paragraph

 

〛This does not aeffect style and position information.  ThatThis is, the frame that has the 〚

N0942:54

N0942:55

COR1

-

9.3.1/

Minimum Height and Width

Change, in the only paragraph

 

The fo:min-height and fo:min-width attributes specify a minimum height andor width for a text box.  If they are existing, they overwrite the height andor width of a text box

N0942:56

N0942:57

COR1

-

9.3.3

Change,in the last item of the first list and the paragraph just before the schema fragment

 

  Objects that do not have an XML representation. These objects only have a binary representation.,  For example, an OLE object has no XML representationAn example for this kind of objects OLE objects (see [OLE]).

The <draw:object> element represents objects that have an XML representation. 〚

N0942:58

N0942:59

COR1

-

9.3.3/
Object Data

Change,in the first list item

 

  The xlink:href attribute links to the object representation, as follows:

         For objects that have an XML representation, the link references the sub package of the object.  The object is contained within this sub page exactly as it would as it is a document of its own.For objects that have an XML representation, the representation of the object is equivalent to a separate document representing that object, except it is stored in a folder in the document package.  The link references that folder.

N0942:60
3814

COR1
WG6

-
N

9.3.9

〚NOTE: In ODF 1.0 (and COR1), there was a section 9.3.9 that is not present in ODF 1.1 and is also removed in AMD1.  The ODF 1.1 section 9.3.9 corresponds to section 9.3.10 in COR1.]
 
  Change,in the first paragraph

 

Frames may behave like hyperlinks.  Such hyperlinks are represented by the <draw:a> element, where, the element's content 〚

N0942:1

COR1

-

9.3.9/
Link Target Frame

Change,in the last paragraph

 

〛 If the value of the this attribute is _blank, the xlink:show attribute value is new.  If the value of the this attribute is any of the other 〚

N0942:2

N0942:3

COR1

-

9.3.10/
Common Image Map Attributes and Elements

〚NOTE: In ODF 1.0 (andCOR1), there was a section 9.3.9 that is not present in ODF 1.1 and is also removed in AMD1.  The ODF 1.1 section 9.3.10 corresponds to section 9.3.11 in COR1.

Change,in the first list item

 

  Link, including an IRI and link target frame.

N0942:4

COR1

-

9.4

Insert, as the first paragraph of the section

 

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.

N0942:52

COR2

-

9.4.1/
3D Transforma-tion

Change,in the last list item

 

  rotatez (<rotate-angle> ), which specifies a rotation by <rotate-angle> degrees along the zy-axis.

N0942:5

COR1

-

9.4.5

Change,in the first paragraph

 

The <dr3d:extrude> element represents a three-dimensional extruded object based on athe 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

COR2

-

9.4.6

Change,in the first paragraph

 

The <dr3d:rotate> element represents a three-dimensional rotation shape based on athe 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

COR2

-

9.5

Change,at the end of the first paragraph

 

〛that provide a simple way to modify the the geometry.

N0942:6

COR1

-

9.5.2/
Extrusion First Light Harsh

Addition, after the only paragraph

 

The draw:extrusion-first-light-harsh attribute specifies if the primary light is harsh.

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.

N1078:32

COR2

-

9.5.2/
Extrusion Second Life Harsh

Addition, after the only paragraph

 

The draw:extrusion-second-light-harsh attribute specifies if the secondary light is harsh.

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.

N1078:32

COR2

-

9.5.3/
Enhanced Path

Change in the first paragraph

 

〛other instructions together with its parameter are describingtheir parameters determine the geometry of a shape which can be filled and/or stroked.〚

3815

WG6

N

9.5.3/
Enhanced Path

Change in the list of parameter enhancements  ? and $

 

If $ is preceding aprecedes an integer value, the value is a indexingindexes a draw:modifiers attribute. The corresponding modifier value is used as the parameter value then.

3816

WG6

N

9.5.3/
Enhanced Path

Change, at the beginning of the Description Entry for Command A

 

(x1,y1) and (x2,y2) is definingdefine the bounding box of an ellipse. 〚

3803

WG6

N

9.5.3/
Enhanced Path

Change, at the end of the Description Entry for Command A

 

〛the end-angle that is specified by point (x4, y4).

N0942:7

COR1

-

9.5.3/
Enhanced Path

Change, in the Description Entry for Command B

 

The same as the A command, except that an implied moveto to the starting point is done.

N0942:8

COR1

-

9.5.3/
Enhanced Path

Change, in the Description Entry for Command V

 

The same as the A command, except that an implied moveto to the starting point is done and the arc is drawn clockwise.

N0942:9

COR1

-

9.5.3/
Text Areas

Change, in the first paragraph

 

The draw:text-areas attribute specifies an optional list of text areas. The text areas are is used to position and align the text. If no text area is omittedspecified, the area of the shape itself is used. If a second text area is availablespecified, it is used for vertical text.

3818

WG6

N

9.5.3/
Text Areas

Change, in the second list item

 

  If $ is preceding aprecedes an integer value, the value is a indexingindexes a draw:modifiers attribute. The corresponding modifier value is used as the parameter value then.

N0942:10
3816

COR1
WG6

-
N

9.5.3/
Text Areas

Change, in the last paragraph

 

An example of the 〚

N0942:11

COR1

-

9.5.3/
Glue Points

Change, in the first paragraph

 

The draw:glue-points attribute specifies a list of object defined glue points. In contradiction toUnlike the user defined glue points which are defined by the <draw:glue-point> sub-element, the position of an object defined glue point can make use ofbe defined using equations and modifiers.

3819

WG6

N

9.5.3/
Glue Points

Change, in the second list item

 

  If $ is preceding aprecedes an integer value, the value is a indexingindexes a draw:modifiers attribute. The corresponding modifier value is used as the parameter value then.

N0942:12
3816

COR1
WG6

-
N

9.5.3/
Glue Points

Change, in the last paragraph

 

An example of the draw:glue-points attribute that defines two glue points, including modifier and equation usage, would be: draw:glue-points="0 ?Formula1 100 $1"

N0942:13
3804

COR1
WG6

-
N

9.5.3/
Glue Point Type

Change, in the last list item

 

  rectangle: the middle of each side of the shape bound rectangle specifies an object specific glue point

N0942:14

COR1

-

9.5.3/
Glue Point Leaving Directions

Change, in the last sentence

 

The position in the list is the same as the to be referenced glue-point 〚

N0942:15

COR1

-

9.5.5/
Equation

Change, in the last sentence

 

Due to the fact that modifier values may be changed 〚

N0942:16

COR1

-

9.5.5/
Formula

Change, in the first paragraph

 

〛A formula can make use of other formulas or modifier values by function and or modifier reference.

N0942:17

COR1

-

9.5.5/
Formula

Change, in the table heading row

 

Iidentifier

N0942:18

COR1

-

9.5.5/
Formula

Change, in the Description entry for Identifier top

 

The top position of the svg:viewBox attribute has to be used.

N0942:19

COR1

-

9.5.5/
Formula

Change, in the Description entry for Identifier right

 

The right position of the svg:viewBox attribute has to be used.

N0942:20

COR1

-

9.5.5/
Formula

Change, in the Description entry for Identifier bottom

 

The bottom position of the svg:viewBox attribute has to be used.

N0942:21

COR1

-

9.5.5/
Formula

Change, in the last paragraph

 

An example for the draw:formula attribute 〚

N0942:22

COR1

-

9.5.6/
Handle Position

Change, in the second list item

 

  If $ is preceding aprecedes an integer value, the value is a indexingindexes a draw:modifiers attribute. The corresponding modifier value is used as the parameter value then.

N0942:23
3816

COR1
WG6

-
N

9.7.2/
Effect

Change, in the tenth list item

 

  lines: the shape is faded in orour out by drawing

N0942:24

COR1

-

9.8.1

Change, at the end of the first paragraph

 

〛animate a single shape and or a shape's paragraphs.

N0942:25

COR1

-

9.8.2/
Command

Change, in the first sentence

 

For presentation documents, theThe anim:command

N0942:26

COR1

-

9.9/
Event Action

Change, in the eighth list item

 

  execute: another application is launched when this event is triggered. 〚

N0942:27

COR1

-

9.10

Change, in the first sentence

 

This section describes text fields that are specific to the text of drawing shapes that are contained in presentations.

N0942:28

COR1

-

9.11.4/
Source

Change, in the first sentence

 

The presentation:source attribute specifies whether the current date/time or the fixed content of the the field declaration is displayed.

N0942:29

COR1

-

10.3.1

Change, in the only paragraph

 

〛This element can contain fixed text or it can contain a <table:cell-address> element pointing to the text that should be displayed as the titlehave a table:cell-range attribute referencing the cell to be taken as the source of the text, over-riding any fixed text.〚

3369

TC

N

11.6

In the Value of script:event-name Attribute column of the table, correct the entry for form:startrealod, adjusting the alphabetical index entry accordingly

 

form:startrealodform:startreload

3805

WG6

Y

11.7.3

Change, at the end of the first paragraph

 

(See section 6.7.1 for more information on value and value type attributes.)

N0942:82

COR1

-

12.4

〚At the end of the last list item where the referenced section number is missing or an error is indicated, insert a cross reference by number to section 9.9 Presentation Events

 

〛Presentation events are described in section 9.9.

N0942:83

COR1

-

12.4.1/
Event Name

〚 In the Value of script:event-name Attribute column of the table, correct the entry for on-mouseout, adjusting the alphabetical index entry accordingly

 

on-mouseoutdom:mouseout

3806

WG6

Y

14.5.1

Change, at the end of the first paragraph

 

〛They have a text:style-name attribute that references these styles.

2716

WG6

Y

14.5.1

Add period at the end of the second paragraph

 

〛created in the corresponding cells.

 

3807

WG6

Y

14.5.1

In schema fragment lines 11519-11523 the <optional> element should include the <attribute> element, not the reverse.

11519      <optional>

11520            <attribute name="text:paragraph-style-name">

                                    <optional>

11521                                            <ref name="styleNameRef"/>

                                    </optional>

11522          </attribute>

11523    </optional>

3808

WG6

Y

14.7.9/
Country

Change, at the end of the first paragraph

 

〛The countrylanguage attribute can be used with all data style elements.

N0942:84

COR1

-

14.10.3/
Bullet Character

In the table, change the UNICODE Character Name entry for UNICODE Character Code U+2794

 

HEAVY WIDE-HEADED RIGHTWARDS ARROW

3809

WG6

Y

15.4.7

Change, in the last line of the only paragraph

See 9.2 of [CSS3Text] for details.

N0942:38

COR1

-

15.4.8

Change, in the next to last sentence of the only paragraph

 

See 9.3 of [CSS3Text] for details.

N0942:38

COR1

-

15.4.19

Change the first sentence of the second paragraph

The value of these propertyies is either an absolute length or a percentage as described in 78.8.4 of [XSL].

3691 N0942:30

WG6

-

15.4.29

Change, in the last line of the only paragraph

See 9.2 of [CSS3Text] for details.

N0942:38

COR1

-

15.4.30

Change, in the last line of the only paragraph

See 9.3 of [CSS3Text] for details.

N0942:38

COR1

-

15.4.33

Change, in the last line of the only paragraph

See 9.5 of [CSS3Text] for details.

N0942:38

COR1

-

15.4.34

Change, in the last line of the only paragraph

See 9.5 of [CSS3Text] for details.

N0942:38

COR1

-

15.4.38

Change the entire text

 

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.

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

COR2

-

15.5.20

Change in the first paragraph

 

〛If the attributes areis contained in a common style, the attributes' values may be also percentages.〚

3810

WG6

-

15.5.29

Change in the referencing of [XSL]

 

See 7.14.99.14 of [XSL] for details.

N0942:31
N0942:34

COR1

-

15.5.38

Change in the title of the section

15.5.38 Snap To Layout Grid

N0942:67

COR1

-

15.5.38

Change in the first sentence

 

The style:snap-to-layout-grid attribute

3811

WG6

N

15.10.1

Change the second paragraph

 

The style:row-height property specifies a fixed row height, while the style:min-row-height property specifies a fixedminimum height.

N0942:97

COR1

-

15.11.9

Change in the only paragraph

 

〛properties of the border lines of the cellpage. 〚

N0942:98

COR1

-

15.11.11

Change in the first referencing of [XSL]

 

See 7.15.13 of [XSL] for details.

N0942:32
N0942:35

COR1

-

15.12/
Font Name

Change in the only paragraph

 

The style:font-name attribute specifies 〚

N0942:96

COR1

-

15.14.12

Change in the first paragraph

 

〛This attribute is only interpreted if the value of the current style:repeat attribute is tiledrepeat. 〚

N1078:28

COR2

-

15.19

Change in the only paragraph

 

〛contained in all kinds of applications.  The layout of the connector is implementation-dependent.

N1078:25

COR2

-

15.20

Change in the only paragraph

 

〛contained in all kinds of applications.  The layout of the measure drawing objects is implementation-dependent.

N1078:29

COR2

-

15.22.5

Change in the first paragraph

 

The attribute dr3d:back-scale attribute specifies the proportion of the background geometry for lathe3D rotation and extrude objects.

N1078:32

COR2

-

15.22.8

Change in the first paragraph

 

The attribute dr3d:end-angle specifies the rotation angle for 3D latherotation objects. If it is the default (360), the lathe3D rotation object is closed and completely rotated. With smaller values less than 360 it is possible to define opened lathe3D rotation objects (segments). The then visible sides are closed and take into account the dr3d:back-scale and dr3d:edge-rounding attributes. With bigger values greater than 360 it is possible to create lathe3D rotation objects with more than one rotation. This will only have a visible effect when e.g., dr3d:back-scale is used.

N1078:32

COR2

-

15.22.9

Change in the only paragraph

 

The dr3d:close-front property specifies whether a front plane shall beis 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.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

COR2

-

15.22.10

Change in the only paragraph

 

The dr3d:close-back property describes if a back plane shall beis 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.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

COR2

-

15.24.4

Change in the only paragraph

 

The attribute dr3d:normals-directiontexture-mode is used to specify how the texture is modulated. 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:30
N1078:31

COR2

-

15.27.21

Change in the list entries

 

        right: Text may wrap around the rightleft side of the drawing shape.

N0942:92

COR1

-

15.27.31

Change in the first paragraph after the schema fragment

 

〛Without wrapping, the images overliey the text 〚

N0942:90
N0942:95

COR1

-

15.27.31

Change in the second paragraph after the schema fragment

 

〛This corresponds to the optionobject once-concurrently.

N0942:94

COR1

-

15.28.3

Change in the only paragraph

 

The draw:frame-margin-horizontal and draw:frame-margin-vertical attributes〚

N0942:88

COR1

-

15.28.4

Change the only paragraph

 

The attributes described in 15.28.5 and 15.28.6this section can be assigned to a graphic style that is assigned to objects.

N0942:93

COR1

-

15.28.6

Change the first sentence

 

For embedded OLE objects, the draw:ole-draw-aspect attribute 〚

3023

WG6

-

15.30.4

Change the only paragraph

 

The width and height of each symbol can be set using the attribute chart:symbol-width and chart:symbol-heightlength.

N0942:87

COR1

-

15.30.9

Change the last sentence

 

The line interpolation is determined by the chart:interpolationsplines property.

N0942:86

COR1

-

15.31.2

Change the first sentence

 

To determine whether or not an axis object is visible, use the chart:axis-visible style property.

N0942:85

COR1

-

15.31.3

Change in the first two paragraphs

 

However, the chart:axis-logarithmic attribute is set to false.

The optional chart:axis-logarithmic attribute can be used to cause logarithmic scaling on an axis. 〚

N0942:81

COR1

-

15.31.4

Change the text

 

The tick mark properties are used to specify the existence of tick marks at an axis. The major marks are drawn with respect to the major interval that may be specified by the chart:axis-interval-major attribute. The minor tick marks refer to the chart:axis-interval-minor attribute. 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 attributesproperties are specified for one mark, one tick mark is drawn that crosses the axis.

N0942:81
N1078:36
3552

COR1
COR2

-

15.36

Change in the first paragraph

 

〛They are contained in a <style:style-drawing-page-properties> element.

N0942:77

COR1

-

15.36

Change end of list immediately before 15.36.1

  Display Date and Time

  Transition Type or Family

  Transition Subtype

  Transition Direction

  Fade Color

N0942:75

 

COR1

-

15.36.8

Change in the first paragraph

 

The attribute presentation:page-duration controls the amount of time 〚

N0942:76

COR1

-

15.36.10

Change the text

 

Sound effects can be added to your presentation pages using the element presentation:sound. It must be included in the <style:presentation-properties> element.

N0942:72

COR1

-

16.1

In the list item for custom data types,change in the first paragraph of the entry for length.  Zoom the text to clearly see the difference in the quotation marks.

 

       length

A (positive, zero, or negative) physical length, consisting of magnitude and unit, in conformance with 5.9.11 of [XSL].  Supported units are cm, mm, in, pt, and pc. 〚

 

N0942:74

COR1
WG6

-

16.1

In the list item for custom data types,change the entry for valueType.

 

       valueType

A list of value types supported value typesfor certain generic values, such as string or date.

N0942:74

COR1

-

17.6

Change in the last paragraph

 

In order to conform to the Thumbnail Managing Standard (TMS) at www.freedesktop.org, Tthumbnails must be saved as 24bit, non-interlaced PNG image with full alpha transparency.

N0942:74

COR1

-

17.7.3/
Media Type

Change in the text

 

〛For a full list of mime types see http://www.isi.edu/in-notes/iana/assignments/media-types/media-typeshttp://www.iana.org/assignments/media-types/. As an example, all XML streams have the media type "text/xml".

N0942:36
N0942:68

COR1

-

17.7.4

Change the first sentence after the schema fragment

 

The <manifest:encryption-data> element contains the following elements:

N1078:33

COR2

-

17.7.6/
Key Derivation Name

Change in the text

 

The manifest:key-derivation-name attribute specifies the name of the algorithm used to derive the encryption keyname.

N0942:69

COR1

-

Appendix B

In the References entry for [ZIP], change the URL

 

ftp://ftp.uu.net/pub/archiving/ziphttp://www.info-zip.org/doc/appnote-19970311-iz.zip

N1309:8

3553

1.0-02

TC

N

Appendix D

In the table entry for Section 12.2, change the Title

 

Number Format for page numbers, etc.

N0942:71

COR1

-

Appendix D

In the table entry for Section 15.16, change the Title

 

Text and Text Alignment Properties

N0942:71

COR1

-

Appendix E.4

Change the only paragraph

 

Please see the additional, detailed Accessibility Guidelines http://docs.oasis-open.org/office/office-accessibility/v1.0/. http://docs.oasis-open.org/office/office-accessibility/guidelines. That more comprehensive document will be the up-to-date set of recommendations for what all  OpenDocument applications should do in order to fully support accessibility.

3817

WG6

N

Appendix F/
Numeric Digits Presentation and Calendars

In the last sentence of the last paragraph

 

number:calendar attribute specified in section 14.7.11.

3813

WG6

N

3       Conformance

This informative document has no conformance clauses.

 

Appendix A                  Acknowledgments

The OASIS Open Document Format for Office Applications (OpenDocument) TC gratefully acknowledges the contribution and partnership of the ISO/IEC JTC1 SC34 WG6 working group on ODF Maintenance for  its participation in the creation of technical alignment between OASIS ODF 1.1 and the International Standard.

Participants

At the OpenDocument TC the following individuals have participated in the creation of this specification and are gratefully acknowledged.

 

Chieko Asakawa, IBM

Thorsten Behrens, Novell

Camilla Boemann, KDE e.V.

Suresh Chande, Nokia Corporation

Robin Cover, OASIS

Jerome Dumonteil, Ars Aperta

Patrick Durusau, Individual Member

Cherie Ekholm, Microsoft Corporation

Jean Gouarne, Ars Aperta

Andreas J. Guelzow, Individual Member

Zhun Guo, Individual Member

Dennis E. Hamilton, Individual Member

Bart Hanssens, Fedict

Donald Harbison, IBM

John Haug, Microsoft Corporation

Regina Henschel, The Document Foundation

Mingfei Jia, IBM

Peter Junge, Beijing Sursen Electronic Technology Co., Ltd.

Kazmer Koleszar, MultiRacio Ltd.

Peter Korn, Oracle Corporation

Jirka Kosek, Individual Member

Robin LaFontaine, Individual Member

David LeBlanc, Microsoft Corporation

Fong Lin, Novell

Yue Ma, IBM

Doug Mahugh, Microsoft Corporation

Gervase Markham, Mozilla Corporation

James Mason, ISO/IEC JTC1/SC34

Tristan Mitchell, Individual Member

Eric Patterson, Microsoft Corporation

Steven Pemberton, Stichting Centrum voor Wiskunde & Informatica

Chris Rae, Microsoft Corporation

Pter  Rakyta, MultiRacio Ltd.

Asokan Ramanathan, IBM

Andre Rebentisch, Ars Aperta

Douglas Schepers, Individual Member

Svante Schubert, Individual Member

Charles  Schulz, Ars Aperta

Richard Schwerdtfeger, IBM

Wei Gui Shi, IBM

Yan Shi, Beijing Sursen Electronic Technology Co., Ltd.

Jomar Silva, OpenDocument Format Alliance

Keld Simonsen, ISO/IEC JTC1/SC34

Michael Stahl, Red Hat

Louis Suarez-Potts, Individual Member

Hironobu Takagi, IBM

Malte Timmermann, Oracle Corporation

John Tolbert, The Boeing Company

Jos van den Oever, KED e.V.

Alex Wang, Beijing Sursen Electronic Technology Co., Ltd.

Robert Weir, IBM

David A. Wheeler, Individual Member

Olvier-Rainer Wittmann, IBM

Kohei Yoshida, Novell

Helen Yue, IBM

Thorsten Zachmann, Nokia Corporation

 

Appendix B                  Issues Not Applicable to ODF 1.1

Some items in previous errata and corrigenda for ODF 1.0 are not reflected in ODF 1.1 Errata 01.  The omissions are because they do not apply to the ODF 1.1 text or they have been disposed of in some other manner.

This informative Appendix provides an accounting for those so it can be understood why those items and related issues are not transposed to ODF 1.1.  This material can also be used to verify that all previous issues and defect reports have been accounted for and none have been overlooked.

Section/
Subsection

Explanation

Issue

Source

Amd?

15.27.22

In the schema fragment, the change of -treshold to -threshold has already been made in ODF 1.1.

N0942:91

COR1

-

15.31.3

COR1 makes the following changes:

 

Change the last paragraph (preceding the last schema fragment)

 

chart:interval-major, chart:interval-minor-divisor – set major and minor interval for ticks or markings on the axis. The chart:interval-major defines the interval value. The minor interval is determined by dividing the chart:interval-major value by the chart:interval-minor-divisor.

However, the ODF 1.0 schema defines only chart:interval-minor.  For ODF 1.1, the inconsistency is resolved by defining chart:interval-minor-divisor in the schema and leaving the original text intact.  ODF 1.2 also uses chart:interval-minor-divisor alone.

N0942:80
3552

COR1

-

Appendix B

COR1 makes a change to the URL for [DOMEvents].  That reference does not occur in ODF 1.1.  Instead, there are new references, [DOMEvents2] and [DOMEvents3] to which the COR1 change does not apply.  IS 26300:2006/AMD1 makes an appropriate adjustment as part of ODF 1.1 alignment.

N0942:39

COR1

-

Appendix C                  IS 26300:2006/Amd1 Reconciliation

There are errata instructions in this ODF 1.1 Errata 01 that are not reflected in IS 26300:2006/Amd1.    This Appendix identifies each of them and where they apply. 

The explanation includes instructions for making aligning changes to an IS 26300:2006 with COR1, COR2, and AMD1 applied.  In some cases the correction is for a deviation introduced in COR1 or COR2.

 

Section/
Subsection

Explanation

Issue

Source

Amd?

3.1.18

Change, in the schema, starting at line 791

 

<optional>

    <attribute name="meta:frame-count">

        <ref name="nonNegativeInteger"/>

    </attribute>

</optional>

<optional>

    <attribute name="meta:sentence-count">

        <ref name="nonNegativeInteger"/>

    </attribute>

</optional>

<optional>

    <attribute name="meta:syllable-count">

        <ref name="nonNegativeInteger"/>

    </attribute>

</optional>

<optional>

    <attribute name="meta:non-whitespace-character-count">

        <ref name="nonNegativeInteger"/>

    </attribute>

</optional>

3743

 TC

N

7.7.1/
Copy Outline Levels

The correction for this section in ODF 1.0 Errata 02 was transposed to IS 26300:2006/COR2 incorrectly.  This change repairs IS 26300:2006/COR2

 

〚In the list defined values, correct the first item〛

 

  false: no indentation is added

N1078:8

1.0-2

N

8.1.3/
Cell Current Currency

The correction for this section in ODF 1.0 Errata 02 was transposed to IS 26300:2006/COR2 incorrectly.  This change repairs IS 26300:2006/COR2

 

Change, in the first paragraph

 

The office:currency attribute specifies the currency system in which the value of the office:value attribute is expressed.

N1078:14

1.0-2

N

9.2.15/
Caption-ID

Change, in the entire text

 

The draw:caption-id attribute establishes a relationship between a drawing objects and its caption. It takes a value of type IDREF. The value forof the draw:caption-id attribute is the target ID assigned to the <draw:text-box> (see section 9.3.1) used to represent the corresponding caption.

When a caption is assigned by a user agent, an id must be assigned to the element containing the text used to caption a drawing element. The drawing element being captioned must then be assigned the draw:caption-id attribute with an IDREF equivalent to the id <draw:text-box> containing the captioning text, thus establishing a relationship between the captioned text and the object captioned as needed for accessibility. Removing the caption should result in removing the draw:caption-id attribute of the object that was being captioned.

If the user agent supports a platform which provides a draw:caption-id relationship in its accessibility API, this relationship for captions should be used to fulfill the relationship.

See appendix E for guidelines how to use this attributeon the use of this provision to support accessibility.

3365
3366
3367

TC

N

9.2.20

ODF 1.1 Errata 01 alignment is achieved by applying this correction to a change introduced in IS 26300:2006/AMD1.

 

Change the last sentence of the section

 

It is further supported byThe <svg:title> and <svg:desc> elements are also usable with layers (see section 9.1.3) and client side image maps (see section 9.3.10).

3368

TC

N

9.3.3/
Object Data

The second part of this errata item (replacing xlink by link) applies to text introduced by IS 26300:2006/COR1

Change,in the first list item

 

  The xlink:href attribute links to the object representation, as follows:

         For objects that have an XML representation, the link references the sub package of the object.  For objects that have an XML representation, the representation of the object is equivalent to a separate document representing that object, except it is stored in a folder in the document package.  The xlink references that folder.

N0942:60
3814

COR1
WG6

-
N

9.5.3/
Enhanced Path

Change in the first paragraph

 

〛other instructions together with its parameter are describingtheir parameters determine the geometry of a shape which can be filled and/or stroked.〚

3815

WG6

N

9.5.3/
Enhanced Path

This change applies to a passage as it already appears in ODF 1.1 and as it appears after IS 26300:2006/AMD1.

 

Change in the list of parameter enhancements  ? and $

 

If $ is preceding aprecedes an integer value, the value is a indexingindexes a draw:modifiers attribute. The corresponding modifier value is used as the parameter value then.

3816

WG6

N

9.5.3/
Enhanced Path

Change, at the beginning of the Description Entry for Command A

 

(x1,y1) and (x2,y2) is definingdefine the bounding box of an ellipse. 〚

3803

WG6

N

9.5.3/
Text Areas

Change, in the first paragraph

 

The draw:text-areas attribute specifies an optional list of text areas. The text areas are is used to position and align the text. If no text area is omittedspecified, the area of the shape itself is used. If a second text area is availablespecified, it is used for vertical text.

3818

WG6

N

9.5.3/
Text Areas

This change modifies the text as modified by COR1. 

 

Change, in the second list item

 

  If $ is precedingprecedes an integer value, the value is indexingindexes a draw:modifiers attribute. The corresponding modifier value is used as the parameter value then.

N0942:10
3816

COR1
WG6

-
N

9.5.3/
Glue Points

Change, in the first paragraph

 

The draw:glue-points attribute specifies a list of object defined glue points. In contradiction toUnlike the user defined glue points which are defined by the <draw:glue-point> sub-element, the position of an object defined glue point can make use ofbe defined using equations and modifiers.

3819

WG6

N

9.5.3/
Glue Points

This change modifies the text as modified by COR1. 

 

Change, in the second list item

 

  If $ is precedingprecedes an integer value, the value is indexingindexes a draw:modifiers attribute. The corresponding modifier value is used as the parameter value then.

N0942:12
3816

COR1
WG6

-
N

9.5.3/
Glue Points

The correction to An is from COR1.

 

Change, in the last paragraph

 

An example of the draw:glue-points attribute that defines two glue points, including modifier and equation usage, would be: draw:glue-points="0 ?Formula1 100 $1"

N0942:13
3804

COR1
WG6

-
N

9.5.6/
Handle Position

This change modifies the text as modified by COR1.

 

Change, in the second list item

 

  If $ is precedingprecedes an integer value, the value is indexingindexes a draw:modifiers attribute. The corresponding modifier value is used as the parameter value then.

N0942:23
3816

COR1
WG6

-
N

10.3.1

Change, in the only paragraph

 

〛This element can contain fixed text or it can contain a <table:cell-address> element pointing to the text that should be displayed as the titlehave a table:cell-range attribute referencing the cell to be taken as the source of the text, over-riding any fixed text.〚

3369

TC

N

15.5.38

Change in the first sentence

 

The style:snap-to-layout-grid attribute

3811

WG6

N

15.31.3

〚This correction rescinds an IS 26300 deviation introduced via IS 26300:2006/COR1.

 

Change in the last paragraph (preceding the last schema fragment)

 

chart:interval-major, chart:interval-minor-divisor – set major and minor interval for ticks or markings on the axis. The chart:interval-major defines the interval value. The minor interval is determined by dividing the chart:interval-major value by the chart:interval-minor-divisor.

 

3552

TC

N

Appendix B

In the References entry for [ZIP], change the URL

 

ftp://ftp.uu.net/pub/archiving/ziphttp://www.info-zip.org/doc/appnote-19970311-iz.zip

N1309:8

3553

1.0-2

TC

N

Appendix E.4

Change the only paragraph

 

Please see the additional, detailed Accessibility Guidelines http://docs.oasis-open.org/office/office-accessibility/v1.0/. http://docs.oasis-open.org/office/office-accessibility/guidelines. That more comprehensive document will be the up-to-date set of recommendations for what all  OpenDocument applications should do in order to fully support accessibility.

3817

WG6

N

Appendix F/
Numeric Digits Presentation and Calendars

In the last sentence of the last paragraph

 

number:calendar attribute specified in section 14.7.11.

3813

WG6

N