Re: [VCARDDAV] Miscellaneous comments

Markus Lorenz <lorenz@atlantika-arts.net> Mon, 19 July 2010 22:18 UTC

Return-Path: <lorenz@atlantika-arts.net>
X-Original-To: vcarddav@core3.amsl.com
Delivered-To: vcarddav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3AA533A698C for <vcarddav@core3.amsl.com>; Mon, 19 Jul 2010 15:18:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.457
X-Spam-Level:
X-Spam-Status: No, score=-1.457 tagged_above=-999 required=5 tests=[AWL=0.532, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hMBlxuO5j0Gw for <vcarddav@core3.amsl.com>; Mon, 19 Jul 2010 15:18:25 -0700 (PDT)
Received: from host46.sitepush.net (server20.server-centrum.de [213.239.241.46]) by core3.amsl.com (Postfix) with ESMTP id 18CC83A697F for <vcarddav@ietf.org>; Mon, 19 Jul 2010 15:18:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by host46.sitepush.net (Postfix) with ESMTP id B8E921FA0002 for <vcarddav@ietf.org>; Tue, 20 Jul 2010 00:18:37 +0200 (CEST)
Received: from host46.sitepush.net ([127.0.0.1]) by localhost (server20.server-centrum.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vSX5ZJToYU+Q for <vcarddav@ietf.org>; Tue, 20 Jul 2010 00:18:37 +0200 (CEST)
Received: from [192.168.0.101] (f053154088.adsl.alicedsl.de [78.53.154.88]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by host46.sitepush.net (Postfix) with ESMTP id 6DAD21FA0001 for <vcarddav@ietf.org>; Tue, 20 Jul 2010 00:18:37 +0200 (CEST)
Message-ID: <4C44CF3A.6050902@atlantika-arts.net>
Date: Tue, 20 Jul 2010 00:18:34 +0200
From: Markus Lorenz <lorenz@atlantika-arts.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.4) Gecko/20100608 Lightning/1.0b2 Thunderbird/3.1
MIME-Version: 1.0
To: vcarddav@ietf.org
References: <44A88E2F417F42C98A086014681E5586@Javier2> <4C444698.4080603@viagenie.ca> <6C4A9E5CC56541FCBA403E46E32A4068@Javier2> <AANLkTimFzxZuJC5C-XMuY4kimJ1egXw37FTRvNGtWvnL@mail.gmail.com>
In-Reply-To: <AANLkTimFzxZuJC5C-XMuY4kimJ1egXw37FTRvNGtWvnL@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [VCARDDAV] Miscellaneous comments
X-BeenThere: vcarddav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF vcarddav wg mailing list <vcarddav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 19 Jul 2010 22:18:28 -0000

Am 20.07.2010 00:05, schrieb Daisuke Miyakawa:
> Hi,
> 
> 2010/7/19 Javier Godoy <rjgodoy@fich.unl.edu.ar
> <mailto:rjgodoy@fich.unl.edu.ar>>
> 
>             2. NAME. "The NAME property is used to convey the display
>             name of the
>             entity to which the directory information pertains"
> 
>             Shouldn't the display name be choosen by the implementation?
>             There is
>             already a mandatory FN property from which the display name
>             could be derived.
> 
>             I remember this issue was discussed before, but I cannot
>             find the rationale
>             for not removing the NAME property.
> 
> 
>         We inherited NAME from vCard 3.0
> 
> 
>     NAME is inherited from RFC 2425, thus it should have been intended
>     as a minimal profile-independent representation of the display name
>     (not only for vCard but also for other "directory profiles" that
>     never existed).
> 
> 
>         I, for one, have no clue how it could be useful.
> 
>         Does anyone know how it is being used currently?
> 
> 
>         and I don't think its removal has ever been discussed.
> 
> 
>     I agree it seems we never discussed it, though it was proposed
>     http://www.vcarddav.org/issues.xhtml#176
>     "The NAME (RFC2425) property is redundant with FN (RFC2426)"
>     Closed without action on 2008-06-09
> 
>     And yes, I said "+1" to closing it, but I cannot remember why... now
>     I think we should do something about it.
> 
> 
> +1 to do something. I prefer removing it, but there's no strong preference.
> 
> I think one problem is that the name is too generic. If NAME is "a
> minimal profile-independent representation of the display name", the
> name should not be
> NAME but SHORT-NAME, SN, or something more appropriate. We don't need to
> inherit that name from vCard 3.0, but its intention.

+1 to remove it. If no one knows how to use it, it can't bring any benefit.

What could a SHORT-NAME be used for? I still can't see the intention.
Was the plan to get at least some useful information out of a
mime-directory format even if you don't understand the specific format?
Are there other mime-directory formats than vCard?