[
https://issues.apache.org/jira/browse/CLEREZZA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037426#comment-13037426
]
Henry Story commented on CLEREZZA-540:
--------------------------------------
You wrote at the top for this issue:
"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. "
I then spent one hour compiling things again, getting things to work, changing
code, debugging, all happily looking forward to using this feature, only then
to find that it does not do what you said it would above. It says "BaseGraph
sources considered AUTHORITATIVE for that resource." Considered authoritative
by whome? Ok, for some local resources I understand that mergers could be done
but only in particular circumstances, otherwise it is going to get to be very
difficult to understand what is going on. If you want graphs that are mergers
of other graphs then there is work that has been done in that space such as the
Work on Networked Graphs
http://blogs.oracle.com/bblfish/entry/opening_sesame_with_networked_graphs
But I don't consider node contexts to be the right solution at all. They are
useful for sure, and I have used them recently happily. But that is not where
one gets authoritative graphs from. Authoritative comes from Author, ie creator
of, and that can only be aplied to a graph or sets of graphs.
Anyway I descrive above a URI I fetched, and you give me 10 times more
resources back. I don't want those! They are not authoritative.
> 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
