Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: xsd:any processContents strict

From: Sandy Gao <sandygao@--.---.--->
To: Bryan Rasmussen <brs@----.-->
Date: 1/25/2006 4:38:00 AM
> If I send an instance to a validator and it encounters content it does 
not
> understand it is up to the processor if it defaults to validate strict, 
lax,
> skip....

Lax or skip, not strict. See [1].

> But if I have an xsd:any and set the processContents to be strict then 
the
> processor must follow the strict validation model for everything that 
within
> the element that can hold 'any', correct? Or is it just that the child
> elements of the element that can hold any must be processed strict?

If an element matches <xsd:any processContents="strict">, then either an 
element declaration or a type definition must be found to validate such 
element. If none can be found, it's a validation error on the *parent* 
element, not the element itself. If this happens, the element may be laxly 
assessed, also see [1]. This doesn't affect content (sub-elements or 
attributes) of this element.

[1] http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/#key-lva

Thanks,
Sandy Gao
XML Parser Development, IBM Canada
(1-905) 413-3255
sandygao@c...


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