Over 300 errors in XML examples have been identified and confirmed. The list of errors was submitted to Polish NB, however recognized to be the same as presented in:
http://surguy.net/articles/ooxmlvalidationandtechnicalreview.xml

According to Microsoft Poland those errors are being now under correction. Polish NB draws the Project Editor’s attention to be sure the corrections will be done.

WordProcessingML Chapter

ed

Proposed Disposition of DIS 29500 Comment PL-0003 (Modified: 2008-01-13) Agreed; the examples in the document will be modified so that they are all well-formed XML trees. A thorough pass will be made to identify all areas where this is not the case. It should be noted though that they will not be validated to the schema files because they are just fragments of a document and not an entire document. As such, they often do not start with the root element, but instead are often just a branch of the tree. In addition, there will often be ellipsis “…” within the example to show where other XML markup would normally appear. This missing markup is not relevant to the example, but it may be necessary in order for the file to be valid. This approach was used in order to get across efficiently the usage of the element to which the example pertains. For an example of the use of ellipsis, see the following, which appears in Part 4 clause 2.16.6: <w:bookmarkStart w:name="Text1" … /> <w:fldSimple w:instr="FORMFIELDTEXT"> <w:ffData> <w:calcOnExit/> … </w:ffData> <w:r> <w:t>1</w:t> </w:r> </w:fldSimple> <w:bookmarkEnd w:name="Text1" … /> <w:fldSimple w:instr="=Text1+10"> <w:r> <w:t>11</w:t> </w:r> </w:fldSimple> Regarding the use of xml:space="preserve", the use of this attribute is determined by the presence of significant leading and/or trailing whitespace within the t element, which is why it is not present in all instances. Similar Comments: CH-0015 , CL-0217 , DE-0147 , DK-0074 , GB-0135 , IE-0011 , NO-0005 , PE-0007 , US-0267