Re: [VCARDDAV] vcardrev nits

Ciny Joy <Ciny.Joy@Sun.COM> Wed, 21 October 2009 23:57 UTC

Return-Path: <Ciny.Joy@Sun.COM>
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 D4CA93A6928 for <vcarddav@core3.amsl.com>; Wed, 21 Oct 2009 16:57:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.017
X-Spam-Level:
X-Spam-Status: No, score=-5.017 tagged_above=-999 required=5 tests=[AWL=1.028, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 4pVXt7hRZ1lT for <vcarddav@core3.amsl.com>; Wed, 21 Oct 2009 16:57:06 -0700 (PDT)
Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133]) by core3.amsl.com (Postfix) with ESMTP id EA5B03A6805 for <vcarddav@ietf.org>; Wed, 21 Oct 2009 16:57:05 -0700 (PDT)
Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n9LNvF2b018083 for <vcarddav@ietf.org>; Wed, 21 Oct 2009 16:57:15 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_IYSvprr7x43MsyEdEoezKg)"
Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KRW00K002HNF900@fe-sfbay-10.sun.com> for vcarddav@ietf.org; Wed, 21 Oct 2009 16:57:15 -0700 (PDT)
Received: from ciny-joys-macbook-pro.local ([unknown] [129.150.0.25]) by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KRW008JC2JE0740@fe-sfbay-10.sun.com> for vcarddav@ietf.org; Wed, 21 Oct 2009 16:57:14 -0700 (PDT)
Date: Wed, 21 Oct 2009 16:57:14 -0700
From: Ciny Joy <Ciny.Joy@Sun.COM>
In-reply-to: <mailman.1937.1256166304.4669.vcarddav@ietf.org>
Sender: Ciny.Joy@Sun.COM
To: vcarddav@ietf.org
Message-id: <4ADF9FDA.7050602@sun.com>
References: <mailman.1937.1256166304.4669.vcarddav@ietf.org>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
Subject: Re: [VCARDDAV] vcardrev nits
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: Wed, 21 Oct 2009 23:57:06 -0000

vcarddav-request@ietf.org wrote:
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 21 Oct 2009 19:05:09 -0400
> From: Simon Perreault <simon.perreault@viagenie.ca>
> Subject: Re: [VCARDDAV] vcardrev nits
> To: vcarddav@ietf.org
> Message-ID: <4ADF93A5.4090505@viagenie.ca>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 21/10/09 01:34 PM, Ciny Joy wrote:
>   
>>> I added the "thing" value which stands for "an inanimate object (e.g. a device,
>>> a server, etc.)"
>>>
>>>       
>> In Calconnect, we have been working on a draft, defining resources, in
>> the calendaring and scheduling context. VCARD is one form of
>> representation we are defining and we are trying to reuse as many
>> attribute definitions as possible from this draft. Would it be possible
>> to have a value of 'resource', for KIND. In scheduling context, that
>> would cover a room, an equipment, or even a role (person with specific
>> skill set).
>>     
>
> I'm not sure I clearly understand the difference between a "thing" and a 
> "resource". Can you elaborate?
>   
It is almost the same. Though a resource can also be a location, like a 
room, or a role, like a plumber.
> Also, does this need to be part of the base spec? You could register 
> this "resource" value and define it properly with all the context it 
> needs in your own document...
>   
Will do that if needed. But that will be adding a value very similar to 
"thing". Hence the question now.

Thanks,
Ciny
> Thanks,
> Simon
>