[
https://issues.apache.org/jira/browse/CLEREZZA-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003403#comment-13003403
]
Reto Bachmann-Gmür commented on CLEREZZA-447:
---------------------------------------------
I think some form of bracketing and quoting in RDF would be heat you're looking
for. Your solution seems not to distinguish between graph and graphnode but is
very close to current best practice: The graph you write would be a
SimpleMGraph created on a get request, this graph is merged with all trusted
graph (where what is trusted depends on the requested resource) and a graphNode
for
<http://localhost:8080/user/admin/people?uri=http://bblfish.net/people/henry/card>
and this union of graphs is returned. Without support for quoting things get
complicated if you want to display untrusted data from different sources,
making it clear to the user what comes from where. Implementing the described
method to get read-only versions of arbitrary named graphs might be an approach.
> GraphNode not appropriate object to send from JSR311 code to Renderlet
> ----------------------------------------------------------------------
>
> Key: CLEREZZA-447
> URL: https://issues.apache.org/jira/browse/CLEREZZA-447
> Project: Clerezza
> Issue Type: Bug
> Reporter: Henry Story
>
> The main reason for Clerezza (zz) having an RDF engine is so that one can
> fetch data off the web and use it to guide the logic of what is going on.
> When that is done one has to carefully distinguish what is said or believed
> by different parts of the engine. *Who* believes *what*, is very important,
> and not making that distinction will create security holes.
> So for example the following is problematic. When a @GET annotated method
> returns a GraphNode in a JSR311 class one has to add information to
> that returned GraphNode that is going to decide which Renderlet gets called
> next. Something like
> resultNode.addProperty(RDF.`type`, PLATFORM.HeadedPage)
> resultNode.addProperty(RDF.`type`,
> CONTROLPANEL.ProfileViewerPage)
> But what if the JSR wants to return a graph that is not controlled by the
> System? What if it wants to return a graph found on the internet in order to
> display it.
> It would have to write something like this:
> @GET
> def viewPerson(@Context uriInfo: UriInfo, @QueryParam("uri") uri:
> UriRef): GraphNode = {
> val foaf: GraphNode =
> descriptionProvider.getWebDescription(uri, Cache.Fetch)
> val resultNode: GraphNode = new GraphNode(new
> UriRef(uriInfo.getAbsolutePath.toString),foaf.getGraph)
> resultNode.addProperty(RDF.`type`, PLATFORM.HeadedPage)
> resultNode.addProperty(RDF.`type`,
> CONTROLPANEL.ProfileViewerPage)
> return result
> }
> But now it has mixed system information with remote information. This means
> that if the foaf profile contained some different type information, perhaps
> set
> by a different instance of Clerezza, the ZZ instance will be randomly
> selecting one of many Renderlets, some of which were not chosen locally. This
> will completely
> confuse the display logic in the system.
> Such a JSR 311 method must instead return a more complex object, consisting
> of a system graph perhaps and a content graph. The System graph is the only
> one that should be
> considered for routing information.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
