Part 3 - Primer
From OOXML-Wiki
[edit] 2.4.1 [36]
Replace "... a designating specifying ..." with "... an attribute specifying ..."
(The same phrase is also used on p34 in 2.3.1 [28] of the WordprocessingML Reference Manual.)
[edit] 2.4.2 [9 on p5]
Run properties are not represented by the r element.
Proposed change: Change the order or the sentence to more directly relate the r element to the run. "The next level of the document hierarchy is the run, which defines a region of text with a common set of 9 properties. A run is represented by an r element, which allows the producer..."
[edit] 2.4.2 [30 on p5]
wrong style: "emphasized" should be in italics.
[edit] 2.4.2 [4 on p6]
Missing forward slash from end tag: </w:rPr>
[edit] 2.4.2 [17 on p6]
Missing forward slash from end tag: </w:rPr>
[edit] 2.4.2 [23 on p6]
Missing forward slash from end tag: </w:rPr>
[edit] 2.4.2 [28 on p6]
Insert "of" in "... only some of the text ..."
[edit] 2.5.2 [17]
Missing closing double quotes in attribute: w:sz="4"
[edit] 2.5.3 [5 on p12]
Replace curly quotes with straight quotes: ... w:val="2"/>
[edit] 2.5.3 [26 on p12]
Replace curly quotes with straight quotes: ... w:val="2"/>
[edit] 2.5.4 [31 on p13]
'W' in 'World' should be lower case: <w:t>Hello, world</w:t>
[edit] 2.5.4 [13 on p14]
Delete line 13: "..."
[edit] 2.5.4 [16 on p14]
Replace "5145" with "7368" to make consistent with example on p12: w:w="7368"
[edit] 2.5.4 [23 on p14]
Replace "2145" with "1488" to make consistent with example on p12: w:w="1488"
[edit] 2.7.1 [1 - 28 on p28]
Delete lines 1 to 28 as the same listing is on the previous page.
[edit] 2.8.2 [2 on p30]
"h" in "heading 1" should be upper case: <w:name w:val="Heading 1"/>
[edit] 2.8.2 [6]
It appears that the child w:priority of w:style has been changed to w:uiPriority in the schema and in the tables in the Language Reference but has not been changed in any of the examples throughout the documents I've seen so far.
Replace "w:priority" with "w:uiPriority"
[edit] 2.8.2 [21 - 31 on p30]
Delete lines 21 to 31.
[edit] 2.8.2 [32 - 33 on p30]
Move lines 32 to 33 to between lines 12 and 13 on p30.
[edit] 2.8.4 [27]
See 2.8.2 [6] above. Replace "w:priority" with "w:uiPriority"
[edit] 2.8.5 [31]
Change line 31 to include the information from lines 28 to 29 on p34 (see below) to: "Consider the following two styles comprising a linked style pairing which defines: font = Arial, font color = green, paragraph spacing = double, indent = 1" left. The resulting style definitions would be:"
[edit] 2.8.5 [28 on p34 - 14 on p35]
The xml listing for the linked styles is repeated unnecessarily.
Move lines 28 and 29 on p34 and merge with line 31 on p33, as specified above. Delete from line 30 on p34 to line 14 on p35.
[edit] 2.8.6 [17]
See 2.8.2 [6] above. Replace "w:priority" with "w:uiPriority"
[edit] 2.8.7 [15 on p38]
See 2.8.2 [6] above. Replace "w:priority" with "w:uiPriority"
[edit] 2.8.11 [26]
Incorrect attribute name. Replace "w:defPriority" with "w:defUIPriority"
[edit] 2.8.11 [31]
See 2.8.2 [6] above. Replace "w:priority" with "w:uiPriority"
[edit] 2.8.11 [32]
See 2.8.2 [6] above. Replace "w:priority" with "w:uiPriority"
[edit] 2.8.11 [35]
See 2.8.2 [6] above. Replace "w:priority" with "w:uiPriority"
[edit] 2.8.11 [36]
See 2.8.2 [6] above. Replace "w:priority" with "w:uiPriority"
[edit] 2.8.11 [1 on p43]
See 2.8.2 [6] above. Replace "w:priority" with "w:uiPriority"
[edit] 2.8.11 [2 on p43]
See 2.8.2 [6] above. Replace "w:priority" with "w:uiPriority"
[edit] 2.8.11 [3 on p43]
See 2.8.2 [6] above. Replace "w:priority" with "w:uiPriority"
[edit] 2.8.11 [4 on p43]
See 2.8.2 [6] above. Replace "w:priority" with "w:uiPriority"
[edit] 2.8.11 [5 on p43]
See 2.8.2 [6] above. Replace "w:priority" with "w:uiPriority"
[edit] 5.8.2.6 [6 on p321]
Add slash to close element.
[edit] 5.9.4.3 [33 on p344]
Replace curly quotes with straight quotes in XML attributes.
[edit] 5.9.4.3.1 [29 on p345]
Replace curly quotes with straight quotes in XML attributes.
[edit] 5.12.3 [p356-7]
The XML example is not well-formed. Although it is acceptable to use ellipsis to elide some information in examples, that should not include the key parts of the example (i.e. the rectangle shape, in this instance).
Proposed change: correct the example to be well-formed and to provide useful information.
Response: Section 5.6.2.28 gives details on how sp(Shape) element can be used. Code snippet that is provided in Section 5.12.3 is intended only to describe the structure of worksheet drawing element. (Note: this response was given before the revision of the comment above, and may now be out-of-date)
[edit] 5.14.3 [p373-4]
The XML example is not well-formed. Although it is acceptable to use ellipsis to elide some information in examples, that should not include the key parts of the example (i.e. the rectangle shape, in this instance).
Proposed change: correct the example to be well-formed and to provide useful information.
[edit] 5.15.3.1.3 [20 on p379]
Add missing quote at end of maxOccurs attribute.
[edit] 5.15.3.1.4 [5 on p380]
Add missing quote at end of CT_Cxn attribute value.
[edit] 5.15.4.1 [26 on p382]
Add missing quote at end of lang attribute value.
[edit] 5.15.4.1.3 [15 on p384]
Add missing quote at end of CT_Colors attribute value.
[edit] 5.15.4.1.6 [9 on p386]
Add missing quote at end of styleLbl attribute value.
[edit] 5.15.4.1.6 [10 on p386]
Remove extraneous text "odoc".
[edit] 5.15.5.1.3 [33 on p389]
Remove backtick at end of line.
[edit] 5.15.6.3.1 [25,26 on p403]
Add missing quotes around "NAME OF TYPE" and "NAME OF SIMPLE TYPE"
[edit] 5.15.6.3.16 [11 on p407]
Add missing quote and space to break up animLvl from type attribute.
[edit] 5.15.6.3.39 [16 on p415]
Add missing quote at end of minOccurs attribute.
[edit] 7.1
On page 1, the Primer states that "this Part contains a detailed introduction to the following Office Open XML topics" and includes "Various shared MLs" in the list. However as far as the "detailed introduction" is concerned:
- There is no example xml in 7.1. Perhaps this is why it contains only 7 pages.
- Looking at the provided docx files, there are only four expressions where oMath has been used. All the rest are picture elements. This explains why the layout looks poor e.g., the baselines are wrong. All the example mathematical expressions must be written using oMath.
- In maths, an expression is not always an equation. If anything, an equation is a maths expression that includes an equal sign, for example. It would be better to use "expression" or "mathematical expression" throughout.
- There is no association between maths and the xml being used in oMath. For example, a maths expression is composed of subexpressions but there is no description of how to go from the mathematical structure to the xml (cf presentation markup in MathML). Other parts of the Primer go into great detail about how the structure of a table or list, say, maps to the xml elements and it should be the same for maths.
- Some examples of how oMath fits with WordprocessingML would have helped to illustrate how paragraphs can be constructed. This type of example is used in other parts of the Primer.
- There is no description of what an operator is and how it is displayed differently to other objects. References are made to such things as "the alignment and manual break properties of operators" but these are not explained.
[edit] 7.1 [18]
The expression "abc" with the arrow and with the brace over the top are both repeated. In each case, one is oMath and the other is a picture. The picture version needs to be deleted in each case.
[edit] 7.1 [19]
The bar fraction "n/k" at the end of the line is repeated. One is oMath and the other is a picture. The picture version needs to be deleted.
[edit] 7.1 [20]
The stack object, n over k, at the start of the line is repeated. One is oMath and the other is a picture. The picture version needs to be deleted.
[edit] 7.1.10 [5]
Replace "x + x + x" with "x + x + ...".
[edit] 7.1.12 [11]
Replace "upper limit" with "lower limit".
[edit] 7.2.1 [6 on p440]
Missing forward slash from end tag: </dc:creator>
[edit] 7.4.3 [7 - 8 on p445]
Insert new line between lines 7 and 8 containing missing end tag: </b:NameList>
[edit] 7.4.3 [14 - 15 on p445]
Insert new line between lines 14 and 15 containing missing end tag: </b:NameList>
[edit] 7.4.3 [21 - 22 on p445]
Insert new line between lines 21 and 22 containing missing end tag: </b:NameList>
[edit] 8.3.4.2.1 [2 - 9 on p470]
XML example not well formed. Insert missing end tags for choice and fallback.
[edit] 8.3.4.1.1 [p455]
The graphic provided in the example is almost impossible to read, and includes malformed XML.
Proposed change: Make an easy to read example (perhaps lighter background color) and make the example well-formed.
