You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As previously mentioned, very often the triplestore behind a SPARQL-Endpoint can technically support all queries, but quite often they fail due to necessary query timeouts, large datasets and the like.
To analyse & tune this, it would be very handy if the queries could be copied and issued manually to the endpoints. Currently the query is only shown on mouse over, which makes it even hard to typewrite them. The best solution would be a 'Copy query to clipboard'-Button, or a link to a text file continaining the queries.
The text was updated successfully, but these errors were encountered:
It would be MUCH better if they were behind disclosure buttons and/or had some other means by which they could be copied and pasted -- as you show failures for every such query on URIBurner, and for many on DBpedia, and likely for many other Virtuoso-serviced endpoints, where most if not all such queries should succeed, and I would like to figure out why the failures are reported and offer adjustments to address them -- whether those adjustments would be applicable on server- or client-side.
Four years seems a very long time to work on adding such a simple link to the report page template!
As previously mentioned, very often the triplestore behind a SPARQL-Endpoint can technically support all queries, but quite often they fail due to necessary query timeouts, large datasets and the like.
To analyse & tune this, it would be very handy if the queries could be copied and issued manually to the endpoints. Currently the query is only shown on mouse over, which makes it even hard to typewrite them. The best solution would be a 'Copy query to clipboard'-Button, or a link to a text file continaining the queries.
The text was updated successfully, but these errors were encountered: