RE: Authentication workflow draft.

 

Nah. It happens offline. Like certs, the outsider, despised, rejected and
totally unworthy of running a global infrastructure (as in fact happens) -
based on  total de-centralization, focused on individuals, somehow
addressing the parallel social needs for spying. Everything W3C claims to be
about, in fact! 

 

Remember, I've spent over 15 years being told how useless certs are (as they
grow year by year, to now global scale, affecting almost every web user on
the planet).

 

They DON'T WORK (spoken as Google puts its https home page on certs.)

 

After 15 years of this, it's actually fun dealing with the rhetoric. The
point is, to make signed foaf file take on the mantle of certs.. Then I'm
finding a win win.

 

 

From: public-xg-webid-request@w3.org [mailto:public-xg-webid-request@w3.org]
On Behalf Of Henry Story
Sent: Tuesday, April 12, 2011 1:58 PM
To: Kingsley Idehen
Cc: peter williams; 'Akbar Hossain'; 'WebID XG'
Subject: Re: Authentication workflow draft.

 

Great Kingsley,

 

   I look forward to you and Peter getting together and hashing out
something initial that holds water here.

In the mean time I will focus a bit on the test suites  here with others to
make sure we interoperate on what we already have. 

 

Henry

 

On 12 Apr 2011, at 22:40, Kingsley Idehen wrote:





On 4/12/11 4:05 PM, Henry Story wrote: 

 

 

<aside topic="rest-vs-soap">

 Btw. REST tools are even more widespread that SOAP or xmlrpc tools, and
they are even more widely understood.  Amazons REST services was used 85%
more in 2003 http://www.oreillynet.com/pub/wlg/3005

And if you ask developers they prefer REST 

   http://stackoverflow.com/questions/76595/soap-or-rest


Be careful, don't make quantum leaps about "developers" and certainly not
"developers" and their comprehension of REST-ful client-server programming.

Peter (as I do sometimes) is explaining in too much detail. He could also
simply say: hey! Let's just WebID enable these existing Windows tools by
subtle tweaks within .NET Frameworks which drives most things these days .



 

Here is a very good presentation btw on REST btw 

: 

http://t.co/l1bmeeZ

 

It's not really worth having arguments on this here. 

</aside>


Does REST really matter if WebID is propagated all over the place by
tweaking existing protocols (good, bad, and the downright ugly) and
libraries across a plethora of platforms? 

RDF is confusing, REST is confusing, both are kinda provincial since the
rehash old ideas in new context. I remember a time when Web wasn't
Client-Server it was Application Server etc.. Then it was about SOAP, then
REST etc.. In reality a much ado about nowt bar rephrasing to celebrate
subtle context tweaks to old patterns via injection of new terminology etc..


Let's get WebID out everywhere. No RDF or REST distractions. Just the
ability to read and write structured data to Network Addresses subject to
ACLs driven by the WebID protocol :-)





-- 
 
Regards,
 
Kingsley Idehen       
President & CEO 
OpenLink Software     
Web: http://www.openlinksw.com <http://www.openlinksw.com/> 
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen 
 
 
 
 

 

Social Web Architect
http://bblfish.net/