Summary
The SPARQL endpoint (POST /api/v1/search/sparql) is fully functional for read-only queries (SELECT, ASK, CONSTRUCT, DESCRIBE). This issue tracks enhancements to support the upcoming frontend SPARQL query explorer.
Enhancements
1. Named graph / default graph support
The default_graph field in SPARQLQuery is currently unused (already noted in sparql-ontology-loading.md). Implement support for:
- Specifying a default graph URI
- Querying across named graphs when multiple ontology files exist in a project
2. Query history (optional)
- Store recent queries per user per project for easy re-execution from the frontend
- Could be a simple PostgreSQL table or Redis cache
Context
The frontend SPARQL query explorer will consume this endpoint. The current endpoint is production-ready for the initial UI — these are follow-up enhancements.
Related
Summary
The SPARQL endpoint (
POST /api/v1/search/sparql) is fully functional for read-only queries (SELECT, ASK, CONSTRUCT, DESCRIBE). This issue tracks enhancements to support the upcoming frontend SPARQL query explorer.Enhancements
1. Named graph / default graph support
The
default_graphfield inSPARQLQueryis currently unused (already noted insparql-ontology-loading.md). Implement support for:2. Query history (optional)
Context
The frontend SPARQL query explorer will consume this endpoint. The current endpoint is production-ready for the initial UI — these are follow-up enhancements.
Related