Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: running XML Schema 1.0 using a 1.1 processor

From: "Michael Kay" <mike@--------.--->
To: "'Andrew Welch'" <andrew.j.welch@-----.--->, <xmlschema-dev@--.--->
Date: 7/11/2008 12:32:00 PM
 
> 
> In Saxon to run a 1.1 schema you need to explicitly enable 
> it, otherwise it will run as 1.0.
> 
> Is there any harm is always enabling 1.1 - even when running 
> 1.0 schemas - or are there issues which mean a 1.0 schema 
> must always be run in 1.0 mode?
> 

The only issue is that you won't get any error messages if you use 1.1
facilities by mistake, for example maxOccurs on particles in an xs:all group
won't be checked against the 1.0 rules.

I did it this way because some of the new facilities in 1.1 don't involve
new syntax, they involve the removal of restrictions on existing syntax, and
I wanted to make sure that people would get the stricter 1.0 checking by
default, especially as 1.1 is still rather bleeding edge.

If your schema is valid against the 1.0 rules then I don't think there are
any cases where it will behave differently if 1.1 is enabled.

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


From dragon-fly999@h... Fri Jul 11 14:25:48 2008
Received: fr


transparent
Print
Mail
Digg
delicious
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