OpenID 1.2 Extensions Proposal
Lukas Rosenstock
inbox at lukasrosenstock.net
Wed Apr 5 08:41:12 UTC 2006
+1
I'm not sure if two Types in one Service can be used like in your second
example, and in the first one it makes no sense to double the URI because
it wouldn't make sense that the extension is on another server.
It could look like this:
<Service>
<Type>http://openid.net/signon/1.2</Type>
<URI>http://www.myopenid.com/server</URI>
</Service>
<Service>
<Type>http://openid.net/extensions/sreg/1.0</Type>
</Service>
Am 05.04.2006, 05:40 Uhr, schrieb Johannes Ernst
<jernst+lists.danga.com at netmesh.us>:
> What's unclear to me is why OpenID needs its own extensibility
> mechanism in the XRDS file -- isn't that what the XRDS file is
> supposed to be all about?
>
> Why not simply declare it as another Yadis service, like this:
>
> <Service priority="20">
> <Type>http://openid.net/signon/1.2</Type>
> <URI>http://www.myopenid.com/server</URI>
> </Service>
> <Service priority="20">
> <Type>http://openid.net/extensions/sreg/1.0</Type>
> <URI>http://www.myopenid.com/server</URI>
> </Service>
>
> or maybe even better, like this:
>
> <Service priority="20">
> <Type>http://openid.net/signon/1.2</Type>
> <Type>http://openid.net/extensions/sreg/1.0</Type>
> <URI>http://www.myopenid.com/server</URI>
> </Service>
>
> Sounds simpler to me (no Yadis parser extensions needed!), and more
> consistent with the architecture.
More information about the yadis
mailing list