Currently, SparqlEndpointGraph can only be instantiated by providing a single connection string that points to a unified SPARQL endpoint (typically .../sparql) exposed by a triplestore.
|
@UriParam(defaultValue = "null") |
|
private String sparqlEndpoint; |
While this works for many triplestores, not all implementations expose such a convenience endpoint. A unified /sparql endpoint is capable of handling both SPARQL queries and updates, dispatching requests based on the HTTP method or content type. However, some triplestores, such as Oxigraph, expose separate endpoints for queries and updates instead.
I would add support for the situation where the query and update endpoints are provided separately. As this is already handled by RDF4J link i think that it would boil down to adding another sparqlEndpoint parameter to the graph get operation.
WDYT @marioscrock?
Currently, SparqlEndpointGraph can only be instantiated by providing a single connection string that points to a unified SPARQL endpoint (typically .../sparql) exposed by a triplestore.
chimera/camel-chimera-graph/src/main/java/com/cefriel/component/GraphEndpoint.java
Lines 45 to 46 in 891f4c1
While this works for many triplestores, not all implementations expose such a convenience endpoint. A unified /sparql endpoint is capable of handling both SPARQL queries and updates, dispatching requests based on the HTTP method or content type. However, some triplestores, such as Oxigraph, expose separate endpoints for queries and updates instead.
I would add support for the situation where the query and update endpoints are provided separately. As this is already handled by RDF4J link i think that it would boil down to adding another sparqlEndpoint parameter to the graph get operation.
WDYT @marioscrock?