...
Each configuration item contained in an XML file must be formatted as specified in an appropriate XML schema (XSD file). Validating against the schemas is an important step in configuring Delft-FEWS, as the XML validation makes sure the syntax of the configuration made is correct. There are two types of configuration in Delft-FEWS. In the first set, for each different schema type, only one default configuration file may be used and the name of the configuration file is unique. For the second set of configuration, multiple configuration types may be available for a specific schema. The names of these may be defined by the user. An XML file contained in the regional configuration element is then used to register these XML files with a user specified name to the system, and identify the type of configuration. This file is referred to as a descriptor file. Table1 identifies for which type of configuration a single files per type is allowed and for which multiple instances for each type of configuration may exist.
Versioning of configuration and XML file naming
...
conventions (now obsolete)
| Warning |
|---|
NB. The "default" versioning name convention described here is not required / recommend anymore for new configurations. |
...
Another version of configuration will have a different version number. The <default> item is omitted. Examples:
| example | description |
|---|---|
| Explorer 1.00 default.xml | A "default" version of the configuration settings for the FEWS Explorer |
| Explorer 2.00.xml | A second version that is not made active, since it has not the "default" tag. |
In the central database active versions of configuration items have synchLevel 11 whereas inactive configuration files have synchLevel 0.