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 Sat, 21 May 2011 17:08:47 GMT


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

Could you post your -1 on the list with the mandatory indication of the reason.

To your prvious comment:
> GraphNodeProvider as described in CLEREZZA-540 does not work. 
could we discuss that there
> So this does not solve that issue. 
It does solve what it describes
> Furthermore there is no way to tell in advance what a URI refers to: a graph or an object.
an object is a resource in rdf terms and a graph is a resource, but TcManager is not about
dereferencing anything but about getting TripleCollection, a graph with a hash does not identify
a TripleCollection that's why this issue says that it should say that there is no such entity
> So since one cannot tell in advance there is no reason to make a distinction for hash
uris. foaf:knows is an object and a robot may now know what it is. 
See the HttpRange-14, to some degree we may discover things about the nature of resource automatically.
> So since WebProxy is meant for automatic dereferencing of resources, one might as well
make it general enough to work on all the resources. 
No its not ment for that, its about getting graphs by name.

> 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