That means turning one feature on/off magically changes the state of
another feature, so the order of setting the features will become
significant. This would definitely confuse people, and result in
unpredictable behavior.
I think we should take the simple and clear approach, and let people
learn/remember what dynamic validation means, instead of letting them
guess/hope what it means.
Cheers,
Sandy Gao
Software Developer, IBM Canada
(1-905) 413-3255
[EMAIL PROTECTED]
Joseph
Kesselman/Watson/ To: [EMAIL PROTECTED]
IBM@IBMUS cc:
Subject: Re: feature
http://apache.org/xml/features/validation/dynamic]
01/23/2003 03:03
PM
Please respond to
xerces-j-dev
>dynamic-validation feature should have effect, when set, whatever's been
>done to the validation feature.
Personally, I like the "you obviously meant" behavior -- turning dynamic on
should imply validation is turned on if not already on. Turning validation
off should turn dynamic off if it isn't already off.
(What we *really* want is a single parameter, validationMode, which covers
all the combinations of schema/dtd must/may/must-not be consulted. But
given how the APIs have been standardized, it's a bit late to make that
large a change.)
______________________________________
Joe Kesselman / IBM Research
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
