e.g. so folks could use a file system (then use svn / git / whatever to version control it) then mirror the configuration to various environments.
Then folks could either just run a command now and again on a machine (e.g. on a svn/git commit hook) to check out the configuration as files, iterate through it and compare it to ZK and apply any changes).
We could then mirror contents of ZK as a tree of property files (or JSON/XML docs) using folders for folders in ZK etc.
Folks could then easily install a configuration in ZK from a file; or do the heroku style model where fabrics can be tied to a branch in a SCM; then the SCM machine can replicate changes to the ZK fabric registries; without the ZK servers having to communicate with unreliable SCM servers etc.