As I stated elsewhere, I think it's easily possible to "auto-detect" revision A without modified version-parameter, so I would go for option 1.
I wouldn't oppose to option 3 either. We should either keep in line with the "version is for the signature method, not the flow"-rule (option 1) or bump the minor version (option 3).. -Morten On May 1, 2009, at 10:25 AM, Blaine Cook wrote: > > We need to build some consensus around the version preference. As I > see it, there are several options: > > 1. "1.0 Rev A" with no version string change (i.e., oauth_version=1.0) > 2. "1.0a" (with oauth_version=1.0a) > 3. "1.1" > > Please indicate your support for one of these options, and try to > refrain from arguing your case here. The other thread remains open for > that purpose. I would especially like to hear from library > implementers here, and others who have not voiced their opinions in > the other threads. > > b. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to oauth@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 -~----------~----~----~----~------~----~------~--~---
