tum-esi / wot-system-description Goto Github PK

This is meant to be a checklist of everything that needs to be added to improve the descriptiveness System Description:

• Allow for branches in atomic mashups
• Allow for all kinds of comparisons in loops and branches

Currently, one needs to put all the TDs of the Things of the system in an array. However, when these TDs are not correct in the sense that an affordance in the plantuml is not found, the following error is generated:

generateSD problem!: TypeError: Cannot read properties of undefined (reading 'forms')

This happens when an affordance cannot be found. It should be easy to log what this affordance is.

Currently, the main.ts is the entry point but other classes and functions also use filesystem etc. making it difficult to use outside of a cli environment (in other packages).
They should be separated to allow easier integration to other packages.

There is a need to write a wiki or a specification-style document that describes the rules and syntax of the SD in both UML and JSON-LD format