[foaf-protocols] Some FOAF services

[Story Henry]

Mischa's qdos foaf search engine could be useful to put together quick  
prototypes of foaf+ssl protocol
described in this post

	http://blogs.sun.com/bblfish/entry/foaf_ssl_adding_security_to

I think the social verification service (3 below) could be especially  
useful .  For step 6 in the diagram posted on the blog referred to  
above.

As I see it though this service currently returns a list of  
identifiers ( one does not quite know which identifiers: could be  
openids, home pages, or other ) of people that are within a specified  
distance of the owner of the initial URL.

For Foaf+ssl we would need the foaf URL of the person, because that is  
the one we are certain of, as it was verified during the SSL connection.

So I am wondering what kind of interface we would need to get the  
inference we need . A SPARQL endpoint perhaps ? What kind of query  
would one have to ask?

SELECT ?p
WHERE { :me qdos:distance_2 ?p } .

Perhaps other queries would be helpful too.

I am not saying one needs the SPARQL interface: a web service  
interface like the one currently on qdos sounds good. It is just  
easier to use SPARQL to describe the type of results that we are  
looking for.


Henry

On 26 Nov 2008, at 16:25, Mischa at Garlik wrote:

> Hello,
>
> Am mailing round to announce some FOAF related services Garlik are  
> hosting at foaf.qdos.com.
>
> 1. FOAF Validator[1]: We have put together a page which can be used  
> to validate foaf documents. We put this together based on common  
> errors we found in FOAF documents online. Any suggestions for  
> further tests are welcomed.
>
> 2. FOAF Reverse Search[2]: This service outputs foaf:knows  
> relationships from our KB stating who claims to know the foaf:Person  
> in question. You can present the service with either a foaf:Person  
> URI like so:
>
> http://foaf.qdos.com/reverse/?path=http://www.w3.org/People/Berners-Lee/card%23i
>
> or you can search for an Inverse Function Property (IFP) if the  
> foaf:Person URI is not known for example, you can find who claims to  
> know the foaf:Person with the following homepage: http://plugin.org.uk/
> like so (notice the inclusion of the GET argument ifp):
>
> http://foaf.qdos.com/reverse/?path=http://plugin.org.uk/&ifp=
>
> Given the decentralised nature of foaf data, this allows data to be  
> presented regarding who claims to know a foaf:Person.
>
> 3. FOAF Social Verification [3]: This allows you to make use of the  
> foaf social network to act as a whitelist for blog, email, and other  
> online activity
>
> 4. FOAF Viewer: You can also use our GUI [5]  to visual your foaf  
> network. For example, see Steve's foaf file here :
> http://foaf.qdos.com/find/?q=http%3A%2F%2Fplugin.org.uk
>
> 5. FOAF pinger: And finally, If we dont have your foaf file in our  
> KB, you can use our ping [4] service to upload your foaf:Document to  
> our KB so that you can make use of our services.
>
> Any thoughts/suggestions welcomed,
>
> Mischa
>
> [1] http://foaf.qdos.com/validator/
>
> [2] http://foaf.qdos.com/reverse
>
> [3] http://foaf.qdos.com/verify-demo & http://foaf.qdos.com/verify-about
>
> [4] http://foaf.qdos.com/find/
>
> [5] http://foaf.qdos.com/ping
> ___________________________________
> Mischa Tuffield
> Email: mischa.tuffield at garlik.com
> Homepage - http://mmt.me.uk/
> FOAF - http://mmt.me.uk/foaf.rdf
>