IETF Logo Mail Archive

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

Gesh <gesh@gesh.uni.cx> Wed, 29 January 2014 10:55 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 C274B1A01FB for <vcarddav@ietfa.amsl.com>; Wed, 29 Jan 2014 02:55:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 L7MBLv3phEkz for <vcarddav@ietfa.amsl.com>; Wed, 29 Jan 2014 02:55:14 -0800 (PST)
Received: from mail-ea0-f169.google.com (mail-ea0-f169.google.com [209.85.215.169]) by ietfa.amsl.com (Postfix) with ESMTP id D4B891A0188 for <vcarddav@ietf.org>; Wed, 29 Jan 2014 02:55:13 -0800 (PST)
Received: by mail-ea0-f169.google.com with SMTP id h10so829398eak.28 for <vcarddav@ietf.org>; Wed, 29 Jan 2014 02:55:10 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:subject:from:to:cc:mime-version :content-type:content-transfer-encoding; bh=qTEsg17tgPry6DFtzQ2h5ubjl9Qx8g0X/JNDI3l3JcE=; b=W/qGxaBXNTfmw36I1yEDiFIVgDTDZr+33tnoxUg2oI8Lno6yjiCOHwimF4U+tzUte2 hQv5yQIvZDfwy2g0cU8+GES26V1xdUgkceUHgHJpwRocQeJ9APJ1og3+yqEkdO2dmmg9 gv1YELAoTAjbj8R7sxd7o7N4XBoYyZ8ffLP0+sxBJy88vfd/v6DRaT1qipVwl0ac25w6 GRar2yOVIVZZrthiqNwZRTfqvecLlnQihHoMVgaX/tN/4YNSx4SytiQulwoaZpVF4Pcl OzT9z01ena6LpX6B8yfx8S/+aqUHnCqYZJdVysy1Umy5pQwfVSKFcizr6fC36CK1TFu7 6v5g==
X-Gm-Message-State: ALoCoQl7tRp5Wvlz4ebiKB+yiPgQxDFnQbCztdNAIB+FKXYiUWGUyFM9v6acqrR1vO8a4SeuYKWf
X-Received: by 10.14.102.67 with SMTP id c43mr8574482eeg.23.1390992909217; Wed, 29 Jan 2014 02:55:09 -0800 (PST)
Received: from [10.0.0.4] (bzq-79-179-136-156.red.bezeqint.net. [79.179.136.156]) by mx.google.com with ESMTPSA id v7sm7065398eel.2.2014.01.29.02.55.07 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 29 Jan 2014 02:55:08 -0800 (PST)
Message-ID: <52e8de0c.87ad0e0a.1e97.49c5@mx.google.com>
Date: Wed, 29 Jan 2014 12:54:52 +0200
From: Gesh <gesh@gesh.uni.cx>
To: Cyrus Daboo <cyrus@daboo.name>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Cc: vcarddav@ietf.org
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: Wed, 29 Jan 2014 10:55:16 -0000

On Jan 28, 2014 11:54 PM, Cyrus Daboo <cyrus@daboo.name> wrote:
> It seems that what you need is a client sort option that uses as the sort 
> key the NICKNAME value if present, else the FN value (using any SORT-AS 
> parameter specified for the selected property). If you do that, there is no 
> need to add the N value as a SORT-AS on the FN value as you did in your 
> examples. 
>
> -- 
> Cyrus Daboo 
>
Thank you. So basically, the alternative names I gave to
FN, N and NICKNAME (Full Name, Name Components and
Common Name, respectively) are correct synonyms?
And a standards-compliant program should understand
this and allow for labeling and sorting on the NICKNAME
property?
Thank you for your time,
Gesh

v2.23.0 | Report a Bug | By Email