Re: [OAUTH-WG] Registration: Internationalization of Human-Readable names
Brian Campbell <bcampbell@pingidentity.com> Mon, 11 March 2013 22:36 UTC
Return-Path: <bcampbell@pingidentity.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 136C321F8FCC for <oauth@ietfa.amsl.com>; Mon, 11 Mar 2013 15:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.807
X-Spam-Level:
X-Spam-Status: No, score=-4.807 tagged_above=-999 required=5 tests=[AWL=-0.584, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R8EIqnZh8+qJ for <oauth@ietfa.amsl.com>; Mon, 11 Mar 2013 15:36:09 -0700 (PDT)
Received: from na3sys009aog111.obsmtp.com (na3sys009aog111.obsmtp.com [74.125.149.205]) by ietfa.amsl.com (Postfix) with ESMTP id D5CC221F8F52 for <oauth@ietf.org>; Mon, 11 Mar 2013 15:36:08 -0700 (PDT)
Received: from mail-ia0-f200.google.com ([209.85.210.200]) (using TLSv1) by na3sys009aob111.postini.com ([74.125.148.12]) with SMTP ID DSNKUT5cWB35opJJyFfNO5dvuB1GCPdSader@postini.com; Mon, 11 Mar 2013 15:36:08 PDT
Received: by mail-ia0-f200.google.com with SMTP id k38so9575017iah.3 for <oauth@ietf.org>; Mon, 11 Mar 2013 15:36:08 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:x-received:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:x-gm-message-state; bh=NL1qELeO2cAR/ELMH8O5cNdc6QlhuMZVo3IfNmbD1Pc=; b=BK4BP3Mm1hZBgSTTfKwmOGBmUu9FpIvgrh3Uh7zzCT5/AYlw+U4twQWrqtv03GX2n6 AWHhYA6JJV8njoiUkbSvUhFgVbvL1K/d4CR51veTAbd8mh9bSLebOn7Dy7MNVpO6NQmJ nhX9mh9Lh0Py0K+YVD7nNsaHN31svPj8D8/yEefFQqENRIMBYH4G7jZjPzYf4UVRW2mT HAvg/A0M9kRlrFEholyjFSq7N3A+MeSoSWlx/1Y3CcXeV4P9v9z8WW2RMsspiqtEzM/5 Vw+HxTvmk0BE4+miocxdT8RhAvjlSOt5ITANayiio3Jsqza0Ho3v3ppKAKF9JTT0Zkn/ hfMQ==
X-Received: by 10.42.30.132 with SMTP id v4mr10249853icc.34.1363041368199; Mon, 11 Mar 2013 15:36:08 -0700 (PDT)
X-Received: by 10.42.30.132 with SMTP id v4mr10249849icc.34.1363041368078; Mon, 11 Mar 2013 15:36:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.32.106 with HTTP; Mon, 11 Mar 2013 15:35:37 -0700 (PDT)
In-Reply-To: <B33BFB58CCC8BE4998958016839DE27E08F3EEB3@IMCMBX01.MITRE.ORG>
References: <B33BFB58CCC8BE4998958016839DE27E08F3EDDF@IMCMBX01.MITRE.ORG> <CA+k3eCSMrt=eAxisUdRF3J49gdErwpu74FarvDorBbbQqZpSQQ@mail.gmail.com> <1B4C0C9F-4B8E-4B2D-BAF7-665D3EBBE56C@ve7jtb.com> <B33BFB58CCC8BE4998958016839DE27E08F3EEB3@IMCMBX01.MITRE.ORG>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Mon, 11 Mar 2013 18:35:37 -0400
Message-ID: <CA+k3eCTR9ch7A2g9AG_7goRodyPu3FYNSeUH5XHQttP+6_MqMw@mail.gmail.com>
To: "Richer, Justin P." <jricher@mitre.org>
Content-Type: multipart/alternative; boundary="20cf301d420e8f196604d7adcc2b"
X-Gm-Message-State: ALoCoQmWEkOGvdudlNBZi4YvXJlo/ktSEgl+/3de37j7HTfOz0SbGshIygO9x5gfHQd7Pzt0iLdbf3WX/yuLH36qTZMUBukTOQzUeFn4kBH1LoY1LKHOd2EOtxcHad8LWQ83KVS1dWsM
Cc: "oauth@ietf.org WG" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Registration: Internationalization of Human-Readable names
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2013 22:36:11 -0000
A fair question but what would need to be pulled in is really probably only a couple sentences (and reference) from http://openid.net/specs/openid-connect-messages-1_0-16.html#ClaimsLanguagesAndScripts(note the reference to 2.1.1.1.3 inside http://openid.net/specs/openid-connect-registration-1_0-15.html is broken) On Mon, Mar 11, 2013 at 6:26 PM, Richer, Justin P. <jricher@mitre.org>wrote: > My concern with this is that OIDC can get away with defining this > multi-language structure because it defines the mechanism once (in > Messages) and applies it to all user-readable strings throughout the whole > application protocol, of which there are several. Do we really want to pull > in that whole structure and mechanism for one field in client registration? > I really don't think it should be something that's defined completely > inside of DynReg for a corner case for a single field, but I also doubt we > want to normatively point to OIDC Messages for this solution either. > > There are also other ways to do this: Webfinger [1] for instance uses > JSON structures to give language tags to field values, and has a default > mechanism: > > { "en_us": "my client", … } > > The fundamental question is this: should a client be able to register > multiple names (in different locales) with a single client_id, or should it > get a different client_id for each display language set? > > -- Justin > > [1] http://tools.ietf.org/html/draft-ietf-appsawg-webfinger-11 > > On Mar 11, 2013, at 5:54 PM, John Bradley <ve7jtb@ve7jtb.com> > wrote: > > 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 <bcampbell@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-metadataand the examples. > > > "client_name": "My Example", > "client_name#ja-Jpan-JP":"クライアント名", > > > > > On Mon, Mar 11, 2013 at 5:15 PM, Richer, Justin P. <jricher@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 > > > >
- [OAUTH-WG] Registration: Internationalization of … Richer, Justin P.
- Re: [OAUTH-WG] Registration: Internationalization… Brian Campbell
- Re: [OAUTH-WG] Registration: Internationalization… Nat Sakimura
- Re: [OAUTH-WG] Registration: Internationalization… John Bradley
- Re: [OAUTH-WG] Registration: Internationalization… Richer, Justin P.
- Re: [OAUTH-WG] Registration: Internationalization… Brian Campbell
- Re: [OAUTH-WG] Registration: Internationalization… Richer, Justin P.
- Re: [OAUTH-WG] Registration: Internationalization… Nat Sakimura
- Re: [OAUTH-WG] Registration: Internationalization… Justin Richer
- Re: [OAUTH-WG] Registration: Internationalization… Brian Campbell
- Re: [OAUTH-WG] Registration: Internationalization… George Fletcher
- Re: [OAUTH-WG] Registration: Internationalization… Justin Richer
- Re: [OAUTH-WG] Registration: Internationalization… Mike Jones
- Re: [OAUTH-WG] Registration: Internationalization… Justin Richer
- Re: [OAUTH-WG] Registration: Internationalization… Mike Jones
- Re: [OAUTH-WG] Registration: Internationalization… Justin Richer
- Re: [OAUTH-WG] Registration: Internationalization… Mike Jones
- Re: [OAUTH-WG] Registration: Internationalization… Justin Richer
- Re: [OAUTH-WG] Registration: Internationalization… Mike Jones
- Re: [OAUTH-WG] Registration: Internationalization… Justin Richer
- Re: [OAUTH-WG] Registration: Internationalization… Nat Sakimura
- Re: [OAUTH-WG] Registration: Internationalization… Nat Sakimura
- Re: [OAUTH-WG] Registration: Internationalization… Manger, James H
- Re: [OAUTH-WG] Registration: Internationalization… Justin Richer
- Re: [OAUTH-WG] Registration: Internationalization… Justin Richer
- Re: [OAUTH-WG] Registration: Internationalization… Mike Jones
- Re: [OAUTH-WG] Registration: Internationalization… SM
- Re: [OAUTH-WG] Registration: Internationalization… Peter Saint-Andre
- Re: [OAUTH-WG] Registration: Internationalization… Peter Saint-Andre
- Re: [OAUTH-WG] Registration: Internationalization… Peter Saint-Andre
- Re: [OAUTH-WG] Registration: Internationalization… Mike Jones