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.

Sign up for GitHub

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

Jump to bottom

Bugfixes, improvements, better support for Virtuoso and Blazegraph #6

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Bugfixes, improvements, better support for Virtuoso and Blazegraph #6

wants to merge 1 commit into from

Conversation

irygaev
Copy link

@irygaev irygaev commented Apr 1, 2016

  • Fixed encoding problem - now safe to use with russian and other Unicode characters in the query text
  • Fixed issue with ASK queries with Virtuoso (they always returned TRUE).
  • Added "Send As" dropdown to choose between "query" and "update" parameters. According to SPARQL1.1 specification update queries MUST be send using "update" parameter (not "query" parameter) and Blazegraph does not support update queries in the query parameter (though Virtuoso do support that).
  • Added support for non-standard responses (i.e not xml). SPARQL1.1 specification does not regulate response format for update queries. While Virtuoso uses standard SPARQL-XML responses, Blazegraph provides plain html message. In case response is not parsable it is displayed as a whole as plain html.
  • Prefixes are displayed one in a row and by default are hidden. Can be shown using [Show Prefixes] button.
  • Added support for in-query prefixes - duplicated prefixes are automatically removed, in-query prefixes are applied to result grid the same way as default prefixes.
  • "Results as XML" did not really work for Virtuoso - added parameter "format=xml"

@irygaev
A number of bugfixes, improvements and better support for Virtuoso an…
66da709 
…d Blazegraph triplestores

* Fixed encoding problem - now safe to use with russian and other Unicode characters in the query text
* Fixed issue with ASK queries with Virtuoso (they always returned TRUE).
* Added "Send As" dropdown to choose between "query" and "update" parameters. According to SPARQL1.1 specification update queries MUST be send using "update" parameter (not "query" parameter) and Blazegraph does not support update queries in the query parameter (though Virtuoso do support that).
* Added support for non-standard responses (i.e not xml). SPARQL1.1 specification does not regulate response format for update queries. While Virtuoso uses standard SPARQL-XML responses, Blazegraph provides plain html message. In case response is not parsable it is displayed as a whole as plain html.
* Prefixes are displayed one in a row and by default are hidden. Can be shown using [Show Prefixes] button.
* Added support for in-query prefixes -
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@irygaev