Feature Request: Variables in validation reports of SPARQLConstraintComponent

[rdflib]

Feature Request: Variables in validation reports of SPARQLConstraintComponent

[baum314nk]

I fixed this problem locally by modifying or adding the methods _evaluate_sparql_constraint & _validate_sparql_query of sparql_based_constraints.py and make_v_result_description, make_v_result_description & _format_sparql_based_result_message of constraint_component.py.

As I change the types of some parameters and return values, I'm not really sure that this workaround won't break some other things, but atm it works fine for me.
pySHACL_constrains_quickfix.zip

[ashleysommer]

Hi @baum314nk
Thanks for opening this issue.
I had intended to implement this optional feature but never got around to it. There was always more important features to get working.

I will look at your patch to see if there is a way of easily integrating it into the rest of the codebase.
Thanks.

[piyush69]

Hi, I would like to work on this issue. I'll work backward from the patch and try to make it work with the existing design structure.

[ashleysommer]

@piyush69
That would be great, if you could make as few changes as possible to the existing code to reproduce the feature. Thanks for your help.

[piyush69]

@ashleysommer, I've put in a PR (#50) for the same.
It makes the following changes:

• add an optional function parameter bound_vars to some methods. It is None by default
• add a function _format_sparql_based_result_message() in sparql_based_constraints.py to replace query variables with their corresponding values in the message

[ashleysommer]

@piyush69
Thank you for your work on this.
I believe there is still one thing missing. I see it does inject the bound vars to the message in the descriptive output, but I think it also needs to inject the bound vars into the sh:message property (if it exists) in the validation report graph too.

[ashleysommer]

Forgot to close this. Closed by #50.