IETF Logo Mail Archive

Re: [VCARDDAV] Questions, Concerns, and Errata concerning vcardrev-13

Simon Perreault <simon.perreault@viagenie.ca> Wed, 03 November 2010 18:23 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 81BFB28C0E2 for <vcarddav@core3.amsl.com>; Wed, 3 Nov 2010 11:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.502
X-Spam-Level:
X-Spam-Status: No, score=-2.502 tagged_above=-999 required=5 tests=[AWL=0.098, 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 gdZRNEvNz7tW for <vcarddav@core3.amsl.com>; Wed, 3 Nov 2010 11:23:33 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id 6C85428C0D7 for <vcarddav@ietf.org>; Wed, 3 Nov 2010 11:23:33 -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 964C920D35; Wed, 3 Nov 2010 14:23:40 -0400 (EDT)
Message-ID: <4CD1A8AC.5020504@viagenie.ca>
Date: Wed, 03 Nov 2010 14:23:40 -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: Rohit Khare <Rohit@Khare.org>
References: <2B2DCE4A-4AC8-4C21-88CA-597A8123C809@Khare.org>
In-Reply-To: <2B2DCE4A-4AC8-4C21-88CA-597A8123C809@Khare.org>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Cc: vcarddav@ietf.org
Subject: Re: [VCARDDAV] Questions, Concerns, and Errata concerning vcardrev-13
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 18:23:34 -0000

On 2010-10-12 02:42, Rohit Khare wrote:
> * … specifically because it makes comma and semicolon handling
> worryingly complex (§3.3). My spidey-senses start tingling when I have
> to scan over special handling for escaping. I always hope for something
> so mandatory that I can pre-process my input with a regex, but I usually
> don’t get that moment of satori :) Short of that, I became concerned
> that if I’m going to be ABNF-driven, that’s fine, but having input
> processing rules that aren’t context-sensitive seemed surprising (every
> comma, everywhere).

I'm not sure I understand this proposal correctly. Are you arguing for
or against context-aware parsing?

Would the following be a faithful summary?

Proposal: relax comma escaping rules.
  - MUST escape commas in values of properties that may have multiple
instances.
  - SHOULD escape commas in other values.

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

v2.23.0 | Report a Bug | By Email