W3C home > Mailing lists > Public > xmlschema-dev@w3.org > April 2007

Re: Permit (greedy) conflicting wildcards

From: <noah_mendelsohn@us.ibm.com>
Date: Tue, 10 Apr 2007 15:06:18 -0400
To: "Pete Cordell" <petexmldev@tech-know-ware.com>
Cc: xmlschema-dev@w3.org
Message-ID: <OF73CC67BE.A50B0349-ON852572B9.00689339-852572B9.0068C094@lotus.com>

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
--------------------------------------
Received on Tuesday, 10 April 2007 19:06:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:59 GMT