Re: [VCARDDAV] KIND:device

[Joe Marcus Clarke <[e-mail]>]

On 1/11/12 9:51 AM, Simon Perreault wrote:
> On 01/09/2012 12:14 PM, Joe Marcus Clarke wrote:
>> We did add UID as a holder for serial number.
> 
> I'd be careful with that idea. What tells a vCard consumer that the UID
> property also happens to contain a serial number? Seems like pointless
> overloading to me. Better just create a new serial number property. It's
> free, you know... ;)

I do.  I was arguing that a "unique identifier" for a device would
likely be a serial number since that is burned into the device.  Gonzalo
and I were debating this further and I'm coming around to provisioning a
serial number property vs. overloading UID.  But since UID can hold a
text value like this, it would be legal to do a serial number here, right?

> 
>> Just like with KIND:application, there could be sub-types.  We
>> specifically indicate that, but do not address it in this draft.  That
>> said, I don't think KIND is the right property for this.  This might be
>> handled in a vendor extension namespace and standardized later.
> 
> Mkay... But it would truly be sad if KIND:DEVICE gets standardized but
> everything else doesn't so basically KIND:DEVICE becomes a new ex-dash
> playground where only one vendor plays.

We're following the model of KIND:application here.  Sub-types and those
properties that might be applicable to different devices is outside the
scope of this draft.  We do not want to make this vendor-specific,
though.  Throughout our thinking on this we have been considering a
number of devices that would come from a number of vendors.  We want to
provide easier identity and asset tracking through well-structured data.
 The use case we have put in the draft can be implemented by any vendor
of any type of networked element.

Joe

-- 
Joe Marcus Clarke, CCIE #5384,         |          |
SCJP, SCSA, SCNA, SCSECA, VCP        |||||      |||||
Distinguished Support Engineer  ..:|||||||||::|||||||||:..
Phone: [phone]         c i s c o  S y s t e m s
Email: [e-mail]

----------------------------------------------------------------------------