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

Re: How can users protect their foaf profile

From: Mo McRoberts <mo.mcroberts@bbc.co.uk>
Date: Wed, 31 Aug 2011 12:51:43 +0100
Cc: public-xg-webid@w3.org
Message-Id: <F3CA8ABC-E0FB-4DFC-926B-4848D8A8D3ED@bbc.co.uk>
To: Andrei Sambra <andrei@fcns.eu>

On 31 Aug 2011, at 12:10, Andrei Sambra wrote:

> Hi,
> 
> There is currently no easy way to do it. If you really care about the data you store in your foaf file, you could try implementing a system (think ACLs) on the machine where you store it.

It struck me recently that one way to do this, in principle, would be to serve your FOAF resource via HTTPS and request an optional certificate. RPs should then provide the server cert used on the site's servers (so it's known in advance). Then you generate a FOAF document according to whoever is requesting it.

The snag is that a request for 'optionally providing a certificate' seems to be pretty broken in servers and clients alike.

M.

-- 
Mo McRoberts - Data Analyst - Digital Public Space,
Zone 1.08, BBC Scotland, 40 Pacific Quay, Glasgow G51 1DA,
Room 7066, BBC Television Centre, London W12 7RJ,
0141 422 6036 (Internal: 01-26036) - PGP key CEBCF03E


http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
					
Received on Wednesday, 31 August 2011 11:52:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 31 August 2011 11:52:22 GMT