Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: SV: SV: Any wildcard and the .NET validator?

From: Jeff Rafter <lists@----------.--->
To: Zafar Abbas <Zafar.Abbas@---------.--->
Date: 10/10/2006 12:30:00 AM
Hi Zafar Abbas,

I used 1.1.x and 2.0.x:

System.Xml.XmlValidating Reader validation 1.1.x
Validating example.xml
Validation Error: Could not find schema information for the element 
'http://www.w3.org/1999/xhtml:em'. An error occurred at 
file:///G:/example.xml, (22, 110).
Validation Error: Could not find schema information for the element 
'http://www.w3.org/1999/xhtml:br'. An error occurred at 
file:///G:/example.xml, (22, 141).
Validation Error: Could not find schema information for the element 
'http://www.w3.org/1999/xhtml:strong'. An error occurred at 
file:///G:/example.xml, (22, 156).

Document is invalid

--------------------------------

System.Xml.XmlReader schema validation 2.x
Validating example.xml
Validation Error: Could not find schema information for the element 
'http://www.w3.org/1999/xhtml:em'.
Validation Error: Could not find schema information for the element 
'http://www.w3.org/1999/xhtml:br'.
Validation Error: Could not find schema information for the element 
'http://www.w3.org/1999/xhtml:strong'.

Document is invalid

I think the specific versions I am using are (v1.1.4322 and v2.0.50727). 
Also, I tried to see if it was the mixed="true" definition throwing it 
off. I created a new non-mixed example and removed that from the 
declaration and got the same errors.

Thanks,
Jeff

Zafar Abbas wrote:
> Bryan,
> What error do you get when validating it through .NET? And which version
> of the .NET framework are you using?
> 
> Thanks,
> Zafar Abbas
> 
> -----Original Message-----
> From: xmlschema-dev-request@w... [mailto:xmlschema-dev-request@w...]
> On Behalf Of Bryan Rasmussen
> Sent: Monday, October 09, 2006 6:14 AM
> To: Xan Gregg
> Cc: lists@j...; xmlschema-dev@w...
> Subject: SV: SV: SV: Any wildcard and the .NET validator?
> 
> 
> 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 zafar.abbas@m... Tue Oct 10 17:04:06 2006
Received: from lisa.w3.org ([128.30.52.41])
	by frink.w3.org with esmtp (Exim 4.50)
	id 1GXL1S-0


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent