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-540) GraphNode provider service
Date Thu, 26 May 2011 12:11:47 GMT


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

Which point against the issue hasn't been answered, I see olny the one about the many if-then
statement which I didn't understand ans thus asked twice for you to specify the problem.

To your new questions:
- "So my issue is how does this service know what is authortitative about some resource?"
The javadoc of the service specifies this quite clearly. The content graph is considered authoritative
for all resources, the public user graphs for resources on a local-instance with a path-section
starting with /user/{username}, for remote resources additionally the triples you get by dereferencing
that resource. (but isn't this exactly what I already said on 23/May/11 07:12 ? )

- "I gave a URI about someone on the Web and I get a 10 times more information back than he
has in his foaf file. Is Clerezza so powerful that it can deduce new relations without looking
at the world?"
yes, the content graphs contains facts taken for granted when it comes to describe the world.
If in other circumstances the difinition of authoritative above is not satisfactory, wehy
not open a new issue?

- "What are the principles that will guide the evolution of this component?"
It provide a useful functionality as it is now. As for any component the evolution will be
driven by the need for functionality and the striving for an elegant api.

What do you think has to be done for this issue to be closable? Please indicate why you think
the point you mention cannot be addressed by new issues.

> 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