incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tommaso Teofili (Updated) (JIRA)" <>
Subject [jira] [Updated] (CLEREZZA-470) improve names of remote graphs and local editions of them
Date Tue, 08 Nov 2011 14:24:00 GMT


Tommaso Teofili updated CLEREZZA-470:

    Fix Version/s: 0.2-incubating
> improve names of remote graphs and local editions of them
> ---------------------------------------------------------
>                 Key: CLEREZZA-470
>                 URL:
>             Project: Clerezza
>          Issue Type: Bug
>            Reporter: Henry Story
>            Assignee: Henry Story
>             Fix For: 0.2-incubating
> Currently the WebProxy component has an illogical naming framework for graphs. 
> given a remote graph <http://joe.example/profile> the name of it in the DB is <http://joe.example/profile.cache>
> Any local additions or changes to the graph are placed in <http://joe.example/profile>
> That is messy because:
>   - if someone names a resource> it will be difficult
to tell by inspection of rdf db if that is now meant to be the local or the remote version
>  - a locally edited remote graph, can be locally edited differently by different local
users. Jane may want to correct Joe's birthdate. Jack may want to correct his housing address.

> In the longer term we may want an ontology so that we don't need to care about the names
of the graphs. But until then, we may as well do this the intuitively correct way.
> So my suggestion is that remote graphs be named by their URL, and hence local graphs
also be named that way.
> And if edits on remote graphs should be done - though the concept is still unclear -
a new graph along the lines
> .../people/jane/edited?uri=
> if that somehow creates too long a URI then I suggest we create a tinyurl service (which
will be useful anyway) and have
> .../people/jane/edited?tiny=ADsf34

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message