Re: [VCARDDAV] Proposal for new VCARD OBJECTCLASS property

Mike,

What about putting a hyphen between "object" and "class" to make it more
readable?

"OBJECT-CLASS"

Cheers,
-Mike
http://code.google.com/p/ez-vcard

On Sun, Nov 4, 2012 at 1:25 AM, Mike Douglass <mikeadouglass@gmail.com>wrote:

>  During discussions on the new vcard resource draft
> http://tools.ietf.org/html/draft-cal-resource-vcard-01 it seemed that we
> had significant overlap with the device specification
>
> http://tools.ietf.org/html/draft-salgueiro-vcarddav-kind-device-02
>
>  and also applications:
>
> RFC6473
>
> We also realized we have a subset of properties which could apply to any
> schedulable entity, e.g. autoschedule, booking window, calendar user
> addresss (cua) and so on.
>
> We propose a new, multiply occurring property: OBJECTCLASS.
>
> A vcard containing one or more occurrences of this property MUST conform
> to the related specification. So for example we might have
>
> OBJECTCLASS: SCHEDULABLE
>
> The appearance of this property and value requires that the cua be present
> but it also allows us to apply appropriate defaults when a property is
> absent. For example, our resource draft states that the absence of the
> AUTOSCHEDULE property implies that invitations are automatically accepted.
>
> A further advantage is that it seems to facilitate mapping from ldap to
> vcard. There are many widely used ldap object classes which it would be
> useful to make visible in vcard.
>
> It enables authors of specifications to worry less about areas in which
> they are not expert. Any entity which is schedulable can be made so simply
> by adding OBJECTCLASS: SCHEDULABLE to the entity (and any appropriate
> properties).
>
> It also avoids trying to resolve strict hierarchies of 'thing'. A device
> is a resource but so is a room and both may or may not be schedulable.
>
> This proposal does not appear to conflict with the current specifications.
> It does however appear to offer a way to enhance the usability of vcards
> and provide consumers of the information with the assurance that it was
> generated correctly.
>
>
> --
>
> Mike Douglass                           douglm@rpi.edu
> Senior Systems Programmer
> Communication & Collaboration Technologies      518 276 6780(voice) 2809
> (fax)
> Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180
>
>
> _______________________________________________
> VCARDDAV mailing list
> VCARDDAV@ietf.org
> https://www.ietf.org/mailman/listinfo/vcarddav
>
>