Re: [VCARDDAV] CardDAV + xCard in query response

Cyrus Daboo <cyrus@daboo.name> Mon, 13 June 2011 19:11 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 B2A521F0C64 for <vcarddav@ietfa.amsl.com>; Mon, 13 Jun 2011 12:11:17 -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=[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 cgOKvM-hWdne for <vcarddav@ietfa.amsl.com>; Mon, 13 Jun 2011 12:11:17 -0700 (PDT)
Received: from daboo.name (daboo.name [151.201.22.177]) by ietfa.amsl.com (Postfix) with ESMTP id AFCAA1F0C58 for <vcarddav@ietf.org>; Mon, 13 Jun 2011 12:11:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 1E8C6E2F12E; Mon, 13 Jun 2011 15:11:16 -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 OMX0046dzt-9; Mon, 13 Jun 2011 15:11:11 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id B5C55E2F11B; Mon, 13 Jun 2011 15:11:10 -0400 (EDT)
Date: Mon, 13 Jun 2011 15:11:07 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Simon Perreault <simon.perreault@viagenie.ca>, vcarddav@ietf.org
Message-ID: <A93F91D639EB4D5B16840D2E@caldav.corp.apple.com>
In-Reply-To: <4DF65BC9.7050306@viagenie.ca>
References: <4DE03A77.6030801@quillaud.org> <4DF65BC9.7050306@viagenie.ca>
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="1223"
Subject: Re: [VCARDDAV] CardDAV + xCard in query response
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: Mon, 13 Jun 2011 19:11:17 -0000

Hi Simon,

--On June 13, 2011 2:49:45 PM -0400 Simon Perreault 
<simon.perreault@viagenie.ca> wrote:

>> http://tools.ietf.org/html/draft-ietf-vcarddav-carddav-10#section-10.4 ,
>> the address-data corresponding to a REPORT response is defined as:
>>
>>        <!ELEMENT address-data (#PCDATA)>
>>        <!-- PCDATA value: address data -->
>>
>> (and the same section contains two paragraph explaining how to deal with
>> CDATA).
>>
>> If I understand this definition correctly, this more or less prevents
>> the use of xCard as the returned format.
>
> Well, no matter what the schema says, the text itself prevents xCard
> from being used. If I understand correctly, CardDAV specifies vCard 3,
> mentions that v4 is compatible, and that's it. I guess we'll need a new
> 1-page RFC to specify xCard inside CardDAV...

Actually the server can advertise support for xCard via the 
CARDDAV:supported-address-data property at which point it is in theory OK 
for the client to send that. Obviously the schema for the address-data 
element would need to be tweaked to allow "embedded" XML, and maybe we have 
a one page spec to do that (actually perhaps two pages as we should deal 
with this for CalDAV too).

-- 
Cyrus Daboo