[foaf-protocols] Lots of confusions ...

[Kingsley Idehen]

Story Henry wrote:
> On 18 May 2010, at 15:29, Melvin Carvalho wrote:
>
>   
>>>> You don't know what's happening here, do you Mr Jones.
>>>>         
>>> There are a few bugs on the foaf.me mailing list.
>>>
>>>       
>> Apologies for this.  There was an attempt made to refactor the library, but
>> it seems some bugs were introduced, that have not yet been patched.  I didnt
>> actually program this piece, but will attempt to work out what's going
>> wrong, or see if I can roll back to the previous version of the library,
>> which was definitely stable.
>>     
>
> This could be related to the bug I found last year that allowed one with 
> Tabulator to edit other people's foaf graphs.
>   

How can you edit someone else's FOAF graphs if FOAF+SSL based ACLs are 
functional?
> I think it is very important to very clearly separate assertions into graphs, and be very clear about who owns them. A weakness in the security here, can lead to mergings of different people's statements, which would lead to the results shown.
>
>   

Please clarify.

I have always held the opinion that a Data Space owner should be able to 
offer CRUD rights to agents via the WebIDs. What I am hearing in this 
thread is a little confusing.


> This is also a reason why I think to start one should avoid SPARQL Updates, and use much simpler tools. Form based entries are much better understood, and less likely to go wrong too. 
>   
Huh?

How on earth can you SPARUL against a Data Space to which you don't have 
Create, Update, Delete privileges?

Is this happening?
> The jump into the semantic web should be taken carefully, small steps at a time.
>
>   Henry
>
>
> _______________________________________________
> foaf-protocols mailing list
> foaf-protocols at lists.foaf-project.org
> http://lists.foaf-project.org/mailman/listinfo/foaf-protocols
>
>   


-- 

Regards,

Kingsley Idehen	      
President & CEO 
OpenLink Software     
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen