[EMAIL PROTECTED] wrote: > > Hi Edwin, > > I'm afraid I'm -1 on the second proposal. I think the intent of 1.4.4 is > to be strictly a maintenance release, where we fix as many bugs as we can > before throwing our whole force as a community behind Xerces2. If we end > up pursuing Xerces1 further for whatever reason, then, for instance if we > were to consider upgrading it to support the future JAXP 1.2, I think this > would make sense--but only as a 1.5 release. But as it stands, by the time > JAXP 1.2 is finished Xerces2 should be the standard and xerces1 should be > deprecated. There's also the point that, if Xerces1 finds a DTD, even if > schema validation is on it won't complain. > > In any event, why plan for the future if there isn't going to be one? :-)
I see your point about Xerces 1.4.4. So another option would be that the default would stay the same if DOMParser or SAXParser was directly instantiated, but XMLSchema validation would be off if the parser is instantiated via JAXP. What do you think? So does this mean that you support changing the XMLSchema validation default to "false" for Xerces 2? -Edwin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
