Re: [VCARDDAV] CardDAV + xCard in query response

Cyrus Daboo <cyrus@daboo.name> Mon, 20 June 2011 18:27 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 3787211E81D0 for <vcarddav@ietfa.amsl.com>; Mon, 20 Jun 2011 11:27:16 -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 r+nN1oVUvT46 for <vcarddav@ietfa.amsl.com>; Mon, 20 Jun 2011 11:27:15 -0700 (PDT)
Received: from daboo.name (daboo.name [151.201.22.177]) by ietfa.amsl.com (Postfix) with ESMTP id 1D6A911E8070 for <vcarddav@ietf.org>; Mon, 20 Jun 2011 11:27:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id B0A94F9BEC0; Mon, 20 Jun 2011 14:27:14 -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 6vzgoLwNH-4V; Mon, 20 Jun 2011 14:27:14 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 5EBBCF9BEB4; Mon, 20 Jun 2011 14:27:13 -0400 (EDT)
Date: Mon, 20 Jun 2011 14:27:10 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Mike Douglass <douglm@rpi.edu>, vcarddav@ietf.org
Message-ID: <915F74B1105AD879546F6462@caldav.corp.apple.com>
In-Reply-To: <4DFF8D82.3090506@rpi.edu>
References: <4DE03A77.6030801@quillaud.org> <4DF65BC9.7050306@viagenie.ca> <A93F91D639EB4D5B16840D2E@caldav.corp.apple.com> <BANLkTi=1WS24Sb_vnSOWq99C0tOuyPJ6ag@mail.gmail.com> <1773B5FAF113A95099870AF8@caldav.corp.apple.com> <4DFF84EF.3030806@viagenie.ca> <4DFF8D82.3090506@rpi.edu>
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="965"
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, 20 Jun 2011 18:27:16 -0000

Hi Mike,

--On June 20, 2011 2:12:18 PM -0400 Mike Douglass <douglm@rpi.edu> wrote:

> I had taken the approach that what is contained within the calendar-data
> element is the XML representation of an event, i.e
>
> <calendar-data>
> <icalendar>
> ...
> </icalendar>
> </calendar-data>
>
> This is more in line with other protocols and allows the entire response
> to be parsed as a whole.
>
> It does raise the issue of whether there is a resource body (there isn't
> in my case) and what representation it takes - is it an XML database
> manufacturing icalendar or an icalendar system manufacturing XML - or
> some other approach manufacturing both.
>
> In essence I don't have a resource body to reproduce exactly...

I think what goes in address-data and calendar-data must match what would 
be returned in the body of a GET response on the corresponding URI. At 
least that was the original intent, but maybe for XML we have to change 
that.

-- 
Cyrus Daboo