: There is some work on SOLR-17 to track this. I put up a patch that's : incomplete, based on the prior work done by Mike Baranczak and Hoss and : others. I've been meaning to get back to it, but have been swamped.
Actually SOLR-17 tracks an XSD for the XML "response" format you get form the XmlResponseWriter. As for schema.xml: because of some design decisions made *way* early on in Solr's lifespan, this is pretty much impossible -- every custom TokenFilterFactory or TokenizerFactory is allowed to define whatever attributes it wants, so while an XSD could be created to verify if some (incredibly simple) schema.xml files are valid, lots of schema.xml files that failed validation could be run fine with the proper plugins loaded. (This is essentially the same problem that ant had in it's early days. If we had thought about it at the time, we could have required plugins to use XML Naamespaces for their custom attributes (the same way ant evnetually idd) but if we had to do it over again i suspect most people would skip custom configuration anyway and go with Spring XML and some custom tags to make the syntax less verbose) -Hoss
