Since it seemed that you hadn't noticed the proposed SMTP Extension for
Yadis Discovery (which happened to predate the one mentioned on the page), I
took the liberty of referencing it as well.
I have also made a few formatting improvements en route.
Regards,
Dmitry
=damnian
I'd agree on specifying HTTP as the only resolution method required.
Unfortunately, I have a conflict of interests with the SMTP service
extension...
Regards,
Dmitry
=damnian
___
specs mailing list
specs@openid.net
Boris,
Did you look at the Identity Manager proposal?
http://blog.phpbb.cc/2007/01/20/identity-manager-a-browser-based-solution-to-openid-phishing/
Regards,
Dmitry
=damnian
___
specs mailing list
specs@openid.net
Dick,
This is definitely an interesting proposal. However, it only attempts to
solve the recycling problem, whereas canonical IDs would solve this and
several more.
Will this break existing OpenID 1.1 RPs? Which ones? Is this going to be
an issue for them?
As far as I can tell, this would
I think this argument is bogus. There is hardly any additional
complexity aside from XRI and Yadis. I'm willing to entertain
suggestions for simplifying the handling of those discovery
mechanisms. The specification is significantly *longer*, but that's
primarily because it's much more
There is a proposed solution that we had consensus on (Dick's
fragment proposal.)
Would you please specify whom you are referring to by we? I understand
that various matters are being discussed outside of this list, but shouldn't
the whole community be part of the decisions made?
I didn't hear
As a relative newcomer to the OpenID community, I realize this may have
been debated endlessly already, and I may just be shouted down.
It definitely has been debated endlessly.
Or am I alone here?
No, you aren't. There are many who agree with this entirely, some of whom
have expressed their
