As of right now, the graph is wiped each time it's updated. This could be problematic for services depending on particular URIs.
This will require a refactoring the triplifier to avoid URI collisions as well as the deployment architecture so that the graph isn't deleted before a triplication.
As of right now, the graph is wiped each time it's updated. This could be problematic for services depending on particular URIs.
This will require a refactoring the triplifier to avoid URI collisions as well as the deployment architecture so that the graph isn't deleted before a triplication.