Re: [VCARDDAV] draft-daboo-carddav-directory-gateway and large/multiple directories
Cyrus Daboo <cyrus@daboo.name> Thu, 11 March 2010 15:02 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 8E3DD3A67D7 for <vcarddav@core3.amsl.com>; Thu, 11 Mar 2010 07:02:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level:
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[AWL=0.114, 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 UEnQB555W8xk for <vcarddav@core3.amsl.com>; Thu, 11 Mar 2010 07:02:46 -0800 (PST)
Received: from daboo.name (daboo.name [151.201.22.177]) by core3.amsl.com (Postfix) with ESMTP id C08BF3A6BA8 for <vcarddav@ietf.org>; Thu, 11 Mar 2010 06:59:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 90EC4102D8ECB; Thu, 11 Mar 2010 09:59:41 -0500 (EST)
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 As9azny3MEjw; Thu, 11 Mar 2010 09:59:39 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.101.32.44]) by daboo.name (Postfix) with ESMTPSA id E58E3102D8EBB; Thu, 11 Mar 2010 09:59:37 -0500 (EST)
Date: Thu, 11 Mar 2010 09:59:34 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Arnaud Quillaud <Arnaud.Quillaud@Sun.COM>, vcarddav@ietf.org
Message-ID: <AB5C9D4528C850C7BCADF499@caldav.corp.apple.com>
In-Reply-To: <4B99001F.9000801@sun.com>
References: <4B99001F.9000801@sun.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="1977"
Subject: Re: [VCARDDAV] draft-daboo-carddav-directory-gateway and large/multiple directories
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: Thu, 11 Mar 2010 15:02:47 -0000
Hi Arnaud, --On March 11, 2010 3:37:19 PM +0100 Arnaud Quillaud <Arnaud.Quillaud@Sun.COM> wrote: > As currently defined, the directory-gateway property > (http://tools.ietf.org/html/draft-daboo-carddav-directory-gateway-01#sect > ion-3) points to a single carddav collection which may aggregate results > from different sources. > I see two problems with that approach: > - In organizations with a very large number of directory entries, it > would be much beneficial to be able to offer a choice of multiple > collections ("all users in my Business Unit", "all conference rooms", > etc...). > - It might always be obvious to aggregate data from various sources, > especially if future extensions allow for paging or sorting of results. > > Hence couldn't we allow the directory-gateway property to point to a > regular collection containing address book collections ? We could mandate > that address book queries be supported at the root collection level to > still allow global searches. Why not provide that "filtering" via the addressbook-query report? i.e. the LDAP OU attribute would map to a vcard property and then the client could "scope" its query by filtering on that property. Yes that does require the client to know what vCard property to "scope" and what values might be appropriate. I am wary of going too far down the road of exposing the "internals" of the directory and its schema via CardDAV - as stated in the document this is not meant as a full replacement of the directory. I think if scoped queries like you propose are needed, then maybe the client should use the directory "protocol" directly. To that end it might help if the CardDAV directory gateway address book had a WebDAV property listing URIs for all the sources of the directory data. That way if a client decided it needed to have a more sophisticated interaction with the directory, then it could look at those URIs and figure out how to do that itself. -- Cyrus Daboo
- [VCARDDAV] draft-daboo-carddav-directory-gateway … Arnaud Quillaud
- Re: [VCARDDAV] draft-daboo-carddav-directory-gate… Cyrus Daboo
- Re: [VCARDDAV] draft-daboo-carddav-directory-gate… Arnaud Quillaud
- Re: [VCARDDAV] draft-daboo-carddav-directory-gate… Cyrus Daboo
- Re: [VCARDDAV] draft-daboo-carddav-directory-gate… Arnaud Quillaud