As I've mentioned in the previous post, I'm not aware of and we have not 
seen any performance degradation for xs:choice compared to xs:sequence in 
system.xml or msxml.

-- 
Stan Kitsis
Program Manager, XML Technologies
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.


"mavis" <donghuad@g...> wrote in message 
news:1149134179.174630.84190@c......
>I guess from validation point of view, using xs:choice in this way is
> not  aproblem
> But from the wirte and read point of view, it might be a problem...I
> guess the performance should not be good if it has large amount of
> elements since it need to loop all the elements for each element.
>
> Thanks!!
>
> -Mavis
>
>
> mavis wrote:
>> Maybe the only thing is just the complexity of the xml processing??
>>
>> Thanks!
>>
>> Mavis
>>
>>
>> Stan Kitsis [MSFT] wrote:
>> > <xs:choice> is a widely used schema construct and I am not aware of any
>> > performance issues of <xs:choice> compared to other constructs, such as
>> > <xs:sequence>.
>> >
>> > --
>> > Stan Kitsis
>> > Program Manager, XML Technologies
>> > Microsoft Corporation
>> >
>> > This posting is provided "AS IS" with no warranties, and confers no 
>> > rights.
>> >
>> > "mavis" <donghuad@g...> wrote in message
>> > news:1148686519.807265.258670@i......
>> > > Thanks a lot!!
>> > > Do you think that may cause the performance problem?
>> > > Is this a good way to design schema?
>> > > Any advices will be highly appreciated!
>> > >
>