Re: [Uri-review] Request for review of "ab:" URI scheme

Cyrus Daboo <cyrus@daboo.name> Tue, 26 April 2011 15:07 UTC

Return-Path: <cyrus@daboo.name>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9F43E07D3 for <uri-review@ietfa.amsl.com>; Tue, 26 Apr 2011 08:07:22 -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 IaFjvktWHONA for <uri-review@ietfa.amsl.com>; Tue, 26 Apr 2011 08:07:22 -0700 (PDT)
Received: from daboo.name (daboo.name [151.201.22.177]) by ietfa.amsl.com (Postfix) with ESMTP id 8681CE077E for <uri-review@ietf.org>; Tue, 26 Apr 2011 08:06:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id C185525EE08; Tue, 26 Apr 2011 11:06:42 -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 bwNT7HpzFz1P; Tue, 26 Apr 2011 11:06:42 -0400 (EDT)
Received: from [17.101.34.182] (unknown [151.201.22.177]) by daboo.name (Postfix) with ESMTPSA id 3A14F25EDFA; Tue, 26 Apr 2011 11:06:41 -0400 (EDT)
Date: Tue, 26 Apr 2011 11:06:44 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Graham Klyne <GK-lists@ninebynine.org>, Barry Leiba <barryleiba@computer.org>
Message-ID: <309A986D19BE857C85CE58A7@[17.101.34.182]>
In-Reply-To: <4DB6D2C8.4090806@ninebynine.org>
References: <BANLkTim8eWcWwKfyERghK2tuSP1rK0SdsA@mail.gmail.com> <4DB1D685.4090706@ninebynine.org> <4DB5D6EE.4080503@isode.com> <4DB6B9B6.8040306@ninebynine.org> <BANLkTinMm0OyBqUNTU_-Er_4w1TK7kW-Eg@mail.gmail.com> <4DB6D2C8.4090806@ninebynine.org>
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="1390"
X-Mailman-Approved-At: Tue, 26 Apr 2011 08:19:44 -0700
Cc: uri-review@ietf.org, draft-ietf-sieve-external-lists.all@tools.ietf.org
Subject: Re: [Uri-review] Request for review of "ab:" URI scheme
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uri-review>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Apr 2011 15:07:22 -0000

Hi Graham,

--On April 26, 2011 3:12:24 PM +0100 Graham Klyne <GK-lists@ninebynine.org> 
wrote:

> In particular, concerning point (3), I think that an "add to address
> book" functionality encoded within a URI would be a Bad Thing.  But
> allowing that operations like Add, Update and Delete might usefully be
> applied to such URIs
>
> Another point about which I worry is the potential mismatch between being
> able to use such URIs as part of the process of, say, adding an entry to
> an address book, and in a context that allows "any URI that can be
> considered to resolve to some sort of list".  (But this maybe a probhlem
> for the Sieve protocol, not the proposed URI scheme.)
>
> In summary, I find myself in the slightly uncomfortable position of
> liking the potential for what an addrbook: URI scheme might offer, but
> fearing that the immediate requirement coming from the Sieve protocol has
> too small a "contact area" with the URI to meaningfully shape the URI
> technical specification to be able to achieve those goals in later
> developments.

Personally I think the "add to address book" use here is not right. 
addrbook: by itself does not include any actual contact data - it is simply 
a reference to an address book. "Add to addressbook" is handled (today) by 
simply providing a link to a vcard resource or use of a Link header point 
to vcard.

-- 
Cyrus Daboo