: conversion tool... Other is to define a "version" on the config and : depending on the version, the expected structure will be different.
FYI: schema.xml does have this ... it's one of hte ,schema> attributes. we've only ever reved it once when multiValue fields were added because we wanted to preserve backwards compatibility for old schemas that expected all fields to be multie valued, but it *really* didnt' make sense for that to be the default moving forward. I'm not sure a schema syntax version bump is really waranted just to chnage "class"=>"factory" in tokenizer/filter declarations .. especially since the main motivation is a ReflectTokenFilterFactory that we would probably recommend against using "in production" for performance reasons. -Hoss
