I'm not an RDF/OWL expert, though that looks reasonable to me. How do
we deal with Auth 1.x which uses openid.server and openid.delegate
versus Auth 2.0 which uses openid2.provider and openid2.local_id?
--David
-Original Message-
From: Benjamin Nowack [mailto:[EMAIL PROTECTED]
Sent:
Is there a wiki page that exists to point to? Josh and Johnny, see any
issues with this?
Also any wording to propose Johannes?
Thanks,
--David
-Original Message-
From: Johannes Ernst [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 23, 2007 12:57 PM
To: Recordon, David
Cc:
The openid2.* links bug me a little.. but due to no openid.ns being
defined in the 1.x protocol, maybe there is no other way to specify by
HTML discovery that your OP is 2.0 capable. Would it be bad to have a
openid.version link instead?
Also, the spec mentions AJAX interactions, but I don't see
Yeah, I'm not a big fan of openid2.* though it was the simplest method
of fixing up HTML discovery to work with multiple protocol versions. I
know Josh thought about this more than I did though.
From what I've seen people do, it is AJAX between your server and
application, then OpenID's
On 1/30/07, Recordon, David [EMAIL PROTECTED] wrote:
Yeah, I'm not a big fan of openid2.* though it was the simplest method
of fixing up HTML discovery to work with multiple protocol versions. I
know Josh thought about this more than I did though.
1. Before authentication is initiated, the RP
