Re: [VCARDDAV] Empty elements

Peter Saint-Andre <stpeter@stpeter.im> Tue, 30 March 2010 20:58 UTC

Return-Path: <stpeter@stpeter.im>
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 1A5A23A68CC for <vcarddav@core3.amsl.com>; Tue, 30 Mar 2010 13:58:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.159
X-Spam-Level:
X-Spam-Status: No, score=-1.159 tagged_above=-999 required=5 tests=[AWL=0.310, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 NKxd78Xin8ug for <vcarddav@core3.amsl.com>; Tue, 30 Mar 2010 13:58:23 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 32EE63A6AE7 for <vcarddav@ietf.org>; Tue, 30 Mar 2010 13:58:19 -0700 (PDT)
Received: from dhcp-64-101-72-158.cisco.com (dhcp-64-101-72-158.cisco.com [64.101.72.158]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id DC59F40D3A for <vcarddav@ietf.org>; Tue, 30 Mar 2010 14:58:48 -0600 (MDT)
Message-ID: <4BB26607.5070204@stpeter.im>
Date: Tue, 30 Mar 2010 14:58:47 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: vcarddav@ietf.org
References: <FAD7B51CDD3D606009042915@446E7922C82D299DB29D899F> <4BAB73BB.7080601@babelmonkeys.de> <4BAB98F1.6080508@viagenie.ca> <F7D958834F3E28192F043987@dhcp-wireless-open-abg-26-102.meeting.ietf.org> <4BAB9B7F.3090600@viagenie.ca>
In-Reply-To: <4BAB9B7F.3090600@viagenie.ca>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms050900000000070802080602"
Subject: Re: [VCARDDAV] Empty elements
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, 30 Mar 2010 20:58:24 -0000

On 3/25/10 11:21 AM, Simon Perreault wrote:
> On 2010-03-25 10:19, Cyrus Daboo wrote:
>> That is fine for these "structured" values - i.e. just make the
>> sub-elements optional. But in other cases we may not want do that. e.g.
>> a property with no value:
>>
>> DESCRIPTION:
>>
>> <description>
>> <text />
>> <description>

Where is the <description/> element defined? I ask because that the
early Jabberites added such an element to XEP-0054, but I can't find it
in RFC 2426 or draft-ietf-vcarddav-vcardrev.

>> or an empty parameter value. Should we say that <text /> should not be
>> present?
> 
> Right. Properties *always* have values. Therefore the <text/> needs to
> be present.

Agreed (or one needs to leave out the property parameter altogether).

Peter

-- 
Peter Saint-Andre
https://stpeter.im/