Re: [VCARDDAV] use case for multiple affiliations

Simon Perreault <simon.perreault@viagenie.ca> Mon, 27 July 2009 11:47 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 8085D3A63EB for <vcarddav@core3.amsl.com>; Mon, 27 Jul 2009 04:47:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.884
X-Spam-Level:
X-Spam-Status: No, score=-1.884 tagged_above=-999 required=5 tests=[AWL=0.717, 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 pOP4nO0vtYCg for <vcarddav@core3.amsl.com>; Mon, 27 Jul 2009 04:47:06 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id 66F0A3A6C20 for <vcarddav@ietf.org>; Mon, 27 Jul 2009 04:47:04 -0700 (PDT)
Received: by jazz.viagenie.ca (Postfix, from userid 8) id D0A9E29E15E2; Mon, 27 Jul 2009 07:47:01 -0400 (EDT)
Received: from dhcp-13e3.meeting.ietf.org (unknown [IPv6:2001:df8:0:16:20a:95ff:fef7:a2af]) by jazz.viagenie.ca (Postfix) with ESMTP id AC37529E15CE; Mon, 27 Jul 2009 07:46:56 -0400 (EDT)
Message-ID: <4A6D93AA.3090004@viagenie.ca>
Date: Mon, 27 Jul 2009 13:46:50 +0200
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: Cyrus Daboo <cyrus@daboo.name>
References: <4A6D6A30.7040805@viagenie.ca> <4A6D6FBB.60701@atlantika-arts.net> <4A6D8E76.5060404@viagenie.ca> <11F91EDD1BFA2AD195978DB5@001ec2bab730.netpoint.com>
In-Reply-To: <11F91EDD1BFA2AD195978DB5@001ec2bab730.netpoint.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: vcarddav@ietf.org
Subject: Re: [VCARDDAV] use case for multiple affiliations
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: Mon, 27 Jul 2009 11:47:07 -0000

Cyrus Daboo wrote:
>>    X-summer-residence.ADR:...
>>    X-summer-residence.TEL:...
>>    X-summer-residence.ORG:Summer residence
> 
> I really don't like the idea of encoding information like that into the
> group name.

What information? I could have used X-asdf and it would have had the
exact same meaning.

> If we want to have special meaning for groups, then we need
> additional properties to describe those groups. e.g.:
> 
>   X-1234.ADR:...
>   X-1234.TEL:...
>   X-1234.ORG:Summer residence
>   X-1234.GROUP-DESCRIPTION:My summer residence from May - September

That's what ORG is for.

> One could also imagine a type property for the group description for
> various cases, e.g. TYPE=HISTORIC for a set of information that is no
> longer valid but included for completeness, or
> TYPE=FUTURE;START=20090921 for contact information that will be active
> from the specified data onwards only.

Is this usage common enough to warrant new properties? Why not leave it
in plain text? Do computers really need to parse this?

Simon
-- 
STUN/TURN server    --> http://numb.viagenie.ca
Interplanetary news --> http://reeves.viagenie.ca
vCard 4.0           --> http://www.vcarddav.org