Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


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

From: Jeff Rafter <lists@----------.--->
To: Bryan Rasmussen <BRS@----.-->
Date: 10/8/2006 8:39:00 PM
I think that is an excellent assessment Bryan. I wonder which is right? 
It is interesting that every other validator I have tried passes the 
document. I haven't tried Saxon, and it seems my Altova is broken... 
must fix that...

Thanks!
Jeff

Bryan Rasmussen wrote:
> 
> I should probably note that I don't 100% agree with this reasoning, I s=
uppose
> that what should be processed laxly is the content of description, not =
any
> the sequence of elements under description. But I do think the reasonin=
g can
> be understood.
> 
> Cheers,
> Bryan Rasmussen
> -----Oprindelig meddelelse-----
> Fra: Bryan Rasmussen 
> Sendt: 9. oktober 2006 09:41
> Til: 'lists@j...'; xmlschema-dev@w...
> Emne: SV: Any wildcard and the .NET validator?
> 
> 
> Well, if "A wildcard provides for =B7validation=B7 of attribute and ele=
ment
> information items dependent on their namespace name, but independently =
of
> their local name." (under wildcards
> http://www.w3.org/TR/xmlschema-1/#Wildcards ) Then I suppose the positi=
on is
> that a text node is not allowable as an any. 
> 
> The position is then also I suppose that Description is the element tha=
t uses
> DescriptionType, it is defined as having any number of elements in the =
xhtml
> namespace and processing should be lax if you happen to run into an ele=
ment
> in say the RDF namespace. But here they are running into a textnode und=
er
> description, description is not processed laxly therefore Description r=
aises
> an error. 
> 
> 
> At any rate, this is what I figure they position is. 
> 
> 
> Cheers,
> Bryan Rasmussen
> 
> -----Oprindelig meddelelse-----
> Fra: xmlschema-dev-request@w...
> [mailto:xmlschema-dev-request@w...]P=E5 vegne af Jeff Rafter
> Sendt: 6. oktober 2006 21:01
> 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="l=
ax"/>
>     </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:stron=
g> 
> blah!</description>
> 
> Works in everything except the .NET tools (even MSXML passes the 
> document...).
> 
> Thanks,
> Jeff
> 
> 
> 


From xan.gregg@j... Mon Oct 09 13:10:22 2006
Received: from maggie.w3.org ([193.51.208.68])
	by frink.w3.org with esmtp (


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