[foaf-dev] Privacy in FOAF

[Story Henry]

The protocols for privacy in foaf don't require much standard work, as  
they build on standard work done elsewhere.

So for example to use openid and foaf as described here
http://blogs.sun.com/bblfish/entry/the_openid_sequence_diagram

you would just need to
   - develop a vocabulary to point to an openid authentication point
   - develop a server that published that information
   - develop a client that knew how to use it

The rest is specified by openid I think.

For foaf+ssl described here,
http://blogs.sun.com/bblfish/entry/foaf_ssl_creating_a_global
you need even less as it builds on the well known https.
You can just use rdfs:seeAlso to point to the https protected  
resource. Then you need a client and a server.
Ah yes, you may need an rdf vocabulary for Romeo's foaf file  
describing his public key.

    I am writing a client that can do this at https://sommer.dev.java.net/
There is also some code we started for the server side. It is an open  
source project, and
I am always happy to accept contributions. The barriers to  
participation there are very low.

It may be good to get the Tabulator folks involved too. At the moment  
I think we are at an exploration
phase. Perhaps this would require its special mailing list?

Henry


On 6 Aug 2008, at 22:45, Hailton Sales wrote:

> Hello everyone,
>
>   I think this question is very interesting.
>   Yesterday I was told about a new service on the web that promises
> revolucionize the Social Networks with an *unrevealed *(anyone here  
> knows
> about that?), protocol that I know nothing about, you can see that  
> "new
> service" here: http://chi.mp/
>
>  I think this community has already stated something considering  
> topics
> like "RDFAuth", but what do you think about a specific protocol for
> descentralized Social Networks, something with the same intentions  
> like
> CHI.MP but more open?
>
>  Could you considerer a Resource-Oriented Social Network ou Really  
> Open
> Social Network, something totally RESTful, where the *FOAF URI* is the
> buzzword?
>  Using GET, POST, PUT, DELETE, HEAD http methods and HTTPS  
> principles, we
> could build a new protocol to achieve the same objects that http://chi.mp
> intends, but in this case the "community" would be included in the
> definitions.
>
>  What do we have in moment about a foaf live? Do we have a standard
> protocol to handle a FOAF in a REST-manner?
>
>
>
> On Wed, Aug 6, 2008 at 4:43 PM, Robert Mark White
> <markwhite28 at comcast.net>wrote:
>
>> here is another very interesting approach to privacy in foaf.
>>
>> http://dig.csail.mit.edu/2007/12/rep.html
>> _______________________________________________
>> foaf-dev mailing list
>> foaf-dev at lists.foaf-project.org
>> http://lists.foaf-project.org/mailman/listinfo/foaf-dev
>>
> _______________________________________________
> foaf-dev mailing list
> foaf-dev at lists.foaf-project.org
> http://lists.foaf-project.org/mailman/listinfo/foaf-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2429 bytes
Desc: not available
Url : http://lists.usefulinc.com/pipermail/foaf-dev/attachments/20080809/810cf46c/smime.bin