[VCARDDAV] CardDAV: UID property

Bernard Desruisseaux <bernard.desruisseaux@oracle.com> Fri, 04 September 2009 13:25 UTC

Return-Path: <bernard.desruisseaux@oracle.com>
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 0477F3A6837 for <vcarddav@core3.amsl.com>; Fri, 4 Sep 2009 06:25:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.908
X-Spam-Level:
X-Spam-Status: No, score=-4.908 tagged_above=-999 required=5 tests=[AWL=-0.724, BAYES_40=-0.185, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 CnPIZJcor5B6 for <vcarddav@core3.amsl.com>; Fri, 4 Sep 2009 06:25:03 -0700 (PDT)
Received: from acsinet12.oracle.com (acsinet12.oracle.com [141.146.126.234]) by core3.amsl.com (Postfix) with ESMTP id 341B83A677E for <vcarddav@ietf.org>; Fri, 4 Sep 2009 06:25:03 -0700 (PDT)
Received: from acsinet13.oracle.com (acsinet13.oracle.com [141.146.126.235]) by acsinet12.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n84DNcEu008708 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <vcarddav@ietf.org>; Fri, 4 Sep 2009 13:23:39 GMT
Received: from hqdfmt02.oracle.com (hqdfmt02.oracle.com [148.87.24.195]) by acsinet13.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n84DP0ul019670 for <vcarddav@ietf.org>; Fri, 4 Sep 2009 13:25:02 GMT
Received: from [10.156.43.80] (/10.156.43.80) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 04 Sep 2009 06:24:11 -0700
Message-ID: <4AA114FA.3040609@oracle.com>
Date: Fri, 04 Sep 2009 09:24:10 -0400
From: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: CardDAV <vcarddav@ietf.org>
Content-Type: multipart/alternative; boundary="------------000304020006060009060504"
X-Source-IP: hqdfmt02.oracle.com [148.87.24.195]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090204.4AA114FF.0172,ss=1,fgs=0
Subject: [VCARDDAV] CardDAV: UID property
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: Fri, 04 Sep 2009 13:25:04 -0000

Hi,

If I'm not mistaken the presence of the UID property in a vCard is a 
CardDAV requirement and not a vCard requirement.

I don't believe the CardDAV draft makes this clear.  I can't find a MUST 
requirement about the presence of UID.

A new precondition (e.g., CARDDAV:valid-addressbook-object-resource) 
should be added for invalid vCard (per CardDAV spec). My understanding 
is that CARDDAV:valid-address-data should be used for invalid vCard (per 
vCard spec).

Also, Section 10.4 leads one to believe that vCard actually requires the 
UID property:

    Furthermore, address object resources specified in the CARDDAV:
    address-data XML element MAY be invalid per their media type
    specification if the CARDAV:address-data XML element part of the
    address book REPORT request did not specify required vCard
    properties (e.g., UID, etc.) 

Cheers,
Bernard