This is the "footnoteLayoutLikeWW8" element. The text given says, "This element specifies that applications shall emulate the behavior of a previously existing word processing application (Microsoft Word 6.x/95/97) when determining the placement of the contents of footnotes relative to the page on which the footnote reference occurs. This emulation typically involves some and/or all of the footnote being inappropriately placed on the page following the footnote reference."

Unsufficient detail is given for an application to replicate the desired behavior.

Define the intended behavior.
We appreciate that this element is intended for backwards compatibility and is optional. However, if a vendor does want to fully implement the standard, for example, in order to read and display all OOXML documents, then this definition is insufficient.
On the other hand, if we think that no other vendor will fully implement this specification, then this brings into question its suitability for an International Standard.

page 1416, lines 14-17 Part 4, Section 2.15.3.26

te

Proposed Disposition of DIS 29500 Comment CL-0095 (Modified: 2008-01-13) Agreed; we will fully define the information necessary to implement this property (specified below). This description provides all of the information needed to mimic a behavior observed in a previously existing word processing application (Word 6.x/95/97). In addition, we will remove it from its current location in the specification (Part 4, §2.15.3.26, pages 1,416­1,417), and place it into a new annex for deprecated features. Following the precedent set by other ISO standards (such as SQL’s ISO 9075:2003 Part 1 and C++’s ISO/IEC 14882:1998), we will make use of a new Annex that contains normative descriptions of all deprecated features. The intent of this Annex is to enable a transitional period during which existing binary documents being migrated to DIS 29500 can make use of those deprecated features to preserve their fidelity, while noting that new documents should not use them. Accordingly, the Conformance clause will also be changed to state that newly created documents (those not created by migrating existing binary documents) should not use deprecated features. All deprecated features will be removed from their current locations in the standard, but will be fully defined in this new Annex. To provide a full description, the existing text in Part 4, §2.15.3.26, pages 1,416, lines 9­17, and page 1,417 lines 1­12, will be replaced with the following: 2.15.3.26 footnoteLayoutLikeWW8 (Ignore Page Break from Continuous Section Mark) This element specifies that applications should override the default behaviour for a continuous section break when one or more footnotes are present on the page with the footnote. This override typically results in text being displayed on the same page as a continuous section break (after the break, which would normally move all following text to the next page). Typically, applications render a continuous section break as a page break when one or more footnoteRef elements (§2.11.13) occur on that page before the break, as described in §2.1.8.84. This element, when present with a val attribute value of true (or equivalent), specifies that applications should allow any paragraph after the section break that contains no footnoteRef elements (§2.11.13) to be displayed on the same page. If the resulting content reaches the page extents, the section’s page break is ignored. [Example: Consider a WordprocessingML document with two footnotes contained in two sections, separated by a continuous section break: <w:p> <w:r> <w:t xml:space="preserve">Here is the first paragraph in the first section.</w:t> </w:r> </w:p> <w:p> <w:r> <w:t>Here is the second paragraph in the first section.</w:t> </w:r> <w:r> <w:rPr> <w:rStyle w:val="FootnoteReference" /> </w:rPr> <w:footnoteReference w:id="2" /> </w:r> </w:p> <w:p/> <w:p> <w:pPr> <w:sectPr> ... </w:sectPr> </w:pPr> </w:p> <w:p> <w:r> <w:t>Here is the first paragraph in the second section.</w:t> </w:r> </w:p> <w:p> <w:r> <w:t xml:space="preserve">Here is the second paragraph in the second section.</w:t> </w:r> <w:r> <w:rPr> <w:rStyle w:val="FootnoteReference" /> </w:rPr> <w:footnoteReference w:id="3" /> </w:r> </w:p> <w:p> <w:r> <w:t xml:space="preserve">Here is the third paragraph in the second section. </w:t> </w:r> </w:p> <w:sectPr> <w:type w:val="continuous" /> ... </w:sectPr> The default rendering of such a document results in the continuous section break as a page break, resulting in the following two page document: However, if this compatibility setting is turned on: <w:compat> <w:footnoteLayoutLikeWW8 /> </w:compat> Then the first paragraph following the section break (not having any footnote references) is displayed on the same page, despite the section break, resulting in the following output: end example] As well, the text in Part 4, §2.18.84, page 1,799, bottom table, will be clarified: Enumeration Value Description continuous (Continuous Section Break) Specifies a continuous section break, which begins the new section on the following paragraph. This means that continuous section breaks might not specify certain page-level section properties, since they must be inherited from the following section. These breaks, however, can specify other section properties, such as line numbering and footnote/endnote settings. If a footnote reference (§2.11.13) occurs on the same page as a section break of this type, the new section shall begin on the following page. Similar Comments: CO-0104 , CZ-0015 , DK-0011 , FR-0062 , GB-0229 , GH-0004 , GR-0031 , IN-0028 , IR-0018 , KR-0007 , PT-0045 , US-0059 , ZA-0012