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 That is also inline with JSON as the one OAuth response type, since it is already limited to UTF encodings. On May 18, 2011, at 9:20 AM, Eran Hammer-Lahav wrote: > The error_description parameter and similar parameters in the MAC and Bearer > specs do not specify the language or encoding used. This is a problem. Can > someone offer a solution? > > EHL > _______________________________________________ > OAuth mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/oauth _______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
