[jira] [Reopened] (CLEREZZA-525) Create caching storageprovider retrieven triple-collections from the web

["Henry Story (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLEREZZA-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henry Story reopened CLEREZZA-525:
----------------------------------


According to recent e-mail discussion, a Proxy Storage that does not know what the name of the machine it is running on is, is problematic.

http://mail-archives.apache.org/mod_mbox/incubator-clerezza-dev/201105.mbox/browser

[[

On 15 May 2011, Reto Bachmann-Gmuer wrote:
> We don't know the names of the current machine, remember that we are
> operating on the rdf access layer (SCB) here. Unlike the WebId service
> this is not on the platform service.

Well perhaps it is at the wrong layer then. Perhaps a WebProxy, being at the web layer needs
to know the name of the service it is running as. Please read through the following  reasoning
carefully before replying.

Consider that the API you are developing has the following method

     def getGraph(name: UriRef)

If the WebProxy services is called like this:

wp.getGraph("https://bblfish.net/user/admin/".uri)

Then it certainly would be very useful for the proxy service to know that bblfish.net is the
local machine, and that it does not need to do an httpS GET to discover the graph. 

A use case can help illustrate this. Imagine a zz service looks at a foaf file that contains
a reference to <https://bblfish.net/user/admin/#me> It sends the request to the cache
proxy to fetch the file so that it can find out more about that resource. What is it? A fish,
a mineral, a human, or an ontology?  So it goes to the web proxy and calls it above. If your
proxy looks in its
  
    urn:x-localinstance:/cache/

namespace it won't find a reference to our URL above. So it will do a GET on the web, find
it,
and place it in 

    urn:x-localinstance:/cache/https://bblfish.net/user/admin/


Now imagine I then update my bblfish.net profile. The next time my zz instance will go and
look in the proxy it will find the above urn and look up the information there. Not only will
we now have the information twice in the database, we will end up getting out of date information
for our own data!
]]

> Create caching storageprovider retrieven triple-collections from the web
> ------------------------------------------------------------------------
>
>                 Key: CLEREZZA-525
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-525
>             Project: Clerezza
>          Issue Type: Improvement
>            Reporter: Reto Bachmann-Gmür
>            Assignee: Reto Bachmann-Gmür
>
> The current api has many undocumented public methods and it seems to make an unsharp distinction between the caching (and respective access) of graphs and of graphnodes.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira