Is there a problem with sticking to UTF-8? OAuth already mandates JSON which is Unicode only.
Would be nice to keep it simple. I'm guessing without guidance, most would convert to UTF-8 and percent encode anyway. On May 18, 2011, at 1:32 PM, Julian Reschke wrote: > On 2011-05-18 22:25, Kris Selden wrote: >> How about taking a page from URI spec since it is a query parameter value >> and follow this for the value of such human readable text params: >> >> When a new URI scheme defines a component that represents textual >> data consisting of characters from the Universal Character Set [UCS], >> the data should first be encoded as octets according to the UTF-8 >> character encoding [STD63]; then only those octets that do not >> correspond to characters in the unreserved set should be percent- >> encoded. >> >> http://tools.ietf.org/html/rfc3986 >> ... > > ...which yields almost the same representation as RFC2231/5987 (except that > in these, the string gets labeled with the charset name). > > Best regards, Julian _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
