Re: [VCARDDAV] Last call comments on vcardrev-11

Markus Lorenz <lorenz@atlantika-arts.net> Tue, 01 June 2010 16:34 UTC

Return-Path: <lorenz@atlantika-arts.net>
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 1AF1B28C188 for <vcarddav@core3.amsl.com>; Tue, 1 Jun 2010 09:34:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.612
X-Spam-Level:
X-Spam-Status: No, score=0.612 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_MISMATCH_NET=0.611]
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 mYzaM8JVRtyM for <vcarddav@core3.amsl.com>; Tue, 1 Jun 2010 09:34:20 -0700 (PDT)
Received: from host46.sitepush.net (server20.server-centrum.de [213.239.241.46]) by core3.amsl.com (Postfix) with ESMTP id C897028C0DE for <vcarddav@ietf.org>; Tue, 1 Jun 2010 09:34:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by host46.sitepush.net (Postfix) with ESMTP id ED5121FA000C for <vcarddav@ietf.org>; Tue, 1 Jun 2010 18:33:49 +0200 (CEST)
Received: from host46.sitepush.net ([127.0.0.1]) by localhost (server20.server-centrum.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G67ULfgZ5vcV for <vcarddav@ietf.org>; Tue, 1 Jun 2010 18:33:49 +0200 (CEST)
Received: from [192.168.0.100] (g224236149.adsl.alicedsl.de [92.224.236.149]) by host46.sitepush.net (Postfix) with ESMTP id BEB8A1FA0002 for <vcarddav@ietf.org>; Tue, 1 Jun 2010 18:33:49 +0200 (CEST)
Message-ID: <4C05366C.5030704@atlantika-arts.net>
Date: Tue, 01 Jun 2010 18:33:48 +0200
From: Markus Lorenz <lorenz@atlantika-arts.net>
Organization: Atlantika Arts Software Development
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4
MIME-Version: 1.0
To: vcarddav@ietf.org
References: <0506F7DE00AA916F6562B1CD@cmu-294450.wv.cc.cmu.edu>
In-Reply-To: <0506F7DE00AA916F6562B1CD@cmu-294450.wv.cc.cmu.edu>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [VCARDDAV] Last call comments on vcardrev-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, 01 Jun 2010 16:34:22 -0000

Am 31.05.2010 19:38, schrieb Cyrus Daboo:
> * Section 5.6: The restriction on "work" and "home" usage related to
> presence and value of "KIND" seems a little odd. What is more, it does
> not use RFC2119 key words so it is not clear if this is a "real"
> requirement or not. This needs to be better defined, or the restriction
> should be removed.

I think the restriction should be removed. Right now I can't imagine a
situation where something other than an "individual" could have a
meaningful property typed "home" or "work". But then you could add
restrictions for all the type-param-related values as well, because
"parent", "child", etc. also make sense only for individuals.

> * Section 6.1.5: "group" should not be restricted to a group of
> "people". For example, I might want a group for all the locations in a
> particular building.

The MEMBER property already allows referring to any kind of URI, neither
only people nor only vCards. Hence you can already add members to a
"group" which are not people and thus the restriction to "people"
doesn't make sense.

Another thing could be to reduce the restrictions of the MEMBER
property. If you were allowed to have members for the KIND "thing" you
could create a vCard for the particular building, describe it as a
"thing" KIND, and associate other vCards (e.g. vCards for servers
describing their location) with it by using the MEMBER property.

Reducing the restriction of the MEMBER property would give you the
ability to build a large tree structure of associated things. This will
not be possible if only the "group" KIND is allowed to have MEMBER
properties. Then only the leaves of such a structure can be a "thing"
and all nodes must be "group".