In the past we had to maintain two smart connector code bases (the old one based on Apache Jena Fuseki) and the newer one that we are using today. During that time we created the SmartConnectorProvider mechanism to have a single interface for both implementations and this would make it easier to switch to the newer version. This actually happened quite shorty after that and the old version was no longer needed.
Currently, this code is still there and could be used in the future if we want to create a new smart connector implementation, but maybe we should remove the code for now because it slightly complicates the REST server.
See: eu.knowledge.engine.smartconnector.api.SmartConnectorProvider
In the past we had to maintain two smart connector code bases (the old one based on Apache Jena Fuseki) and the newer one that we are using today. During that time we created the SmartConnectorProvider mechanism to have a single interface for both implementations and this would make it easier to switch to the newer version. This actually happened quite shorty after that and the old version was no longer needed.
Currently, this code is still there and could be used in the future if we want to create a new smart connector implementation, but maybe we should remove the code for now because it slightly complicates the REST server.
See: eu.knowledge.engine.smartconnector.api.SmartConnectorProvider