http://www.hueniverse.com/hueniverse/2009/03/state-of-the-oauth-union.html
OAuth Core 1.0 was declared as final specification almost a year and a half
ago. The overall reception was incredible with almost overnight adoption from
major web players like Google, Yahoo, and MySpace. We even got the attention of
the major internet standard bodies, approaching us, some officially, some less
so, to bring the work over. It has been a good year for community-driven
specifications with OAuth leading the charge.
During the past year, we've also seen a lot of new ideas and new requirements
coming up. Most people are not aware that there are about 15 proposed
extensions for OAuth covering a wide range of topics. There is also a lot of
confusion regarding what is going on with the specification, how should
extension be proposed (and made "official"), and recent announcements.
This post will try to answer some of the questions I receive from people on a
daily basis. If you care about OAuth, implemented it or plan to, or have any
dependency on the specification, technology, or community, this should be a
helpful read. If I missed an important question, please let me know in the
comments.
* What's Up?
* What is the Status of OAuth Core 1.0?
* Is there a New Version Coming?
* What is Being Done to Make the Current Specification Easier to Read?
* Is OAuth Moving to the IETF?
* Why the IETF?
* Why does the IETF want OAuth?
* Who Made You In Charge (to Bring OAuth to the IETF)?
* Why isn't the Current Specification Good Enough? Why Seek a Standard?
* OAuth doesn't Address My Use Case, How can I Extend it?
* Any Upcoming OAuth Events?
EHL
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"OAuth" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/oauth?hl=en
-~----------~----~----~----~------~----~------~--~---
