JSCalendar: A JSON Representation of Calendar Data
draft-ietf-calext-jscalendarbis-01
| Document | Type |
Expired Internet-Draft
(calext WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Neil Jenkins , Robert Stepanek | ||
| Last updated | 2024-11-03 (Latest revision 2022-10-27) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Dead 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
This specification defines a data model and JSON representation of calendar data that can be used for storage and data exchange in a calendaring and scheduling environment. It aims to be an alternative and, over time, successor to the widely deployed iCalendar data format. It also aims to be unambiguous, extendable, and simple to process. In contrast to the jCal format, which is also based on JSON, JSCalendar is not a direct mapping from iCalendar but defines the data model independently and expands semantics where appropriate. This specification obsoletes [RFC8984].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)