Oops you're right, I didn't notice that mixed was set to true. In that =
case I
would assume that All validators but .Net are correct in this instance. 

Cheers,
Bryan Rasmussen




-----Oprindelig meddelelse-----
Fra: Xan Gregg [mailto:xan.gregg@j...]
Sendt: 9. oktober 2006 15:10
Til: Bryan Rasmussen
Cc: lists@j...; xmlschema-dev@w...
Emne: Re: SV: SV: Any wildcard and the .NET validator?


I don't see what the confusion is. Text nodes are allowed because  
DescriptionType has mixed=true, and xhtml element nodes are allowed  
because of the <any> particle. The lax value only means that  
unrecognized xhtml element nodes won't be assessed for validity, but  
recognized xhtml element nodes will be assessed. Element nodes in  
other namespaces (e.g., RDF) are disallowed outright.

xan

On Oct 9, 2006, at 6:50 AM, Bryan Rasmussen wrote:

> Well I think no matter which is right the spec at this point is  
> unclear
> (unless clarified at some other place in the spec in which case it  
> is just
> convoluted)
>
>> -----Oprindelig meddelelse-----
>> Fra: Jeff Rafter
>> Til: xmlschema-dev@w...
>> Emne: Any wildcard and the .NET validator?
>>
>> Does anyone here have information on the .NET XML Schema validator  
>> and
>> their position on lax validation of wildcards?
>>
>> i.e.:
>>
>>   <complexType name="DescriptionType" mixed="true">
>>     <sequence>
>>       <any minOccurs="0" maxOccurs="unbounded"
>>         namespace="http://www.w3.org/1999/xhtml"  
>> processContents="lax"/>
>>     </sequence>
>>   </complexType>
>>
>>     <description xmlns:html="http://www.w3.org/1999/xhtml">Blah
>> Blah<html:em>blah</html:em>.<html:br/>Blah<html:strong>blah</ 
>> html:strong>
>> blah!</description>


From Leo.Antoli@M... Mon Oct 09 15:50:06 2006
Received: from maggie.w3.org ([193.51.208.68])