[
https://issues.apache.org/jira/browse/CLEREZZA-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037493#comment-13037493
]
Henry Story commented on CLEREZZA-533:
--------------------------------------
"I find it very confusing that the issue has been renamed, this issue is not
about TcProvider in general but about storage.web. "
I find it confusing that you say that it is about StorageWeb, when the code
that is changed is WebProxy which is a WeightedTcProvider.
If TcProviders were purely about getting graphs, nothing more, then what you
say would make sense. They would be like Sesame then. But by placing the
WebProxy into the TcProvider class hierarchy, things take on a different turn,
since now a layer of web knowledge has been added. Asking for a URI in a proxy
is to ask for a procedure to be followed whereby you then get the graph related
to the URI. In that scenario a whole new layer of naming semantics has been
added. Once you admit that this process should be started, then there is no
reason now to have the system take care of hash URIs in the same way you will
have to take care of uris such as http://xmlns.com/foaf/0.1/knows
But I mentioned those argumetns a few times above. So the problem is what
should one do, which is why I changed the thread name to a question. Your patch
is ok as short term thing, to help people realise that this issue is not fixed,
and needs solving. You could put an error message pointing to this bug, to get
people to come here and vote or propose solutions for when they rewrite for the
nth time a hash removal code.
> TcProvider does not (should not?) dereference URIs with hash
> ------------------------------------------------------------
>
> Key: CLEREZZA-533
> URL: https://issues.apache.org/jira/browse/CLEREZZA-533
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Reto Bachmann-Gmür
> Priority: Critical
>
> URIs with hash do not name the graph but a resource within that graph so we
> should not just return the graph (which has the uri subsection before the
> hash sign as name)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira