Re: Using Twitter as an IdP space for WebID

On 11/1/11 8:53 AM, Michael Brunnbauer wrote:
> Hello Kingsley,
> you can do in your "data space" (whatever that is) whatever you want - as long
> as things stay there. The problem is they don't. You put URIs like
> in SAN fields and by this you suggest to other
> people that this URI can be used to identify a person.

An entry in a SAN field != Identify a Person. An application processing 
a security token (e.g. X.509 Cert.) decides what to make of the entries 
in the extension. In addition, the entry in the SAN is not supposed to 
be an end-user matter, it is strictly for WebID processors.

So what happens when I use an acct: or mailto: scheme URI in the SAN? 
This also works with WebID via Webfinger and other Web Linking patterns. 
Do they identify people? Have they broken some non existent rule of URI 

>   It cannot - except in
> your data space where you make the rules. Outside of your data space,
> people have to agree on rules and meanings.

See my comments and example above.

You are trying to defend namespaces (incorrectly) by compromising the 
essence of URIs, unfortunately.

> Regards,
> Michael Brunnbauer
> On Mon, Oct 31, 2011 at 02:24:46PM -0400, Kingsley Idehen wrote:
>> On 10/31/11 11:12 AM, Michael Brunnbauer wrote:
>>> Hello Kingsley,
>>> I just discovered that the WebID wiki ( seems
>>> to
>>> support your position of calling your idea a WebID: "A WebID is a way to
>>> uniquely identify a person, company, organization, or other agent using a
>>> URI.
>>> One direct use of this concept is the protocol known as foaf+ssl...".
>>> Maybe the draft at should
>>> reflect this...
>>>>> If twitter does not use the #this hashtag to identify a
>>>>> person
>>>>> or account, you should not do it.
>>>> Sorry, I don't agree.
>>> Here, we stay in disagreement.
>> Okay, but you will ultimately see where I am coming from. For instance,
>> you are in way inferring that the following statement can't existing in
>> a graph hosted in my data space:
>> <>  foaf:knows
>> <>  .
>> <>  owl:sameAs
>> <{your-twitter-handle}#this>.
>> <>  owl:sameAs
>> <>  .
>> You cannot tell people what claims to make in their own data spaces.
>> Misconceptions of this nature are what's lead to the 12+ odyssey re.
>> Semantic Web vision comprehension, appreciation, and adoption. The game
>> is never about:
>> 1. telling people what they can or cannot do in their own data spaces .
>> 2. mandating a global ontology .
>> 3. constraining underlying data model to a specific syntax .
>> I am making statements in my own data space (or that of a specific agent
>> e.g., a WebID protocol compliant relying agent) that are the basis of
>> inference in said data space en route to providing value that may or may
>> not be utilized by others. Everything is optional, and that's the only
>> way it can be.
>> The beauty of URIs is that the WWW (in its 1.0 and 2.0 dimensions) has
>> already generated millions (if not billions) of globally unique
>> identifiers that are http: scheme based, so lets put them to use without
>> getting all draconian about matters.
>>> Regards,
>>> Michael Brunnbauer
>> -- 
>> Regards,
>> Kingsley Idehen	
>> President&   CEO
>> OpenLink Software
>> Company Web:
>> Personal Weblog:
>> Twitter/ handle: kidehen
>> Google+ Profile:
>> LinkedIn Profile:



Kingsley Idehen	
President&  CEO
OpenLink Software
Company Web:
Personal Weblog:
Twitter/ handle: kidehen
Google+ Profile:
LinkedIn Profile:

Received on Tuesday, 1 November 2011 14:01:49 UTC