Re: [OAUTH-WG] Underscore, dash, green, blue

["William Mills" <[e-mail]>]

+1 for _
 
I don't find HTTP header names having dashes confusing, because they all
do.


________________________________

	From: [e-mail] [mailto:[e-mail]] On
Behalf Of Joseph Smarr
	Sent: Friday, July 02, 2010 3:16 PM
	To: Eran Hammer-Lahav
	Cc: OAuth WG ([e-mail])
	Subject: Re: [OAUTH-WG] Underscore, dash, green, blue
	
	
	Just remember that dashes are problematic for JavaScript, since
oauth_token is a valid variable name, but oauth-token is not. So unless
you're sure this will never be a problem, +1 to underscores everywhere.
I know HTTP headers normally use dash, but if you want to use dashes for
headers and underscores everywhere, you have the burden of proof that
this won't cause too much confusion... 

	Thanks, js
	
	
	On Thu, Jul 1, 2010 at 11:25 AM, Eran Hammer-Lahav
<[e-mail]> wrote:
	

		The 1.0 install base is small enough to ignore. Looking
at the interest and community around 2.0 makes such considerations
marginal.
		
		There is no problem with underscores in headers, it is
just unusual.
		
		EHL
		

		> -----Original Message-----
		> From: Marius Scurtescu [mailto:[e-mail]]
		> Sent: Thursday, July 01, 2010 11:19 AM
		> To: Eran Hammer-Lahav
		
		> Cc: Luke Shepard; OAuth WG ([e-mail])
		> Subject: Re: [OAUTH-WG] Underscore, dash, green, blue
		>
		> 3 - all underscores.
		>
		> If underscores are a big issue with headers then we
should consider 1
		> - all dashes. The problem with all dashes is that it
is counterintuitive for
		> people that know OAuth 1.
		>
		> Marius
		>
		>
		>
		> On Thu, Jul 1, 2010 at 11:01 AM, Eran Hammer-Lahav
		> <[e-mail]> wrote:
		> >
		> >
		> >> -----Original Message-----
		> >> From: Luke Shepard [mailto:[e-mail]]
		> >> Sent: Thursday, July 01, 2010 10:58 AM
		> >> To: Eran Hammer-Lahav
		> >> Cc: Justin Hart; Pelle Braendgaard; OAuth WG
([e-mail])
		> >> Subject: Re: [OAUTH-WG] Underscore, dash, green,
blue
		> >>
		> >> Don't really care, but to pick one - underscores
throughout.
		> >>
		> >> Why not headers?
		> >
		> > Historically, HTTP headers use dashes and not
underscores, but there is
		> nothing to prevent us from using underscores
throughout.
		> >
		> > EHL
		> >
		> >> On Jul 1, 2010, at 9:23 AM, Eran Hammer-Lahav
wrote:
		> >>
		> >> > That's wasn't an option for a reason. Beside
offending my esthetic
		> >> sensibility :-) having the same parameter use a
different name
		> >> between the header and endpoint makes registration
of extension
		> >> parameters much harder. For example, if we used
this scheme, the
		> >> 'error-uri' parameter would require two
registration requests, one
		> >> for 'error-uri' and another for 'error_uri'.
		> >> >
		> >> > EHL
		> >> >
		> >> >> -----Original Message-----
		> >> >> From: [e-mail]
[mailto:[e-mail]] On
		> >> >> Behalf Of Justin Hart
		> >> >> Sent: Thursday, July 01, 2010 7:10 AM
		> >> >> To: Pelle Braendgaard
		> >> >> Cc: OAuth WG ([e-mail])
		> >> >> Subject: Re: [OAUTH-WG] Underscore, dash, green,
blue
		> >> >>
		> >> >> +1 for underscores except header keys.
		> >> >> ----
		> >> >> -- Justin Hart
		> >> >> -- [e-mail]
		> >> >>
		> >> >>
		> >> >>
		> >> >>
		> >> >>
		> >> >>
		> >> >> On Jul 1, 2010, at 7:39 AM, Pelle Braendgaard
wrote:
		> >> >>
		> >> >>> I already implemented 09 but it was a (very
tiny) bit of a hassle
		> >> >>> to have to convert underscores.
		> >> >>>
		> >> >>> So I also agree with 3 except headers
		> >> >>>
		> >> >>> On Thu, Jul 1, 2010 at 2:41 AM, Lukas
Rosenstock
		> >> >>> <[e-mail]>
		> >> >> wrote:
		> >> >>>> 3 except headers.
		> >> >>>>
		> >> >>>> 2010/7/1 Eran Hammer-Lahav
<[e-mail]>:
		> >> >>>>> First, sorry about this. J
		> >> >>>>>
		> >> >>>>>
		> >> >>>>>
		> >> >>>>> I do my best not to ask the group this kind
of questions and
		> >> >>>>> just pick something on my own, but I can't
decide so I'll run a
		> >> >>>>> quick vote (yes, a VOTE - I can't imagine
seeking a consensus call on
		> this).
		> >> >>>>>
		> >> >>>>>
		> >> >>>>>
		> >> >>>>> -09 uses underscores for parameter names
(except for in the
		> >> >>>>> headers) and dashes for parameter values.
This seems like an
		> >> >>>>> odd
		> >> selection.
		> >> >>>>> Before, it used dashes for header parameter
names, and
		> >> >>>>> underscore everywhere else. Not great either.
		> >> >>>>>
		> >> >>>>>
		> >> >>>>>
		> >> >>>>> So...
		> >> >>>>>
		> >> >>>>>
		> >> >>>>>
		> >> >>>>> The changes my OCD can live with:
		> >> >>>>>
		> >> >>>>>
		> >> >>>>>
		> >> >>>>> 1. Use dashes throughout
		> >> >>>>>
		> >> >>>>> 2. Use underscores for all parameter names
(headers included),
		> >> >>>>> dashes for all values
		> >> >>>>>
		> >> >>>>> 3. Use underscores throughout
		> >> >>>>>
		> >> >>>>>
		> >> >>>>>
		> >> >>>>> I want to get this done with in a day because
people are
		> >> >>>>> writing code for
		> >> >>>>> -09 and I'd like to stop making changes
beyond editorial.  I
		> >> >>>>> just think that having different styles
between the endpoint
		> >> >>>>> parameters and header parameters is broken.
		> >> >>>>>
		> >> >>>>>
		> >> >>>>>
		> >> >>>>> EHL
		> >> >>>>>
		> >> >>>>>
_______________________________________________
		> >> >>>>> OAuth mailing list
		> >> >>>>> [e-mail]
		> >> >>>>> https://www.ietf.org/mailman/listinfo/oauth
		> >> >>>>>
		> >> >>>>>
		> >> >>>>
		> >> >>>>
		> >> >>>>
		> >> >>>> --
		> >> >>>> http://lukasrosenstock.net/
		> >> >>>>
_______________________________________________
		> >> >>>> OAuth mailing list
		> >> >>>> [e-mail]
		> >> >>>> https://www.ietf.org/mailman/listinfo/oauth
		> >> >>>>
		> >> >>>
		> >> >>>
		> >> >>>
		> >> >>> --
		> >> >>> http://agree2.com - Reach Agreement!
		> >> >>> http://stakeventures.com - My blog about
startups and agile
		> >> >>> banking
		> _______________________________________________
		> >> >>> OAuth mailing list
		> >> >>> [e-mail]
		> >> >>> https://www.ietf.org/mailman/listinfo/oauth
		> >> >>
		> >> >> _______________________________________________
		> >> >> OAuth mailing list
		> >> >> [e-mail]
		> >> >> https://www.ietf.org/mailman/listinfo/oauth
		> >> > _______________________________________________
		> >> > OAuth mailing list
		> >> > [e-mail]
		> >> > https://www.ietf.org/mailman/listinfo/oauth
		> >
		> > _______________________________________________
		> > OAuth mailing list
		> > [e-mail]
		> > https://www.ietf.org/mailman/listinfo/oauth
		> >
		_______________________________________________
		OAuth mailing list
		[e-mail]
		https://www.ietf.org/mailman/listinfo/oauth