Hi folks,
Once xerces2 beta3 comes out, we'll probably want to move fairly quickly on integrating schema support more closely into the Xerces2 code base. Aside from where all the files should live--a question which we've discussed before and about which I'll post again hopefully tomorrow--, one of the questions we'll have to answer is whether to have the SchemaValidator as a component in the StandardParserConfiguration or whether to continue the practice of having a SchemaParserConfiguration extending StandardParserConfiguration. Although you can always argue that the number of possible configurations is infinite, I'm persuaded that there are enough folks who want to only use DTD's--especially in performance-critical applications--that having a separate SchemaParserConfiguration class makes sense. On the other hand, I imagine it's less likely people would only want schema validation without any kind of DTD validation; some folks like to use entities in their schema documents. What do people think? Is providing a DTD-only configuration worth having an extra class? Cheers, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
