On 13 May 2011, at 17:04, Reto Bachmann-Gmür wrote:
> ----- Original message -----
> >
> > On 13 May 2011, at 16:07, Reto Bachmann-Gmür wrote:
> >
> > > Well I did suggest an alternative in
> > > >
> > > >
>
> > > >
> > > > and in fact that is what the WebProxy implements - I think.
> > > >
> > > > And that is in short that remote graphs use the name of the remote
> > > > resource from which they come, and local graphs have local names.
> > >
> > > I argues why i strongly believe the local cache version must have a
> > > distint name than the remote graph. I agree the the original .cache
> > > suffix was not at all ideal, but i disagree with your change of just
> > > naming it by the uri of the remote graph.
> >
> > Sorry I must have missed that argument. Where do you argue that a local
> > cache version must have a distinct name?
>
> Clerrezza-489 and you also quote may statement of 463. okay, you might say
> that I'm stating rather than arguing.
>
:-)
> The argument: they are different thing, both intensionally (cache and source)
> as in many case extensionally (triples may differ).
>
in that sense I agree.
But then the other point I made is also true, and that is that different users
may get different
graphs back for the same remote resource. In fact those users may be the same
user at different times. Since those are all different graphs by your
definition above one should also give them different names.
So local graph naming schemes should take that into account, which is why I
suggest that we have an API that can allow for extensibility here.
in Clerezza-489 I wrote that one could describe each graph like this in a
special Cache graph perhaps.
:g202323 a :Graph;
= { ... };
:fetchedFrom <https://remote.com/>;
:fetchedBy <http://bblfish.net/people/henry/card#me>;
:representation <file:/tmp/repr/202323>;
:httpMeta [ etag "sdfsdfsddfs";
validTo "2012...."^^xsd:dateTime;
... redirected info?
] .
:g202324 a :Graph;
= { ... };
:fetchedFrom <https://remote.com/>;
:fetchedBy <http://farewellutopia.com/reto#me>;
:representation <file:/tmp/repr/202324>;
:httpMeta [ etag "ddfsdfsddfd";
validTo "2012...."^^xsd:dateTime;
... redirected info?
] .
Then this API could use information from this graph to and information from the
user's request
to find the correct local graph he wants.
Henry
PS. Having said that one then may just wonder why local graphs should ever have
anything other than
local URLs, since every time someone made a copy of a local graph it would be
different.
> Reto
> >
> > Henry
> >
> >
> >
> > Social Web Architect
> > http://bblfish.net/
> >
>
>
Social Web Architect
http://bblfish.net/
