On 11/06/14 12:20, Rob Vesse wrote:
Hi All
On behalf on my employer I reported an interesting quirk of ARQ that may be
a bug/feature depending on your point of view. You can read the full
details and developer discussion at JENA-712
(https://issues.apache.org/jira/browse/JENA-712)
I understand the technical issue but I don't understand when it might
arise in practice.
A compete different line is to validate the query and not allow relative
URIs (not Jena's job to enforce), i.e. set a IRIResolver that checks for
relative URIs while parsing.
(I am minded to prefer always printing the BASE URI, which is don't pay
much attention to the explicitly/implicitly set base boolean - I doubt
anyone relies on print a query and getting relative URIs. The equality
comparator needs attention for this to work.)
I am not vastly in favour of options due to a long term risk with a
proliferation of options that never get used. I don't think it really
helps, just hides a decision base don the default setting.
Updates may be different and need more care as relative URIs can make
more sense there but updates do have an issue that when there is a base
URI is, if strictly from the RFC, it's not unhelpful.
Andy
