[VCARDDAV] Confusion regarding the correct use of FN, N and NICKNAME in RFC6350 with regards to nicknames and honorifics
Gesh hseG <gesh@gesh.uni.cx> Wed, 29 January 2014 00:18 UTC
Return-Path: <gesh@gesh.uni.cx>
X-Original-To: vcarddav@ietfa.amsl.com
Delivered-To: vcarddav@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91BC31A039E for <vcarddav@ietfa.amsl.com>; Tue, 28 Jan 2014 16:18:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.531
X-Spam-Level:
X-Spam-Status: No, score=0.531 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_84=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CRUp8eTrTuPU for <vcarddav@ietfa.amsl.com>; Tue, 28 Jan 2014 16:18:41 -0800 (PST)
Received: from mail-wg0-f47.google.com (mail-wg0-f47.google.com [74.125.82.47]) by ietfa.amsl.com (Postfix) with ESMTP id DE8EC1A043A for <vcarddav@ietf.org>; Tue, 28 Jan 2014 16:18:39 -0800 (PST)
Received: by mail-wg0-f47.google.com with SMTP id m15so2169271wgh.2 for <vcarddav@ietf.org>; Tue, 28 Jan 2014 16:18:36 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=a/SkXNuw3sFln5Uw3DQrLRSSK5N24twRlN6z1gpnP48=; b=WCsl8tEd2f4IMTgyl0ghk7K7yMC2Ib2p7K160rahcb8H6vUSIMcQ7U8/Q7hgdcpXLT /ZcJtcZWwm3FgTBOYqzrtDD5yxndi3pFPeC5HNhsxLtKZ/+WUhonvrRYsxeamaa5Bl+y yZu+Siew8jTklWpVXKXZbD9VgiTGK0tbARsMnJkIUBsLRVrccEAXWDt6W0c3hjZn1Ksj o+9sEdYU4QHCmlbbbNXm+c9aP/fIjvIdVdmql0VpThKUVBLrKOc/L0Ug51R7AbG6nNap jdrYkn2EdtKQ5Z3S7juS2hBcqaAZBZK8Q/qhYeYkVEF85lfw+jvoH29mqD8L3w3FXa60 vibA==
X-Gm-Message-State: ALoCoQkV+bIZorrgRGnELV6iu93iLTIAprh3uhHOSDgbD/nTwpNk2Ld0HG5QbGyuI8e0FBekhA68
X-Received: by 10.194.59.210 with SMTP id b18mr182717wjr.60.1390954716657; Tue, 28 Jan 2014 16:18:36 -0800 (PST)
MIME-Version: 1.0
Received: by 10.180.100.167 with HTTP; Tue, 28 Jan 2014 16:18:16 -0800 (PST)
X-Originating-IP: [109.65.133.119]
From: Gesh hseG <gesh@gesh.uni.cx>
Date: Wed, 29 Jan 2014 02:18:16 +0200
Message-ID: <CACS5XqM=S--v0Wp746oBky3XKkyt6072tQHnFpbJLK2Gu6=iFA@mail.gmail.com>
To: vcarddav@ietf.org
Content-Type: multipart/alternative; boundary="047d7b86df66c90f2204f110e15e"
Subject: [VCARDDAV] Confusion regarding the correct use of FN, N and NICKNAME in RFC6350 with regards to nicknames and honorifics
X-BeenThere: vcarddav@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF vcarddav wg mailing list <vcarddav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vcarddav/>
List-Post: <mailto:vcarddav@ietf.org>
List-Help: <mailto:vcarddav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 00:33:33 -0000
Hello. The correct usage of FN/N/NICKNAME in the following scenario is unclear to me: Suppose I have an acquaintance who is either more or less close to me than the average acquaintance, thus leading to my referring to them using a nickname or honorific, respectively. Then it appears that in a vCard referring to them, I should specify their full name in FN, their name broken down into components in N, and the name by which I refer to them in NICKNAME. In addition, assuming I wish for this person to be sorted by the referring name, I should set the SORT-AS parameter of N to the value of NICKNAME. Thus: FN:Mr. John Joe Doe\, MSc N;SORT-AS="Dad":Doe;John;Joe;Mr.;MSc NICKNAME:Dad FN:Lady Jane Dale N;SORT-AS="Lady Dale":Dale;Jane;;Lady; NICKNAME:Lady Dale FN:Jeff Lebowski N;SORT-AS="The Dude":Lebowski;Jeff;;; NICKNAME:The Dude However, this reading means the property names do not reflect their use (FN, N, and NICKNAME should instead be called Full Name, Name Components, Common Name, respectively), and causes the duplication of data (the value of SORT-AS and NICKNAME is duplicated). In addition, it is unclear what name should be used by an application to refer to a person. As far as I can tell, preferably, one would use FN to signify the regionally-correct concatenation of the components of N. Both of these would refer to the full legal name of the person in question. Any personal appellations that one has for the person in question would be given by NICKNAME. These appellations would be used by applications to label and sort the person. Of course, he application may permit the usage of FN, Last Name, First Name or First Name, Last Name as the appellation by which a person is labeled and sorted. However, the default behavior would be to use NICKNAME. This has the benefit of allowing people to supply vCards which would then need to be only minimally modified by their acquaintances - just enough to have the vCard use the name those acquaintances use to label those people,. Thus, John Joe Doe from the example above would give the same vCard, who would then insert a line causing him to be referred to as "Boss", "Dad", "Kid", etc. In brief, assuming I refer to a person by a name that is not their full name, how do I A) correctly note this in their vCard, B) write a standards-conforming program that displays and sorts the person the same way I refer to them? Thank you in advance, Gesh
- [VCARDDAV] Confusion regarding the correct use of… Gesh hseG
- Re: [VCARDDAV] Confusion regarding the correct us… Cyrus Daboo
- Re: [VCARDDAV] Confusion regarding the correct us… Gesh
- Re: [VCARDDAV] Confusion regarding the correct us… Thomas Tanghus
- Re: [VCARDDAV] Confusion regarding the correct us… Simon Perreault
- Re: [VCARDDAV] Confusion regarding the correct us… Renato Iannella
- Re: [VCARDDAV] Confusion regarding the correct us… Renato Iannella