Re: [VCARDDAV] review of draft-cauchie-vcarddav-oma-cab-extensions
Cyrus Daboo <cyrus@daboo.name> Thu, 23 June 2011 14:37 UTC
Return-Path: <cyrus@daboo.name>
X-Original-To: vcarddav@ietfa.amsl.com
Delivered-To: vcarddav@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D66711E80B1 for <vcarddav@ietfa.amsl.com>; Thu, 23 Jun 2011 07:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZOSzs-F+r1Br for <vcarddav@ietfa.amsl.com>; Thu, 23 Jun 2011 07:37:46 -0700 (PDT)
Received: from daboo.name (daboo.name [151.201.22.177]) by ietfa.amsl.com (Postfix) with ESMTP id 431EE11E80A5 for <vcarddav@ietf.org>; Thu, 23 Jun 2011 07:37:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 8A148102D104; Thu, 23 Jun 2011 10:37:45 -0400 (EDT)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (chewy.daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gOt0uastR4O5; Thu, 23 Jun 2011 10:37:40 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 71EB6102D0F7; Thu, 23 Jun 2011 10:37:38 -0400 (EDT)
Date: Thu, 23 Jun 2011 10:37:34 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: CardDAV <vcarddav@ietf.org>
Message-ID: <29C874D62F4B84B9566D05A3@caldav.corp.apple.com>
In-Reply-To: <4E026E3D.2040306@stpeter.im>
References: <4E026E3D.2040306@stpeter.im>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size="1192"
Subject: Re: [VCARDDAV] review of draft-cauchie-vcarddav-oma-cab-extensions
X-BeenThere: vcarddav@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 23 Jun 2011 14:37:47 -0000
Hi , --On June 22, 2011 4:35:41 PM -0600 Peter Saint-Andre <stpeter@stpeter.im> wrote: > 4. SERVICE seems somewhat underspecified; in particular the "label" is > just a free-form name for the service, but it seems that different > people might call the same service by different names, leading to > confusion (e.g., "facebook" vs. "FaceBook", "Google" vs. "Gmail" vs. > "Google Talk"). WRT SERVICE I would like to draw people's attention to <http://tools.ietf.org/id/draft-daboo-vcard-service-type-00.txt> (which is now expired). This takes a different approach of defining a SERVICE-TYPE parameter for use on existing properties such as EMAIL and IM. This allow those communications properties to be "tagged" with the service provider identifier. I wonder whether instead of SERVICE we should be using the existing vCard URL property combined with SERVICE-TYPE. The existing property already states "social networking site identifiers" as one possible use case. I realize this might make it a little bit harder to do a simple one-to-one mapping with OMA attributes, but I do think we should try and re-use existing vCard properties where ever it makes sense. -- Cyrus Daboo
- Re: [VCARDDAV] review of draft-cauchie-vcarddav-o… Cyrus Daboo
- [VCARDDAV] review of draft-cauchie-vcarddav-oma-c… Peter Saint-Andre
- Re: [VCARDDAV] review of draft-cauchie-vcarddav-o… Likepeng
- Re: [VCARDDAV] review of draft-cauchie-vcarddav-o… Simon Perreault