Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Permit (greedy) conflicting wildcards

From: noah_mendelsohn@--.---.---
To: "Pete Cordell" <petexmldev@--------------.--->
Date: 4/10/2007 11:06:00 AM
Pete Cordell writes:

> I think it will be possible to find many cases where such an 
> extension does not make sense.  But I also think that it will 
> be possible to find many cases where it does make sense. 

Sure, but you can always allow for it.  For example, you could do:

        <choice>
                <element ref="html"/>
                <any notQname="##defined"/>
        </choice>

Many other strategies are possible.  For example, instead of the ref to 
the HTML element, that could be a reference to a group with a choice of 
several elements.  The point is, if it's in your schema, you tend to know 
about it, and can reference it if you want to allow it. 

Furthermore, nothing requires you to use a NIS wildcard.  You've 
acknowledged it's useful in some cases.  In the others, use something 
else!

--------------------------------------
Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------





From petexmldev@t... Tue Apr 10 19:43:52 2007
Received: from aji.w3


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