Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use prefixes from the query in construct (turtle) results #226

Open
jneubert opened this issue Dec 29, 2013 · 2 comments
Open

Use prefixes from the query in construct (turtle) results #226

jneubert opened this issue Dec 29, 2013 · 2 comments

Comments

@jneubert
Copy link

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.

@LaurensRietveld
Copy link
Collaborator

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)

@jneubert
Copy link
Author

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 :).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants