I think it's a great idea. I personally didn't know where to find the RFC draft until reading about it on your blog yesterday. I'm sure many people would be in a similar position. A note at the top of the oauth.net specs would definitely be helpful.
- Paul On 2009-11-24, at 2:39 AM, Eran Hammer-Lahav wrote: > How do people feel about adding a note at the top of: > > http://oauth.net/core/1.0 > http://oauth.net/core/1.0a > > Pointing visitors to the OAuth Core 1.0 RFC draft (pending IESG approval): > > http://tools.ietf.org/html/draft-hammer-oauth > > The new draft is significantly better and easier to read. We can't switch the > content at the two URIs above because they are linked to the IPR agreements. > We also shouldn't because those specs represent a community product that > should be kept for future documentation and many existing links point there. > > For those not paying attention, the new draft also contains a few protocol > changes and clarifications which may have a small impact in existing > libraries. For the list of changes: > > http://tools.ietf.org/html/draft-hammer-oauth-07#appendix-A > > Comments? > > EHL > > -- > > You received this message because you are subscribed to the Google Groups > "OAuth" group. > To post to this group, send email to oa...@googlegroups.com. > To unsubscribe from this group, send email to > oauth+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/oauth?hl=en. > > -- You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to oa...@googlegroups.com. To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/oauth?hl=en.
