OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Implement data rules in application code?

I have often felt concern for how difficult filling out forms must be for Dr Who. Which address should he give, if he can be multiple places at the same external time? If he cannot reveal his name, I guess he gets his wife to fill in that part of the form? How would he handle choosing his age from a pull down list? Better to run around old quarries rather than fill in a form.

I expect most of us know people with similar problems: an Indonesian mate has only one name "What is your first name?" "Munali" What is your last name?" "Munali" "So Munali Munali?" "No just Munali".  Transgender people must be quite patient. Are validations against men having husbands or women having wives being disabled as we sit here?


On 12 Apr 2017 17:27, "Michael Kay" <mike@saxonica.com> wrote:
> For example, that your travel-agency application does not handle red-haired people.

And in practice, many integrity constraints are actually guards to prevent "edge cases" reaching the application when the application can't handle them.

Typical example: every bank branch must have a postal address. Meaning: sorry, this application can't handle the travelling bank-in-a-bus that we introduced to serve remote rural communities. You're just going to have to give the bus a dummy address, or things won't work.

Michael Kay

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS