Sorry to jump in to the middle of a discussion,
> > I don't think this would be backward compatible to the previous spec > > version. Old apps may want to validate against a DTD and expect an > > error if instance doc does not reference one. > > First of all, I could not find anywhere in JAXP specs that setting > setValidation() sets validation against DTD. > So it was parser/implementation specific. Maybe so, but I guess when JAXP is developed, "validation" implied nothing but DTD, since there wasn't XML Schema at that time. And even if I'm wrong, I'm sure many developers made this assumption. So I think Edwin is right from practical point of view. > > 3) app wants to validate to DTD or XSD, the case you state > > On factory, set validation to true. Language property is not specified. > For Xerces implementation it would mean that we create a parser with all > available validators (currently use DTDXSParserConfiguration). How can I specify this behavior without relying on the parser default behavior? If this #3 use case is really anticipated, we should have a mechanism to explicitly specify this behavior. (Edwin wrote:) > I don't think this is backward compatible. We may need to come up w/ a > new schemaLanguage value for this case. Although I can't think of any other way, I'm not sure if it's a good idea to treat DTD-or-w3c-schema auto detection feature as one virtual schema language. For one, what happens with respect to the schemaLocation property? Or, why can't I do DTD-or-relax-ng auto detection, while I can do DTD-or-w3c-schema? One additional comment: don't we need to take JAXP schemaLocation property into account? regards, ---------------------- K.Kawaguchi E-Mail: [EMAIL PROTECTED] _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
