Comments on: What can/should you do with an OpenID end-point? http://kveton.com/blog/2008/01/13/what-canshould-you-do-with-an-openid-end-point/ I iz on site, mis spelin ur last naymz Sun, 20 Jul 2008 14:49:52 +0000 http://wordpress.org/?v=2.3.2 By: faineant http://kveton.com/blog/2008/01/13/what-canshould-you-do-with-an-openid-end-point/#comment-94327 faineant Sat, 29 Mar 2008 07:14:33 +0000 http://kveton.com/blog/2008/01/13/what-canshould-you-do-with-an-openid-end-point/#comment-94327 Услуги ветеринара. Выезд. <a href="http://faineant.pochta.ru" rel="nofollow">Ветеринарная помощь</a> Услуги ветеринара. Выезд.
Ветеринарная помощь

]]> By: Michael Anckaert http://kveton.com/blog/2008/01/13/what-canshould-you-do-with-an-openid-end-point/#comment-77335 Michael Anckaert Mon, 14 Jan 2008 16:25:54 +0000 http://kveton.com/blog/2008/01/13/what-canshould-you-do-with-an-openid-end-point/#comment-77335 The use of URL's as identifiers is natural as more and more people associate them with URL's. For the idea about calendar service and such perhaps it would be suitable to make the SREG list expandable and create some sort of list of all possible attributes. Then it would be possible to add a 'calendar' attribute and set the value to the location of your calendar. This would make for a very flexible system. The use of URL’s as identifiers is natural as more and more people associate them with URL’s.

For the idea about calendar service and such perhaps it would be suitable to make the SREG list expandable and create some sort of list of all possible attributes. Then it would be possible to add a ‘calendar’ attribute and set the value to the location of your calendar. This would make for a very flexible system.

]]> By: MyStrands Blog » OpenIDDevCamp a success http://kveton.com/blog/2008/01/13/what-canshould-you-do-with-an-openid-end-point/#comment-77334 MyStrands Blog » OpenIDDevCamp a success Mon, 14 Jan 2008 15:37:27 +0000 http://kveton.com/blog/2008/01/13/what-canshould-you-do-with-an-openid-end-point/#comment-77334 [...] of the highlights included discussions about OpenID as end-points as well as how OpenID and OAuth could work together [...] […] of the highlights included discussions about OpenID as end-points as well as how OpenID and OAuth could work together […]

]]> By: OpenID » Blog Archive » The First OpenIDDevCamp was a Success http://kveton.com/blog/2008/01/13/what-canshould-you-do-with-an-openid-end-point/#comment-77333 OpenID » Blog Archive » The First OpenIDDevCamp was a Success Mon, 14 Jan 2008 15:33:38 +0000 http://kveton.com/blog/2008/01/13/what-canshould-you-do-with-an-openid-end-point/#comment-77333 [...] good group discussion about the possibilities around what we can land at OpenID end-points. (see Scott’s post on this). Consensus is that we’ve got the pieces and now its time to crank out some [...] […] good group discussion about the possibilities around what we can land at OpenID end-points. (see Scott’s post on this). Consensus is that we’ve got the pieces and now its time to crank out some […]

]]> By: Luigi Montanez http://kveton.com/blog/2008/01/13/what-canshould-you-do-with-an-openid-end-point/#comment-77326 Luigi Montanez Sun, 13 Jan 2008 17:03:23 +0000 http://kveton.com/blog/2008/01/13/what-canshould-you-do-with-an-openid-end-point/#comment-77326 The default photo service/calendar idea is outstanding. The more we can make the Web act like an OS Desktop, the more users will start to clearly see the advantages of data portability. I think the next logical step is coming up with some preliminary attribute definitions based on OpenID AX for the in-browser experience. Also, because OAuth is simply for auth, there may be a need for a common attribute exchange format for that as well. Looking forward to more updates from the Camp. Also, for readers like me who had not heard of XRDS before now, <a href="http://www.windley.com/archives/2007/05/using_xrds.shtml" rel="nofollow">this post is helpful</a>. The default photo service/calendar idea is outstanding. The more we can make the Web act like an OS Desktop, the more users will start to clearly see the advantages of data portability.

I think the next logical step is coming up with some preliminary attribute definitions based on OpenID AX for the in-browser experience. Also, because OAuth is simply for auth, there may be a need for a common attribute exchange format for that as well. Looking forward to more updates from the Camp.

Also, for readers like me who had not heard of XRDS before now, this post is helpful.

]]> By: Gabe Wachob http://kveton.com/blog/2008/01/13/what-canshould-you-do-with-an-openid-end-point/#comment-77320 Gabe Wachob Sun, 13 Jan 2008 03:56:33 +0000 http://kveton.com/blog/2008/01/13/what-canshould-you-do-with-an-openid-end-point/#comment-77320 Glad to see that "discovery" is getting folks excited. It's what's been motivating those of us in the XRI TC since day one (along with some other things, of course). I've always described XRI resolution (from which XRDS comes) as a discovery protocol. Discovery before transaction is not exactly a new concept, but to do it at the granularity of individuals (rather than pre-determined business partners or network endpoints, or trading partners, etc) is a new mindset... BTW, this is the promise of "identifier-based identity" (as opposed to "card-based identity") - not that one is inherently better than the other. Rather, the analogy to the real world for card-based systems is clearer, so there is more intuitive understanding of the benefits of card-based identity. Identifier-based identity has (probably to us) obvious advantages and its interesting and cool to see ya'll talking about some of those at OpenIDDevCamp... Glad to see that “discovery” is getting folks excited. It’s what’s been motivating those of us in the XRI TC since day one (along with some other things, of course). I’ve always described XRI resolution (from which XRDS comes) as a discovery protocol. Discovery before transaction is not exactly a new concept, but to do it at the granularity of individuals (rather than pre-determined business partners or network endpoints, or trading partners, etc) is a new mindset…

BTW, this is the promise of “identifier-based identity” (as opposed to “card-based identity”) - not that one is inherently better than the other. Rather, the analogy to the real world for card-based systems is clearer, so there is more intuitive understanding of the benefits of card-based identity. Identifier-based identity has (probably to us) obvious advantages and its interesting and cool to see ya’ll talking about some of those at OpenIDDevCamp…

]]>