Description
Have a versioning + upgrade system for the dao-params.json schema. This way, when the migration script is given an old version of a dao-params.json file ( v0.5 for example), it can run it through incremental upgrade scripts that turn it into the latest version (v0.9 for example), and then it knows for sure that the schema is what it's expecting. Major updates can still be made that break backwards compatibility, but it'd be up to the upgrade script to determine that and report back the error state.
The idea behind this is to make the dao-params.json file format much more robust than it currently is, eventually making it a well defined and widely used DAO serialization file format. An example of such a file format in the wild today is the FBX file format pioneered by Autodesk. It started as proprietary, but is now used as an "industry standard" for digital content creators (film, games, etc).