On 5ÔÂ15ÈÕ, ÏÂÎç8ʱ25·Ö, Joe Kesselman <keshlam-nos....@comcast.netwrote:
Enumeration won't do it, since you want to enumerate the forbidden
values. You might be able to get this via regular expressions... or it
might make more sense to just check it in the application rather than in
the schema. Given your examples, I suspect that this may actually wind
up wanting to be decided on a per-installation or per-user basis, which
would be another reason to keep it in the application rather than the
schema.
--
() ASCII Ribbon Campaign | Joe Kesselman
/\ Stamp out HTML e-mail! | System architexture and kinetic poetry
thanks for your reply.
Using regular expressions to describe such a "blacklist" is too hard.
Actually, I use an xml as the configure file of my application,
the configuration validation and the configuration loading are
seprated,
so i must do the restriction at the stage of configuration validation.