Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: XML Schema spec: Attribute Wildcard Intersection

From: richard@------.--.--.-- (------- -----)
To: NULL
Date: 5/3/2005 11:57:00 AM
In article <d575lm$1c13$1@n...>,
Alain Frisch <frisch@c...> wrote:
>I have another question. Rule 5 is:
>
>=============================================
>If the two are negations of different namespace names, then the 
>intersection is not expressible.
>=============================================
>
>Can this actually happen in a valid XML Schema document?  Does the spec 
>make it impossible with another condition somewhere else?  Otherwise, how 
>is the processor supposed to handle this case?

It can happen, if you restrict one ##other wildcard with another
(obviously you must have imported a schema for another namespace to be
able to do this).

I think the processor is supposed to handle it by saying "you can't do
that".

-- Richard



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