The vObject Model and vFormat Syntax
draft-calconnect-vobject-vformat-04
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Ronald Henry Tse , Peter Tam , Kenneth Murchison , Michael Douglass | ||
Last updated | 2018-12-09 (Latest revision 2018-06-07) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document specifies the vObject data model and its corresponding syntax vFormat. vObject represents the generalized data model, and vFormat the generalized data format, of the following specifications and fully covers them: o RFC 6350, vCard version 4.0: the VCARD component; o RFC 5545, Internet Calendaring and Scheduling Core Object Specification (iCalendar): the VCALENDAR, VEVENT, VJOURNAL, VFREEBUSY, VTIMEZONE, VALARM, VTODO, STANDARD and DAYLIGHT components; o RFC 7953, Calendar Availability Extensions: the VAVAILABILITY and AVAILABLE components; o I-Ddaboo-icalendar-vpatch, iCalendar Patching: the VPATCH component; and o alternative formats for iCalendar and vCard, including RFC 6321, xCal; RFC 7265, jCal; RFC 6351, xCard; and RFC 7095, jCard. This work is produced by the CalConnect TC-VCARD and TC-CALENDAR committees.
Authors
Ronald Henry Tse
Peter Tam
Kenneth Murchison
Michael Douglass
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)