[foaf-protocols] [foaf-dev] New FOAF services from Garlik

[Story Henry]

Hi Steve,

If you are willing to experiment a little, one thing that could be  
very interesting would be to give everyone (optionally if needed) who  
signs up with you a public/private key pair, downloadable as a .p12  
file [1], and add public key information as described in "foaf+ssl:  
adding security to open distributed social networks" to the foaf file.  
Having made it easy for people to get the client certificate in their  
browser, it will be much easier to play with developing real services.  
We currently have implementations in python, ruby, and java [3] you  
can look at to see how to do this. It is not a huge amount of work and  
could be full of potential.

Henry


[1] http://filext.com/file-extension/P12
[2] http://blogs.sun.com/bblfish/entry/foaf_ssl_adding_security
[3] http://blogs.sun.com/bblfish/entry/python_and_php_implementations_of

On 18 Dec 2008, at 19:08, Steve Harris wrote:

> Garlik is making available a beta-phase FOAF builder, along with it's
> FOAF index containing 10M+ FOAF files.
>
> http://foafbuilder.qdos.com/
>
> FOAF Builder is a beta-phase web application that allows you to
> create, edit, and augment FOAF files. You can start with an existing
> FOAF file, FOAF generated via existing web systems (Flickr, Last.fm,
> and LiveJournal), or start from scratch.
>
> Data entered into the FOAF builder can be marked as "private" in which
> case it will be stored independently of the public portion of the FOAF
> file.
>
> Once built, you can download the FOAF file to publish on your own
> server or you can opt to let Garlik host it in your behalf. Private
> data hosted by us will be stored in an OAuth[1] server. 3rd party
> applications may request access to this OAuth protected data, however
> control over this is in the owners hands. Using OpenID[2] the owner  
> can,
> if he chooses, grant access keys to allow the 3rd party to process the
> private FOAF data.
>
> The Garlik OAuth server is available at http://private.qdos.com/ -
> currently authors of 3rd party apps need to explicitly request client
> keys, but we will automate this in the future. Sample OAuth code
> demonstrating how to request private FOAF data, and host your own
> OAuth server will be available shortly.
>
> http://foaf.qdos.com/
>
> The foaf.qdos.com index of FOAF files now contains 10M FOAF files
> harvested from the web. FOAF files can be browsed, and you can
> navigate by both incoming and outgoing friend links. If your FOAF file
> is not yet indexed, please add it at http://foaf.qdos.com/ping
>
> This beta-phase service is available for non-commercial use only.
>
> We are keen to get feedback, so if you have any ideas or suggestions
> about enhancing this service please email qdos AT garlik.com.
>
> [1] http://oauth.net/
> [2] http://openid.net/
>
> --  
> Steve Harris
> Garlik Limited
> 2 Sheen Road
> Richmond  TW9 1AE
>
> T   +44(0)20 8973 2465
> F   +44(0)20 8973 2301
> www.garlik.com
>
> Registered in England and Wales 535 7233 VAT # 849 0517 11
> Registered office: Thames House, Portsmouth Road, Esher, Surrey, KT10
> 9AD
>
> _______________________________________________
> foaf-dev mailing list
> foaf-dev at lists.foaf-project.org
> http://lists.foaf-project.org/mailman/listinfo/foaf-dev