<xsd:element name="filename" type="oval-def:EntityObjectStringType" nillable="true">
    <xsd:annotation>
        <xsd:documentation>The filename element specifies the name of a file to evaluate. If the nillable attribute is set to true, then the object being specified is the higher level directory object. (not all the files in the directory) In this case, the filename element should not be used during collection and would result in the set of collected objects being the directories themselves. For example, one would set nillable to true if the desire was to as test the attributes or permissions associated with a directory. Setting nil equal to true is different than using a .* pattern match, which says to collect every file under a given path.</xsd:documentation>
        <xsd:appinfo>
            <sch:pattern id="fap53objfilename" xmlns:sch="http://purl.oclc.org/dsdl/schematron">
                <sch:rule context="win-def:fileauditedpermissions53_object/win-def:filename">
                    <sch:assert test="not(@datatype) or @datatype='string'">
                        <sch:value-of select="../@id" /> - datatype attribute for the filename entity of a fileauditedpermissions53_object should be 'string'</sch:assert>
                    <sch:assert test="if (not(@operation) or @operation='equals' or @operation='not equal') then (not(contains(.,'\') or contains(.,'/') or contains(.,':') or contains(.,'*') or contains(.,'?') or contains(.,'&gt;') or contains(.,'|'))) else (1=1)">
                        <sch:value-of select="../@id" /> - filename entity can not contain the characters / \ : * ? &gt; | </sch:assert>
                </sch:rule>
            </sch:pattern>
        </xsd:appinfo>
    </xsd:annotation>
</xsd:element>

• oval-def:EntityBaseType
  • oval-def:EntityObjectBaseType
    • oval-def:EntityObjectStringType
      • filename