Remove support for Sesame
glenrobson opened this issue · comments
SAS supports too many options which makes development and maintenance more difficult. The original reason to support Sesame was to give a Web front end to access the annotations as linked data. This can now be done with Jena using the Fueski web front end.
Jena is a better solution for an RDF store as it can run locally without a separate Web App so it fits the primary use case of a simple install.
Unless issues are raised here Sesame support will be removed in the near future.
What about updating SAS to work with the SPARQL/Update protocol, and then you can put to SPARQL 1.1 compliant update endpoint, which will work with Sesame, Fuseki, and most other open source or commercial platforms. Then SAS interacts via a standardized API rather than a directory of binary files (TDB?) My use case is that SAS and other web applications need to be able to read and write to Fuseki running in Tomcat, so pointing to a data directory might not be feasible.
Thanks that sounds a neat solution to cutting down the custom connectors while supporting more back ends :-)