[
https://issues.apache.org/jira/browse/CLEREZZA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henry Story reopened CLEREZZA-540:
----------------------------------
This does not solve a problem I had. It currently has a mysteriously bad smell
to it this provider, as it seems to be completely adhock.
If I get the URL <http://heddley.com/edd/foaf.rdf#edd> it returns me with a
graph with over 1000 triples, the whole content of the database it seems - and
an empty database btw, freshly installed.
The same URL dereferenced from the web just contains 157 triples. If I want to
show someone what the content of the remote graph is, I don't want them to see
the content of every other graph. Now someone may find this userful. But this
does not seem to be what it set itself out to be. I quote "implement a platform
service that returns GraphNodes for URIs. The GraphNode is the resource
identified by that uri with as BaseGraph sources considered authoritative for
that resource. ". So this is either a bug in the implementation or a bug in the
description of this issue. In either case I don't think it can be closed.
As far as the smell goes: the point of replacing the WebIdCache was to push
that into the TcProvider. It was quite simple to understand. Here there are a
huge number of local TcProvider wrappers that are used, where TcProvider itself
iteratres through a stack of providers. So here we seem to have a completely ad
hock solution to what was the WebCache.
> GraphNode provider service
> --------------------------
>
> Key: CLEREZZA-540
> URL: https://issues.apache.org/jira/browse/CLEREZZA-540
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Reto Bachmann-Gmür
> Labels: platform, rdf
>
> Implement a platform service that returns GraphNodes for URIs. The GraphNode
> is the resource identified by that uri with as BaseGraph sources considered
> authoritative for that resource.
> Note: it ois left to possible subsequent issues to connect this to the
> ability manually refresh caches pertinent to a resource on demand.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
