[foaf-protocols] Privacy concern: different FOAF file depending on what website is asking

[Henry Story]

On 9 Dec 2011, at 13:19, Kingsley Idehen wrote to the foaf-protocols mailing list:

> We need a property in a owl:subPropertyOf relation with rdfs:seeAlso that offers a pathway to an ACL protected resource. 

+1
I think something like this would be the simplest.

> 
> You can also use owl:sameAs relations, but that brings in a need for reasoning capability on the part of a WebID verifier. This issue is basically ultimately about authorization that factors in pseudonyms via handling of co-references etc..

> 
> Kingsley 




Social Web Architect
http://bblfish.net/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.foaf-project.org/pipermail/foaf-protocols/attachments/20111209/d0a91799/attachment.htm