[
https://issues.apache.org/jira/browse/JENA-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492556#comment-17492556
]
Andy Seaborne commented on JENA-2282:
-------------------------------------
This would be great.
My hope is that we divide the UI into parts - working with data (query, update
and upload), monitoring the server, and configuring the server.
The first part, working with data, is using SPARQL protocol operations so we
could have it a project output that for any SPARQL endpoint, not Fuseki
specifically.
[Elsewhere|https://jena.apache.org/documentation/fuseki2/fuseki-modules], there
is work to have modules for the server. One such usage is having a drop-in for
Fuseki/Main which provides some or all of the UI. With that, we decouple the UI
from needing the webapp framework and containers can be less clunky.
We don't have to decide now whether the query developer is core or a drop-in.
We do probably need to discuss where the whole UI is going so we can have new
features in releases without ending up in a big release but later.
> Fuseki2 Query Store
> -------------------
>
> Key: JENA-2282
> URL: https://issues.apache.org/jira/browse/JENA-2282
> Project: Apache Jena
> Issue Type: Wish
> Components: Fuseki UI
> Affects Versions: Jena 4.4.0
> Reporter: Nicholas
> Priority: Minor
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Many triplestore applications have a way to store SPARQL queries. These sorts
> of application parts are really useful: you can keep coming back to useful
> queries. If the queries can be named, then you can build up a query library.
> Not hard to make and super useful. Unless there is already an extension for
> this or plans for such, I'm happy to (have my staff) give this a go!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
