Damned, sorry my previous message got sent before I completed it.

Hello :)

>From what I understood you want something like this :

<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified" attributeFormDefault="unqualified">

    <xsd:element name="elementB">
        <xsd:complexType>
            <xsd:simpleContent>
                <xsd:extension base="xsd:string">
                    <xsd:attribute name="name" type="xsd:string"
use="required" />
                </xsd:extension>
            </xsd:simpleContent>
        </xsd:complexType>
    </xsd:element>

    <xsd:element name="elementA">
        <xsd:complexType>
            <xsd:choice>

                <xsd:element name="elementB">
                    <xsd:complexType>
                        <xsd:sequence>
                            <xsd:element name="elementC" type="xsd:string"/>
                            <xsd:element name="elementD" type="xsd:string"/>
                        </xsd:sequence>
                    </xsd:complexType>
                </xsd:element>

                <xsd:element ref="elementB" />

            </xsd:choice>
        </xsd:complexType>
    </xsd:element>
</xsd:schema>

does this help or you want something more specific ?

2008/6/22 Arshad Noor <arshad.noor@s...>:
>
>
>> How is it possible to define an XSD to allow an element to
>> either contain custom sub-elements, or a fixed string?
>>
>> For example, I would like to be able to do the following:
>>
>> <ElementA>
>>   <ElementB>
>>      <ElementC>Some value</ElementC>
>>      <ElementD>Another value</ElementD>
>>   </ElementB>
>> </ElementA>
>>
>> or
>>
>> <ElementA>
>>   <ElementB>Any</ElementB>
>> </ElementA>
>>
>> I'm not sure how to use <xsd:choice> to define this?  Thanks
>> for any suggestions.
>>
>> Arshad Noor
>> StrongAuth, Inc.
>>
>>
>>
>