Description of the enhancement

Support reading content of config.ttl from a SPARQL endpoint. This would require to add two new properties in config.ttl, such as skosmos:configEndpoint and skosmos:configGraph to config.ttl so additional triples are taken from referenced SPARQL endpoint

Configuration is loaded in model/GlobalConfig.php and cached for performance reasons. I think the end of initializeConfig may be a good place to add loading of additional configuration via SPARQL. To avoid doing a SPARQL request each time, the result should be cached as well. I'm not sure on cache invalidation. Maybe only reload on request with a special query parameter e.g. ?config=reload.

Who are the users that would benefit from the enhancement and how?

User who prefer to manage their configuration in Fuseki database.

What new functionalities would the enhancement make possible?

In particular this would allow to manage vocabularies in one place (Fuseki).

Why is the enhancement important?

Adition of vocabularies requires to modify both config.ttl and import into Fuseki. This feature woul allow to manage it in one place and make sure the configuration is valid RDF (no invalid Turtle syntax).