[VCARDDAV] CardDAV resources website, was Re: Implementations of CardDAV and/or MKCOLext?, was: CardDAV and MKCOLext

Cyrus Daboo <cyrus@daboo.name> Wed, 15 July 2009 19:46 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 115DC3A6AA4 for <vcarddav@core3.amsl.com>; Wed, 15 Jul 2009 12:46:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.415
X-Spam-Level:
X-Spam-Status: No, score=-2.415 tagged_above=-999 required=5 tests=[AWL=0.184, BAYES_00=-2.599]
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 Lu4YCbM1-WKn for <vcarddav@core3.amsl.com>; Wed, 15 Jul 2009 12:46:26 -0700 (PDT)
Received: from daboo.name (daboo.name [151.201.22.177]) by core3.amsl.com (Postfix) with ESMTP id EAE3F3A6A56 for <vcarddav@ietf.org>; Wed, 15 Jul 2009 12:46:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 7638D16D5077 for <vcarddav@ietf.org>; Wed, 15 Jul 2009 15:44:48 -0400 (EDT)
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 ac3k5e1rnypc for <vcarddav@ietf.org>; Wed, 15 Jul 2009 15:44:48 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.101.32.44]) by daboo.name (Postfix) with ESMTP id BA64716D5070 for <vcarddav@ietf.org>; Wed, 15 Jul 2009 15:44:47 -0400 (EDT)
Date: Wed, 15 Jul 2009 15:44:44 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: vcarddav@ietf.org
Message-ID: <60D97EFC56AEA02199EEA7E0@caldav.corp.apple.com>
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="658"
Subject: [VCARDDAV] CardDAV resources website, was Re: Implementations of CardDAV and/or MKCOLext?, was: CardDAV and MKCOLext
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: Wed, 15 Jul 2009 19:46:27 -0000

Hi,

--On July 15, 2009 9:19:53 PM +0200 Julian Reschke <julian.reschke@gmx.de> 
wrote:

> Related to this: for the purpose of determining support for this
> protocol, it would be interesting to find out about current
> implementation efforts (for both specs!).

Speaking of which, I have created a CardDAV website to help maintain 
information like this along the lines of the same one we have for CalDAV.

The site is at <http://carddav.calconnect.org>.

If you have comments, requests etc please email me directly or use the form 
on the website to submit details.

Equivalent CalDAV one is <http://caldav.calconnect.org> for comparison.

-- 
Cyrus Daboo