Parliament's current REST API implementation is based on a heavily customized version of Jena's Joseki project. This code has been obsoleted by Fuseki, but migrating Parliament to Fuseki turns out to be more costly than it is worth. Re-customizing it would take a great deal of time, and then land us in the same difficult situation when we need to migrate to a newer version. Instead, the better approach is to write our own REST API implementation, because this is not particularly difficult.
Additional tasks that would go nicely with this effort:
Conversion of the JSP pages to something more modern, like Angular
Switch from Jetty to Spring Boot
Incorporate the Map view for geospatial data from the DOMEX demo effort
Incorporate the graph view (a la Analyst's Notebook) from the DOMEX demo effort
Realize the primary benefit of ditching Joseki, i.e., update to the latest version of Jena ARQ/Core
Parliament's current REST API implementation is based on a heavily customized version of Jena's Joseki project. This code has been obsoleted by Fuseki, but migrating Parliament to Fuseki turns out to be more costly than it is worth. Re-customizing it would take a great deal of time, and then land us in the same difficult situation when we need to migrate to a newer version. Instead, the better approach is to write our own REST API implementation, because this is not particularly difficult.
Additional tasks that would go nicely with this effort: