Re: [VCARDDAV] PREF interoperability

Simon Perreault <simon.perreault@viagenie.ca> Wed, 03 November 2010 20:34 UTC

Return-Path: <simon.perreault@viagenie.ca>
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 B75A63A6883 for <vcarddav@core3.amsl.com>; Wed, 3 Nov 2010 13:34:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.519
X-Spam-Level:
X-Spam-Status: No, score=-2.519 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 hxvAjTr8oYQh for <vcarddav@core3.amsl.com>; Wed, 3 Nov 2010 13:34:42 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id F3FD93A66B4 for <vcarddav@ietf.org>; Wed, 3 Nov 2010 13:34:41 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c000:39b4:3937:b348:8153]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 6651020D35 for <vcarddav@ietf.org>; Wed, 3 Nov 2010 16:34:49 -0400 (EDT)
Message-ID: <4CD1C768.5060502@viagenie.ca>
Date: Wed, 03 Nov 2010 16:34:48 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101027 Fedora/3.1.6-1.fc14 Thunderbird/3.1.6
MIME-Version: 1.0
To: vcarddav@ietf.org
References: <2B2DCE4A-4AC8-4C21-88CA-597A8123C809@Khare.org> <4CD1C5E6.1000802@viagenie.ca>
In-Reply-To: <4CD1C5E6.1000802@viagenie.ca>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Subject: Re: [VCARDDAV] PREF interoperability
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, 03 Nov 2010 20:34:44 -0000

On 2010-11-03 16:28, Simon Perreault wrote:
> On 2010-10-12 02:42, Rohit Khare wrote:
>> * PREF reminds me of content-negotiation in HTTP. It was a
>> beautiful idea that was convoluted too far to really ever work. The
>> similarities begin with the arbitrary 0-100 scale (oops! 1-100 see?
>> and 1 > 100, don’t forget — this kind of scaling jiggery-pokery is
>> unlikely to interoperate, much less compose (concatenating records
>> from multiple sources). Where is the actual reference to a running
>> system with that much subtlety of expression?
> 
> At this late stage in the process, we need concrete and explicit 
> proposals. I can't find one in this (still interesting and valuable) 
> comment.

I'm sorry, I found your proposal in the following:

> Editorial Recommendation: By contrast, I can bet you that users care
> immensely about the *exact order* that fields were typed in. Why not
> make this ORDER, if we don’t want the original sequential occurrence
> of lines in the file to be controlling law? If anything, I’d wish we
> ruled out the use of PREF precisely because the same four characters
> exist in RFC 2426 with a completely different meaning (and it’s a
> presence/absence token to boot, not a parameter)

The order of properties is irrelevant since at least vCard 2.1.
Introducing this would mean a major break of backward compatibility.
This idea (which I proposed myself IIRC) was ruled out by the working
group in favour of an integer-valued PREF parameter.

Using the order of properties would also create other problems:

- Non-preference is going to be the most common case, but there is no
way to represent that when preference follows order.

- CardDAV would need to be heavily modified to keep properties in order.
  - There is also no way in CardDAV to make queries related to the order
of properties, whereas it is easy to construct queries including the
value of the PREF parameter.

Simon
-- 
NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server        --> http://numb.viagenie.ca
vCard 4.0               --> http://www.vcarddav.org