Bugfixes, improvements, better support for Virtuoso and Blazegraph #6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
irygaev
commented
Apr 1, 2016
irygaev
commented
- 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"
…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
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.