Programmatic generation of documentation diagrams

[coolharsh55]

Adding diagrams to present/explain:

1. Taxonomy for each module, e.g. hierarchy of concepts under 'Purpose'
2. Properties available under each module and their use e.g. 'Purpose'
3. Properties possible for use for each concept, e.g. 'Store' as a processing category can use hasLocation, hasStorage, hasDuration (tbd)

Diagrams depend on concepts, which may change over time. Their generation, therefore, should be preferably programmatic. It should not add a burden to the development and should not be 'difficult' to modify or understand in case changes need to be made. Some available opportunities to explore for this:

• WebVOWL
• Graphviz
• Custom JS diagramming libraries such as mxGraph

[coolharsh55]

https://harshp.com/dpv-x/documentation-generator-diagrams/ (edited link for demo) Trying to autogenerate svg for each concept using GraphViz

[coolharsh55]

We have used plantuml for the diagrams in DPV 2.0 docs - which can be used to automatically update the source files as concepts change in the future, thus ensuring diagrams are always up to date. Some creative querying/filtering would be needed to select specifically those concepts represented in the diagrams - the modular structure of DPV and extensions will simplify this.