sparql

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:

Let's show some examples of integration with kgextension
https://kgextension.readthedocs.io/en/latest/

Could be another notebook added to the tutorial.

Where it fits, we might also integrate as a dependency?

There are several components to this:

• good documentation both within the code as well as in the repo (e.g. README) and issues (e.g. labels)
• interoperability (e.g. indentation style)
• behavioural guidance (e.g. code of conduct or issue templates)

Some more points in this post (albeit with a certain bias for Node).