Having two ways to do something almost always hurts interop and always makes implementations bigger
From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf Of Craig McClanahan Sent: Wednesday, January 30, 2013 2:48 PM To: Justin Richer Cc: IETF oauth WG Subject: Re: [OAUTH-WG] draft-richer-oauth-introspection-01 scope syntax On Wed, Jan 30, 2013 at 2:29 PM, Justin Richer <jric...@mitre.org<mailto:jric...@mitre.org>> wrote: We could fairly easily define it as the same space-delimited string if enough people want to keep the scope format consistent. Can't we have our cake and eat it too, and accept either syntax? JSON makes it pretty easy to introspect what's there and deal with either version appropriately. I am one of those that finds the array version of things like this more convenient, but for the folks who are used to dealing with the space-delimited string version of scopes, we could easily support that too. -- Justin Craig McClanahan
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
