Debug logging for lifecycle methods like initialization and when data has to be re-inferred (eg. when something is deleted).

Trace logging would be per statement to log what gets inferred.

At the moment, global plugins are declared in a list (which is – by default – ordered). However, this is not the case for vocabulary-specific plugins, please see https://github.com/NatLibFi/Skosmos/wiki/Plugins#activating-plugins. This will cause trouble as I can not guarantee/change their respective execution order.

I think implementing this will request two kinds of changes to the code base:

Provide support for working with UML diagrams as graphs, e.g., applying inference, shape constraints, probabilistic rules, etc.

These are the approximate steps to follow:

1. Identify a reasonably small UML diagram to use as test case.
2. Scope/Discovery: in what ways are UML diagrams represented commonly?

• Graphviz DOT files, e.g.,
• https://github.com/abulka/pynsource
• <http

e.g. as per fnielsen/wembedder#13 .

As long as that does not exist, we could also link to https://arxiv.org/abs/1710.04099 to get things rolling.