Hi all, There seems to be some disagreement between the description of this feature and its implementation.
The description [1] (along with that of the feature "http://xml.org/sax/features/validation"; [2]) seems to indicate that if you want dynamic validation, you only need to turn on the dynamic validation feature, but not the validation feature. But in the implementation, for dynamic DTD validation to happen, both features need to be turned on. The implementation of Schema validation, on the other hand, does work as what the description says: turning on dynamic validation is sufficient to get the behavior. So what should we do here? Fix DTD validation so that it doesn't require both features to be turned on? Or fix the feature description and Schema implementation? (I talked to some of the committers privately, but didn't come to a consent. :-( ) The difference between the 2 interpretations only appears when the validation feature is off, but the dynamic validation feature is on. My preference would be to fix the DTD validation so that we perform dynamic validation in the above case. This would make our documentation and implementation more consistent. One may fear such change might break some people. But when a user turns on the dynamic validation feature (whether the validation feature is on or off), he's expecting something to happen, isn't he? So I don't think we would actually break anybody. [1] http://xml.apache.org/xerces2-j/features.html#validation.dynamic [2] http://xml.apache.org/xerces2-j/features.html#validation Thanks, Sandy Gao Software Developer, IBM Canada (1-905) 413-3255 [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
