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
It would be great if, in the results of construct queries in turtle format, full URIs would be replaced by prefixed ones, with the prefixes already defined in the query:
Much more compact, and much more readable.
Especially with temporary fancy URIs, such as in this example.
The text was updated successfully, but these errors were encountered:
I'm a bit hesitant implementing this, but maybe you can convince me. Reasons:
We currently show the response from the endpoint as-is. Making changes to this response, would make a tasks like debugging less reliable (as we are changing the response before showing it to the user).
This is something the endpoint itself should take care of
An option would be to make this feature optional. For example, a button in the right top of the result section, converting the results to a prefixed version. (or, perhaps better, automatic conversion, and a button which can toggle to the -original- response)
I like the idea of having a button for getting to the original query result: The default would be most convenient for users and still leave the chance for debugging the original result.
As I just verified in my stwv endpoint, prefixes are returned by Fuseki when they are part of the construct template, but not when ?predicate is a variable. I found no way to tune this in the endpoint itself - which would open an opportunity for yasgui to add even more value :).
It would be great if, in the results of construct queries in turtle format, full URIs would be replaced by prefixed ones, with the prefixes already defined in the query:
Much more compact, and much more readable.
Especially with temporary fancy URIs, such as in this example.
The text was updated successfully, but these errors were encountered: