Re: [VCARDDAV] some issues with draft 13

Simon Perreault <simon.perreault@viagenie.ca> Fri, 08 October 2010 12:51 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 7ECB53A68A4 for <vcarddav@core3.amsl.com>; Fri, 8 Oct 2010 05:51:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.575
X-Spam-Level:
X-Spam-Status: No, score=-2.575 tagged_above=-999 required=5 tests=[AWL=0.025, 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 3CQbx2hGePsu for <vcarddav@core3.amsl.com>; Fri, 8 Oct 2010 05:51:21 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id B15573A6884 for <vcarddav@ietf.org>; Fri, 8 Oct 2010 05:51:20 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c000:21d:60ff:fed7:e732]) by jazz.viagenie.ca (Postfix) with ESMTPSA id DB53F20D23 for <vcarddav@ietf.org>; Fri, 8 Oct 2010 08:52:24 -0400 (EDT)
Message-ID: <4CAF1408.2030300@viagenie.ca>
Date: Fri, 08 Oct 2010 08:52:24 -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: <AANLkTinMBy2G+uLh1G4-n-Z_QHAc154MkG34fFb4sLmY@mail.gmail.com>
In-Reply-To: <AANLkTinMBy2G+uLh1G4-n-Z_QHAc154MkG34fFb4sLmY@mail.gmail.com>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Subject: Re: [VCARDDAV] some issues with draft 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: Fri, 08 Oct 2010 12:51:23 -0000

On 2010-10-08 03:18, Kevin Marks wrote:
> *4.7.  BINARY*
> 
> While this format needs preserving for backwards compatibility, I'd
> suggest deprecating it in favour of using a data URL per RFC 2397. 
> 
> This is already common practice for inline embedding of images in PHOTO
> or LOGO. 
> 
> Adding a data URL example to section 4.2, would clarify this, and making
> this a recommended practice going forwards will simplify the spec
> overall, as currently which fields that can be specified as BINARY need
> to be explicitly called out.

I really like this. Unless people disagree, I'll do exactly that for the
next version.

> *7.2 Matching*
> 
> The examples here repeatedly state that FN has a cardinality of 1,
> whereas FN now has a cardinality of n, so the examples need revising to
> reflect this - apply the cardinality n merge model to FN, and add a
> cardinality 1 property to the example to illustrate that behaviour.

Wow, good catch! I'll revise the examples.

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