Right, I'd agree with that. This would just be the first case where the Auth spec doesn't provide at least one service type for the file. In any case, adding the ability seems important.
--David -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Atkins Sent: Monday, October 16, 2006 12:37 AM To: specs@openid.net Subject: Re: Discussion: RP Yadis URL? Recordon, David wrote: > > I'm torn if this parameter should be added to the spec at this time or > not. Adding the parameter is conceptually simple, though I don't > think there is agreement on what the RP should be publishing in their > Yadis file. There is the section > http://openid.net/specs/openid-authentication-2_0-10.html#anchor42 > which has the RP publish a return_to URL, though the section was meant > to be removed as that URL may not be the right entry point to start a > transaction. > I would say that what's inside the Yadis document is outside the scope of OpenID Auth. It's simply a hook to enable extensions that must be instrumented at the RP side. In other words, OpenID auth just needs to specify how to find an RP's Yadis document. The rest is for other people to figure out. That is the point of Yadis, after all. (and then this IdP-initiated login thing could be an extension built upon this ability, and thus not hold up Auth 2.0.) _______________________________________________ specs mailing list specs@openid.net http://openid.net/mailman/listinfo/specs _______________________________________________ specs mailing list specs@openid.net http://openid.net/mailman/listinfo/specs
