Re: [VCARDDAV] Questions about vCard 4.0 (draft rev-11)

"Javier Godoy" <rjgodoy@fich.unl.edu.ar> Tue, 22 June 2010 21:19 UTC

Return-Path: <rjgodoy@fich.unl.edu.ar>
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 92C4828C0F8 for <vcarddav@core3.amsl.com>; Tue, 22 Jun 2010 14:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, STOX_REPLY_TYPE=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 OJOsmAxTgYmd for <vcarddav@core3.amsl.com>; Tue, 22 Jun 2010 14:19:55 -0700 (PDT)
Received: from fich.unl.edu.ar (fich.unl.edu.ar [168.96.132.90]) by core3.amsl.com (Postfix) with ESMTP id 3B4E328C0D0 for <vcarddav@ietf.org>; Tue, 22 Jun 2010 14:19:54 -0700 (PDT)
Received: from Javier2 ([190.193.124.162]) (authenticated user rjgodoy@fich.unl.edu.ar) by fich.unl.edu.ar (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits)); Tue, 22 Jun 2010 18:20:11 -0300
Message-ID: <8822D300A5ED445A8CB9C6BB9B60A4E7@Javier2>
From: Javier Godoy <rjgodoy@fich.unl.edu.ar>
To: Simon Perreault <simon.perreault@viagenie.ca>, vcarddav@ietf.org
References: <AANLkTiniY60njEGixPGeKvs_m1LE_uVrvtnDQuXrP7jV@mail.gmail.com> <4C20B501.6030802@viagenie.ca>
Date: Tue, 22 Jun 2010 18:16:31 -0300
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5512
Subject: Re: [VCARDDAV] Questions about vCard 4.0 (draft rev-11)
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, 22 Jun 2010 21:19:56 -0000

Hi,

On 2010-06-22 10:05 Simon Perreault wrote:

> On 2010-06-21 22:27, Daisuke Miyakawa wrote:

>> 1-b) How about BEGIN and END?
>> There's no mention about how BEGIN/END should be emitted. Is it ok to
>> use "begin:vcard"?
>
> No. Unless specified otherwise, property values are case sensitive.
> Therefore "begin:VCARD", "BEGIN:VCARD", and "Begin:VCARD" would be
> valid, but "begin:vcard" would not. The ABNF in section 6.1.1 makes this
> clear.
>

I only found the following statement in section 3.2 "Parameter values MAY be 
case sensitive or case insensitive, depending on their definition.", but it 
refers to parameter values, not to property values. I found nothing about 
property values, but this is one of the few cases where a case-sensitive 
string is specified as literal , so I think we do not need a general 
interpretation, but we need to be explicit about case sensitivity..

In section 3.2, ABNF is given as
 vcard = "BEGIN" ":" "VCARD" CRLF

And in section 6.1
 BEGIN-value = "VCARD"

>From section 2.3 of RFC 5234
 ABNF strings are case insensitive .
 To specify a rule that is case sensitive, specify the characters 
individually.
 For example:
   rulename    =  %d97 %d98 %d99

So the ABNF above should be

BEGIN-value = %d86 %d67 %d65 %d82 %d68; uppercase "VCARD"

(and the same in section 3.2).

Maybe we also want to review the ABNF for "Z" and "T" in zone and timestamp.


>> 2) VERSION
>>
>> I think it would be better to explicitly mention that "VERSION:4.0 MUST
>> be just after BEGIN:VCARD line" for better comfortability of actual
>> implementation.
>
> I tend to agree. Unless people disagree, this will be part of the next
> revision.

+1


Regards

Javier