Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Unique Particle Attribution constraint and XML schema extensions

From: Xan Gregg <xan.gregg@---.--->
To: Tony Opatha <topatha@-----.--->
Date: 4/30/2004 4:35:00 AM
> Will adding elements right after the:
>
> <xs:any namespace="##other" processContents="lax" minOccurs="0"/>, or
> <xs:any namespace="##any" processContents="lax" minOccurs="0"/>
>
> violate unique particle attribute rule, i.e., we have a case of 
> non-deterministic content model? if they do not violate what is the 
> reason that they don't?

Yes, adding particles with extension will violate the constraint since 
the wildcard is optional, except in the case you mention when you add 
particles in the original target namespace after the ##other wildcard.  
The value of processContents does not affect UPA.  Nor does the value 
of abstract.

One alternative I've seen is to put the wildcard in a wrapper 
extensibility element; I think WSDL uses this technique for 
extensibility.  XML Schema itself uses this technique via the 
xs:appinfo elements.

xan



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