jCard: The JSON Format for vCard
draft-ietf-jcardcal-jcard-07

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>,
    jcardcal mailing list <jcardcal@ietf.org>,
    jcardcal chair <jcardcal-chairs@tools.ietf.org>
Subject: Protocol Action: 'jCard: The JSON format for vCard' to Proposed Standard (draft-ietf-jcardcal-jcard-07.txt)

The IESG has approved the following document:
- 'jCard: The JSON format for vCard'
  (draft-ietf-jcardcal-jcard-07.txt) as Proposed Standard

This document is the product of the JSON data formats for vCard and
iCalendar Working Group.

The IESG contact persons are Pete Resnick and Barry Leiba.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-jcardcal-jcard/

Ballot Text

Technical Summary

   The document defines "jCard", which is a JSON format for vCard
   [RFC6350] data.

   The main advantage of using a JSON-based format over the classic
   vCard format is easier processing for JavaScript based widgets and
   libraries, especially in the scope of web-based applications.

   The jCard format is designed to be semantically equivalent to the
   vCard format, and conversion between the formats can be done without
   loss.

   Finally, the jCard format is designed to be easily used by a similar
   JSON-based format for calendar data: jCal. The latter format is still
   under development, but is expected to be finalized soon after
   finalization of jCard.

Working Group Summary

   Since the document's WG adoption on 25 March 2013, it has been widely
   discussed on the mailing list. In addition, other working groups have
   been consulted. The IETF working groups are SCIM, WEIRDS and CALSIFY.
   In addition, we have contacted W3C public-contacts-cord and the
   portablecontacts Google group. In-dept comments have been received
   from WEIRDS and CALSIFY. WEIRDS has a jCal example in its
   draft-ietf-json-response.

   All technical issues raised on the mailing list have been resolved.
   The topics have not been controversial, although several topics
   required some rounds of discussion. Topics included the format for
   date and time, handling of default values when converting between
   vCard and jCard, structured values and grouping.

Document Quality

   Section 6 of the draft mentions three implementations. These are
   ICAL.js, Py Calendar and ez-vcard. The implementations have led to
   some discussions on the list, resulting in clarifications in the
   text.

Personnel

   Shepherd: Bert Greevenbosch
   AD: Pete Resnick

RFC Editor Note