IRI Rewriting in SPARQL Result Set Can Lead to Confusing Results

[ktk]

When an IRI matches the pattern specified by -dataset-base-url, it undergoes a rewrite in the SPARQL result set. This is observed:

• In the Yasgui display.
• In plain (raw) result sets.

I've confirmed this behavior for SELECT statements, though I haven't tested it with CONSTRUCT statements.

Problem:
Such rewriting can:

• Produce confusing results for end-users.
• Potentially disrupt applications or services that consume the response.

Original Intent:
The primary reason for implementing this rewrite feature was to facilitate easier "follow your nose" browsing, especially in a test environment.

Suggestion:
Considering its initial intent, it might be best if this rewrite function was limited to dereferencing actions only. It shouldn't apply to result sets or triples returned from the SPARQL endpoint.

[l00mi]

As mentioned per PM, I think #119 is the better, more sustainable solution. It would allow to dereference on PROD, but using the other environments.

[ludovicm67]

I was thinking of having a parameter on the sparql-proxy, to allow rewriting.

That way by default it does not rewrite anything, but if you add ?rewrite=true to the endpoint, you will get the rewritten responses, as it is also sometime useful while playing with data, and being able to directly dereference results.

The renderer for the pages will query the endpoint by providing that parameter, so that it works directly for dereferencing, like before.

This would be the easiest way to tackle this.

[ludovicm67]

Done using the rewrite=true query parameter in the endpoint created by the sparql-proxy plugin.