r - run (§3:2.4.2). The description of a run is confused about whether it is limited to text-only, and whether it contains additional markup. "[A run] Can contain multiple types of run content, primarily text ranges. … A run is a contiguous piece of text with identical properties; a run contains no additional text markup." Part 3 and Part 4 reiterate "…the run, which defines a region of text…" [Implied "text-only" is wrong] Part 3 and Part 4 define with many examples that the run can contain a range of additional text markup in child elements like delText, endnoteRef, fldChar, … (e.g., see §4:2.3.2.23). Part 3 and Part 4 also define that the run can contain non-text items like drawing (DrawingML Object), object (Inline Embedded Object), pict (VML Object), … (e.g., see §4:2.3.2.23).

Proposed change: Clearly define the general concept of a run that can contain multiple types of content, primarily a text range with the same properties. [If the primary intent of a run is for text rather than other content types - if not the primary intent, use words like "such as a text range ...".] This also needs changes to the sections in Parts 3 and 4, including section titles that imply runs are only for text. [The text content is defined by a sub-element, t. §4:2.3.3.30]

5.2 WORDPROCESSINGML [p11]

te

Proposed Disposition of DIS 29500 Comment GB-0007 (Modified: 2007-10-27) The document “Office Open XML Overview” was intended to provide some background and contextual information about OOXML for reviewers during both the Ecma adoption stage and the 5-month Ballot stage of the Fast-Track process. (Such a document is often referred to as a white paper.) As such, this document will not be included in the published standard. Similar Comments: CA-0002 , DE-0140 , DK-0043 , GB-0004 , GB-0006 , GB-0008 , GB-0009 , GB-0010 , GB-0011 , GB-0015 , IN- 0050 , JP-0018 , PT-0002 , US-0004