[
https://issues.apache.org/jira/browse/CLEREZZA-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henry Story reopened CLEREZZA-533:
----------------------------------
This seems to have been solved with this code:
if (name.getUnicodeString.indexOf('#') != -1) {
logger.debug("not dereferencing URI with hash sign")
throw new NoSuchEntityException(name)
}
Why not just remove the hash, instead at that point? After all, what happens if
the URI refers to an object like the eiffel tower or a relation such as
foaf:knows is dereferenced - which could very well happen in automated
dereferencing schemes. Then dererferencing that URL will return a "303 See
Other" and that resource will be the proper name of the graph.
My feeling is that instead of trying to get the requesting code to work out
what type of resource is being requested, it would be a lot better for the
Graph returned to have a field containing it's final name.
> atorage.web: dont derference 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
>
> 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
