There is no built-in mechanism that does this type of verification.  There 
might be workarounds depending on what you're trying to do.  Here's one 
idea.  If your setting elements are in a sequence under the same parent, set 
minOccurs to the total number of entries you want and use a uniqueness 
constraint to make sure they are all different.

<xs:element name="parent">
    <xs:complexType
        <xs:sequence
            <xs:element name="setting" minOccurs="10" maxOccurs="10">
                ...
            </xs:element>
        </xs:sequence>
    </xs:complexType>
    <xs:unique  ...>
        ...
    </xs:unique>
</xs:element>

Of course, this doesn't work if you want to allow multiple settings with the 
same name.

-- 
Stan Kitsis
Program Manager, XML Tools & Technologies
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"J Mon" <JMon@d...> wrote in message 
news:975E221B-BC4B-42B9-B520-D45AA5E2F425@m......
> Hi I am trying to set up my XML Schema to validate my XML files to check 
> that
> the necessary settings are all there.  I have an element called <setting>
> which has attribute "name".  I want to make sure that all the required 
> names
> exist in the document.
>
> I've tried using this:
> <xs:element name="setting" minOccurs="1" maxOccurs="unbounded">
> <xs:complexType>
>  <xs:attribute name="name" type="string" form="unqualified" 
> use="required">
>     <xs:simpleType>
>        <xs:restriction base="xs:string">
> <xs:enumeration value="ConnectionString"></xs:enumeration> <xs:enumeration
> value="LocalisationConnString"></xs:enumeration>
> <xs:enumeration value="FeedListSupported"></xs:enumeration>
>                 ...etc...
>        </xs:restriction>
>      </xs:simpleType>
>    </xs:attribute>
> </xs:complexType>
> </xs:element>
>
> This ensures that the correct values for the setting name's are used;
> however it doesn't ensure that EVERY ONE is used.  Is there a way to 
> validate
> for this?