#7 Parsing Specification Documents to populate configurations

[hoos]

Currently we manually populate the Genesis configuration hierarchy from the Genesis specification documents. These documents are typically written using Word or XHTML.

We need to create templates for these documents in popular formats and then write a parsing task for Genesis so that we can automate the population of the configuration hierarchy. The task should also check the configurations using the schemas defined by us or the organisation specific schemas to ensure standards such as nomenclature are adhered to.

The benefits of this approach include:

- Reducing the time it takes to populate the hierarchy.
- Eliminating manual errors in the population process.
- Automated validation of configurations.