Some custmers want to have the validation for XMLs in the config repository.
That is a good point to have a set of XSD schemas to perform verification.
There can be several ways to do this:
Offline validation.
According to the idea of keeping the configuration as readonly on production and do not modify it there directly, there is no strict need to perform validation each time on loading the documents. On the preprod environment where the configuration is prepared the Editor may run validation against the XSD once the files are edited.
Validation at runtime.
Due to the flexibility of Config Server processors and their generic behavior we cannot predict how the source files will be used by processors we cannot even know which files are text and which binaries and we do not know in forehead which are XMLs and which are not. So, the processors can be implemented in a way to explicitly validate the loaded documents if they pretend to be XMLs. That is however not really needed as a typical operating environment have already tested and verified configuration repository from the SCM.
According to the above description the only reasonable way to validate configuration repository is ofline validation of edited XML files on pre-prod environment. That environment should be typically used to modify and design the configuration. The config files get to the SCM from that environment and then those files are checked out on prod.
At the later stage, when we introduce the Config Editor UI, the editing process will involve the validation prior to the saving XML files to filesystem.
In order to have the offline validation we need to create a set o XSD schemas for all kinds of configuration sources.
However, I would not cosider those XSDs (on this stage) as stable as we are planning to review the current CD and PE configuration format and redesign it. Current configuration format is difficult to maintain.
That means that we will spend some effort to create the XSD files for current structure and then we will throw these schemas after we review the configuration.
Some custmers want to have the validation for XMLs in the config repository. That is a good point to have a set of XSD schemas to perform verification. There can be several ways to do this:
According to the above description the only reasonable way to validate configuration repository is ofline validation of edited XML files on pre-prod environment. That environment should be typically used to modify and design the configuration. The config files get to the SCM from that environment and then those files are checked out on prod.
At the later stage, when we introduce the Config Editor UI, the editing process will involve the validation prior to the saving XML files to filesystem. In order to have the offline validation we need to create a set o XSD schemas for all kinds of configuration sources.
However, I would not cosider those XSDs (on this stage) as stable as we are planning to review the current CD and PE configuration format and redesign it. Current configuration format is difficult to maintain.
That means that we will spend some effort to create the XSD files for current structure and then we will throw these schemas after we review the configuration.