[
https://issues.apache.org/jira/browse/CLEREZZA-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037424#comment-13037424
]
Henry Story commented on CLEREZZA-533:
--------------------------------------
So of course then the issue is that there is the danger of naming graphs
locally that have a hash, which should certainly be avoided, as I myself
reported in CLEREZZA-538 .
But here it is easier, because all locally named graphs can be controlled.
Before creating a graph remove the hash. For remote graphs the same can be
done, but it could be improved by using the status codes to work out what the
real name of the graph is. So it is only in such a way that one can work out
what the name of the foaf:knows graph is.
It would be worth working out in details what the answer to that should be in
due course in fact. And so this brings us back to the thread on graph naming.
> 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
