[
https://issues.apache.org/jira/browse/CLEREZZA-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henry Story reopened CLEREZZA-544:
----------------------------------
This issue cannot be closed while CLEREZZA-540 is open, as it depends on that.
This could be rewritten to not depend on CLEREZZA-540, which has certain
assumptions about what are authortitive graphs that can be questioned. To build
such assumptions into the core of Clerezza, is to bo beyond what an open stack
should provide.
Some suggestions that could get the same effect:
Allow multiple UriRefs to be requested, and a service to create the union
graph of them, and return that. That would allow each application to decide for
itself what is authoritative.
> Allow call to render (or analogous method) so that the passed resource gats
> rendered in the context provided GraphNodeProvider
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLEREZZA-544
> URL: https://issues.apache.org/jira/browse/CLEREZZA-544
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Reto Bachmann-Gmür
>
> Currently when calling render the resource is rendered with the same base
> graph as the calling renderlet. We could add a render-method that takes a
> uri-ref and renders this resource in the context returned by
> GraphNodeProvider, or think of a new method name (for it to take GraphNode
> like render so it can fall back to render if the node is a bnode).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
