- From: Andrei Sambra <andrei.sambra@gmail.com>
- Date: Thu, 8 Aug 2013 13:13:17 +0200
- To: Nick Jennings <nick@silverbucket.net>
- Cc: Kingsley Idehen <kidehen@openlinksw.com>, "public-lod@w3.org" <public-lod@w3.org>, "public-rww@w3.org" <public-rww@w3.org>, "public-webid@w3.org" <public-webid@w3.org>
- Message-ID: <CAFG79eg58bX17Xd-fasW6M3NDWkwqJhMKD=Z98jB=HoG-MgfZA@mail.gmail.com>
Hi Nick, On Wed, Aug 7, 2013 at 6:43 PM, Nick Jennings <nick@silverbucket.net> wrote: > It would help if there was some way one could reliably get and manage > WebID. As it is right now, neither rww.io nor my-profile.eu (which are > the only ones I know about) are functioning in terms of generating a WebID > for the browser. > > I had some from my-profile.eu that were generated several months ago, but > I removed them all during some tests and was unable to get a new one. I > tried in both Firefox and Chrome. Anyone having trouble as well? > I just tested both rww.io and my-profile.eu and I was able to issue certs without any problem (I am managing for both services). If you want to recover your account on my-profile.eu, just tell me the URI of your WebID and I'll bind your current email address to it so you can use the recovery feature. You can remove the email address once you have recovered your account and issued a new cert from your profile page. Andrei > > > > > > On Tue, Aug 6, 2013 at 8:01 PM, Kingsley Idehen <kidehen@openlinksw.com>wrote: > >> All, >> >> Following the earlier posts about WebID (and by implication, WebID+TLS), >> here is a very simple demonstration of how we can put this technology to >> good use re., protected document authoring and editing. >> >> For this exercise I've performed the following steps: >> >> 1. Created a protected Turtle document at: <http://kingsley.idehen.net/** >> DAV/home/kidehen/Public/**Linked%20Data%20Documents/** >> WebID-ACL-Demos/simple-shared-**turtle-doc.ttl<http://kingsley.idehen.net/DAV/home/kidehen/Public/Linked%20Data%20Documents/WebID-ACL-Demos/simple-shared-turtle-doc.ttl> >> > >> >> 2. Used WebID (Agent entity type denotation), WebID+TLS (for agent >> identity authentication), and an ACL (itself expressed in Turtle) to create >> a data access policy that enables anyone read the document's content, but >> only allowing those with verifiable WebIDs to perform read, write, and >> delete operations. >> >> This entire exercise is driven by Linked Data. >> >> Let everyone know how you get on :-) >> >> >> -- >> >> Regards, >> >> Kingsley Idehen >> Founder & CEO >> OpenLink Software >> Company Web: http://www.openlinksw.com >> Personal Weblog: http://www.openlinksw.com/**blog/~kidehen<http://www.openlinksw.com/blog/~kidehen> >> Twitter/Identi.ca handle: @kidehen >> Google+ Profile: https://plus.google.com/**112399767740508618350/about<https://plus.google.com/112399767740508618350/about> >> LinkedIn Profile: http://www.linkedin.com/in/**kidehen<http://www.linkedin.com/in/kidehen> >> >> >> >> >> >> >
Received on Thursday, 8 August 2013 11:14:05 UTC