- From: Michael Kay <mike@saxonica.com>
- Date: Wed, 2 May 2007 20:22:28 +0100
- To: "'Bryce Nesbitt'" <bryce1@obviously.com>, <xmlschema-dev@w3.org>
- Cc: "'Pete Cordell'" <petexmldev@tech-know-ware.com>, "'Chuck Herrick'" <cherrick@spamcop.net>
This sounds like just another example of conditional type assignment: type="if (@enum_extension) then xs:string else my:enumerated-type" Michael Kay http://www.saxonica.com/ > -----Original Message----- > From: xmlschema-dev-request@w3.org > [mailto:xmlschema-dev-request@w3.org] On Behalf Of Bryce Nesbitt > Sent: 02 May 2007 20:08 > To: xmlschema-dev@w3.org > Cc: Pete Cordell; Chuck Herrick > Subject: Re: Schema 1.1: xs:anyEnumeration considered? > > > The original poster (that's me) was drawing an analogy > between Java and XML, perhaps a little unfair. In the Java > world packages outside the core get an "x" in their name (for > "experimental" or "extended") until they are eventually > folded into the core. > > For XML enums it might look like this. Imagine an > enumeration containing "schwinn", "huffy" and "specialized", then: > > <vendor>specialized</vendor> > <vendor>heffy</vendor> > <vendor>Schwinn</vendor> > <vendor enum_extension="true">breezer</vendor> > > when validated "heffy" would be invalid, but "breezer" is > clearly marked as existing outside the predefined list of > bicycle manufacturers. > > > > Pete Cordell wrote: > > > > Gee, thanks. Believe it or not I had already tried that, but it > > didn't actually give me any additional insight into what > the OP was suggesting. > > About as useful as suggesting: > > > > > http://www.google.com/search?hl=en&q=computer+science&btnG=Google+Sear > > ch > >
Received on Wednesday, 2 May 2007 19:22:46 UTC