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

Re: WebIDRealm RDFa

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Wed, 04 Jan 2012 18:45:44 -0500
Message-ID: <4F04E4A8.5060901@openlinksw.com>
To: public-xg-webid@w3.org
On 1/4/12 6:25 PM, Henry Story wrote:
>> I really don't know what to say.
> You could say: "Good idea! Let's work on improving automatic validators. How can we do that easily?"
>> >  Testing this stuff should be dead simple. There's a spec, there are implementations, and then QA test runs.
> The spec is simple but as you see there are a lot of different pieces, and a lot of people joining who don't know all the pieces.

Err.. that isn't news. And as I've already stated, we haven't even got 
to the real challenges yet. Anyway, I am going to leave those issues to 
play out naturally.

>   You even have had trouble as witnessed on this list recently. And it even looks like you are not parsing xsd:hexBinary correctly as we discovered today.

What are you referring to?
Which WebID is failing?
> I am having other issues it seems.


>   So clearly its not THAT simple.

It could be that simple, but again, this is one of those things that 
will just have to play itself out. Eventually, you will find out that 
"deceptively simple" doesn't have to be "mercurially simple".

>   It's simpler than OpenId, but as we are moving to security space, things just are more complicated.

I haven't inferred anything about OpenID vs WebID.

OpenID is good for WebID, they are mutually beneficial in the real 
world. Same applies to OAuth.



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 Wednesday, 4 January 2012 23:46:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:29 UTC