jCal: The JSON Format for iCalendar
RFC 7265
Document | Type |
RFC - Proposed Standard
(May 2014; Errata)
Updated by RFC 7529
|
|
---|---|---|---|
Last updated | 2016-11-11 | ||
Replaces | draft-kewisch-et-al-icalendar-in-json | ||
Stream | IETF | ||
Formats | plain text pdf html bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Peter Saint-Andre | ||
Shepherd write-up | Show (last changed 2014-01-06) | ||
IESG | IESG state | RFC 7265 (Proposed Standard) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Pete Resnick | ||
Send notices to | (None) | ||
IANA | IANA review state | IANA OK - Actions Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) P. Kewisch Request for Comments: 7265 Mozilla Category: Standards Track C. Daboo ISSN: 2070-1721 Apple, Inc. M. Douglass RPI May 2014 jCal: The JSON Format for iCalendar Abstract This specification defines "jCal", a JSON format for iCalendar data. The iCalendar data format is a text format for capturing and exchanging information normally stored within a calendaring and scheduling application, for example, tasks and events. JSON is a lightweight, text-based, language-independent data interchange format commonly used in Internet applications. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7265. Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Kewisch, et al. Standards Track [Page 1] RFC 7265 jCal May 2014 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions Used in This Document . . . . . . . . . . . . . . 4 3. Converting from iCalendar to jCal . . . . . . . . . . . . . . 4 3.1. Pre-processing . . . . . . . . . . . . . . . . . . . . . 4 3.2. iCalendar Stream and Objects (RFC 5545, Section 3.4) . . 5 3.3. Components (RFC 5545, Section 3.6) . . . . . . . . . . . 6 3.4. Properties (RFC 5545, Sections 3.7 and 3.8) . . . . . . . 6 3.4.1. Special Cases for Properties . . . . . . . . . . . . 8 3.4.1.1. GEO Property (RFC 5545, Section 3.8.1.6) . . . . 8 3.4.1.2. REQUEST-STATUS Property (RFC 5545, Section 3.8.8.3) . . . . . . . . . . . . . . . . . . . . 8 3.5. Parameters (RFC 5545, Section 3.2) . . . . . . . . . . . 9 3.5.1. VALUE Parameter . . . . . . . . . . . . . . . . . . . 10 3.5.2. Multi-value Parameters . . . . . . . . . . . . . . . 11 3.6. Values (RFC 5545, Section 3.3) . . . . . . . . . . . . . 11 3.6.1. Binary (RFC 5545, Section 3.3.1) . . . . . . . . . . 12 3.6.2. Boolean (RFC 5545, Section 3.3.2) . . . . . . . . . 12 3.6.3. Calendar User Address (RFC 5545, Section 3.3.3) . . . 12 3.6.4. Date (RFC 5545, Section 3.3.4) . . . . . . . . . . . 12 3.6.5. Date-Time (RFC 5545, Section 3.3.5) . . . . . . . . . 13 3.6.6. Duration (RFC 5545, Section 3.3.6) . . . . . . . . . 13 3.6.7. Float (RFC 5545, Section 3.3.7) . . . . . . . . . . . 14 3.6.8. Integer (RFC 5545, Section 3.3.8) . . . . . . . . . . 14 3.6.9. Period of Time (RFC 5545, Section 3.3.9) . . . . . . 14 3.6.10. Recurrence Rule (RFC 5545, Section 3.3.10) . . . . . 15 3.6.11. Text (RFC 5545, Section 3.3.11) . . . . . . . . . . . 16 3.6.12. Time (RFC 5545, Section 3.3.12) . . . . . . . . . . . 16 3.6.13. URI (RFC 5545, Section 3.3.13) . . . . . . . . . . . 17 3.6.14. UTC Offset (RFC 5545, Section 3.3.14) . . . . . . . . 17 3.7. Extensions . . . . . . . . . . . . . . . . . . . . . . . 17 4. Converting from jCal into iCalendar . . . . . . . . . . . . . 17 5. Handling Unrecognized Properties or Parameters . . . . . . . 18 5.1. Converting iCalendar into jCal . . . . . . . . . . . . . 18 5.2. Converting jCal into iCalendar . . . . . . . . . . . . . 19 5.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . 19 6. Security Considerations . . . . . . . . . . . . . . . . . . . 20Show full document text