Re: [VCARDDAV] KIND in draft 15

Cyrus Daboo <cyrus@daboo.name> Tue, 21 December 2010 16:04 UTC

Return-Path: <cyrus@daboo.name>
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 10F733A6B29 for <vcarddav@core3.amsl.com>; Tue, 21 Dec 2010 08:04:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.272
X-Spam-Level:
X-Spam-Status: No, score=-102.272 tagged_above=-999 required=5 tests=[AWL=-0.273, BAYES_00=-2.599, J_CHICKENPOX_45=0.6, USER_IN_WHITELIST=-100]
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 kvJDLy5xG4iu for <vcarddav@core3.amsl.com>; Tue, 21 Dec 2010 08:04:30 -0800 (PST)
Received: from daboo.name (daboo.name [151.201.22.177]) by core3.amsl.com (Postfix) with ESMTP id 1A5D33A6B0C for <vcarddav@ietf.org>; Tue, 21 Dec 2010 08:04:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id C623E1B0C5739; Tue, 21 Dec 2010 11:06:25 -0500 (EST)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (chewy.mulberrymail.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WhvmWZ5Q6QCQ; Tue, 21 Dec 2010 11:06:24 -0500 (EST)
Received: from [17.101.34.182] (unknown [17.101.34.182]) by daboo.name (Postfix) with ESMTPSA id 14A781B0C572D; Tue, 21 Dec 2010 11:06:23 -0500 (EST)
Date: Tue, 21 Dec 2010 11:06:30 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: jsmarr@stanfordalumni.org, Andy Mabbett <andy@pigsonthewing.org.uk>
Message-ID: <BB98A5C1EA4AA623BDE64DDA@cyrus.local>
In-Reply-To: <AANLkTim28Z2U1dqahuE2gdYvHKHVKc_tc=9DoHDbftYr@mail.gmail.com>
References: <AANLkTikckYf5A0rUZ6k=JN2UZwp+__bBFHndxbfLcEHK@mail.gmail.com> <4D0B6AC9.1080607@viagenie.ca> <4D0B83AE.4060601@stpeter.im> <AANLkTimA-AuKRoOm6ZRmqSTmOBzHkWCah52ezCJCmvVp@mail.gmail.com> <4D0FA8C9.7080201@viagenie.ca> <AANLkTimM2sAX3_4+Y2sBXuUxbWdRxpJ2bLq5Pq12pGOr@mail.gmail.com> <4D0FB317.1050004@viagenie.ca> <AANLkTim-026NEKwmEwHi6hY2BfTunny11q191+9Wdw+g@mail.gmail.com> <5B90C712-865E-4760-ACE4-451B063999C8@opengroupware.org> <9944D1A448E2AEEC76264B1F@cyrus.local> <AANLkTing1mcsJgD+W8+dkg9Sb=SkbfLNagHrYtCujMa2@mail.gmail.com> <5C90ECF3EB063458C5F1692F@cyrus.local> <AANLkTinHUBPF6ECVkwf17_1FB1K=vNbikptUPP=8_dNx@mail.gmail.com> <AANLkTim28Z2U1dqahuE2gdYvHKHVKc_tc=9DoHDbftYr@mail.gmail.com>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline; size="1739"
Cc: vcarddav@ietf.org
Subject: Re: [VCARDDAV] KIND in draft 15
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: Tue, 21 Dec 2010 16:04:31 -0000

Hi Joseph,

--On December 21, 2010 7:55:23 AM -0800 Joseph Smarr <jsmarr@gmail.com> 
wrote:

> Let me just add (at the risk of dragging this thread out any longer) that
> one reason KIND:GROUP is a *bad* idea IMO is that clients who aren't
> aware of it will end up with a "contact" that is not really a "contact",
> so you're kind of polluting the list of vCards. 
>
>
> It's one thing to specify KIND for things like companies or
> autoresponders that really do show up *in* people's address books as
> contacts. You could even do the same for KIND:MAILING-LIST for
> yahoo/google/ietf-group mailing lists with a single address that shows up
> in your contacts. In those cases, if you ignore KIND (as most/all clients
> will do for the foreseeable future, by definition), it doesn't hurt
> you--you thought you had a normal contact, and you do, you're just
> missing some helpful classification information. 
>
>
> But to store contact group metadata in a fake contact and then try to
> "hide" it by saying KIND:GROUP is a very different thing. That's not a
> normal contact, and a client that ignores it will not only miss the
> metadata there, they'll end up with a bogus contact that wasn't in their
> address book before. That seems unacceptable to me, unless I'm missing
> something about the source of these KIND:GROUP contacts.

Well the point is we are expecting vCard v4 clients to understand the 
difference. A client that only knows about vCard v3 in theory will reject 
the v4 cards. Nearly all desktop contacts clients have some concept of a 
group like this, so what v4 is doing is providing them with a way to 
exchange that information as well as individual contacts. I think this 
counts as progress.

-- 
Cyrus Daboo