W3C home > Mailing lists > Public > public-xg-webid@w3.org > June 2011

WebID and client tools - was: WebID vs. JSON (Was: Re: Think before you write Semantic Web crawlers)

From: Henry Story <henry.story@bblfish.net>
Date: Wed, 22 Jun 2011 18:07:24 +0200
Cc: Linked Data community <public-lod@w3.org>
Message-Id: <BDAC5D1D-41A6-4CC0-8A33-E3557BA9348F@bblfish.net>
To: William Waites <ww@styx.org>, WebID XG <public-xg-webid@w3.org>

On 22 Jun 2011, at 16:41, William Waites wrote:

> 
> [1] examples of non-WebID aware clients: rapper / rasqal, python
> rdflib, curl, the javascript engine in my web browser that doesn't
> properly support client certificates, etc.

curl is WebID aware. You just need to get yourself a certificate for your crawler, and then use

  -E/--cert  <certificate[:password]> 

arguments to pass that certificate if the server requests it. 

The specs for HTTPS client certs are so old and well established that it is built by default into most libraries. So it would not take a lot to expose it, if it is not already in all the libs you mention.

But thanks for this new FAQ [1]. We'll try to fill in the details on how to work with the libs above using webid.

There is a Javascript layer for https too, but what is the point of doing that there? Let the browser do the https for you.

Henry

[1] http://www.w3.org/wiki/Foaf%2Bssl/FAQ

Social Web Architect
http://bblfish.net/
Received on Wednesday, 22 June 2011 16:07:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:24 UTC