Re: [VCARDDAV] KIND:device

Zoltan Ordogh <zordogh@rim.com> Mon, 09 January 2012 17:32 UTC

Return-Path: <zordogh@rim.com>
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 2C3B011E80D4 for <vcarddav@ietfa.amsl.com>; Mon, 9 Jan 2012 09:32:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.001
X-Spam-Level:
X-Spam-Status: No, score=-5.001 tagged_above=-999 required=5 tests=[AWL=0.998, BAYES_00=-2.599, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_MED=-4]
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 ngyNIoiJnO8K for <vcarddav@ietfa.amsl.com>; Mon, 9 Jan 2012 09:32:01 -0800 (PST)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id EE5B911E80C7 for <vcarddav@ietf.org>; Mon, 9 Jan 2012 09:32:00 -0800 (PST)
X-AuditID: 0a41282f-b7fce6d000006a46-db-4f0b2490c2a1
Received: from XHT109CNC.rim.net (xht109cnc.rim.net [10.65.12.218]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by mhs060cnc.rim.net (SBG) with SMTP id 03.72.27206.0942B0F4; Mon, 9 Jan 2012 17:32:00 +0000 (GMT)
Received: from XCT107CNC.rim.net (10.65.161.207) by XHT109CNC.rim.net (10.65.12.218) with Microsoft SMTP Server (TLS) id 8.3.159.2; Mon, 9 Jan 2012 12:32:00 -0500
Received: from XMB108FCNC.rim.net ([fe80::b582:c49b:f967:ac82]) by XCT107CNC.rim.net ([fe80::b815:71ef:9f8f:e07c%16]) with mapi id 14.01.0339.001; Mon, 9 Jan 2012 12:31:59 -0500
From: Zoltan Ordogh <zordogh@rim.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Thread-Topic: [VCARDDAV] KIND:device
Thread-Index: AQHMzKC9snFBccitPkChjXPRIPpqJZYERZMQgABZ4oD//68zQA==
Date: Mon, 09 Jan 2012 17:31:58 +0000
Message-ID: <1DE983233DBBEB4A81F18FABD8208D7614088062@XMB108FCNC.rim.net>
References: <4F073CD8.1060102@stpeter.im> <1DE983233DBBEB4A81F18FABD8208D7614088000@XMB108FCNC.rim.net> <4F0B20F7.4080404@stpeter.im>
In-Reply-To: <4F0B20F7.4080404@stpeter.im>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.70.110.253]
Content-Type: text/plain; charset="utf-8"
content-transfer-encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrHKsWRmVeSWpSXmKPExsXC5chzS3eCCre/wePbChbH9vQzW8ycMJHF gcljyZKfTB5z97xgDmCKamC0SczLyy9JLElVSEktTrZV8klNT8xRCCjKLEtMrlRwySxOzknM zE0tUlLITLFVMlFSKMhJTE7NTc0rsVVKLChIzUtRsuNSwAA2QGWZeQqpecn5KZl56bZKnsH+ uhYWppa6hkp2ukgg4R93xvHts9kLOgQr3q1byt7AeEGgi5GTQ0LAROLCvZusELYYkL2erYuR i0NIoJdJYvbamYwgCSGBZYwSS57qQNhbGSXePvXtYuTgYBNQlZhzNRYkLCKgJXHpWh87iM0s IC8xcc9HNhBbWEBZ4ubKTYwQNSoSC5uPskPYThIdjx4yg9gsQPFLh2aA1fAKeEpM6e6GuqGT UeLu2uOMILs4gRbcnhwNUsMoICux++x1Johd4hK3nsxngrhfQGLJnvPMELaoxMvH/6D+UpRY 1PkdbAyzgKbE+l36EK2KQKseskOsFZQ4OfMJC8SHMhLPp1xin8AoMQvJhlkI3bOQdM9C0r2A kWUVo2BuRrGBmUFyXrJeUWauXl5qySZGcELR0N/B2LdX6xCjAAejEg+vjTS3vxBrYllxZe4h RgkOZiUR3nkMQCHelMTKqtSi/Pii0pzU4kOMFsDwmcgsxZ2cD0x2eSXxxgYGKBwlcV5N9Xt+ QgLpwNSVnZpakFoE08rEwSnVwOg688CBS0fNotfOfl1j2PE2Y8WJ/fIr2LgfFMaV+IQ2L9s0 6+9KN4OvZ36q/L21mnvCmQ9ue76kxO8q2Pr76qJ5Qeqin9v9Xp4+c3z7uZSEk2zH//h3TLo/ Z4r7KXZuQe8Pl/1mSsx5eC6vetWv32yZITW+x9U3xwVze2YzH0jkZj62fAFjM4OHEktxRqKh FnNRcSIAF/THX0EDAAA=
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:32:02 -0000

Hi Peter,

> > In section 3:
> > "The following base properties make sense for vCards that represent devices..."
> > 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

I meant the paragraph about what makes sense and what does not.
Joe pointed out that it's informative (not normative), so it's ok.

> 
> > 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>


I think that a registry would be a good idea.
As for the format - whatever works.


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.