iCalendar v2.0 Formal Public Identifier
draft-ietf-calsch-icalfpi-01
| Document | Type |
Expired Internet-Draft
(calsch WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Paul E. Hoffman , Frank Dawson | ||
| Last updated | 1999-04-11 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
The IETF has defined a standard format for exchanging calendaring and scheduling data, called iCalendar. This format is useful for exchange of personal calendar data across the Internet, as well as in non- Internet environments. In a number of environments where the iCalendar will be used, the format type and version needs to be identified. For example, when registering the iCalendar as a format for memory-based 'clipboard' or 'drag/drop' user interface interactions. For these cases, a definitive formal public identifier (FPI) for the iCalendar will be required. This memo defined the FPI to be used when referring to the version 2.0 (the value in the 'VERSION' property) of the iCalendar format.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)