Re: [VCARDDAV] KIND:device

Peter Saint-Andre <stpeter@stpeter.im> Mon, 09 January 2012 17:17 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: vcarddav@ietfa.amsl.com
Delivered-To: vcarddav@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C39C011E809B for <vcarddav@ietfa.amsl.com>; Mon, 9 Jan 2012 09:17:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.273
X-Spam-Level:
X-Spam-Status: No, score=-102.273 tagged_above=-999 required=5 tests=[AWL=-0.274, BAYES_00=-2.599, J_CHICKENPOX_46=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PedpRDd+AHRl for <vcarddav@ietfa.amsl.com>; Mon, 9 Jan 2012 09:17:20 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 126A311E80A2 for <vcarddav@ietf.org>; Mon, 9 Jan 2012 09:16:37 -0800 (PST)
Received: from dhcp-64-101-72-243.cisco.com (unknown [64.101.72.243]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 8976D40058; Mon, 9 Jan 2012 10:25:31 -0700 (MST)
Message-ID: <4F0B20F7.4080404@stpeter.im>
Date: Mon, 09 Jan 2012 10:16:39 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Zoltan Ordogh <zordogh@rim.com>
References: <4F073CD8.1060102@stpeter.im> <1DE983233DBBEB4A81F18FABD8208D7614088000@XMB108FCNC.rim.net>
In-Reply-To: <1DE983233DBBEB4A81F18FABD8208D7614088000@XMB108FCNC.rim.net>
X-Enigmail-Version: 1.3.4
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: CardDAV <vcarddav@ietf.org>
Subject: Re: [VCARDDAV] KIND:device
X-BeenThere: vcarddav@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF vcarddav wg mailing list <vcarddav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 09 Jan 2012 17:17:23 -0000

On 1/9/12 10:03 AM, Zoltan Ordogh wrote:
> Hi Peter,
> thank you.
> I checked -01:
> http://tools.ietf.org/html/draft-salgueiro-vcarddav-kind-device
> 
> 
> In section 3:
> "The following base properties make sense for vCards that represent devices..."
> According to whom? 

By stipulation of the authors. :)

It's something that we need to figure out for each new KIND, so let's
discuss it.

> Could this be removed?

No, because Section 6.1.4 of RFC 6350 states the following about new
values for the KIND property:

      An iana-token.  Additional values may be registered with IANA (see
         Section 10.3.4).  A new value's specification document MUST
         specify which properties make sense for that new kind of vCard
         and which do not.

http://tools.ietf.org/html/rfc6350#section-6.1.4

> Having seen the example in section 4, I wonder if
> <kind><text>device</text></kind>
> Could be:
> <kind><text>device</text></kind>
> <kind>
> 	<parameters>
> 		<type><text>device-type</text></type>
> 	</parameters>
> 	<text>router</text>
> </kind>
> would make sense (with a device-type registry).

The same section of RFC 6350 states:

      An x-name.  vCards MAY include private or experimental values for
         KIND.  Remember that x-name values are not intended for general
         use and are unlikely to interoperate.

If we wanted to create a public registry for this, I think we'd want to
define a "device-type" extension in the XML representation, e.g.:

<device xmlns='urn:ietf:params:xml:ns:device-type'>router</device>

Peter

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