In 2.1 we introduced to read the schema name from configuration, to be abel to produce same name as in 2.0. However we discovered, in last minute, that this was wrong. The schema name shoudl be DATEXIISchema_[model base version]_[tool major version]_[tool minor version].xsd
The last minute change did not revert back to the old rules, instead we just changed to configuration file. That will create a wrong schema name if you use a 2.0 model or if you use a future version. So the best is to revert back to old rules.
I did make it even more flexible. No if the LevelAPost2_0SchemaName tag is in the configuration it will be used. Otherwise the olde rules will be used.
Will be in next release.