Page History

...

1. The output of the generator shall be capable of being used as input to further tooling, e.g. tooling that executes the schema in the database.
2. As the output can be used as input to further tooling, it should allow configuration of output to support major options in the DB schema without manual editing, to support automation of the complete processing chain.
3. The generator shall have an architecture that supports extension for further DBs unless it becomes very clear that different DBs require seperate implementations for recognised architectural reasons.
4. The generator shall separate input of VSS catalog, DB meta-data and VSS overlays. This allows a separation of concerns.
5. VSS overlays should be supported as an input to allow the set of VSS nodes to be processed to be defined. Along with additional meta-data.
6. DB meta-data should be supported to allow the generator to make effective use of DB features such as data-types, encoding, attributes and tags.
7. Development should consider whether it should be implemented as part of the VSS-tools exporter toolset.
8. Development should consider what existing tooling eco-systems exist that it could leverage. For example, mapping VSS vspec to a memory model in VSS-tools, or third-party DB tooling.

...