jCal: The JSON Format for iCalendar
draft-ietf-jcardcal-jcal-10
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2014-05-29
|
10 | (System) | RFC Editor state changed to AUTH48-DONE from AUTH48 |
2014-05-23
|
10 | (System) | RFC Editor state changed to AUTH48 from RFC-EDITOR |
2014-05-05
|
10 | (System) | RFC Editor state changed to RFC-EDITOR from EDIT |
2014-04-04
|
10 | Robert Sparks | Request for Last Call review by GENART Completed: Ready with Nits. Reviewer: Robert Sparks. |
2014-04-03
|
10 | Gunter Van de Velde | Closed request for Last Call review by OPSDIR with state 'No Response' |
2014-04-02
|
10 | (System) | IANA Action state changed to RFC-Ed-Ack from Waiting on RFC Editor |
2014-04-01
|
10 | (System) | IANA Action state changed to Waiting on RFC Editor from Waiting on Authors |
2014-04-01
|
10 | (System) | IANA Action state changed to Waiting on Authors from In Progress |
2014-04-01
|
10 | Amy Vezza | IESG state changed to RFC Ed Queue from Approved-announcement sent |
2014-03-31
|
10 | (System) | RFC Editor state changed to EDIT |
2014-03-31
|
10 | (System) | Announcement was received by RFC Editor |
2014-03-31
|
10 | Pete Resnick | Notification list changed to : jcardcal-chairs@tools.ietf.org, draft-ietf-jcardcal-jcal@tools.ietf.org |
2014-03-31
|
10 | (System) | IANA Action state changed to In Progress |
2014-03-31
|
10 | Amy Vezza | IESG state changed to Approved-announcement sent from Approved-announcement to be sent |
2014-03-31
|
10 | Amy Vezza | IESG has approved the document |
2014-03-31
|
10 | Amy Vezza | Closed "Approve" ballot |
2014-03-31
|
10 | Amy Vezza | Ballot approval text was generated |
2014-03-27
|
10 | Cindy Morgan | IESG state changed to Approved-announcement to be sent from IESG Evaluation |
2014-03-27
|
10 | Spencer Dawkins | [Ballot Position Update] New position, No Objection, has been recorded for Spencer Dawkins |
2014-03-27
|
10 | Amanda Baber | IANA Review state changed to IANA OK - Actions Needed from Version Changed - Review Needed |
2014-03-26
|
10 | Joel Jaeggli | [Ballot Position Update] New position, No Objection, has been recorded for Joel Jaeggli |
2014-03-26
|
10 | Barry Leiba | [Ballot comment] I very much like this document, and have switched to "Yes". Thanks for resolving my DISCUSS and considering my other comments. |
2014-03-26
|
10 | Barry Leiba | [Ballot Position Update] Position for Barry Leiba has been changed to Yes from Discuss |
2014-03-26
|
10 | Richard Barnes | [Ballot Position Update] New position, Yes, has been recorded for Richard Barnes |
2014-03-26
|
10 | Pete Resnick | Ballot writeup was changed |
2014-03-26
|
10 | Philipp Kewisch | IANA Review state changed to Version Changed - Review Needed from IANA OK - Actions Needed |
2014-03-26
|
10 | Philipp Kewisch | New version available: draft-ietf-jcardcal-jcal-10.txt |
2014-03-25
|
09 | Jari Arkko | [Ballot comment] Some changes are being discussed due to Robert Spark's gen-art review, but I do not see a new draft. Shouldn't that appear before … [Ballot comment] Some changes are being discussed due to Robert Spark's gen-art review, but I do not see a new draft. Shouldn't that appear before we make the final approval of this document? |
2014-03-25
|
09 | Jari Arkko | [Ballot Position Update] New position, No Objection, has been recorded for Jari Arkko |
2014-03-25
|
09 | Benoît Claise | [Ballot Position Update] New position, No Objection, has been recorded for Benoit Claise |
2014-03-25
|
09 | Alia Atlas | [Ballot Position Update] New position, No Objection, has been recorded for Alia Atlas |
2014-03-24
|
09 | Stephen Farrell | [Ballot comment] section 1: this is odd: "Extensions to the underlying iCalendar specification must not lead to requiring an update to jCal." How are you … [Ballot comment] section 1: this is odd: "Extensions to the underlying iCalendar specification must not lead to requiring an update to jCal." How are you going to prevent that happening? I think the best you can do is point out how such an extension could break jcal and recommend to not do that. |
2014-03-24
|
09 | Stephen Farrell | [Ballot Position Update] New position, No Objection, has been recorded for Stephen Farrell |
2014-03-24
|
09 | Kathleen Moriarty | [Ballot comment] Thanks for addressing the SecDir review comments. |
2014-03-24
|
09 | Kathleen Moriarty | [Ballot Position Update] New position, No Objection, has been recorded for Kathleen Moriarty |
2014-03-24
|
09 | Brian Haberman | [Ballot Position Update] New position, No Objection, has been recorded for Brian Haberman |
2014-03-23
|
09 | Martin Stiemerling | [Ballot Position Update] New position, No Objection, has been recorded for Martin Stiemerling |
2014-03-23
|
09 | Alissa Cooper | [Ballot comment] I'm good with this assuming the gen-art points and Barry's issues get resolved. One nit in section 3.5.2: "To ease processing in jCal, … [Ballot comment] I'm good with this assuming the gen-art points and Barry's issues get resolved. One nit in section 3.5.2: "To ease processing in jCal, the value to such parameters MUST be represented in an array containing the separated values." I think this is supposed to say "of such parameters". |
2014-03-23
|
09 | Alissa Cooper | [Ballot Position Update] New position, No Objection, has been recorded for Alissa Cooper |
2014-03-23
|
09 | Adrian Farrel | [Ballot comment] To update and support Barry's Discuss, RFC 7158 and RFC 7159 have now been published. |
2014-03-23
|
09 | Adrian Farrel | [Ballot Position Update] New position, No Objection, has been recorded for Adrian Farrel |
2014-03-21
|
09 | Barry Leiba | [Ballot discuss] I very much like this document, and will switch to "Yes" after we resolve a couple of easy points. RFC 4627 is clearly … [Ballot discuss] I very much like this document, and will switch to "Yes" after we resolve a couple of easy points. RFC 4627 is clearly a normative reference, not an informative one. Apart from that, the replacement to 4627 is in the RFC Editor queue, and will become an RFC before this document does. I strongly suggest replacing the 4627 reference with one to the I-D, so the new RFC gets dropped in by the RFC Editor. (If you do that, the eval() advice in Section 6 needs to change accordingly.) -- Section 4 -- Character escaping and line folding MUST be applied to the resulting iCalendar data as required by [RFC5545] and [RFC6868]. The line folding part is in conflict with Section 3.1: The reverse order applies when converting from jCal to iCalendar. First, JSON escaping MUST be unescaped. Afterwards, iCalendar escaping MUST be applied. Finally, long lines SHOULD be folded as described in [RFC5545]. Which is meant, SHOULD (Section 3.1) or MUST (Section 4) ? |
2014-03-21
|
09 | Barry Leiba | [Ballot comment] Non-blocking comments to consider: -- Appendix B -- I'm quite unhappy with using raw ABNF to describe JSON payloads. You're duplicating the ABNF … [Ballot comment] Non-blocking comments to consider: -- Appendix B -- I'm quite unhappy with using raw ABNF to describe JSON payloads. You're duplicating the ABNF in the JSON spec, and it's prone to errors, not to mention being hard to read. What you want to do here is to specify JSON structures, not to specify the JSON syntax itself. Look at RFC 7071 Section 6.2 for one way that this has been handled. http://tools.ietf.org/html/draft-newton-json-content-rules-01 specifies another way. Please consider changing to one of those. I know that Cyrus has responded that he's reluctant to change this now, but please consider it: I think this section is essentially useless as it stands. On the other hand, note that this is a non-blocking comment, so I will not hold anything up if you decide to leave it be. -- Section 3 -- Pedantic nit pet peeve: In [RFC5545], iCalendar objects are comprised of a set of "components", "properties", "parameters" and "values". In correct usage, the whole "comprises" the parts. So: NEW In [RFC5545], an iCalendar object comprises a set of "components", "properties", "parameters" and "values". END (If you don't like that, use "is composed of" instead of "is comprosed of".) |
2014-03-21
|
09 | Barry Leiba | [Ballot Position Update] New position, Discuss, has been recorded for Barry Leiba |
2014-03-21
|
09 | Pete Resnick | Ballot has been issued |
2014-03-21
|
09 | Pete Resnick | Ballot writeup was changed |
2014-03-21
|
09 | Pete Resnick | [Ballot comment] Sounds like the document editor has the GenArt and SecDir reviews in hand and is working through the issues. No showstoppers in there … [Ballot comment] Sounds like the document editor has the GenArt and SecDir reviews in hand and is working through the issues. No showstoppers in there as far as I see, but we will make sure to address those before publication. |
2014-03-21
|
09 | Pete Resnick | Ballot comment text updated for Pete Resnick |
2014-03-21
|
09 | Pete Resnick | Notification list changed to : jcardcal-chairs@tools.ietf.org, draft-ietf-jcardcal-jcal@tools.ietf.org, jcardcal@ietf.org |
2014-03-21
|
09 | Pete Resnick | IESG state changed to IESG Evaluation from Waiting for AD Go-Ahead |
2014-03-21
|
09 | Pete Resnick | Ballot has been issued |
2014-03-21
|
09 | Pete Resnick | [Ballot Position Update] New position, Yes, has been recorded for Pete Resnick |
2014-03-21
|
09 | Pete Resnick | Created "Approve" ballot |
2014-03-20
|
09 | Jean Mahoney | Request for Last Call review by GENART is assigned to Robert Sparks |
2014-03-20
|
09 | Jean Mahoney | Request for Last Call review by GENART is assigned to Robert Sparks |
2014-03-12
|
09 | (System) | IESG state changed to Waiting for AD Go-Ahead from In Last Call |
2014-03-11
|
09 | Robert Sparks | Request for Last Call review by GENART Completed: Ready with Nits. Reviewer: Robert Sparks. |
2014-03-10
|
09 | (System) | IANA Review state changed to IANA OK - Actions Needed from IANA - Review Needed |
2014-03-10
|
09 | Pearl Liang | IESG/Authors/WG Chairs: IANA has reviewed draft-ietf-jcardcal-jcal-09. Authors should review the comments and/or questions below. Please report any inaccuracies and respond to any questions as soon … IESG/Authors/WG Chairs: IANA has reviewed draft-ietf-jcardcal-jcal-09. Authors should review the comments and/or questions below. Please report any inaccuracies and respond to any questions as soon as possible. IANA's reviewer has the following comments/questions: IANA understands that, upon approval of this document, there are two actions which IANA must complete. ACTION 1: This document requests adding a media type to the applications media type registry located at: http://www.iana.org/assignments/media-types/application/index.html The media type to be added are: calendar+json ACTION: 2: in the Value Data Types Values subregistry of the iCalendar Element Registries located at: http://www.iana.org/assignments/icalendar the following three registrations will be added: Value Data Type: UNKNOWN Status: Reserved - Do not use Reference: [ RFC-to-be, section 5 ] IANA understands these two actions to be the only one required upon approval of this document. Note: The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed. |
2014-03-05
|
09 | Cindy Morgan | Removed telechat returning item indication |
2014-03-05
|
09 | Cindy Morgan | Telechat date has been changed to 2014-03-27 from 2014-03-20 |
2014-02-27
|
09 | Tero Kivinen | Request for Last Call review by SECDIR Completed: Has Nits. Reviewer: Klaas Wierenga. |
2014-02-21
|
09 | Gunter Van de Velde | Request for Last Call review by OPSDIR is assigned to Benson Schliesser |
2014-02-21
|
09 | Gunter Van de Velde | Request for Last Call review by OPSDIR is assigned to Benson Schliesser |
2014-02-20
|
09 | Jean Mahoney | Request for Last Call review by GENART is assigned to Robert Sparks |
2014-02-20
|
09 | Jean Mahoney | Request for Last Call review by GENART is assigned to Robert Sparks |
2014-02-20
|
09 | Tero Kivinen | Request for Last Call review by SECDIR is assigned to Klaas Wierenga |
2014-02-20
|
09 | Tero Kivinen | Request for Last Call review by SECDIR is assigned to Klaas Wierenga |
2014-02-19
|
09 | Pete Resnick | Changed consensus to Yes from Unknown |
2014-02-19
|
09 | Amy Vezza | IANA Review state changed to IANA - Review Needed |
2014-02-19
|
09 | Amy Vezza | The following Last Call announcement was sent out: From: The IESG To: IETF-Announce CC: Reply-To: ietf@ietf.org Sender: Subject: Last Call: (jCal: The JSON format for … The following Last Call announcement was sent out: From: The IESG To: IETF-Announce CC: Reply-To: ietf@ietf.org Sender: Subject: Last Call: (jCal: The JSON format for iCalendar) to Proposed Standard The IESG has received a request from the JSON data formats for vCard and iCalendar WG (jcardcal) to consider the following document: - 'jCal: The JSON format for iCalendar' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2014-03-12. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. 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. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-jcardcal-jcal/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-jcardcal-jcal/ballot/ No IPR declarations have been submitted directly on this I-D. |
2014-02-19
|
09 | Amy Vezza | IESG state changed to In Last Call from Last Call Requested |
2014-02-19
|
09 | Pete Resnick | Last call was requested |
2014-02-19
|
09 | Pete Resnick | Ballot approval text was generated |
2014-02-19
|
09 | Pete Resnick | IESG state changed to Last Call Requested from AD Evaluation::AD Followup |
2014-02-19
|
09 | Pete Resnick | Last call announcement was changed |
2014-02-19
|
09 | Pete Resnick | Last call announcement was generated |
2014-02-19
|
09 | (System) | Sub state has been changed to AD Followup from Revised ID Needed |
2014-02-19
|
09 | Cindy Morgan | New revision available |
2014-02-18
|
08 | Pete Resnick | Ballot writeup was changed |
2014-02-18
|
08 | Pete Resnick | Ballot writeup was generated |
2014-02-18
|
08 | Pete Resnick | Last call announcement was generated |
2014-02-18
|
08 | Pete Resnick | Placed on agenda for telechat - 2014-03-20 |
2014-02-09
|
08 | Pete Resnick | IESG state changed to AD Evaluation::Revised I-D Needed from AD Evaluation |
2014-01-27
|
08 | Pete Resnick | State changed to AD Evaluation from Publication Requested |
2014-01-06
|
08 | Peter Saint-Andre | Shepherd's write-up for draft-ietf-jcardcal-jcal-08 1. Summary The shepherd for this document is Peter Saint-Andre. The responsible Area Director is Pete Resnick. This document defines an … Shepherd's write-up for draft-ietf-jcardcal-jcal-08 1. Summary The shepherd for this document is Peter Saint-Andre. The responsible Area Director is Pete Resnick. This document defines an alternative representation for iCalendar data (RFC 5545), structured using the JSON data interchange format (RFC 4627). Defining this "jCal" representation for iCalendar allows easier integration of such data with web or other Javascript-based applications, and other JSON-based protocols being developed within the IETF. Because jCal is amenable to multiple technical implementations and interoperability testing, the document is Standards Track. 2. Review and Consensus The document emerged from discussion within the XML-JSON technical committee of the Calendaring and Scheduling Consortium, where it experienced early review from at least three participants in that forum. Upon adoption by the JCARDCAL WG, another half a dozen individuals reviewed and commented on the specification. Although it might appear that the document has not received "wide" review, the population of implementers interested in the topic is relatively small (only ~50 people are subscribed to the JCARDCAL WG discussion list). In addition, the jCal specification was preceded into WG Last Call, IETF Last Call, and IESG review by "jCard", a sister specification defining the JSON representation of vCard data. As a result, many issues surrounding jCal were first ironed out through work on jCard (e.g., handling of unknown structured values), thus leading to fewer open issues related to jCal specifically. The calendaring and scheduling community is very interested in this specification, there are several implementations, and there is good consensus to advance the specification to Proposed Standard. 3. Intellectual Property All three of the authors have confirmed that they do not have direct, personal knowledge of any IPR related to this document. There are no IPR disclosures related to this document. 4. Other Points According to the IDnits tool, there are no downward references. This document adds one entry to the iCalendar Data Types registry (parallel to the "UNKNOWN" entry already added to the vCard Value Data Types registry) and also registers a new media type "calendar+json". Review of the media type registration was requested on the media-types list on January 6, 2014: http://www.ietf.org/mail-archive/web/media-types/current/msg00563.html There was no special controversy about this specification within the JCARDCAL WG, and in the shepherd's opinion both jCard and jCal are rather straightforward alternative representations of existing data models. The two main points of focus in this work have been ensuring that the JSON representations use JSON in appropriate ways and are consistent with the existing textual and XML representations. Much attention has been paid to these issues within the JCARDCAL WG, and the shepherd is satisfied that these considerations have been addressed in draft-ietf-jcardcal-jcal-08. END |
2014-01-06
|
08 | Peter Saint-Andre | State Change Notice email list changed to jcardcal-chairs@tools.ietf.org, draft-ietf-jcardcal-jcal@tools.ietf.org |
2014-01-06
|
08 | Peter Saint-Andre | Responsible AD changed to Pete Resnick |
2014-01-06
|
08 | Peter Saint-Andre | IETF WG state changed to Submitted to IESG for Publication |
2014-01-06
|
08 | Peter Saint-Andre | IESG state changed to Publication Requested |
2014-01-06
|
08 | Peter Saint-Andre | Working group state set to Submitted to IESG for Publication |
2014-01-06
|
08 | Peter Saint-Andre | IESG state set to Publication Requested |
2014-01-06
|
08 | Peter Saint-Andre | IESG process started in state Publication Requested |
2014-01-06
|
08 | Peter Saint-Andre | Changed document writeup |
2013-12-09
|
08 | Philipp Kewisch | New version available: draft-ietf-jcardcal-jcal-08.txt |
2013-08-14
|
07 | Peter Saint-Andre | IETF WG state changed to Waiting for WG Chair Go-Ahead from In WG Last Call |
2013-08-14
|
07 | Peter Saint-Andre | IETF WG state changed to In WG Last Call from WG Document |
2013-08-14
|
07 | Peter Saint-Andre | Intended Status changed to Proposed Standard from None |
2013-08-14
|
07 | Peter Saint-Andre | Document shepherd changed to Peter Saint-Andre |
2013-07-15
|
07 | Philipp Kewisch | New version available: draft-ietf-jcardcal-jcal-07.txt |
2013-07-14
|
06 | Philipp Kewisch | New version available: draft-ietf-jcardcal-jcal-06.txt |
2013-07-03
|
05 | Philipp Kewisch | New version available: draft-ietf-jcardcal-jcal-05.txt |
2013-06-10
|
04 | Philipp Kewisch | New version available: draft-ietf-jcardcal-jcal-04.txt |
2013-06-09
|
03 | Philipp Kewisch | New version available: draft-ietf-jcardcal-jcal-03.txt |
2013-04-30
|
02 | Philipp Kewisch | New version available: draft-ietf-jcardcal-jcal-02.txt |
2013-04-02
|
01 | Philipp Kewisch | New version available: draft-ietf-jcardcal-jcal-01.txt |
2013-03-26
|
00 | Philipp Kewisch | New version available: draft-ietf-jcardcal-jcal-00.txt |