Add the possibility to add warnings to the parsing of a SPARQL query. Such a warning could be ignored by default, but aim to be used as part of a potential SPARQL query editor.
A use case for warning instead of a straight-up exception arose during #455. The SPARQL 1.1 standard defines that certain filters and operands must accept only specific datatypes. However, the Effective Boolean Value defines that any literal that is not "true" can be considered as the boolean literal "false".
This permissivity of the SPARQL evaluation defeats the point of a validation system if we cannot at least warn the user of the usage, as an example, on a function returning numerics as a filter.
Add the possibility to add warnings to the parsing of a SPARQL query. Such a warning could be ignored by default, but aim to be used as part of a potential SPARQL query editor.
A use case for warning instead of a straight-up exception arose during #455. The SPARQL 1.1 standard defines that certain filters and operands must accept only specific datatypes. However, the Effective Boolean Value defines that any literal that is not "
true" can be considered as the boolean literal "false".This permissivity of the SPARQL evaluation defeats the point of a validation system if we cannot at least warn the user of the usage, as an example, on a function returning numerics as a filter.