You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Oliver Strässer (JIRA)" <ji...@apache.org> on 2010/04/29 09:15:54 UTC
[jira] Created: (CLEREZZA-199) User BNodes - why not with UriRef ?
User BNodes - why not with UriRef ?
------------------------------------
Key: CLEREZZA-199
URL: https://issues.apache.org/jira/browse/CLEREZZA-199
Project: Clerezza
Issue Type: Improvement
Reporter: Oliver Strässer
Priority: Minor
It will be easier for the developer, if the user nodes are not BNodes .
The clear node reference with an UriRef helps, if I want to connect GraphNodes in a seperate graph, with an user.
example:
Nodes with the type ClipFeed are stored in a graph called "http://tpf.localhost/clips.graph". Now I want to save the creator of the feed - so that I can show the personal feeds of the current logged in user.
To reach that, its necessary to save the triple " clipfeed - dcterms.creator - user resource" in the content graph (all other properties of the clipfeed are stored in the graph http://tpf.localhost/clips.graph)
if I wouldn't do that, the reference between the clipfeed and the BNode of the user is lost after a sytem restart (because the user is a BNode).
If the user node has an UriRef, I can save the Triple about the user in my own graph.
If you need more examples - ask me - I have more...
So the question is: Why you don't save the user node with an UriRef example: http://tpf.localhost/user/df6f91c5-71e2-4b80-804f-2d09abda642a - it's a small change with a big benefit
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (CLEREZZA-199) User BNodes - why not with UriRef ?
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Reto Bachmann-Gmür closed CLEREZZA-199.
---------------------------------------
Assignee: Reto Bachmann-Gmür
Resolution: Fixed
"Roaming" users logging in with foaf+ssl do have a uri. For that I made sure that everything works regardless whether the user is represented by a bnode or a named node.
For the application you describe you can create user with a uri-ref. Howver I think its good to also support bnode users, as cross-site or cross-graph referencing is not always needed. I'm currently working on a profile editor (CLEREZZA-243, as extension to the account control panel) which will allow the user to switch from bnode top named node (creating a new or using an existing web-id).
> User BNodes - why not with UriRef ?
> ------------------------------------
>
> Key: CLEREZZA-199
> URL: https://issues.apache.org/jira/browse/CLEREZZA-199
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Oliver Strässer
> Assignee: Reto Bachmann-Gmür
> Priority: Minor
>
> It will be easier for the developer, if the user nodes are not BNodes .
> The clear node reference with an UriRef helps, if I want to connect GraphNodes in a seperate graph, with an user.
> example:
> Nodes with the type ClipFeed are stored in a graph called "http://tpf.localhost/clips.graph". Now I want to save the creator of the feed - so that I can show the personal feeds of the current logged in user.
> To reach that, its necessary to save the triple " clipfeed - dcterms.creator - user resource" in the content graph (all other properties of the clipfeed are stored in the graph http://tpf.localhost/clips.graph)
> if I wouldn't do that, the reference between the clipfeed and the BNode of the user is lost after a sytem restart (because the user is a BNode).
> If the user node has an UriRef, I can save the Triple about the user in my own graph.
> If you need more examples - ask me - I have more...
> So the question is: Why you don't save the user node with an UriRef example: http://tpf.localhost/user/df6f91c5-71e2-4b80-804f-2d09abda642a - it's a small change with a big benefit
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.