Re: [scim] Name Internationalization
Bert Greevenbosch <Bert.Greevenbosch@huawei.com> Mon, 25 March 2013 05:41 UTC
Return-Path: <Bert.Greevenbosch@huawei.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 2E20521F8E4D for <scim@ietfa.amsl.com>; Sun, 24 Mar 2013 22:41:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.247
X-Spam-Level: *
X-Spam-Status: No, score=1.247 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, MIME_BASE64_TEXT=2.796, MIME_CHARSET_FARAWAY=2.45, 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 zmlkL1Z7nBiI for <scim@ietfa.amsl.com>; Sun, 24 Mar 2013 22:41:11 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5D1F721F8E69 for <scim@ietf.org>; Sun, 24 Mar 2013 22:41:10 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APT30696; Mon, 25 Mar 2013 05:41:09 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 25 Mar 2013 05:40:53 +0000
Received: from SZXEML406-HUB.china.huawei.com (10.82.67.93) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 25 Mar 2013 13:41:05 +0800
Received: from szxeml558-mbx.china.huawei.com ([169.254.7.185]) by szxeml406-hub.china.huawei.com ([10.82.67.93]) with mapi id 14.01.0323.007; Mon, 25 Mar 2013 13:41:00 +0800
From: Bert Greevenbosch <Bert.Greevenbosch@huawei.com>
To: Marc Blanchet <marc.blanchet@viagenie.ca>, Shelley <randomshelley@gmail.com>
Thread-Topic: [scim] Name Internationalization
Thread-Index: AQHOJ3KFy727VUoVnEmlhNc7iCT2rJi06r4AgAD7whA=
Date: Mon, 25 Mar 2013 05:41:00 +0000
Message-ID: <46A1DF3F04371240B504290A071B4DB63D688951@szxeml558-mbx.china.huawei.com>
References: <CAGUsYPwE4JCm-zsmWqNaXPHaLGGL_22jCE+uWneT7W3Fb5b2Hw@mail.gmail.com> <A37D572D-A5A4-4BD8-82DD-0B71107C9B6D@viagenie.ca>
In-Reply-To: <A37D572D-A5A4-4BD8-82DD-0B71107C9B6D@viagenie.ca>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.162.63]
Content-Type: multipart/alternative; boundary="_000_46A1DF3F04371240B504290A071B4DB63D688951szxeml558mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "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 05:41:12 -0000
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<mailto: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<mailto:scim@ietf.org> https://www.ietf.org/mailman/listinfo/scim
- [scim] Name Internationalization Shelley
- Re: [scim] Name Internationalization Marc Blanchet
- Re: [scim] Name Internationalization Bert Greevenbosch
- Re: [scim] Name Internationalization Tom Scavo
- Re: [scim] Name Internationalization Tatsuo Kudo
- Re: [scim] Name Internationalization Shelley
- Re: [scim] Name Internationalization 関森信之
- Re: [scim] Name Internationalization Erik Wahlström
- Re: [scim] Name Internationalization Bert Greevenbosch
- Re: [scim] Name Internationalization Kelly Grizzle
- Re: [scim] Name Internationalization Nobuyuki Sekimori
- Re: [scim] Name Internationalization n-sakimura