 |
|
|
Pete Cordell wrote:
Hi
> Personally I think that, subject to occurrence constraints, the
> particle that is currently gobbling up input, should have
> priority (i.e. they're greedy).
So the following, from the current example:
<xs:sequence maxOccurs="unbound">
<xs:element ref="elem"/>
<xs:any namespace="##targetNamespace" maxOccurs="unbound"/>
</xs:sequence>
would be valid, while a bit of an obfuscation because the maxOccurs on
the sequence won't be taken into account. Right?
Is the above quote what tells XML Schema 1.1? If yes, where it is in
the WD?
Regards,
--drkm
_____________________________________________________________________________
Envoyez avec Yahoo! Mail. Une boite mail plus intelligente http://mail.yahoo.fr
From petexmldev@c... Wed Jun 25 12:41:23 2008
Received: from [128.30.52.63] (h
|
|
| |
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.
| |
| |
|
|
|
