Re: [scim] Name Internationalization

Tatsuo Kudo <tatsuo.kudo@gmail.com> Mon, 25 March 2013 15:46 UTC

Return-Path: <tatsuo.kudo@gmail.com>
X-Original-To: scim@ietfa.amsl.com
Delivered-To: scim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72E2D21F8D24 for <scim@ietfa.amsl.com>; Mon, 25 Mar 2013 08:46:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 q7tWKWcYirRw for <scim@ietfa.amsl.com>; Mon, 25 Mar 2013 08:46:09 -0700 (PDT)
Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 10D6E21F8C97 for <scim@ietf.org>; Mon, 25 Mar 2013 08:46:05 -0700 (PDT)
Received: by mail-la0-f52.google.com with SMTP id fs12so11573047lab.39 for <scim@ietf.org>; Mon, 25 Mar 2013 08:46:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=RfQRJd1STM/wUzvpWwrubq2XEsq9e92y0IrPYex2q8Y=; b=A15znOaBAgkd09fSmabP5M4KRfl7a7acR2+StfC99ZQy0PcIFxbSry8y96hf1BeiKg CyBnfq6uqIhDy7gHEL43tIaFn0GqZbNvWfPjPLafphGRi2aqZnhotjM8QsKIGdKTuWA7 GD+6YA9ucG9DQaBgvHhusxX8QzXnaFHQUql9dslDZX/oOHSUNa2zqKHsslaZwI6Uz7Jv q8nFURDFEILkZu6ltgb7rWdB/YcE52sQO6s6ZEWSqVoAKg5K+hBQxvS8/iw3i4XLjOLW sZ8jPYLOAapw9BsxlwJKvTuEjXGmjp+oz6PeOTw/89jbzyFj7W/A7iYZlCTFBXENzEuS MhOg==
X-Received: by 10.112.39.138 with SMTP id p10mr6359530lbk.31.1364226364926; Mon, 25 Mar 2013 08:46:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.3.163 with HTTP; Mon, 25 Mar 2013 08:45:44 -0700 (PDT)
In-Reply-To: <46A1DF3F04371240B504290A071B4DB63D688951@szxeml558-mbx.china.huawei.com>
References: <CAGUsYPwE4JCm-zsmWqNaXPHaLGGL_22jCE+uWneT7W3Fb5b2Hw@mail.gmail.com> <A37D572D-A5A4-4BD8-82DD-0B71107C9B6D@viagenie.ca> <46A1DF3F04371240B504290A071B4DB63D688951@szxeml558-mbx.china.huawei.com>
From: Tatsuo Kudo <tatsuo.kudo@gmail.com>
Date: Tue, 26 Mar 2013 00:45:44 +0900
Message-ID: <CAG-hk4gp85BEGRgRYpj_YgYzas1J0ewtkwq7B1haNLC6NTmrQg@mail.gmail.com>
To: Bert Greevenbosch <Bert.Greevenbosch@huawei.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>, Shelley <randomshelley@gmail.com>, "scim@ietf.org" <scim@ietf.org>
Subject: Re: [scim] Name Internationalization
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Simple Cloud Identity Management BOF <scim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/scim>, <mailto:scim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/scim>
List-Post: <mailto:scim@ietf.org>
List-Help: <mailto:scim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/scim>, <mailto:scim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Mar 2013 15:46:10 -0000

I think most of attributes currently defined as "Singular Attributes"
in the schema draft should allow multi-valued ones as well for
non-English environment.  For example, businesses in Japan usually
store Kanji and Kana characters (cf.
http://en.wikipedia.org/wiki/Japanese_writing_system) for almost all
attributes from name to department.

I prefer Kelly Grizzle's suggestion in his follow-up to my question last month.

 http://www.ietf.org/mail-archive/web/scim/current/msg00926.html

And would like to apply it other than phonetic representation like:

"displayName": [
    { "value": "<Kana characters>", "locale": "ja-kana-JP" },
    { "value": "<Kanji characters>", "locale": "ja-JP" }
  ]

Thoughts?

Tatsuo.


On Mon, Mar 25, 2013 at 2:41 PM, Bert Greevenbosch
<Bert.Greevenbosch@huawei.com> wrote:
> I stumbled across the same issue when doing v02 of the SCIM/vCard mapping
> draft. See section 6.
>
> http://datatracker.ietf.org/doc/draft-greevenbosch-scim-vcard-mapping/
>
>
>
> Indeed in vCard multiple surnames, given names and additional names are
> possible.
>
>
>
> Best regards,
>
> Bert
>
>
>
> From: scim-bounces@ietf.org [mailto:scim-bounces@ietf.org] On Behalf Of Marc
> Blanchet
> Sent: 2013年3月25日 6:35
> To: Shelley
> Cc: scim@ietf.org
> Subject: Re: [scim] Name Internationalization
>
>
>
> might want to look at vCard  (RFC6350).
>
>
>
> Marc.
>
>
>
> Le 2013-03-22 à 22:59, Shelley <randomshelley@gmail.com> a écrit :
>
>
>
> As a SCIM service provider, we are trying to determine the best approach for
> accepting and managing names that may be federated from global consumers.
>
> Were there any considerations made in the SCIM core schema for using
> multi-valued attributes for the individual name components? The use of the
> "familyName" and "givenName" as opposed to "firstName"/"lastName" helps
> minimize a western/US-centric approach, but using three individual, singular
> attributes for these name components still hints at a particular name format
> that may not be global.
>
> For example, in many countries, individuals have a given name and two last
> names (rather than first name, middle name, last name). Does SCIM provide
> any recommendations for how to represent this using the existing name
> components? For example, are consumers expected to consolidate all last
> names into the single familyName attribute to accommodate this scenario?
> Likewise, there are many other cases [1,2] that don't quite cleanly fit into
> these singular name components.
>
> The "formattedName", "displayName", and "nickName" attributes help to
> mitigate some concerns around formatting names and addressing users, but
> we're still trying to iron out how to accept identity data from varying
> contributing sources as well as enable consumers to obtain the discrete name
> components.
>
> [1] http://www.w3.org/International/questions/qa-personal-names
> [2] http://en.wikipedia.org/wiki/Personal_name
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim
>
>
>
>
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim
>