|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: semantics in schema (xsd)
On Fri, Feb 27, 2004 at 10:50:02AM -0500, Irene Polikoff wrote: > What you are bringing up is that in some countries a husband may be also > a male. One way to handle it is to create a subclass of homosexual males Actually it's nothing about whether one is heterosexual or homosexual -- a homosexual man may marry a woman in every country I'm aware of, and in some are encouraged to do so. So can a bisexual. The point I was trying to make, though, was just that it's an example of overspecification in software. Another (perhaps less controversial) example is the time I could not book an airline ticket from a particular US airline... their Web page had a "Canadian orders" page, but they checked that the city in the billing address of your credit card matched the "zip code" of your address... and the form didn't let you put anything except a US-format zip code... my postal code starts with an "M", and they didn't allow that... so the credit card test filaed, and I couldn't order the ticket. They've sinced fixed it, so I won't name them :-) Other examples include requiring telephone digits to have a particular number of digits or not allowing "extension" or "ask for Susan" in text there... These are all examples of the software applying too rigid a test and failing with real-world data. > This is, however, going quite beyond the scope of the original example. Agreed :-) But it can be useful to think about sometimes, for people who work with schemas that constrain data. Liam -- Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/ http://www.holoweb.net/~liam/
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||

Cart








