This specification describes a new property for vCard Format Specification
© 2013 The Calendaring and Scheduling Consortium, Inc.
This document is not a CalConnect Standard. It is distributed for review and comment, and is subject to change without notice and may not be referred to as a Standard. Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from the address below.
The Calendaring and Scheduling Consortium, Inc.
4390 Chaffin Lane
McKinleyville
California 95519
United States of America
www.calconnect.org
This specification describes a new property for vCard Format Specification
The objectclass concept is used in ldap to allow the specification of a set of properties which describe a given type of object. For example, a schedulable entity SHOULD contain some form of contact and the absence of the AUTOSCHEDULE property implies certain defaults.
Furthermore the OBJECTCLASS property allows for simple searching for a particular class of entry. If we are trying to book a room for example, the query only needs to specify an OBJECTCLASS of schedulable and the type of entry (that is, a room).
Without the OBJECTCLASS property it may be hard to determine that a room is actually schedulable. The resence of an email address does not guarantee that an entity is schedulable. Current scheduling systems also work asynchronously. The user may create scheduling invitations only to learn later on that the scheduled entity is not going to reply.
An ldap objectclass may be of 3 kinds, structural, abstract and auxiliary. The vcard KIND property is equivalent to the structural objectclass in that a vcard can be of only one kind. The kind requires that certain properties be present and also defines defaults for absent properties.
The OBJECTCLASS property defined here is equivalent in many ways to the auxiliary objectclass in ldap. They are not related to each other in some hierarchy and may overlap in their use of properties.
Objectclass definitions can only specify properties which MUST, SHOULD or MAY be present. They cannot disallow the use of properties as these may be required by another objectclass.
This specification describes a new property for vCard Format Specification
No terms and definitions are listed in this document.
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in
Format and cardinality of new vCard properties are defined as described in
OBJECTCLASS
To specify the objectclass for this vcard.
IANA value.
*
None.
schedulable
This property MAY be present 1 or more times. For each occurrence of the property the vcard MUST conform to the specification for that objectclass.
These examples do not draw on any currently defined objectclass but are intended to indicate some uses. Properties used here may not be defined in any specification.
The eduperson ldap objectclass provides for a number of attributes considered useful for interaction between members of educational organizations. A corresponding vcard objectclass would allow for better mappping of ldap directories onto a vcard representation.
The 201203 specification of the LDAP objectclass for reference. Note that all attributes are MAY so would have a vcard cardinality of *1 or *.
A vcard mapping would, where possible use existing vcard properties. Where not possible new properties could be defined.
A schedulable entity can be scheduled for meetings (as a person) or for use (as a resource). For a scheduling system to be able to usefully manage the schedule it needs specific information.
At the very least there needs to be some form of calendar user address. It’s useful to know whether requests can be auto accepted if the slot is available.
Building on the previous example we’ll make Jack schedulable.
As this document only defines a schema related property and does not refer to the actual storage mechanism itself, no special security considerations are required as part of this document.
New objectclass values will be defined according to the process specified in
This specification is a result of discussions that took place within the Calendaring and Scheduling Consortium’s Resource Technical Committee. The authors thank the participants of that group.
The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
This memo defines three mechanisms for obtaining a URI to a user’s calendar and free/busy time. [STANDARDS-TRACK]
This document defines a date and time format for use in Internet protocols that is a profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.
This document creates a registry for describing the types of places a human or end system might be found. The registry is then referenced by other protocols that need a common set of location terms as protocol constants. Examples of location terms defined in this document include aircraft, office, and train station. [STANDARDS-TRACK]
This document defines the vCard data format for representing and exchanging a variety of information about individuals and other entities (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.). This document obsoletes RFCs 2425, 2426, and 4770, and updates RFC 2739. [STANDARDS-TRACK]