Parent Elements

body (§2.2.2); comment (§2.13.4.2); customXml (§2.5.1.3); customXml (§2.5.1.4); customXml (§2.5.1.5); customXml (§2.5.1.6); deg (§7.1.2.26); del (§2.13.5.12); den (§7.1.2.28); docPartBody (§2.12.6); e (§7.1.2.32); endnote (§2.11.2); fldSimple (§2.16.21); fName (§7.1.2.37); footnote (§2.11.10); ftr (§2.10.3); hdr (§2.10.4); hyperlink (§2.16.24); ins (§2.13.5.20); lim (§7.1.2.52); moveFrom (§2.13.5.21); moveTo (§2.13.5.26); num (§7.1.2.75); oMath (§7.1.2.77); p (§2.3.1.22); rt (§2.3.3.23); rubyBase (§2.3.3.26); sdtContent (§2.5.2.32); sdtContent (§2.5.2.33); sdtContent (§2.5.2.34); sdtContent (§2.5.2.35); smartTag (§2.5.1.9); sub (§7.1.2.112); sup (§7.1.2.114); tbl (§2.4.36); tc (§2.4.62); tr (§2.4.75); txbxContent (§2.17.1.1)

Attributes

Description

displacedByCustomXml (Annotation Marker Relocated For Custom XML Markup)

Specifies that the parent annotation's placement shall be directly linked with the location of the physical presentation of a custom XML element in the document. This element only has an effect when the custom XML element is block-level (i.e. surrounds an entire paragraph), as in this scenario the logical and physical placement of the annotation and custom XML element may differ.

Specifically, in this case, the custom XML is presented *around* the block-level object it encloses (the paragraph, table, table row, or table cell), but is physically represented within that same object (i.e. within the paragraph, table, table row or table cell). This requirement stems from the fact that there is no location for the location of the annotation within the document at its logical location (around a table, for example).

If this element is omitted, then the annotation shall be anchored inside of all block-level custom XML elements in the paragraph. If this element is present, but no block-level custom XML tag is located at the position it specifies (before or after), then it shall be ignored.

[Example: Consider a paragraph with block level custom XML markup and two comment anchor annotations (one before and one after the custom XML element's physical representation), as follows:

Since all three of these items are around the entire paragraph, they are stored outside of the paragraph. However, in order to ensure that their relative positions are stored correctly, any annotation which shall be displaced by the physical custom XML element specifies this information, resulting in the following WordprocessingML:

<w:commentRangeStart w:id="0" />
<w:commentRangeStart w:id="1" w:displaced byCustomXml="next" />
<w:customXml w:element="spec" … />
<w:p>
…
</w:p>

The displacedByCustomXml attribute specifies that even though all three of these items are around the paragraph and will be moved inside the paragraph to be represented physically, the comment with ID 0 shall be inside the custom XML, but the comment with ID 1 shall be displaced to stay outside of the relative location of the next custom XML element (the spec element). end example]

The possible values for this attribute are defined by the ST_DisplacedByCustomXml simple type (§2.18.17).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).