xsd:string is the datatype by default and becomes implicit in SPARQL results srx srj #75
Conversation
This file contains 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
… all jmeter's files w3c#51
…ions in the manifest w3c#51
…edMustToHave In manifest, replace /sparql/ by /sparql and insert new status dawgt:ApprovedMustToHave for 3 tests. fix 3 tests jmx w3c#51
…g/TR/sparql11-results-json/) Replace the type "typed-literal" with "literal"
|
Closed in favor of #76. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
xsd:string seems to become the datatype by default and so, it becomes implicit in sparql results.
Here, I propose to modify the SPARQL results of tests in order to be in coformity with the SPARQL results generate today by the classic SPARQL services.