17.15.1.54 ignoreMixedContent

This element specifies that applications should ignore all text content which is not contained within a leaf custom XML markup element when validating the contents of the custom XML markup in this document against one or more attached custom XML schema(s). A leaf element is a custom XML element which has no child custom XML elements (it is a leaf in the custom XML tree).

If this element is omitted, then text content in leaf elements shall not be ignored when validating the custom XML markup against one or more custom XML schema(s).

[Example: Consider a WordprocessingML document that contains the following markup:

<w:customXml w:element="invoice" w:uri="http://www.example.com/invoice">
  <w:p>
    <w:r>
      <w:t>Invoice #:</w:t>
    </w:r>
    <w:customXml w:element="id" w:uri="http://www.example.com/invoice">
      <w:r>
        <w:t>012345</w:t>
      </w:r>
    </w:customXml>
  </w:p>
  <w:p>
    <w:r>
      <w:t>Invoice Date:</w:t>
    </w:r>
    <w:customXml w:element="date" w:uri="http://www.example.com/invoice">
      <w:r>
        <w:t>01/29/2009</w:t>
      </w:r>
    </w:customXml>
  </w:p>
</w:customXml>

If all the custom markup is extracted from the document, that markup would include all content in the document, i.e.:

<invoice xmlns="http://www.example.com/invoice">
  Invoice #:
  <id>012345</id>
  Invoice Date
  <date>01/29/2009</date>
</invoice>

The content shown above is formatted for readability. In fact, there is no such space in the XML.

However, if the ignoreMixedContent element is present with a val attribute value of true (or equivalent) then an application should ignore all text nodes in elements with mixed content, i.e.:

<invoice xmlns="http://www.example.com/invoice">
  <id>012345</id>
  <date>01/29/2009</date>
</invoice>

end example]

This element’s content model is defined by the common boolean property definition in 17.17.4.