- From: Norman Gray <norman@astro.gla.ac.uk>
- Date: Wed, 7 Aug 2013 13:47:58 +0100
- To: Kingsley Idehen <kidehen@openlinksw.com>
- Cc: public-lod@w3.org
Greetings, all Relevant to the question of serving the FOAF file... On 2013 Aug 7, at 02:07, Kingsley Idehen wrote: > Circa. 2013 we have storage services such as Dropbox, Amazon S3, Google Drive, Microsoft SkyDrive, Box.NET etc.., all of these can host a profile document that describes claims that mirror those stored in your local keychain hosted X.509 cert. You simply use the SAN slot to connect these profile documents via a WebID and the leave the rest to logic expressible in queries delivered over HTTP e.g., SPARQL ASK :-) I just tried this. My WebID <http://nxg.me.uk/norman/> does a 303 redirect to a FOAF file. Right now, if you ask for text/turtle, it does a 303 redirect to <https://www.dropbox.com/s/getd5vxhafbutgl/norman.ttl>, which then does a 302 redirect to some hash on Dropbox's content delivery network. ...and this still works, according to <https://webid.turnguard.com/WebIDTestServer/debug>! This is, I suppose parenthetically, another way of doing the indirection that Hugh was talking about. My WebID is merely a .htaccess file, but could be something like a purl.org URI redirecting to a file on Dropbox or similar. That's nice and easy. (I don't think this would _quite_ work with purl.org right now, because of conneg intricacies, but it's near-as-dammit, and one can imagine a very similar service which did). All the best, Norman -- Norman Gray : http://nxg.me.uk SUPA School of Physics and Astronomy, University of Glasgow, UK
Received on Wednesday, 7 August 2013 12:48:31 UTC