IETF Logo Mail Archive

Re: [VCARDDAV] Confusion regarding the correct use of FN, N and NICKNAME in RFC6350 with regards to nicknames and honorifics

Renato Iannella <ri@semanticidentity.com> Fri, 31 January 2014 01:36 UTC

Return-Path: <ri@semanticidentity.com>
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 9E7051A051E for <vcarddav@ietfa.amsl.com>; Thu, 30 Jan 2014 17:36:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.599
X-Spam-Level:
X-Spam-Status: No, score=0.599 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, J_CHICKENPOX_84=0.6] 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 KxayNQXFpFfo for <vcarddav@ietfa.amsl.com>; Thu, 30 Jan 2014 17:36:41 -0800 (PST)
Received: from cp31.ezyreg.com (cp31.ezyreg.com [202.191.62.219]) by ietfa.amsl.com (Postfix) with ESMTP id 063E31A051A for <vcarddav@ietf.org>; Thu, 30 Jan 2014 17:36:40 -0800 (PST)
Received: from c211-31-36-79.rochd5.qld.optusnet.com.au ([211.31.36.79]:55130 helo=[192.168.1.9]) by cp31.ezyreg.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1) (envelope-from <ri@semanticidentity.com>) id 1W931y-002HiO-Vr for vcarddav@ietf.org; Fri, 31 Jan 2014 12:36:36 +1100
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Renato Iannella <ri@semanticidentity.com>
In-Reply-To: <1697636.22izYpbot2@tanghus-laptop>
Date: Fri, 31 Jan 2014 11:36:34 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <2641774C-0F12-40F4-895B-58090CBC8FC2@semanticidentity.com>
References: <CACS5XqM=S--v0Wp746oBky3XKkyt6072tQHnFpbJLK2Gu6=iFA@mail.gmail.com> <BBD6BBCDA4FB468FCBB3024D@cyrus.local> <1697636.22izYpbot2@tanghus-laptop>
To: vcarddav@ietf.org
X-Mailer: Apple Mail (2.1827)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cp31.ezyreg.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - semanticidentity.com
X-Get-Message-Sender-Via: cp31.ezyreg.com: authenticated_id: ri@semanticidentity.com
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: Re: [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: Fri, 31 Jan 2014 01:36:43 -0000

On 30 Jan 2014, at 12:53, Thomas Tanghus <thomas@tanghus.net> wrote:

> Both specs call it (briefly said) "formatted name", which I see as the way you 
> would want the name formatted if you for example wanted to send an email to 
> said person.
> 
> Say you have a vCard with:
>   N:Public;John;Quinlan;Sir;Esquire
> The FN *could* be:
>   FN:John Q. Public
> And the NICKNAME maybe:
>   NICKNAME:Joey

All 3 properties are semantically independent - that is - you cant assume any part of N must/should/could be in FN, let alone NICKNAME.

The confusion is from N/FN having "name of the object" in their definitions.

In practice, I think, FN is more like the "common name" of the object and FN is more the "formal structured name".

Cheers...
Renato Iannella
Semantic Identity
http://semanticidentity.com
Mobile: +61 4 1313 2206

v2.27.8 | Report a Bug | By Email | System Status