-
Notifications
You must be signed in to change notification settings - Fork 35
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
Selecting a literal from a list does not format the sparql query correctly #539
Comments
This may come from your data: can you make an export of your data ? maybe the datatype was inserted as a language in your data. |
This is not precise enough wrt to the language and datatypes of literals. Can you please provide a ttl or RDF/XML file ? |
I run into the same issue with the following .ttl
It seems like having an AutocompleteProperty with rdfs:range a Literal uses the : But when I click on a result, for example, Livaitom, I get the following sparql query :
As you can see "Livaitom" is transformed into I expect literal to be transform the following way : In most similar example, you are not using autocompleteProperty but SearchProperty, and it works but it doesn't achieve the same need, for example, if I use SearchProperty and click on a result, for example, Livaitom, I get the following sparql query :
Both widgets have different purposes so I expect them to work differently, but I think this highlight where may the issue comes from to help your debugging the issue (if that is one) I would also add that we should add the xsd prefix in the sparql query if it not already in yet |
This is fixed. Let me know if it works for you if you can test on the latest master branch. Otherwise you need to wait for the next release. Thanks |
I use the following sparnatural configuration:
When it came to making my choice with sparnatural :
![Screenshot from 2023-12-01 14-20-22](https://private-user-images.githubusercontent.com/131978217/292164977-b73b9d02-54a6-4c09-bc54-6050689f4004.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjIzNzczNjAsIm5iZiI6MTcyMjM3NzA2MCwicGF0aCI6Ii8xMzE5NzgyMTcvMjkyMTY0OTc3LWI3M2I5ZDAyLTU0YTYtNGMwOS1iYzU0LTYwNTA2ODlmNDAwNC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzMwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDczMFQyMjA0MjBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1hMmEwN2M1N2E2MzQwM2JlYTBmNzYwYzI2MDZiODBjNDQxNWViZjFmYTFhNTQ4YzZjMWM5YzU1MzcwMjNlNzI0JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.0RLe0f_Btwh_COtbRelHyrBXT0C9jmqftHnOWkNWNh8)
The SPARQL query is formatted as follows:
This way, the query cannot be executed due to the incorrect formatting of the XSD:string uri (@http://www.w3.org/2001/xmlschema#string). Instead, the query should be :
The text was updated successfully, but these errors were encountered: