---

Defect Report on ISO/IEC 26300:2006

Japanese national member body for SC34

December 3, 2007

1. Section 9.3.10, 27th line on page 310
   Current description:
   Such hyperlinks are represented by the  element, where. the 
   element's content is the frame that should be the source of the link.
   Proposal:
   The period after "where" should be removed from the current sentence as 
   follows:
   Such hyperlinks are represented by the  element, where the 
   element's content is the frame that should be the source of the link.
   
   

2. Section 9.3.10, 32nd line on page 311
   Current description:
   If the value of the this attribute is _blank, the xlink:show attribute 
   value is new.
   Proposal:
   The second "the" should be removed from the current sentence as follows:
   If the value of this attribute is _blank, the xlink:show attribute value 
   is new.
   
   

3. Section 9.3.10, 33rd line on page 311
   Current description:
   If the value of the this attribute is any of the other value options, the 
   value of the xlink:show attribute is replace.
   Proposal:
   The second "the" should be removed from the current sentence as follows:
   If the value of this attribute is any of the other value options, the 
   value of the xlink:show attribute is replace.
   
   

4. Section 9.3.11, 15th line on page 315
   Current description:
   Link, including a IRI and link target frame.
   Proposal:
   "a" should be "an" as follows:
   Link, including an IRI and link target frame.
   
   

5. Section 9.4.1, 38th line on page 319
   Current description:
   rotatez ( ), which specifies a rotation by  
   degrees along the y-axis.
   Proposal:
   "y-axis" should be "z-axis" as follows:
   rotatez ( ), which specifies a rotation by  
   degrees along the z-axis.
   
   

6. Section 9.4.6, 24th line on page 323
   Current description:
   This geometry may be visualized in office application user interfaces, for 
   instance by displaying interaction handles, that provide a simple way to 
   modify the the geometry.
   Proposal:
   The last "the" should be removed from the current sentence as follows:
   This geometry may be visualized in office application user interfaces, for 
   instance by displaying interaction handles, that provide a simple way to 
   modify the geometry.
   
   

7. Section 9.5.3, 36th line on page 334
   Current description:
    Parameters: (x1 y1 x2 y2 x3 y3 x y)+
    Description: (x1, y1) and (x2, y2) is defining the bounding box of a 
   ellipse. A line is then drawn from the current point to the start angle of 
   the arc that is specified by the radial vector of point (x3, y3) and then 
   counter clockwise to the end-angle that is specified by point (x4, y4). 
   Proposal:
   Change x4 and y4 in the description to x and y, respectively, as follows:
   (x1, y1) and (x2, y2) is defining the bounding box of a ellipse. A line is 
   then drawn from the current point to the start angle of the arc that is 
   specified by the radial vector of point (x3, y3) and then counter 
   clockwise to the end-angle that is specified by point (x, y).
   
   

8. Section 9.5.3, 37th line on page 334
   Current description:
   The same as the "A" command, except that a implied moveto to the starting 
   point is done.
   Proposal:
   "a" should be "an" as follows:
   The same as the "A" command, except that an implied moveto to the starting 
   point is done. 
   
   

9. Section 9.5.3, 40st line on page 334
   Current description:
   The same as the "A" command, except that a implied moveto to the starting 
   point is done and the arc is drawn clockwise.
   Proposal:
   "a" should be "an" as follows:
   The same as the "A" command, except that an implied moveto to the starting 
   point is done and the arc is drawn clockwise.
   
   

10. Section 9.5.3, 3rd line on page 336
    Current description:
    If "$" is preceding a integer value, the value is a indexing a 
    draw:modifiers attribute.
    Proposal:
    The first "a" should be "an" and the second "a" should be removed as 
    follows:
    If "$" is preceding an integer value, the value is indexing a 
    draw:modifiers attribute.
    
    

11. Section 9.5.3, 5th line on page 336
    Current desciption:
    A example of the draw:text-areas attribute that defines two text areas, 
    including modifier and equation usage, would be:
    Proposal:
    "A" should be "An" as follows:
    An example of the draw:text-areas attribute that defines two text areas, 
    including modifier and equation usage, would be:
    
    

12. Section 9.5.3, 23rd line on page 336
    Current description:
    If "$" is preceding a integer value, the value is a indexing a 
    draw:modifiers attribute.
    Proposal:
    "a" should be "an" and the second "a" should be removed as follows:
    If "$" is preceding an integer value, the value is indexing a 
    draw:modifiers attribute.
    
    

13. Section 9.5.3, 25th line on page 336
    Current description:
    A example of the draw:glue-points attribute that defines two glue points, 
    including modifier and equation usage, would be:
    Proposal:
    "A" should be "An" as follows:
    An example of the draw:glue-points attribute that defines two glue points, 
    including modifier and equation usage, would be:
    
    

14. Section 9.5.3, 40st line on page 336
    Current description:
    the middle of each side of the shape bound rectangle specifies a object 
    specific glue point
    Proposal:
    "a" should be "an" as follows:
    the middle of each side of the shape bound rectangle specifies an object 
    specific glue point
    
    

15. Section 9.5.3, 12th line on page 337
    Current description:
    The position in the list is the same as the to be referenced glue-point of 
    the draw:glue-points attribute.
    Proposal:
    "to be" should be removed as follows:
    The position in the list is the same as the referenced glue-point of the 
    draw:glue-points attribute.
    
    

16. Section 9.5.5, 42nd line on page 338
    Current description:
    Due to the fact that modifier values may changed by interaction it is a 
    convenient way to integrate dynamic values into the shape geometry.
    Proposal:
    "be" should be inserted between "may" and "changed" as follows:
    Due to the fact that modifier values may be changed by interaction it is a 
    convenient way to integrate dynamic values into the shape geometry.
    
    

17. Section 9.5.5, 18th line on page 339
    Current description:
    A formula can make use of other formulas or modifier values by function 
    and or modifier reference.
    Proposal:
    "and or" should be "or" as follows:
    A formula can make use of other formulas or modifier values by function or 
    modifier reference.
    
    

18. Section 9.5.5, 1st line on page 340
    Current description:
    identifier
    Proposal:
    "identifier" should be capitalized to "Identifer" in the same way as 
    "Description."
    
    

19. Section 9.5.5, 3rd line on page 340
    Current description:
    The top position the svg:viewBox attribute has to be used.
    Proposal:
    "of" should be inserted after "position" as follows:
    The top position of the svg:viewBox attribute has to be used.
    
    

20. Section 9.5.5, 4th line on page 340
    Current description:
    The right position the svg:viewBoxattribute has to be used.
    Proposal:
    "of" should be inserted after "position" as follows:
    The right position of the svg:viewBoxattribute has to be used.
    
    

21. Section 9.5.5, 5th line on page 340
    Current description:
    The bottom position the svg:viewBox attribute has to be used.
    Proposal:
    "of" should be inserted after "position" as follows:
    The bottom position of the svg:viewBox attribute has to be used.
    
    

22. Section 9.5.5, 14th line on page 340
    Current description:
    A example for the draw:formula attribute would be:
    Proposal:
    "A" should be "An" as follows:
    An example for the draw:formula attribute would be:
    
    

23. Section 9.5.6, 34th line on page 341
    Current description:
    If "$" is preceding a integer value, the value is a indexing a 
    draw:modifiers attribute.
    Proposal:
    The first "a" should be "an" and the second "a" should be removed as 
    follows:
    If "$" is preceding an integer value, the value is indexing a 
    draw:modifiers attribute.
    
    

24. Section 9.7.2, 6th line on page 349
    Current description:
    the shape is faded in our out by drawing or removing line by line, either 
    horizontally or vertically, in a random fashion.
    Proposal:
    "our" should be "or" as follows:
    the shape is faded in or out by drawing or removing line by line, either 
    horizontally or vertically, in a random fashion.
    
    

25. Section 9.8.1, 9th line on page 354
    Current description:
    An effect is a combination of one or more animation elements that animate 
    a single shape and or a shape's paragraphs.
    Proposal:
    "and or" should be "or" as follow:
    An effect is a combination of one or more animation elements that animate 
    a single shape or a shape's paragraphs.
    
    

26. Section 9.8.2, 16th line on page 357
    Current description:
    For presentation documents, The anim:command attribute of the 
     element (see section 13.6.1) can have the following values:
    Proposal:
    "The" should be "the" as follows:
    For presentation documents, the anim:command attribute of the 
     element (see section 13.6.1) can have the following values:
    
    

27. Section 9.9, 35th line on page 360
    Current description:
    execute: another application is lunched when this event is triggered.
    Proposal:
    "lunched" should be changed to "launched" as follows:
    execute: another application is launched when this event is triggered.
    
    

28. Section 9.10, 3rd line on page 363
    Current description:
    This section describes text fields that are specific to the text of 
    drawing shapes that are contained presentations.
    Proposal:
    "in" should be inserted before "presentations" as follows:
    This section describes text fields that are specific to the text of 
    drawing shapes that are contained in presentations.
    
    

29. Section 9.11.4, 19th line on page 365
    Current description:
    The presentation:source attribute specifies whether the current date/time 
    or the fixed content of the the field declaration is displayed.
    Proposal:
    The duplicated "the" should be removed as follows:
    The presentation:source attribute specifies whether the current date/time 
    or the fixed content of the field declaration is displayed.
    
    

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

31. In 15.5.29, subsection 7.9.14 of XSL is referenced, but 
    it should be 7.19.4.
    
    

32. In 15.11.11, subsection 7.5.13 of XSL is referenced, but 
    it should be 7.15.13.
    
    

33. In 15.4.19, subsection 8.8.4 of XSL is referenced, but it 
    should be 7.8.4.
    
    

34. In 15.5.29, subsection 7.9.14 of XSL is referenced, but 
    it should be 7.19.4.
    
    

35. In 15.11.11, subsection 7.5.13 of XSL is referenced, but 
    it should be 7.15.13.
    
    

36. The IRI for the list of media types should be changed.  
    It is now http://www.iana.org/assignments/media-types/
    
    

37. The URI for the Thumbnail Managing Standard(TMS) should be 
    changed, but I do not know what is the latest URI.
    
    

38. An obsolete working draft of CSS3 text is
    referenced in a normative manner.
    
    

39. An obsolete candidate recommendation of DOM3 event is
    referenced in a normative manner.
    
    

40.  In 2.1.1, the first value of text:display is defined as follows:
    
    	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.
    
    First, what does "these cases" mean?  The cases that fields do not 
    support this value?  Second, what does "respectively" mean?  
    I guess that there are two cases.  In the first case, the permissible 
    values are value or none; in the second case, they are value or formula.  
    But I have no ideas about what the two cases are.
    
    I have the same question about the second value of text:display, namely
    formula.
    
    
    
    

41. Unclear sentence in 2.1.1
    
     	Note that  may contain all supported top-level
    	elements. None of the four subdocument root elements contain the 
    	complete data, but four combined do.
    
    What does "but four combined do" mean?  Four subdocument root elements 
    collectively contain the complete data?
    
    

42. Section 9.2.6, 4th line on page 279
    
    Current description:
    Some implementations may only supports a subset of the SVG path 
    specification, for instance no mixtures of open and closed curves for one 
    shape, or no elliptical arc command.
    Proposal:
    "supports" should be "support" after the modal verb "may" as follows:
    Some implementations may only support a subset of the SVG path 
    specification, for instance no mixtures of open and closed curves for one 
    shape, or no elliptical arc command.
    
    

43. Section 9.2.7, 8th line on page 280
    Current description:
    If this optional attribute are not set, the position and size attributes 
    are used to create circle.
    Proposal:
    The first "are" should be "is" as the subjective has a singular form:
    If this optional attribute is not set, the position and size attributes 
    are used to create circle.
    
    

44. Section 9.2.12, 17th line on page 287
    Current description:
    The attributes draw:control attribute specifies the control within a form 
    (see section 11.5.2) that is linked to the control shape.
    Proposal:
    "attributes" should be removed from the current sentence as follows:
    The draw:control attribute specifies the control within a form (see 
    section 11.5.2) that is linked to the control shape.
    
    

45. Section 9.2.18, 29th line on page 295
    Current description:
    The following defined attributes are common for all shapes that supports 
    styles and no text.
    Proposal:
    "supports" should be "support" as follows:
    The following defined attributes are common for all shapes that support 
    styles and no text.
    
    

46. Section 9.2.18, 38th line on page 295
    Current description:
    The following defined attributes are common for all shapes that supports 
    styles and text.
    Proposal:
    "supports" should be "support" as follows:
    The following defined attributes are common for all shapes that support 
    styles and text. 
    
    

47. Section 9.2.19, 21st line on page 296
    Current description:
    The svg:x and svg:y attributes specifies the position of the glue point.
    Proposal:
    "specifies" should be "specify" as follows:
    The svg:x and svg:y attributes specify the position of the glue point.
    
    

48. Section 9.2.19, 39th line on page 296
    Current description:
    The attribute draw:align specifies the alignment behavior of the glue 
    point if the drawing object is resized and the shape edge to which the 
    glue point's position relates.
    Proposal:
    The description in "if" clause should be paraphrased. For example, please 
    advise whether the following understanding is correct or not. It it is the 
    case, please correct the description accordingly: 
    The attribute draw:align specifies the alignment behavior of the glue 
    point if the drawing object is resized and aligned to the shape edge to 
    which the glue point's position relates.
    
    

49. Section 9.2.19, 12th line on page 297
    Current description:
    The value horizontal means the the connection line may escape to the left 
    or to the right, the value vertical means that the connection line may 
    escape up or down.
    Proposal:
    The first "the" in "the the" should be "that." The words "left" and
    "right" are in a different font, while "up" and down" are not.  Since
    all of them are values of the draw:escape-direction attribute, 
    the same font should be used.
    
    

50. Section 9.3, 24th line on page 297
    Current description:
    A frame is a rectangular container where that contains enhanced content 
    like text boxes, images or objects.
    Proposal:
    "where" should be removed as follows:
    A frame is a rectangular container that contains enhanced content like 
    text boxes, images or objects.
    
    

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

52. Section 9.3, 21st line on page 299
    Current description:
    The value scale-min equals the value scale, except that the calculated 
    width or height is a minimum height rather than an absolute one.
    Proposal:
    Different fonts are used for the word "scale" and "scale-min".  
    
    

53. Section 9.3, 25th line on page 299
    Current description:
    To support application that don't support relative with and heights, 
    applications that save the attributes style:rel-width or style:rel-height 
    should also provide the real width and heights in the svg:width and 
    svg:height/fo:min-height attributes.
    
    Proposal:
    "/" should be "or".
    
    

54. Section 9.3, 5th line on page 300
    Current description:
    This does not effect style and position information.
    Proposal:
    "effect" should be "affect" considering the semantics as follows:
    This does not affect style and position information. 
    
    

55. Section 9.3, 5th line on page 300
    Current description:
    This is, the frame that has the draw:copy-of attribute has its own style 
    and position information and does not use the one of the referenced frame.
    Proposal:
    "This" should be "That" as follows:
    That is, the frame that has the draw:copy-of attribute has its own style 
    and position information and does not use the one of the referenced frame.
    
    

56. Section 9.3.1, 12th line on page 301
    Current description:
    The fo:min-height and fo:min-width attributes specify a minimum height or 
    width for a text box.
    Proposal:
    "or" should be "and" to synchronize with two attributes connected with 
    "and" as follows:
    The fo:min-height and fo:min-width attributes specify a minimum height and 
    width for a text box.
    
    

57. Section 9.3.1, 14th line on page 301
    Current description:
    If they are existing, they overwrite the height or width of a text box 
    specified by the svg:height and svg:width attributes of the surrounding 
    draw:frame element.
    Proposal:
    "or" should be "and" as follows:
    If they are existing, they overwrite the height and width of a text box 
    specified by the svg:height and svg:width attributes of the surrounding 
    draw:frame element.
    
    

58. Section 9.3.3, 5th line on page 304
    Current description:
    These objects only have a binary representation, An example for this kind 
    of objects OLE objects (see [OLE]).
    Proposal:
    The first sentence should end with a period "." and the second sentence 
    should have "is" as follows:
    These objects only have a binary representation. An example for this kind 
    of objects is OLE objects (see [OLE]).
    
    

59. Section 9.3.3, 6th line on page 304
    Current description:
    The  element represents objects that have a XML 
    representation.
    Proposal:
    "a" should be "an" as follows:
    The  element represents objects that have an XML 
    representation.
    
    

60. Section 9.3.3, 37th line on page 304
    Current description:
    The object is contained within this sub page exactly as it would as it is 
    a document of its own.
    Proposal:
    The current sentence should be paraphrased in a different way. Please 
    explain what "sub page" means and what the whole sentence means.
    The whole sentence sounds to me as follows: 
    The object is contained in the document on the target page referenced by 
    the xlink:href attribute although the source page does not actually 
    contain the object. For end users, it exactly looks like that the source 
    page contains the object. 
    Is my understanding correct? 
    
    
    

61. Section 8.11.7
    Current description: 
    The  element specified the id of a previously 
    tracked change that gets deleted by the current change.
    Proposal:
    "specified" should read "specifies" as follows:
    The  element specifies the id of a previously
    �@tracked change that gets deleted by the current change.
    
    

62. Section 8.11.8, 2nd line on page 259
    Current description:
    Depending on the deletion type, It is either the number of a row, a column 
    or a table.
    Proposal: "It" should be "it" as follows: 
    Depending on the deletion type, it is either the number of a row, a column 
    or a table.
    
    

63. Section 8.11.14, 8th line on page 264
    Current description:
    The change track table cells additionally supports the attributes 
    table:formula, table:number-matrix-rows-spanned, 
    table:number-matrix-columns-spanned, office:value-type, office:value, 
    office:date-value, office:time-value and office:string-value as described 
    in section 8.1.3.
    Proposal:
    "cells" should be the singular form "cell" as follows:
    The change track table cell additionally supports the attributes 
    table:formula, table:number-matrix-rows-spanned, 
    table:number-matrix-columns-spanned, office:value-type, office:value, 
    office:date-value, office:time-value and office:string-value as described 
    in section 8.1.3.
    
    

64. Section 9.1.4, 12th line on page 271
    Current description:
    The word "borders" is a keyword in the following sentence: 
    Defines properties such as the size and borders of the drawing page
    Proposal:
    The word "borders" shouldn't be akey word.
    
    

65. Section 9.1.5, Example: Drawing page on 273
    Current descripton:
    
    presentation:notes>
            this is a note
    
    Proposal:
    presentaion:notes should be delineated by angle brackets as follows:
    
    
            this is a note
    
    
    

66. Section 9.2.5, 5th line on page 278
    Current description:
    In general, if r is the radius of the polygon, and s is the sharpness, the 
    inner corners a located on a ellipse that's radius is r(100-s)/100.
    Proposal: Please check if the following is the intended description: 
    In general, if r is the radius of the polygon, and s is the sharpness, the 
    inner corners are located on an ellipse whose radius is r(100-s)/100.
    
    

67. 15.5.38 Snap To Layout
    
    The title should be "Snap to Layout Grid".
    
    

68. The last para of  17.7.3
    
    	As an example, all XML streams have the media type "text/xml".
    
    This is incorrect.  First, there are lots of specialized media types 
    (*/*+xml) for XML.  Second, even for generic XML, application/xml is
    almost always more appropriate than text/xml .
    
    
    

69. The first para of "Key Derivation Name" in 17.7.6 
    	The manifest:key-derivation-name attribute specifies the name of
    	the algorithm used to derive the name.
    
    Perhaps, the second "name" should be replaced with "encryption key"?
    
    
    

70. The last para of 17.5
    
       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.
    
    First, an absolute IRI reference begins with a scheme (rather than protocol), 
    and it does not start with an authority or an absolute-path.  
    
    Second, I do not undestand the second half of the second sentence.  Is
    something missing?
    
    
    

71. Mismatch of section titles and Appendix F o
    
    The title of 15.16 is "Text and Text Alignment Properties", but 15.16
    is quoted as "Text Alignment Properties" in the table in Appendix F.
    
    Likewise, the title of 12.2 is "Number format", while 12.2 is quoted
    as "Number Format for page numbers, etc." in the table in Appendix F.
    
    
    

72. Undefined elements in 15.36.10 "Sound" 
    
    The  element is mentioned 
    in 15.36.10, but is never defined in the schema.
    
    

73. valueType in 16.1 "Data Types" 
    
    The schema implies that the permissible values of this type 
    is either   "float", "time", "date", "percentage", "currency", 
    "boolean", or "string".  However, the definition in 16.1 is:
    
    	valueType
    	A list of value types supported for certain generic values, such
    	as "string" or "date".
    
    This text appears to allow "date string percentage currency boolean" 
    as a single permissible value of this type.
    
    
    

74. Is zero allowed as a length in Chap 10?
    
    "A (positive or negative) physical length" (page 691) appears to
    disallow zero.
    
    
    

75. Missing bullets in 15.36 "Presentation Page Attributes"
    
    
    The itemized list immediately before 15.36.1 should enumerate all
    properties.  However, the following properties are missing, although
    they do appear in subsubsections of 15.36.
    
    Transition Type or Family
    Transition Subtype
    Transition Direction
    Fade Color
    
    

76. Another conflict of attribute names in 15.36.8 "Page Duration"
    
    presentation:page-duration is used in the body text, while 
    presentation:duration is used in the schema. 
    
    
    
    

77. Element name conflict in 15.36 "Presentation Page Attributes" 
    
    The second sentence in this subsection says , 
    but the schema appears to imply .
    
    
    
    

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

79. Attribute names in 15.31.4 "Tick Marks" 
    
    Two attributes (chart:axis-interval-major and
    chart:axis-interval-minor) appear in the body text, while four
    different attributes, (chart:tick-marks-major-inner,
    chart:tick-marks-major-outer, chart:tick-marks-minor-inner, and
    chart:tick-marks-minor-outer) appear in the schema.
    
    
    

80. Attribute names in 15.31.3 "Scaling"
    
    chart:interval-minor-divisor is used in the body text, while 
    chart:interval-minor is used in the schema. 
    
    

81. Attribute names in 15.31.3 "Scaling"
    
    chart:axis-logarithmic is used in the body text, while 
    chart:logarithmic is used in the schema. 
    
    
    

82. "vale" in 11.7.3 in ISO/IEC 26300 should read "value".
    
    	See section 6.7.1 for more information on vale and 
    	value type attributes.
    
    

83. missing section number in 12.4 
    
    There is no section number at the last of the following paragraph in
    12.4 Event Listener Tables.
    
    "The  element represents events that are
    bound to an action that is specific to a presentation, for example, go
    to the next page. Presentation events are described in section ."
    
    

84. In 14.7.9 Common Data Style Attributes, there is a mistake at the
    last sentence of the description about Country attribute. The excerpt
    of the sentences is as follows.
    
    	Country
    
    	The number:country attribute specifies the country of the
    	style. The value of the attribute is a country code in
    	conformance with [RFC3066]. The country code is used to
    	retrieve information about any display properties that are
    	country-dependent. The "language" attribute can be used with
    	all data style elements.
    
    "language" must be replaced with "country".
    
    
    
    

85. Attribute names in 15.31.2 "Visibility" 
    
    chart:axis-visible is used in the body text, while 
    chart:visible is used in the schema. 
    
    

86. Attribute names in 15.30.9 "Lines"
    
    chart:splines is used in the body text, while 
    chart:lines is used in the schema. 
    
    

87. Attribute names in 15.30.4 "Chart Symbol Size" 
    
    chart:symbol-length is used in the body text, while 
    chart:symbol-height is used in the schema. 
    
    
    

88. Attribute names in 15.28.3 Margins of ODF 1.0
    
    draw:margin-horizontal is used in the body text, while 
    draw:frame-margin-horizontal is used in the schema.  
    Likewise, draw:margin-vertical is used in the body text, while 
    draw:frame-margin-vertical is used in the schema.  
    
    
    

89. The first para of 15.3.4 is:
    
    	If a page contains borders, the border line width attributes 
    	style:border-line-width, style:border-line-width-top,
    	style:border-line-width-bottom, style:borderline-width-left and 
    	style:border-line-width-right specify the properties of the
    	border lines of the headers and footers.
    
    
    However, since 15.3 applies to headers and footers, should "If a page" 
    be replaced with "If a header or footer"?
    
    
    

90. The last sentence of the second para of 15.27.31 "Wrap Influence on Position"
    is:
    
    	Without wrapping, the images overly the text and can simply be
    	placed at the given offset from the anchor.
    
    
    Perhaps, "overly" should read "overlies"?
    
    

91. The first para in 15.27.22 says style:wrap-dynamic-threshold, while 
    the schema fragment in this subsection says style:wrap-dynamic-treshold.
    ("h" between "t" and "r" is missing.)
    
    

92. In 15.27.21 Wrapping, the third bullet in the first itemized list is:
    
    	right: Text may wrap around the left side of the drawing shape.
    
    But "the left side" should read "the right side".
    
    

93. What does "this section" in 15.28.4 mean?  Does it 
    refer to 15.28.4 or 15.28?
    
    

94. The third paragraph of 15.27
    
    	This corresponds to the object once-concurrently.
    
    I believe that "object" should be replaced with "option".
    
    

95. I do not understand the second sentence of the second para of 15.27.31.
    
    	Without wrapping, the images overly the text and can simply be
    	placed at the given offset from the anchor.
    
    What does "overly the text" mean?
    
    

96. "species" in 15.12 in ISO/IEC 26300 should read "specifies".
    
    

97. Is the following text in 15.10.1 Row Height correct?
    
    	The style:row-height property specifies a fixed row height, 
    	while the style:min-row-height property specifies a fixed height.
    
    These properties look exactly the same, since the latter obviously 
    apply to rows.  However, doesn't the latter specify a *minimum* hight?  
    
    

98. In 15.5.26 Border Line Width of ODF 1.0, we have:
    
    	The border line width attributes style:border-line-width,
    	style:border-line-wid th-top, style:border-line-width-bottom,
    	style:border-line-width-left and style:border-line-width-right
    	specify the properties of the border lines of the page. 
    
    
    Is the last word really "page"?