incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Bachmann-Gmür (JIRA) <>
Subject [jira] [Commented] (CLEREZZA-533) TcProvider does not (should not?) dereference URIs with hash
Date Sun, 22 May 2011 01:13:47 GMT


Reto Bachmann-Gmür commented on CLEREZZA-533:

Ok, Reverted my change as asked for by Henry.

I find it very confusing that the issue has been renamed, this issue is not about TcProvider
in general but about storage.web.

I'm still convinced that the issue is legitimate and my proposed patch appropriate.


1. TcProvider#getGraph returns a graph given the name of a graph and thorws a NoSuchEntityExcpetion
if there is no such graph, i.e. a Provider should return a triple collection if such a graph
exists or can reasonable be assumed to exits and throw an exception otherwise
2. If on the web I get an RDF representation doing a GET request against
I have a reason to assume that <> is the name of the graph obtained
by interpreting the returned representation.
3. The web gives no reason to assume that the infinity of URIs starting with,
denote a graph

4. storage.web should return a graph for the name <>
5. storage web should throw a NoSuchEntityException for the uris starting with

I assume you disagree with premise 1, but that's the current definition of the API, and blocking
bug-fixes that are to guarantee that the implementation matches the API is not an acceptable
way to propose changes to the API.

> TcProvider does not (should not?) dereference URIs with hash
> ------------------------------------------------------------
>                 Key: CLEREZZA-533
>                 URL:
>             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:

View raw message