Re: [VCARDDAV] vcarddav-birth-death-extensions update

Simon Perreault <simon.perreault@viagenie.ca> Fri, 04 November 2011 16:44 UTC

Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: vcarddav@ietfa.amsl.com
Delivered-To: vcarddav@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAFAA11E8081 for <vcarddav@ietfa.amsl.com>; Fri, 4 Nov 2011 09:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4hVSz6hjwmI6 for <vcarddav@ietfa.amsl.com>; Fri, 4 Nov 2011 09:44:55 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by ietfa.amsl.com (Postfix) with ESMTP id D252211E8082 for <vcarddav@ietf.org>; Fri, 4 Nov 2011 09:44:55 -0700 (PDT)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67]) by jazz.viagenie.ca (Postfix) with ESMTPSA id E73FC21F04 for <vcarddav@ietf.org>; Fri, 4 Nov 2011 12:44:24 -0400 (EDT)
Message-ID: <4EB41668.4050603@viagenie.ca>
Date: Fri, 04 Nov 2011 12:44:24 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20110927 Thunderbird/7.0
MIME-Version: 1.0
To: vcarddav@ietf.org
References: <CAC4RtVBLpmkZJP3+qFNp+87BCAgKahRQ8OWgrLd0Q7-NggdPYA@mail.gmail.com> <4EB3DF52.9020302@viagenie.ca> <1E4E86DF2C18BFEDE8B074E3@caldav.corp.apple.com> <CALaySJJmph-d1P+5_5QREhzKfDH7xeH3dz1YqdBG-MKLktRibw@mail.gmail.com> <CAC4RtVAZVa7kOMvgufL8wZC3Uc7iW4H9==SynCdas+UA1XEmEw@mail.gmail.com>
In-Reply-To: <CAC4RtVAZVa7kOMvgufL8wZC3Uc7iW4H9==SynCdas+UA1XEmEw@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [VCARDDAV] vcarddav-birth-death-extensions update
X-BeenThere: vcarddav@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF vcarddav wg mailing list <vcarddav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 04 Nov 2011 16:44:56 -0000

On 11/04/2011 12:12 PM, Barry Leiba wrote:
> Updated; same URL:
> http://trac.tools.ietf.org/wg/vcarddav/trac/browser/draft-ietf-vcarddav-birth-death-extensions-02.txt
>
> Please check to make sure I got it right, including the ABNF and the examples.

I reviewd the changes and have a few comments. First, the simple syntax 
errors.

Commas in double-quoted parameter strings don't need to be escaped. 
Also, there are 7 components so 6 semicolons are needed.

OLD:
	DEATHPLACE;LABEL="Aboard the Titanic\, near Newfoundland";	
	 GEO="geo:41.731944,-49.945833":;;;;;
NEW:
	DEATHPLACE;LABEL="Aboard the Titanic, near Newfoundland";	
	 GEO="geo:41.731944,-49.945833":;;;;;;

OLD:
	BIRTHPLACE;GEO="geo:46.769307,-71.283079":;;;;;Canada
NEW:
	BIRTHPLACE;GEO="geo:46.769307,-71.283079":;;;;;;Canada

==============

More importantly, what is the difference between this

	DEATHPLACE;LABEL="Aboard the Titanic\, near Newfoundland";	
	 GEO="geo:41.731944,-49.945833":;;;;;

and this?

	DEATHPLACE;LABEL="Aboard the Titanic\, near Newfoundland";	
	 VALUE=uri:geo:41.731944\,-49.945833

(ADR didn't allow URI values so it didn't have the same possible 
ambiguity...)

==============

Reserving the English string "unknown" seems awkward to me. How is the 
LANGUAGE parameter supposed to handle this?

Is this supposed to be interpreted as "unknown"?

	DEATHDATE;VALUE=text;LANGUAGE=en:unknown

How about this one?

	DEATHDATE;VALUE=text;LANGUAGE=en-US:unknown

How about this one?

	DEATHDATE;VALUE=text;LANGUAGE=fr:inconnue

How about this?

	DEATHDATE;VALUE=text;LANGUAGE=en:unknown
	DEATHDATE;VALUE=text;LANGUAGE=fr:inconnue

An idea, which I'm not sure is a good one, could be to reserve the empty 
string instead.

	DEATHDATE;VALUE=text:

With or without a LANGUAGE parameter, it would always be the same.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca