Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: Possible to restrict top-level xs:element names?

From: "Michael Kay" <mike@--------.--->
To: "'C. M. Sperberg-McQueen'" <cmsmcq@-------------.--->,
Date: 11/7/2009 10:27:00 AM
>    (b) make sure your processor distinguishes between elements
>        with [validity]=invalid and those with [validity]=notKnown
>        (again, how you do this is between you and your processor,
>        and out of scope for the XSD spec); and

You might like to note that Saxon's schema processor, and perhaps some other
products, expose this distinction by allowing you to select "strict" or
"lax" validation. Strict validation fails if the outcome is
[validity]=notKnown, whereas lax validation succeeds.

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay 




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