incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henry Story (JIRA)" <>
Subject [jira] [Commented] (CLEREZZA-540) GraphNode provider service
Date Mon, 30 May 2011 13:16:47 GMT


Henry Story commented on CLEREZZA-540:

If this package were just standing there used only by your applications then this would not
be a problem, and the javadoc information would be ok.
But looking at the dependent issues such as CLEREZZA-544, the GraphNodeProvider will be  used
directly by the CallbackRenderer, the login module, and other places it seems. So this is
not just a package that is for a specific use case. It is meant to be used in the core modules.
It is then also very misleadingly named, because it is not just a GraphNodeProvider, but at
least a AuthoritativeGraphNodeProvider, and then according to some notion of authority that
is not transparent at all.

Now who controlls the content-graph? How big can that become?  But that is not the only graph
that gets shipped along: The following get sent too (with the number of triples in an new
instance of ZZ):

 - <urn:x-localinstance:/documentation.graph>   1002 triples
 - <urn:x-localinstance:/config.graph>           176 triples
 - <urn:x-localinstance:/web-resources.graph>    621 triples
 - <urn:x-localinstance:/enrichment.graph>         0 triples
You can test this with the following code:

zz> import org.apache.clerezza.platform.graphnodeprovider._
zz> val gnp = $[GraphNodeProvider]
zz> val tbl = gnp.get(new UriRef(""))
zz> tbl.getGraph.size
res0: Int = 1878

If I get Tim Berners Lee's Graph on the command line I find

$ rapper | wc
rapper: Parsing URI with parser rdfxml
rapper: Serializing with serializer ntriples
rapper: Parsing returned 78 triples
     78     380    9978

So we get 1700 triples back more, containing documentation, and other stuff. What if one documentation
package uses Tim Berners Less URL as an example, and adds rdf tying him to some imaginary
feature? Can one now hack the system by adding documentation?


The issue is to understand what problem this component is trying to solve. It seems that if
we look there we may well find that something a lot simpler could be workable here.
The idea of a graph node provider seems a good one, but perhaps if the user could ask for
a number of graphs and get their union then the user could specify what he things to be trustworthy.

> GraphNode provider service
> --------------------------
>                 Key: CLEREZZA-540
>                 URL:
>             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:

View raw message