|
From: <jas...@ma...> - 2005-06-14 08:00:20
|
On 13 Jun 2005, at 17:47, Fredrik Lindgren wrote: > On Mon, 13 Jun 2005 09:51:04 +0200, <jas...@ma...> wrote: >> >>> Please go ahead and add the custm xml functionality, but in the >>> Spring spirit, keep the validation implementation pluggable. >>> >> >> It is! :) >> >> Whatever the end user uses to validate their XML is up to them - >> either DTD, XSD or no validation are the choices right now. >> > > I know. That's why I support adding the functionality as it is > right now. I only objected to the idea of switching to XSD as a > required/default validation mechanism for the spring XML. > Personally I prefer to use RELAX NG for my validation needs since > it has better support for alternative syntaxes (attribute or child > content) and support for cooccurence constraints which might be > helpful for catching some additional configuration errors. I'll > check out the implementation details and try to get back with more > constructive feedback. Agreed! XSD is a PITA :) It might even be simpler to write the Spring schema in terms of RelaxNG, then code generate the DTD and XSD from it - letting folks use whichever schema validation mechanism they wish - DTD or XSD or if they can Relax NG. http://thaiopensource.com/relaxng/trang.html If nothing else, this will mean we don't have to hand-maintain both the DTD and the XSD - but also RelaxNG is so much simpler to read James ------- http://radio.weblogs.com/0112098/ |