jCal: The JSON format for iCalendar
draft-ietf-jcardcal-jcal-09

The information below is for an old version of the document
Document Type Active Internet-Draft (jcardcal WG)
Authors Philipp Kewisch  , Cyrus Daboo  , Mike Douglass 
Last updated 2014-03-24 (latest revision 2014-02-19)
Replaces draft-kewisch-et-al-icalendar-in-json
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized 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 IESG Evaluation
Consensus Boilerplate Yes
Telechat date
Needs 8 more YES or NO OBJECTION positions to pass.
Responsible AD Pete Resnick
Send notices to jcardcal-chairs@tools.ietf.org, draft-ietf-jcardcal-jcal@tools.ietf.org, jcardcal@ietf.org
IANA IANA review state IANA OK - Actions Needed
JSON data formats for vCard and iCalendar                     P. Kewisch
Internet-Draft                                                   Mozilla
Intended status: Standards Track                                C. Daboo
Expires: August 22, 2014                                     Apple, Inc.
                                                             M. Douglass
                                                                     RPI
                                                       February 18, 2014

                  jCal: The JSON format for iCalendar
                      draft-ietf-jcardcal-jcal-09

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 Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 22, 2014.

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

Kewisch, et al.         Expires August 22, 2014                 [Page 1]
Internet-Draft                    jCal                     February 2014

   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.

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 (RFC5545 section 3.4)  . . .   5
     3.3.  Components (RFC5545 section 3.6)  . . . . . . . . . . . .   6
     3.4.  Properties (RFC5545 section 3.7 and 3.8)  . . . . . . . .   6
       3.4.1.  Special Cases for Properties  . . . . . . . . . . . .   7
         3.4.1.1.  GEO Property (RFC5545 Section 3.8.1.6)  . . . . .   8
         3.4.1.2.  REQUEST-STATUS Property (RFC5545 Section 3.8.8.3)   8
     3.5.  Parameters (RFC5545 section 3.2)  . . . . . . . . . . . .   9
       3.5.1.  VALUE parameter . . . . . . . . . . . . . . . . . . .  10
       3.5.2.  Multi-value Parameters  . . . . . . . . . . . . . . .  11
     3.6.  Values (RFC5545 section 3.3)  . . . . . . . . . . . . . .  11
       3.6.1.  Binary (RFC5545 section 3.3.1)  . . . . . . . . . . .  12
       3.6.2.  Boolean  (RFC5545 section 3.3.2)  . . . . . . . . . .  12
       3.6.3.  Calendar User Address (RFC5545 section 3.3.3) . . . .  12
       3.6.4.  Date (RFC5545 section 3.3.4)  . . . . . . . . . . . .  12
       3.6.5.  Date-Time (RFC5545 section 3.3.5) . . . . . . . . . .  13
       3.6.6.  Duration (RFC5545 section 3.3.6)  . . . . . . . . . .  13
       3.6.7.  Float (RFC5545 section 3.3.7) . . . . . . . . . . . .  14
       3.6.8.  Integer (RFC5545 section 3.3.8) . . . . . . . . . . .  14
       3.6.9.  Period of Time (RFC5545 section 3.3.9)  . . . . . . .  14
       3.6.10. Recurrence Rule (RFC5545 section 3.3.10)  . . . . . .  15
       3.6.11. Text (RFC5545 section 3.3.11) . . . . . . . . . . . .  16
       3.6.12. Time (RFC5545 section 3.3.12) . . . . . . . . . . . .  16
       3.6.13. URI (RFC5545 section 3.3.13)  . . . . . . . . . . . .  17
       3.6.14. UTC Offset (RFC5545 section 3.3.14) . . . . . . . . .  17
     3.7.  Extensions  . . . . . . . . . . . . . . . . . . . . . . .  17
   4.  Converting from jCal into iCalendar . . . . . . . . . . . . .  18
   5.  Handling Unrecognized Properties or Parameters  . . . . . . .  18
     5.1.  Converting iCalendar into jCal  . . . . . . . . . . . . .  19
     5.2.  Converting jCal into iCalendar  . . . . . . . . . . . . .  19
Show full document text