draft-ietf-calext-jscalendar-22.txt   draft-ietf-calext-jscalendar-23.txt 
Calendaring extensions N. Jenkins Calendaring extensions N. Jenkins
Internet-Draft R. Stepanek Internet-Draft R. Stepanek
Intended status: Standards Track Fastmail Intended status: Standards Track Fastmail
Expires: June 7, 2020 December 05, 2019 Expires: August 21, 2020 February 18, 2020
JSCalendar: A JSON representation of calendar data JSCalendar: A JSON representation of calendar data
draft-ietf-calext-jscalendar-22 draft-ietf-calext-jscalendar-23
Abstract Abstract
This specification defines a data model and JSON representation of This specification defines a data model and JSON representation of
calendar data that can be used for storage and data exchange in a calendar data that can be used for storage and data exchange in a
calendaring and scheduling environment. It aims to be an calendaring and scheduling environment. It aims to be an
alternative, and over time successor to, the widely deployed alternative, and over time successor to, the widely deployed
iCalendar data format and to be unambiguous, extendable and simple to iCalendar data format and to be unambiguous, extendable and simple to
process. In contrast to the JSON-based jCal format, it is not a process. In contrast to the JSON-based jCal format, it is not a
direct mapping from iCalendar and expands semantics where direct mapping from iCalendar and expands semantics where
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 7, 2020. This Internet-Draft will expire on August 21, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 4, line 24 skipping to change at page 4, line 24
8.2.6. Initial Contents for the JSCalendar Properties 8.2.6. Initial Contents for the JSCalendar Properties
Registry . . . . . . . . . . . . . . . . . . . . . . 58 Registry . . . . . . . . . . . . . . . . . . . . . . 58
8.3. Creation of "JSCalendar Types" Registry . . . . . . . . . 65 8.3. Creation of "JSCalendar Types" Registry . . . . . . . . . 65
8.3.1. JMAP Types Registry Template . . . . . . . . . . . . 65 8.3.1. JMAP Types Registry Template . . . . . . . . . . . . 65
8.3.2. Initial Contents for the JSCalendar Types Registry . 65 8.3.2. Initial Contents for the JSCalendar Types Registry . 65
8.4. Creation of "JSCalendar Enum Values" Registry . . . . . . 67 8.4. Creation of "JSCalendar Enum Values" Registry . . . . . . 67
8.4.1. JMAP Enum Subregistry Creation Template . . . . . . . 67 8.4.1. JMAP Enum Subregistry Creation Template . . . . . . . 67
8.4.2. JMAP Enum Subregistry Template . . . . . . . . . . . 67 8.4.2. JMAP Enum Subregistry Template . . . . . . . . . . . 67
8.4.3. Initial Contents for the JSCalendar Enum Registry . . 68 8.4.3. Initial Contents for the JSCalendar Enum Registry . . 68
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 72 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 72
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 72 10. Informative References . . . . . . . . . . . . . . . . . . . 72
10.1. Normative References . . . . . . . . . . . . . . . . . . 72
10.2. Informative References . . . . . . . . . . . . . . . . . 75
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 75
1. Introduction 1. Introduction
This document defines a data model for calendar event and task This document defines a data model for calendar event and task
objects, or groups of such objects, in electronic calendar objects, or groups of such objects, in electronic calendar
applications and systems. It aims to be unambiguous, extendable and applications and systems. It aims to be unambiguous, extendable and
simple to process. simple to process.
The key design considerations for this data model are as follows: The key design considerations for this data model are as follows:
skipping to change at page 72, line 44 skipping to change at page 72, line 44
Table 14 Table 14
9. Acknowledgments 9. Acknowledgments
The authors would like to thank the members of CalConnect for their The authors would like to thank the members of CalConnect for their
valuable contributions. This specification originated from the work valuable contributions. This specification originated from the work
of the API technical committee of CalConnect, the Calendaring and of the API technical committee of CalConnect, the Calendaring and
Scheduling Consortium. Scheduling Consortium.
10. References 10. Informative References
10.1. Normative References
[COLORS] "CSS Color Module", <https://www.w3.org/TR/css-color-3/>. [COLORS] "CSS Color Module", <https://www.w3.org/TR/css-color-3/>.
[LINKRELS] [LINKRELS]
"IANA Link Relation Types", "IANA Link Relation Types",
<https://www.iana.org/assignments/link-relations/link- <https://www.iana.org/assignments/link-relations/link-
relations.xhtml>. relations.xhtml>.
[MIME] "IANA Media Types", <https://www.iana.org/assignments/
media-types/media-types.xhtml>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource
Locators", RFC 2392, DOI 10.17487/RFC2392, August 1998, Locators", RFC 2392, DOI 10.17487/RFC2392, August 1998,
<https://www.rfc-editor.org/info/rfc2392>. <https://www.rfc-editor.org/info/rfc2392>.
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:
skipping to change at page 75, line 26 skipping to change at page 75, line 22
DOI 10.17487/RFC8259, December 2017, DOI 10.17487/RFC8259, December 2017,
<https://www.rfc-editor.org/info/rfc8259>. <https://www.rfc-editor.org/info/rfc8259>.
[RFC8288] Nottingham, M., "Web Linking", RFC 8288, [RFC8288] Nottingham, M., "Web Linking", RFC 8288,
DOI 10.17487/RFC8288, October 2017, DOI 10.17487/RFC8288, October 2017,
<https://www.rfc-editor.org/info/rfc8288>. <https://www.rfc-editor.org/info/rfc8288>.
[TZDB] "IANA Time Zone Database", [TZDB] "IANA Time Zone Database",
<https://www.iana.org/time-zones>. <https://www.iana.org/time-zones>.
10.2. Informative References
[MIME] "IANA Media Types", <https://www.iana.org/assignments/
media-types/media-types.xhtml>.
Authors' Addresses Authors' Addresses
Neil Jenkins Neil Jenkins
Fastmail Fastmail
PO Box 234 PO Box 234
Collins St West Collins St West
Melbourne VIC 8007 Melbourne VIC 8007
Australia Australia
Email: neilj@fastmailteam.com Email: neilj@fastmailteam.com
 End of changes. 8 change blocks. 
15 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/