Re: [VCARDDAV] Proposal around escape character handling (2nd round)

Simon Perreault <simon.perreault@viagenie.ca> Tue, 13 July 2010 15:41 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 03D643A681E for <vcarddav@core3.amsl.com>; Tue, 13 Jul 2010 08:41:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.156
X-Spam-Level:
X-Spam-Status: No, score=-2.156 tagged_above=-999 required=5 tests=[AWL=0.444, 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 AXYAK+TzoYNy for <vcarddav@core3.amsl.com>; Tue, 13 Jul 2010 08:41:17 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id 2CD793A6A6A for <vcarddav@ietf.org>; Tue, 13 Jul 2010 08:41:07 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c000:414d:a107:d36:5c5f]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 86F0820D3A for <vcarddav@ietf.org>; Tue, 13 Jul 2010 11:40:47 -0400 (EDT)
Message-ID: <4C3C8815.4010304@viagenie.ca>
Date: Tue, 13 Jul 2010 11:36:53 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10) Gecko/20100621 Fedora/3.0.5-1.fc13 Thunderbird/3.0.5
MIME-Version: 1.0
To: vcarddav@ietf.org
References: <AANLkTilx6XgI2iosuKf5zmHnLggkmYe4EeeN-PijvI5K@mail.gmail.com> <36FF8BB750F3694C0400EAC1@caldav.corp.apple.com>
In-Reply-To: <36FF8BB750F3694C0400EAC1@caldav.corp.apple.com>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [VCARDDAV] Proposal around escape character handling (2nd round)
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: Tue, 13 Jul 2010 15:41:27 -0000

On 2010-07-13 10:59, Cyrus Daboo wrote:
> So there is a real problem here. For example, if in the future I define
> a new property FOO that uses a ;-delimited compound value, then I want
> to be sure that clients not aware of this property will properly
> "round-trip" it. So if I send such a client this:
> 
> FOO:delimited;text\;string

Right, there is a problem with the current text.

Assume we specify that semicolons that are not component separators MUST
be escaped. Then a client can correctly interpret this unknown property
as having two components. And it will always output it exactly the way
it received it. That fixes the problem, right?

If so, this would point toward the acceptance of proposal 1.

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