W3C home > Mailing lists > Public > public-webid@w3.org > September 2012

Re: Perceived issues with TLS Client Auth

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Thu, 27 Sep 2012 09:22:43 -0400
Message-ID: <50645323.7050300@openlinksw.com>
To: Henry Story <henry.story@bblfish.net>
CC: Ben Laurie <benl@google.com>, public-webid <public-webid@w3.org>
On 9/27/12 6:34 AM, Henry Story wrote:
> I don't think we should expect everyone to write Turtle ( though I think as part of a logic course at high school that would be a great idea ), but that does not mean we should assume people have no intelligence at all. And certainly we should not try to act as if they did not have any either, and we should not use the pretext of a too quickly assigned mental level - that marketing folks like to promote to people they sell advertising to - in order to remove people's freedom.

Note, when I make reference to write Turtle by hand [1][2][3], its 
purely as a basis for:

1. understanding Linked Data concepts modulo distractions such as:
     - domain name ownership
     - dns access and admin privileges
     - http server access and admin privileges
     - entity name disambiguation matters associated with http: scheme 
uris when used as entity denotation (naming) mechanism

2. appreciate the benefits of tools.

I just want to be crystal clear about the reasons behind my view that:

1. people should learn the basics of Linked Data via a simple Turtle 
document
2. ditto the basics of the WebID authentication protocol.

All my staff and kids (bar my 5 year old that's getting close) can read 
and write simple Turtle documents. The can create simple digital 
sentences that claim:

## Doc Content Start ##

<#i> like <#that> .
<#i> know <#thatPerson> .
<#i> made <#that> .

## Doc content end ##

After that, they open up a Linked Data browser and just can't stop 
expanding what started off as a very basic experiment re. self 
expression. Especially, when the understand the power of cross 
referencing URIs from DBpedia etc..

>
>> >
>>>> >>>If I visit joe.name and cannot log in because I have no cert, I
>>>> >>>have to somehow get a new cert issued with the right WebID (i.e. the
>>>> >>>one joe.name is expecting). How do I do that?
>>> >>
>>> >>If you lost your Google+ certificate you:
>>> >>
>>> >>1. go to google+
>>> >>2. login - if you lost your password, you get your social network to help you recover it
>>> >>3. delete the old certificate listed there
>>> >>4. get a new certificate
>> >
>> >See above.
> Don't underestimate people's intelligence.
>
Amen!

Links:

1. http://bit.ly/NYwGCd -- basic Turtle template
2. http://bit.ly/SBDmXr -- describing stuff you like via a simple Turtle 
document
3. http://bit.ly/O4LNKf -- how to create and control your own Web-scale 
verifiable identity .

-- 

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







Received on Thursday, 27 September 2012 13:23:06 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:40:59 UTC