<xsd:element name="relative_dn" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1" nillable="true">
    <xsd:annotation>
        <xsd:documentation>The relative_dn field is used to uniquely identify an object inside the specified naming context. It contains all the parts of the objects distinguished name except those outlined by the naming context. If the nillable attribute is set to true, then the item being represented is the higher level naming context. Using xsi:nil here will result in a status of 'does not exist' for object_class, adstype, and value since these entities are not associated with a naming context by itself. Note that when nil is used for the relative dn element, the attribute element should also be nilled.</xsd:documentation>
        <xsd:appinfo>
            <sch:pattern id="aditemrelative_dn" xmlns:sch="http://purl.oclc.org/dsdl/schematron">
                <sch:rule context="win-sc:activedirectory_item/win-sc:relative_dn">
                    <sch:assert test="not(@datatype) or @datatype='string'">item <sch:value-of select="../@id" /> - datatype attribute for the relative_dn entity of an activedirectory_item should be 'string'</sch:assert>
                    <sch:assert test="not(@xsi:nil='true') or ../win-sc:attribute/@xsi:nil='true'">
                        <sch:value-of select="../@id" /> - attribute entity must be nil when relative_dn is nil</sch:assert>
                </sch:rule>
            </sch:pattern>
        </xsd:appinfo>
    </xsd:annotation>
</xsd:element>

• oval-sc:EntityItemBaseType
  • oval-sc:EntityItemStringType
    • relative_dn