Re: Simple WebID, WebID+TLS Protocol, and ACL Dogfood Demo

On 8/7/13 12:43 PM, Nick Jennings wrote:
> It would help if there was some way one could reliably get and manage 
> WebID. As it is right now, neither rww.io <http://rww.io> nor 
> my-profile.eu <http://my-profile.eu> (which are the only ones I know 
> about) are functioning in terms of generating a WebID for the browser.

Does this also apply to:

1. http://youid.openlinksw.com
2. http://id.myopenlink.net/certgen .

Note, both of these provide the pkcs#12 option (as opposed to keygen) by 
default.

In addition, if you already have a FOAF profile doc, use the second tab 
(we forgot to list FOAF where you see OpenID). Then follow the wizard to 
then end of the process which basically provides content for you to 
manually add to your FOAF profile. Of course, if you don't manage your 
own profile document, you take the defaults which leads to the profile 
document be hosted at id.myopenlink.net.

As I type, I just realized we overlooked a key feature and that's 
setting an ACL on the profile document generated on id.myopenlink.net so 
that you control the ACLs going forward.

Note to self (and rest of OpenLink Data Spaces team), that's a new 
feature zilla :-)


Kingsley
>
> I had some from my-profile.eu <http://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?
>
>
>
>
> On Tue, Aug 6, 2013 at 8:01 PM, Kingsley Idehen 
> <kidehen@openlinksw.com <mailto: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>
>
>     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/%7Ekidehen>
>     Twitter/Identi.ca handle: @kidehen
>     Google+ Profile: https://plus.google.com/112399767740508618350/about
>     LinkedIn Profile: http://www.linkedin.com/in/kidehen
>
>
>
>
>
>


-- 

Regards,

Kingsley Idehen 
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen