Hey Steve Ebersole,

whatever drives this process needs to know that the user wants to drop and recreate the schema or validate the schema etc

+1 That makes sense.

The other option I see is to have the "driver" do that all parsing/interpretation and passing a parameter-object representation of that into the SchemaCreator, etc.

The parameter object seems good. I suppose we'll still need a representation of the "target" as part of that parameter object, but just as an enum or so, so impls SchemaCreator et al. can decide whether to write to the DB or file (or console). It should also allow to have just one method on each of SchemaCreator instead of the plethora of overloaded methods.