That is what I was thinking. It would be up to the AS to determine what language and script to present based on the user preference.
While a large number of clients will be native and might be able to customize themselves for a single user during registration , we don't want to forget the web server clients that are multi user. On 2013-03-11, at 10:49 PM, Brian Campbell <bcampb...@pingidentity.com> wrote: > FWIW, the closely related OpenID Connect client registration draft does have > some support for doing this, which could maybe be borrowed. See client_name > in §2 at > http://openid.net/specs/openid-connect-registration-1_0-15.html#client-metadata > and the examples. > > "client_name": "My Example", > "client_name#ja-Jpan-JP":"クライアント名", > > > > On Mon, Mar 11, 2013 at 5:15 PM, Richer, Justin P. <jric...@mitre.org> wrote: > It was brought up at the in-person meeting today that we'll want to consider > issues around internationalization and localization of human-readable fields > like client_name in the client registration. Which is to say: if a client > supports ten languages and wants to present itself in ten languages, should > it have to register itself ten times with an AS? > > At the moment, I'm of the opinion a client with ten languages could register > itself ten times, or do something with the context in which it runs to > determine which human-facing language to use. Keep in mind that in some cases > (such as native clients), you'll be dynamically registering a client for each > user, in effect. In other words, I personally think that this is a rathole > that will cause more harm than good. > > -- Justin > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
