dick at sxip.com
Sun Jan 8 19:35:24 UTC 2006
I don't see the path for how YADIS provides a "clean foundation" for
building user-controlled identity. Would you elaborate on that Johannes?
I get the protocol discovery, but still think that <link rel= > works
fine for that.
btw: if the value of rel was a URI, then the name space issue of what
the <link> tag is all about is dealt with.
On 6-Jan-06, at 4:49 PM, Johannes Ernst wrote:
> Exactly, why do something cleanly if a hack is just half as good? ;-)
> But for those on this list who are still puzzled by this question:
> because YADIS provides a clean foundation to build on top of.
> Authentication against a website -- like OpenID does today and LID
> and friends -- is probably somewhere in the area of 1% of what the
> identity visionaries (Google "identity gang") are envisioning that
> user-controlled identity will turn into:
> Disintermediating eBay would be closer to the 100% than the 0%, and
> that's only one of the examples.
> And one can't hope to build the 100% if one starts kludging after
> 1% of the work is done. So that's why we all agree that YADIS is
> (Sorry if you think that I'm continually stating and restating the
> very very obvious, I'm an earthling after all, dear Ford Prefect)
> On Jan 6, 2006, at 16:37, Martin Atkins wrote:
>> Johannes Ernst wrote:
>>> Let's define yourself a new YADIS capability ... and you are
>>> able to participate in the same framework. That doesn't mean
>>> that your
>>> new SSO can instantly be used to log into LiveJournal -- but it
>>> it opens up a defined path for Relying Parties to recognize
>>> "your" URLs
>>> and do something smart with it...
>> Of course, the same could be said for adding an element to the
>> HTML HEAD:
>> <link rel="alexid.server" href="http://www.not-an-openid-
>> Why do we need YADIS, again? :)
>> (I'm just joking, by the way!)
> Johannes Ernst
> NetMesh Inc.
More information about the yadis