draft-ietf-calext-jscalendar-23.txt   draft-ietf-calext-jscalendar-24.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: August 21, 2020 February 18, 2020 Expires: August 23, 2020 February 20, 2020
JSCalendar: A JSON representation of calendar data JSCalendar: A JSON representation of calendar data
draft-ietf-calext-jscalendar-23 draft-ietf-calext-jscalendar-24
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
alternative, and over time successor to, the widely deployed and, over time, successor to the widely deployed iCalendar data
iCalendar data format and to be unambiguous, extendable and simple to format, and to be unambiguous, extendable, and simple to process. In
process. In contrast to the JSON-based jCal format, it is not a contrast to the jCal format, which is also JSON-based, JSCalendar is
direct mapping from iCalendar and expands semantics where not a direct mapping from iCalendar, but defines the data model
appropriate. independently and expands semantics where appropriate.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 August 21, 2020. This Internet-Draft will expire on August 23, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 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
skipping to change at page 2, line 14 skipping to change at page 2, line 14
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Motivation and Relation to iCalendar and jCal . . . . . . 5 1.1. Motivation and Relation to iCalendar and jCal . . . . . . 5
1.2. Notational Conventions . . . . . . . . . . . . . . . . . 6 1.2. Notational Conventions . . . . . . . . . . . . . . . . . 6
1.3. Type Signatures . . . . . . . . . . . . . . . . . . . . . 6 1.3. Type Signatures . . . . . . . . . . . . . . . . . . . . . 6
1.4. Data Types . . . . . . . . . . . . . . . . . . . . . . . 6 1.4. Data Types . . . . . . . . . . . . . . . . . . . . . . . 7
1.4.1. Int . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.4.1. Int . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4.2. UnsignedInt . . . . . . . . . . . . . . . . . . . . . 7 1.4.2. UnsignedInt . . . . . . . . . . . . . . . . . . . . . 7
1.4.3. UTCDateTime . . . . . . . . . . . . . . . . . . . . . 7 1.4.3. UTCDateTime . . . . . . . . . . . . . . . . . . . . . 7
1.4.4. LocalDateTime . . . . . . . . . . . . . . . . . . . . 7 1.4.4. LocalDateTime . . . . . . . . . . . . . . . . . . . . 7
1.4.5. Duration . . . . . . . . . . . . . . . . . . . . . . 7 1.4.5. Duration . . . . . . . . . . . . . . . . . . . . . . 7
1.4.6. SignedDuration . . . . . . . . . . . . . . . . . . . 8 1.4.6. SignedDuration . . . . . . . . . . . . . . . . . . . 8
1.4.7. Id . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.4.7. Id . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4.8. PatchObject . . . . . . . . . . . . . . . . . . . . . 9 1.4.8. PatchObject . . . . . . . . . . . . . . . . . . . . . 9
1.4.9. Time Zones . . . . . . . . . . . . . . . . . . . . . 9 1.4.9. Time Zones . . . . . . . . . . . . . . . . . . . . . 9
1.4.10. Relation . . . . . . . . . . . . . . . . . . . . . . 9 1.4.10. Relation . . . . . . . . . . . . . . . . . . . . . . 9
skipping to change at page 3, line 5 skipping to change at page 3, line 5
4.2.1. title . . . . . . . . . . . . . . . . . . . . . . . . 14 4.2.1. title . . . . . . . . . . . . . . . . . . . . . . . . 14
4.2.2. description . . . . . . . . . . . . . . . . . . . . . 15 4.2.2. description . . . . . . . . . . . . . . . . . . . . . 15
4.2.3. descriptionContentType . . . . . . . . . . . . . . . 15 4.2.3. descriptionContentType . . . . . . . . . . . . . . . 15
4.2.4. showWithoutTime . . . . . . . . . . . . . . . . . . . 15 4.2.4. showWithoutTime . . . . . . . . . . . . . . . . . . . 15
4.2.5. locations . . . . . . . . . . . . . . . . . . . . . . 15 4.2.5. locations . . . . . . . . . . . . . . . . . . . . . . 15
4.2.6. virtualLocations . . . . . . . . . . . . . . . . . . 17 4.2.6. virtualLocations . . . . . . . . . . . . . . . . . . 17
4.2.7. links . . . . . . . . . . . . . . . . . . . . . . . . 17 4.2.7. links . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2.8. locale . . . . . . . . . . . . . . . . . . . . . . . 19 4.2.8. locale . . . . . . . . . . . . . . . . . . . . . . . 19
4.2.9. keywords . . . . . . . . . . . . . . . . . . . . . . 19 4.2.9. keywords . . . . . . . . . . . . . . . . . . . . . . 19
4.2.10. categories . . . . . . . . . . . . . . . . . . . . . 19 4.2.10. categories . . . . . . . . . . . . . . . . . . . . . 19
4.2.11. color . . . . . . . . . . . . . . . . . . . . . . . . 19 4.2.11. color . . . . . . . . . . . . . . . . . . . . . . . . 20
4.3. Recurrence Properties . . . . . . . . . . . . . . . . . . 20 4.3. Recurrence Properties . . . . . . . . . . . . . . . . . . 20
4.3.1. recurrenceId . . . . . . . . . . . . . . . . . . . . 20 4.3.1. recurrenceId . . . . . . . . . . . . . . . . . . . . 20
4.3.2. recurrenceRules . . . . . . . . . . . . . . . . . . . 20 4.3.2. recurrenceRules . . . . . . . . . . . . . . . . . . . 20
4.3.3. recurrenceOverrides . . . . . . . . . . . . . . . . . 28 4.3.3. recurrenceOverrides . . . . . . . . . . . . . . . . . 28
4.3.4. excluded . . . . . . . . . . . . . . . . . . . . . . 29 4.3.4. excluded . . . . . . . . . . . . . . . . . . . . . . 30
4.4. Sharing and Scheduling Properties . . . . . . . . . . . . 30 4.4. Sharing and Scheduling Properties . . . . . . . . . . . . 30
4.4.1. priority . . . . . . . . . . . . . . . . . . . . . . 30 4.4.1. priority . . . . . . . . . . . . . . . . . . . . . . 30
4.4.2. freeBusyStatus . . . . . . . . . . . . . . . . . . . 30 4.4.2. freeBusyStatus . . . . . . . . . . . . . . . . . . . 30
4.4.3. privacy . . . . . . . . . . . . . . . . . . . . . . . 30 4.4.3. privacy . . . . . . . . . . . . . . . . . . . . . . . 30
4.4.4. replyTo . . . . . . . . . . . . . . . . . . . . . . . 32 4.4.4. replyTo . . . . . . . . . . . . . . . . . . . . . . . 32
4.4.5. participants . . . . . . . . . . . . . . . . . . . . 32 4.4.5. participants . . . . . . . . . . . . . . . . . . . . 32
4.5. Alerts Properties . . . . . . . . . . . . . . . . . . . . 37 4.5. Alerts Properties . . . . . . . . . . . . . . . . . . . . 37
4.5.1. useDefaultAlerts . . . . . . . . . . . . . . . . . . 37 4.5.1. useDefaultAlerts . . . . . . . . . . . . . . . . . . 37
4.5.2. alerts . . . . . . . . . . . . . . . . . . . . . . . 37 4.5.2. alerts . . . . . . . . . . . . . . . . . . . . . . . 37
4.6. Multilingual Properties . . . . . . . . . . . . . . . . . 39 4.6. Multilingual Properties . . . . . . . . . . . . . . . . . 39
4.6.1. localizations . . . . . . . . . . . . . . . . . . . . 39 4.6.1. localizations . . . . . . . . . . . . . . . . . . . . 39
4.7. Time Zone Properties . . . . . . . . . . . . . . . . . . 40 4.7. Time Zone Properties . . . . . . . . . . . . . . . . . . 40
4.7.1. timeZone . . . . . . . . . . . . . . . . . . . . . . 40 4.7.1. timeZone . . . . . . . . . . . . . . . . . . . . . . 40
4.7.2. timeZones . . . . . . . . . . . . . . . . . . . . . . 40 4.7.2. timeZones . . . . . . . . . . . . . . . . . . . . . . 40
5. Type-specific JSCalendar Properties . . . . . . . . . . . . . 42 5. Type-specific JSCalendar Properties . . . . . . . . . . . . . 43
5.1. JSEvent Properties . . . . . . . . . . . . . . . . . . . 42 5.1. JSEvent Properties . . . . . . . . . . . . . . . . . . . 43
5.1.1. start . . . . . . . . . . . . . . . . . . . . . . . . 42 5.1.1. start . . . . . . . . . . . . . . . . . . . . . . . . 43
5.1.2. duration . . . . . . . . . . . . . . . . . . . . . . 43 5.1.2. duration . . . . . . . . . . . . . . . . . . . . . . 43
5.1.3. status . . . . . . . . . . . . . . . . . . . . . . . 43 5.1.3. status . . . . . . . . . . . . . . . . . . . . . . . 43
5.2. JSTask Properties . . . . . . . . . . . . . . . . . . . . 43 5.2. JSTask Properties . . . . . . . . . . . . . . . . . . . . 44
5.2.1. due . . . . . . . . . . . . . . . . . . . . . . . . . 43 5.2.1. due . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.2.2. start . . . . . . . . . . . . . . . . . . . . . . . . 44 5.2.2. start . . . . . . . . . . . . . . . . . . . . . . . . 44
5.2.3. estimatedDuration . . . . . . . . . . . . . . . . . . 44 5.2.3. estimatedDuration . . . . . . . . . . . . . . . . . . 44
5.2.4. progress . . . . . . . . . . . . . . . . . . . . . . 44 5.2.4. progress . . . . . . . . . . . . . . . . . . . . . . 44
5.2.5. progressUpdated . . . . . . . . . . . . . . . . . . . 45 5.2.5. progressUpdated . . . . . . . . . . . . . . . . . . . 45
5.3. JSGroup Properties . . . . . . . . . . . . . . . . . . . 45 5.3. JSGroup Properties . . . . . . . . . . . . . . . . . . . 45
5.3.1. entries . . . . . . . . . . . . . . . . . . . . . . . 46 5.3.1. entries . . . . . . . . . . . . . . . . . . . . . . . 46
5.3.2. source . . . . . . . . . . . . . . . . . . . . . . . 46 5.3.2. source . . . . . . . . . . . . . . . . . . . . . . . 46
6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 46 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.1. Simple event . . . . . . . . . . . . . . . . . . . . . . 46 6.1. Simple event . . . . . . . . . . . . . . . . . . . . . . 46
6.2. Simple task . . . . . . . . . . . . . . . . . . . . . . . 46 6.2. Simple task . . . . . . . . . . . . . . . . . . . . . . . 47
6.3. Simple group . . . . . . . . . . . . . . . . . . . . . . 47 6.3. Simple group . . . . . . . . . . . . . . . . . . . . . . 47
6.4. All-day event . . . . . . . . . . . . . . . . . . . . . . 47 6.4. All-day event . . . . . . . . . . . . . . . . . . . . . . 48
6.5. Task with a due date . . . . . . . . . . . . . . . . . . 48 6.5. Task with a due date . . . . . . . . . . . . . . . . . . 48
6.6. Event with end time-zone . . . . . . . . . . . . . . . . 48 6.6. Event with end time-zone . . . . . . . . . . . . . . . . 49
6.7. Floating-time event (with recurrence) . . . . . . . . . . 49 6.7. Floating-time event (with recurrence) . . . . . . . . . . 49
6.8. Event with multiple locations and localization . . . . . 49 6.8. Event with multiple locations and localization . . . . . 50
6.9. Recurring event with overrides . . . . . . . . . . . . . 50 6.9. Recurring event with overrides . . . . . . . . . . . . . 51
6.10. Recurring event with participants . . . . . . . . . . . . 51 6.10. Recurring event with participants . . . . . . . . . . . . 52
7. Security Considerations . . . . . . . . . . . . . . . . . . . 53 7. Security Considerations . . . . . . . . . . . . . . . . . . . 54
7.1. Expanding Recurrences . . . . . . . . . . . . . . . . . . 53 7.1. Expanding Recurrences . . . . . . . . . . . . . . . . . . 54
7.2. JSON Parsing . . . . . . . . . . . . . . . . . . . . . . 53 7.2. JSON Parsing . . . . . . . . . . . . . . . . . . . . . . 54
7.3. URI Values . . . . . . . . . . . . . . . . . . . . . . . 54 7.3. URI Values . . . . . . . . . . . . . . . . . . . . . . . 55
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55
8.1. Media Type Registration . . . . . . . . . . . . . . . . . 54 8.1. Media Type Registration . . . . . . . . . . . . . . . . . 55
8.2. Creation of "JSCalendar Properties" Registry . . . . . . 55 8.2. Creation of "JSCalendar Properties" Registry . . . . . . 56
8.2.1. Preliminary Community Review . . . . . . . . . . . . 56 8.2.1. Preliminary Community Review . . . . . . . . . . . . 57
8.2.2. Submit Request to IANA . . . . . . . . . . . . . . . 56 8.2.2. Submit Request to IANA . . . . . . . . . . . . . . . 57
8.2.3. Designated Expert Review . . . . . . . . . . . . . . 56 8.2.3. Designated Expert Review . . . . . . . . . . . . . . 57
8.2.4. Change Procedures . . . . . . . . . . . . . . . . . . 57 8.2.4. Change Procedures . . . . . . . . . . . . . . . . . . 58
8.2.5. JMAP Properties Registry Template . . . . . . . . . . 57 8.2.5. JMAP Properties Registry Template . . . . . . . . . . 58
8.2.6. Initial Contents for the JSCalendar Properties 8.2.6. Initial Contents for the JSCalendar Properties
Registry . . . . . . . . . . . . . . . . . . . . . . 58 Registry . . . . . . . . . . . . . . . . . . . . . . 59
8.3. Creation of "JSCalendar Types" Registry . . . . . . . . . 65 8.3. Creation of "JSCalendar Types" Registry . . . . . . . . . 66
8.3.1. JMAP Types Registry Template . . . . . . . . . . . . 65 8.3.1. JMAP Types Registry Template . . . . . . . . . . . . 66
8.3.2. Initial Contents for the JSCalendar Types Registry . 65 8.3.2. Initial Contents for the JSCalendar Types Registry . 66
8.4. Creation of "JSCalendar Enum Values" Registry . . . . . . 67 8.4. Creation of "JSCalendar Enum Values" Registry . . . . . . 68
8.4.1. JMAP Enum Subregistry Creation Template . . . . . . . 67 8.4.1. JMAP Enum Subregistry Creation Template . . . . . . . 68
8.4.2. JMAP Enum Subregistry Template . . . . . . . . . . . 67 8.4.2. JMAP Enum Subregistry Template . . . . . . . . . . . 68
8.4.3. Initial Contents for the JSCalendar Enum Registry . . 68 8.4.3. Initial Contents for the JSCalendar Enum Registry . . 69
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 72 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 73
10. Informative References . . . . . . . . . . . . . . . . . . . 72 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 73
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 75 10.1. Normative References . . . . . . . . . . . . . . . . . . 73
10.2. Informative References . . . . . . . . . . . . . . . . . 75
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 76
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:
o The attributes of the calendar entry represented must be described o The attributes of the calendar entry represented must be described
as a simple key-value pair. Simple events are simple to as simple key-value pairs. Simple events are simple to represent;
represent, complex events can be modelled accurately. complex events can be modelled accurately.
o Wherever possible, there should be only one way to express the o Wherever possible, there should be only one way to express the
desired semantics, reducing complexity. desired semantics, reducing complexity.
o The data model should avoid ambiguities and make it difficult to o The data model should avoid ambiguities, which often lead to
make mistakes during implementation. interoperability issues between implementations.
o The data model should be compatible with the iCalendar data format o The data model should be compatible with the iCalendar data format
[RFC5545] [RFC7986] and extensions, but the specification should [RFC5545] [RFC7986] and extensions, but the specification should
add new attributes where the iCalendar format currently lacks add new attributes where the iCalendar format currently lacks
expressivity, and drop widely unused, obsolete or redundant expressivity, and drop seldom-used, obsolete, or redundant
properties. This means translation with no loss of semantics properties. This means translation with no loss of semantics
should be easy with most common iCalendar files but is not should be easy with most common iCalendar files.
guaranteed with the full specification.
o Extensions, such as new properties and components, MUST NOT lead o Extensions, such as new properties and components, generally do
to requiring an update to this document. not require updates to this document.
The representation of this data model is defined in the I-JSON format The representation of this data model is defined in the I-JSON format
[RFC7493], which is a strict subset of the JavaScript Object Notation [RFC7493], which is a strict subset of the JavaScript Object Notation
(JSON) Data Interchange Format [RFC8259]. Using JSON is mostly a (JSON) Data Interchange Format [RFC8259]. Using JSON is mostly a
pragmatic choice: its widespread use makes JSCalendar easier to pragmatic choice: its widespread use makes JSCalendar easier to
adopt, and the ready availability of production-ready JSON adopt, and the ready availability of production-ready JSON
implementations eliminates a whole category of parser-related implementations eliminates a whole category of parser-related
interoperability issues, which iCalendar has often suffered from. interoperability issues, which iCalendar has often suffered from.
1.1. Motivation and Relation to iCalendar and jCal 1.1. Motivation and Relation to iCalendar and jCal
The iCalendar data format [RFC5545], a widely deployed interchange The iCalendar data format [RFC5545], a widely deployed interchange
format for calendaring and scheduling data, has served calendaring format for calendaring and scheduling data, has served calendaring
vendors for a long while, but contains some ambiguities and pitfalls vendors for a long while, but contains some ambiguities and pitfalls
that can not be overcome without backward-incompatible changes. that can not be overcome without backward-incompatible changes.
For example, iCalendar defines various formats for local times, UTC Sources of implementation errors include the following:
time and dates, which confuses new users and often leads to
implementation errors. Other sources for errors are the requirement o iCalendar defines various formats for local times, UTC time, and
for custom time zone definitions within a single calendar component, dates.
as well as the iCalendar format itself; the latter causing
interoperability issues due to misuse of CR LF terminated strings, o iCalendar requires custom time zone definitions within a single
line continuations and subtle differences between iCalendar parsers. calendar component.
The definition of recurrence rules is ambiguous and has resulted in
differing understandings even between experienced calendar o iCalendar's definition of recurrence rules is ambiguous and has
developers. resulted in differing understandings even between experienced
calendar developers.
o The iCalendar format itself causes interoperability issues due to
misuse of CRLF-terminated strings, line continuations, and subtle
differences among iCalendar parsers.
In recent years, many new products and services have appeared that In recent years, many new products and services have appeared that
wish to use a JSON representation of calendar data within their API. wish to use a JSON representation of calendar data within their APIs.
The JSON format for iCalendar data, jCal [RFC7265], is a direct The JSON format for iCalendar data, jCal [RFC7265], is a direct
mapping between iCalendar and JSON. In its effort to represent full mapping between iCalendar and JSON. In its effort to represent full
iCalendar semantics, it inherits all the same pitfalls and uses a iCalendar semantics, it inherits all the same pitfalls and uses a
complicated JSON structure unlike most common JSON data complicated JSON structure unlike most common JSON data
representations. representations.
As a consequence, since the standardization of jCal, the majority of As a consequence, since the standardization of jCal, the majority of
implementations and service providers either kept using iCalendar, or implementations and service providers either kept using iCalendar, or
came up with their own proprietary JSON representations, which are came up with their own proprietary JSON representations, which are
incompatible with each other and often suffer from common pitfalls, incompatible with each other and often suffer from common pitfalls,
such as storing event start times in UTC (which become incorrect if such as storing event start times in UTC (which become incorrect if
the timezone's rules change in the future). JSCalendar is intended the timezone's rules change in the future). JSCalendar meets the
to meet this demand for JSON-formatted calendar data, and to provide demand for JSON-formatted calendar data that is free of such known
a standard, elegant representation as an alternative to new problems and provides a standard representation as an alternative to
proprietary formats. the proprietary formats.
1.2. Notational Conventions 1.2. Notational Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
The underlying format used for this specification is JSON. The underlying format used for this specification is JSON.
Consequently, the terms "object" and "array" as well as the four Consequently, the terms "object" and "array" as well as the four
primitive types (strings, numbers, booleans, and null) are to be primitive types (strings, numbers, booleans, and null) are to be
interpreted as described in Section 1 of [RFC8259]. interpreted as described in Section 1 of [RFC8259].
Some examples in this document contain "partial" JSON documents used Some examples in this document contain "partial" JSON documents used
for illustrative purposes. In these examples, three periods "..." for illustrative purposes. In these examples, three periods "..."
are used to indicate a portion of the document that has been removed are used to indicate a portion of the document that has been removed
for compactness. for compactness.
skipping to change at page 6, line 44 skipping to change at page 6, line 50
o "Boolean" - The JSON boolean type. o "Boolean" - The JSON boolean type.
o "A[B]" - A JSON object where the keys are all of type "A", and the o "A[B]" - A JSON object where the keys are all of type "A", and the
values are all of type "B". values are all of type "B".
o "A[]" - An array of values of type "A". o "A[]" - An array of values of type "A".
o "A|B" - The value is either of type "A" or of type "B". o "A|B" - The value is either of type "A" or of type "B".
Other types may also be given, with their representation defined Other types may also be given, with their representations defined
elsewhere in this document. elsewhere in this document.
1.4. Data Types 1.4. Data Types
In addition to the standard JSON data types, the following data types In addition to the standard JSON data types, the following data types
are used in this specification: are used in this specification:
1.4.1. Int 1.4.1. Int
Where "Int" is given as a data type, it means an integer in the range Where "Int" is given as a data type, it means an integer in the range
-2^53+1 <= value <= 2^53-1, the safe range for integers stored in a -2^53+1 <= value <= 2^53-1, the safe range for integers stored in a
floating-point double, represented as a JSON "Number". floating-point double, represented as a JSON "Number".
1.4.2. UnsignedInt 1.4.2. UnsignedInt
Where "UnsignedInt" is given as a data type, it means an "Int" where Where "UnsignedInt" is given as a data type, it means an integer in
the value MUST be in the range 0 <= value <= 2^53-1. the range 0 <= value <= 2^53-1, represented as a JSON "Number".
1.4.3. UTCDateTime 1.4.3. UTCDateTime
This is a string in [RFC3339] "date-time" format, with the further This is a string in [RFC3339] "date-time" format, with the further
restrictions that any letters MUST be in uppercase, the time restrictions that any letters MUST be in uppercase, the time
component MUST be included and the time offset MUST be the character component MUST be included and the time offset MUST be the character
"Z". Fractional second values MUST NOT be included unless non-zero "Z". Fractional second values MUST NOT be included unless non-zero
and MUST NOT have trailing zeros, to ensure there is only a single and MUST NOT have trailing zeros, to ensure there is only a single
representation for each date-time. representation for each date-time.
For example "2010-10-10T10:10:10.003Z" is OK, but For example "2010-10-10T10:10:10.003Z" is OK, but
"2010-10-10T10:10:10.000Z" is invalid and MUST be encoded as "2010-10-10T10:10:10.000Z" is invalid and MUST be encoded as
"2010-10-10T10:10:10Z". "2010-10-10T10:10:10Z".
In common notation, it should be of the form "YYYY-MM-DDTHH:MM:SSZ".
1.4.4. LocalDateTime 1.4.4. LocalDateTime
This is a date-time string with no time zone/offset information. It This is a date-time string with no time zone/offset information. It
is otherwise in the same format as UTCDateTime, including fractional is otherwise in the same format as UTCDateTime, including fractional
seconds. For example "2006-01-02T15:04:05" and seconds. For example "2006-01-02T15:04:05" and
"2006-01-02T15:04:05.003" are both valid. The time zone to associate "2006-01-02T15:04:05.003" are both valid. The time zone to associate
the LocalDateTime with comes from an associated property, or if no the LocalDateTime with comes from an associated property, or if no
time zone is associated it defines *floating time*. Floating date- time zone is associated it defines *floating time*. Floating date-
times are not tied to any specific time zone. Instead, they occur in times are not tied to any specific time zone. Instead, they occur in
every time zone at the same wall-clock time (as opposed to the same each time zone at the given wall-clock time (as opposed to the same
instant point in time). instant point in time).
1.4.5. Duration 1.4.5. Duration
Where Duration is given as a type, it means a length of time Where Duration is given as a type, it means a length of time
represented by a subset of ISO8601 duration format, as specified by represented by a subset of ISO8601 duration format, as specified by
the following ABNF: the following ABNF:
dur-secfrac = "." 1*DIGIT dur-secfrac = "." 1*DIGIT
dur-second = 1*DIGIT [dur-secfrac] "S" dur-second = 1*DIGIT [dur-secfrac] "S"
skipping to change at page 8, line 26 skipping to change at page 8, line 26
unless the fraction is non-zero. unless the fraction is non-zero.
1.4.6. SignedDuration 1.4.6. SignedDuration
A SignedDuration represents a length of time that may be positive or A SignedDuration represents a length of time that may be positive or
negative and is typically used to express the offset of a point in negative and is typically used to express the offset of a point in
time relative to an associated time. It is represented as a time relative to an associated time. It is represented as a
Duration, optionally preceded by a sign character. It is specified Duration, optionally preceded by a sign character. It is specified
by the following ABNF: by the following ABNF:
signed-duration = (["+"] / "-") duration signed-duration = ["+" / "-"] duration
A negative sign indicates a point in time at or before the associated A negative sign indicates a point in time at or before the associated
time, a positive or no sign a time at or after the associated time. time, a positive or no sign a time at or after the associated time.
1.4.7. Id 1.4.7. Id
Where "Id" is given as a data type, it means a "String" of at least 1 Where "Id" is given as a data type, it means a "String" of at least 1
and a maximum of 255 octets in size, and it MUST only contain and a maximum of 255 octets in size, and it MUST only contain
characters from the "URL and Filename Safe" base64 alphabet, as characters from the "URL and Filename Safe" base64url alphabet, as
defined in Section 5 of [RFC4648], excluding the pad character ("="). defined in Section 5 of [RFC4648], excluding the pad character ("=").
This means the allowed characters are the ASCII alphanumeric This means the allowed characters are the ASCII alphanumeric
characters ("A-Za-z0-9"), hyphen ("-"), and underscore ("_"). characters ("A-Za-z0-9"), hyphen ("-"), and underscore ("_").
Unless otherwise specified, Ids are arbitrary and only have meaning Unless otherwise specified, Ids are arbitrary and only have meaning
within the object where they are being used. Ids need not be unique within the object where they are being used. Ids need not be unique
between different objects. For example, two JSEvent objects MAY use among different objects. For example, two JSEvent objects might use
the same ids in their respective "links" properties. Or within the the same ids in their respective "links" properties. Or within the
same JSEvent object the same Id could appear in the "participants" same JSEvent object the same Id could appear in the "participants"
and "alerts" properties. This does not imply any semantic connection and "alerts" properties. These situations do not imply any semantic
between the two. connections among the objects.
Nevertheless, a UUID is typically a good choice. Nevertheless, a UUID is typically a good choice.
1.4.8. PatchObject 1.4.8. PatchObject
A PatchObject is of type "String[*]", and represents an unordered set A PatchObject is of type "String[*]", and represents an unordered set
of patches on a JSON object. The keys are a path in a subset of of patches on a JSON object. Each key is a path represented in a
[RFC6901] JSON pointer format, with an implicit leading "/" (i.e. subset of JSON pointer format [RFC6901]. The paths have an implicit
prefix each key with "/" before applying the JSON pointer evaluation leading "/", so each key is prefixed with "/" before applying the
algorithm). JSON pointer evaluation algorithm.
A patch within a PatchObject is only valid if all of the following A patch within a PatchObject is only valid if all of the following
conditions apply: conditions apply:
1. The pointer MUST NOT reference inside an array (i.e. it MUST NOT 1. The pointer MUST NOT insert/delete from an array; the array MUST
insert/delete from an array; the array MUST be replaced in its be replaced in its entirety instead.
entirety instead).
2. When evaluating a path, all parts prior to the last (i.e. the 2. When evaluating a path, all parts prior to the last (i.e., the
value after the final slash) MUST exist. value after the final slash) MUST exist.
3. There MUST NOT be two patches in the PatchObject where the 3. There MUST NOT be two patches in the PatchObject where the
pointer of one is the prefix of the pointer of the other, e.g. pointer of one is a prefix of the pointer of the other, e.g.,
"alerts/foo/offset" and "alerts". "alerts/foo/offset" and "alerts".
The value associated with each pointer is either: The value associated with each pointer is either:
o null: Remove the property from the patched object. If not present o null: Remove the property at the given path from the patched
in the parent, this a no-op. object. If the property is not present in the object, this a no-
op.
o Anything else: The value to set for this property (this may be a o Anything else: Set the value for the property to this value (this
replacement or addition to the object being patched). may be a replacement or addition to the object being patched).
Implementations MUST reject a PatchObject if any of its patches are Implementations MUST reject in its entirety a PatchObject if any of
invalid. its patches is invalid. Implementations MUST NOT apply partial
patches.
1.4.9. Time Zones 1.4.9. Time Zones
By default, time zones in JSCalendar are identified by their name in By default, time zones in JSCalendar are identified by their names in
the IANA Time Zone Database [TZDB], and the zone rules of the the IANA Time Zone Database [TZDB], and the zone rules of the
respective zone record apply. respective zone records apply.
Implementations MAY embed the definition of custom time zones in the Implementations MAY embed the definitions of custom time zones in the
"timeZones" property (see Section 4.7.2). "timeZones" property (see Section 4.7.2).
1.4.10. Relation 1.4.10. Relation
A Relation object defines the relation to other objects, using a A Relation object defines the relation to other objects, using a
possibly empty set of relation types. The object that defines this possibly empty set of relation types. The object that defines this
relation is the linking object, the other object is the linked relation is the linking object, while the other object is the linked
object. The Relation object has the following property: object. The Relation object has the following properties:
o @type: "String" (mandatory) o @type: "String" (mandatory)
Specifies the type of this object. This MUST be "Relation". Specifies the type of this object. This MUST be "Relation".
o relation: "String[Boolean]" (optional, default: empty Object) o relation: "String[Boolean]" (optional, default: empty Object)
Describes how the linked object is related to the linking object. Describes how the linked object is related to the linking object.
The relation is defined as a set of relation types. If empty, the The relation is defined as a set of relation types. If empty, the
relationship between the two objects is unspecified. relationship between the two objects is unspecified.
Keys in the set MUST be one of the following values, or specified Keys in the set MUST be one of the following values, or specified
in the property definition where the Relation object is used, or in the property definition where the Relation object is used, or a
an IANA-registered value, or a vendor-specific value: value registered in the IANA JSCalendar Enum Registry, or a
vendor-specific value:
* "first": The linked object is the first in a series the linking * "first": The linked object is the first in a series the linking
object is part of. object is part of.
* "next": The linked object is the next in a series the linking * "next": The linked object is the next in a series the linking
object is part of. object is part of.
* "child": The linked object is a subpart of the linking object. * "child": The linked object is a subpart of the linking object.
* "parent": The linking object is part of the overall linked * "parent": The linking object is a subpart of the linked object.
object.
The value for each key in the set MUST be true. The value for each key in the set MUST be true.
Note, the Relation object only has one property (except @type); it is
specified as an object with a single property to allow for extension
in the future.
2. JSCalendar Objects 2. JSCalendar Objects
This section describes the calendar object types specified by This section describes the calendar object types specified by
JSCalendar. JSCalendar.
2.1. JSEvent 2.1. JSEvent
MIME type: "application/jscalendar+json;type=jsevent" Media type: "application/jscalendar+json;type=jsevent"
A JSEvent represents a scheduled amount of time on a calendar, A JSEvent represents a scheduled amount of time on a calendar,
typically a meeting, appointment, reminder or anniversary. Multiple typically a meeting, appointment, reminder or anniversary. It is
participants may partake in the event at multiple locations. required to start at a certain point in time and typically has a non-
zero duration. Multiple participants may partake in the event at
multiple locations.
The @type (Section 4.1.1) property value MUST be "jsevent". The @type (Section 4.1.1) property value MUST be "jsevent".
2.2. JSTask 2.2. JSTask
MIME type: "application/jscalendar+json;type=jstask" Media type: "application/jscalendar+json;type=jstask"
A JSTask represents an action-item, assignment, to-do or work item. A JSTask represents an action-item, assignment, to-do or work item.
It may start and be due at certain points in time, may take some
estimated time to complete, and may recur, none of which is required.
The @type (Section 4.1.1) property value MUST be "jstask". The @type (Section 4.1.1) property value MUST be "jstask".
A JSTask may start and be due at certain points in time, may take
some estimated time to complete and may recur; none of which is
required. This notably differs from JSEvent (Section 2.1) which is
required to start at a certain point in time and typically takes some
non-zero duration to complete.
2.3. JSGroup 2.3. JSGroup
MIME type: "application/jscalendar+json;type=jsgroup" Media type: "application/jscalendar+json;type=jsgroup"
A JSGroup is a collection of JSEvent (Section 2.1) and/or JSTask A JSGroup is a collection of JSEvent (Section 2.1) and/or JSTask
(Section 2.2) objects. Typically, objects are grouped by topic (e.g. (Section 2.2) objects. Typically, objects are grouped by topic
by keywords) or calendar membership. (e.g., by keywords) or calendar membership.
The @type (Section 4.1.1) property value MUST be "jsgroup". The @type (Section 4.1.1) property value MUST be "jsgroup".
3. Structure of JSCalendar Objects 3. Structure of JSCalendar Objects
A JSCalendar object is a JSON object, which MUST be valid I-JSON (a A JSCalendar object is a JSON object, which MUST be valid I-JSON (a
stricter subset of JSON), as specified in [RFC8259]. Property names stricter subset of JSON), as specified in [RFC8259]. Property names
and values are case-sensitive. and values are case-sensitive.
The object has a collection of properties, as specified in the The object has a collection of properties, as specified in the
skipping to change at page 12, line 10 skipping to change at page 12, line 5
the encoded calendar object to determine ETag equivalence). the encoded calendar object to determine ETag equivalence).
Normalization of JSCalendar objects is hindered because of the Normalization of JSCalendar objects is hindered because of the
following reasons: following reasons:
o Custom JSCalendar properties may contain arbitrary JSON values, o Custom JSCalendar properties may contain arbitrary JSON values,
including arrays. However, equivalence of arrays might or might including arrays. However, equivalence of arrays might or might
not depend on the order of elements, depending on the respective not depend on the order of elements, depending on the respective
property definition. property definition.
o Several JSCalendar property values are defined as URIs and MIME o Several JSCalendar property values are defined as URIs and media
types, but normalization of these types is inherently protocol and types, but normalization of these types is inherently protocol-
scheme-specific, depending on the use-case of the equivalence and scheme-specific, depending on the use-case of the equivalence
definition (see Section 6 of [RFC3986]). definition (see Section 6 of [RFC3986]).
Considering this, the definition of equivalence and normalization is Considering this, the definition of equivalence and normalization is
left to client and server implementations and to be negotiated by a left to client and server implementations and to be negotiated by a
calendar exchange protocol or defined by another RFC. calendar exchange protocol or defined elsewhere.
3.2. Vendor-specific Property Extensions and Values 3.2. Vendor-specific Property Extensions and Values
Vendors MAY add additional properties to the calendar object to Vendors MAY add additional properties to the calendar object to
support their custom features. The names of these properties MUST be support their custom features. The names of these properties MUST be
prefixed with a domain name controlled by the vendor to avoid prefixed with a domain name controlled by the vendor to avoid
conflict, e.g. "example.com/customprop". conflict, e.g., "example.com/customprop".
Some JSCalendar properties allow vendor-specific value extensions. Some JSCalendar properties allow vendor-specific value extensions.
If so, vendor-specific values MUST be prefixed with a domain name Such vendor-specific values MUST be prefixed with a domain name
controlled by the vendor, e.g. "example.com/customrel". controlled by the vendor, e.g., "example.com/customrel".
Vendors are strongly encouraged to register any new property values Vendors are strongly encouraged to register any new property values
or extensions that are useful to other systems as well, rather than or extensions that are useful to other systems as well, rather than
use a vendor-specific prefix. use a vendor-specific prefix.
4. Common JSCalendar Properties 4. Common JSCalendar Properties
This section describes the properties that are common to the various This section describes the properties that are common to the various
JSCalendar object types. Specific JSCalendar object types may only JSCalendar object types. Specific JSCalendar object types may only
support a subset of these properties. The object type definitions in support a subset of these properties. The object type definitions in
Section 5 describe the set of supported properties per type. Section 5 describe the set of supported properties per type.
4.1. Metadata Properties 4.1. Metadata Properties
4.1.1. @type 4.1.1. @type
Type: "String" (mandatory). Type: "String" (mandatory).
Specifies the type which this object represents. This MUST be one of Specifies the type which this object represents. This MUST be one of
the following values, an IANA-registered value, or a vendor-specific the following values:
value:
o "jsevent": a JSCalendar event (Section 2.1). o "jsevent": a JSCalendar event (Section 2.1).
o "jstask": a JSCalendar task (Section 2.2). o "jstask": a JSCalendar task (Section 2.2).
o "jsgroup": a JSCalendar group (Section 2.3). o "jsgroup": a JSCalendar group (Section 2.3).
4.1.2. uid 4.1.2. uid
Type: "String" (mandatory). Type: "String" (mandatory).
A globally unique identifier, used to associate the object as the A globally unique identifier, used to associate the object as the
same across different systems, calendars and views. The value of same across different systems, calendars and views. The value of
this property MUST be unique across all JSCalendar objects, even if this property MUST be unique across all JSCalendar objects, even if
they are of different type. [RFC4122] describes a range of they are of different type. [RFC4122] describes a range of
established algorithms to generate universally unique identifiers established algorithms to generate universally unique identifiers
(UUID), and the random or pseudo-random version is recommended. (UUID). UUID version 4, described in Section 4.4 of [RFC4122], is
RECOMMENDED.
For compatibility with [RFC5545] UIDs, implementations MUST be able For compatibility with [RFC5545] UIDs, implementations MUST be able
to receive and persist values of at least 255 octets for this to receive and persist values of at least 255 octets for this
property, but they MUST NOT truncate values in the middle of a UTF-8 property, but they MUST NOT truncate values in the middle of a UTF-8
multi-octet sequence. multi-octet sequence.
4.1.3. relatedTo 4.1.3. relatedTo
Type: "String[Relation]" (optional). Type: "String[Relation]" (optional).
skipping to change at page 14, line 10 skipping to change at page 14, line 8
modified (i.e., whenever the "updated" property is set). modified (i.e., whenever the "updated" property is set).
The vendor of the implementation SHOULD ensure that this is a The vendor of the implementation SHOULD ensure that this is a
globally unique identifier, using some technique such as an FPI globally unique identifier, using some technique such as an FPI
value, as defined in [ISO.9070.1991]. It MUST only use characters of value, as defined in [ISO.9070.1991]. It MUST only use characters of
an iCalendar TEXT data value (see Section 3.3.11 of [RFC5545]). an iCalendar TEXT data value (see Section 3.3.11 of [RFC5545]).
This property SHOULD NOT be used to alter the interpretation of a This property SHOULD NOT be used to alter the interpretation of a
JSCalendar object beyond the semantics specified in this document. JSCalendar object beyond the semantics specified in this document.
For example, it is not to be used to further the understanding of For example, it is not to be used to further the understanding of
non-standard properties. non-standard properties, a practice that is knows to cause long-term
interoperability problems.
4.1.5. created 4.1.5. created
Type: "UTCDateTime" (optional). Type: "UTCDateTime" (optional).
The date and time this object was initially created. The date and time this object was initially created.
4.1.6. updated 4.1.6. updated
Type: "UTCDateTime" (mandatory). Type: "UTCDateTime" (mandatory).
The date and time the data in this object was last modified. The date and time the data in this object was last modified (or its
creation date/time if not modified since).
4.1.7. sequence 4.1.7. sequence
Type: "UnsignedInt" (optional, default: 0). Type: "UnsignedInt" (optional, default: 0).
Initially zero, this MUST be incremented by one every time a change Initially zero, this MUST be incremented by one every time a change
is made to the object, except if the change only modifies the is made to the object, except if the change only modifies the
"participants" property (see Section 4.4.5). "participants" property (see Section 4.4.5).
This is used as part of iTIP [RFC5546] to know which version of the This is used as part of iTIP [RFC5546] to know which version of the
skipping to change at page 15, line 19 skipping to change at page 15, line 19
A longer-form text description of the object. The content is A longer-form text description of the object. The content is
formatted according to the "descriptionContentType" property. formatted according to the "descriptionContentType" property.
4.2.3. descriptionContentType 4.2.3. descriptionContentType
Type: "String" (optional, default: "text/plain"). Type: "String" (optional, default: "text/plain").
Describes the media type [RFC6838] of the contents of the Describes the media type [RFC6838] of the contents of the
"description" property. Media types MUST be sub-types of type "description" property. Media types MUST be sub-types of type
"text", and SHOULD be "text/plain" or "text/html" [MIME]. They MAY "text", and SHOULD be "text/plain" or "text/html" [MIME]. They MAY
define parameters and the "charset" parameter value MUST be "utf-8", include parameters and the "charset" parameter value MUST be "utf-8",
if specified. Descriptions of type "text/html" MAY contain "cid" if specified. Descriptions of type "text/html" MAY contain "cid"
URLs [RFC2392] to reference links in the calendar object by use of URLs [RFC2392] to reference links in the calendar object by use of
the "cid" property of the Link object. the "cid" property of the Link object.
4.2.4. showWithoutTime 4.2.4. showWithoutTime
Type: "Boolean" (optional, default: false). Type: "Boolean" (optional, default: false).
Indicates the time is not important to display to the user when Indicates that the time is not important to display to the user when
rendering this calendar object, for example an event that rendering this calendar object. An example of this is an event that
conceptually occurs all day or across multiple days, such as "New conceptually occurs all day or across multiple days, such as "New
Year's Day" or "Italy Vacation". While the time component is Year's Day" or "Italy Vacation". While the time component is
important for free-busy calculations and checking for scheduling important for free-busy calculations and checking for scheduling
clashes, calendars may choose to omit displaying it and/or display clashes, calendars may choose to omit displaying it and/or display
the object separately to other objects to enhance the user's view of the object separately to other objects to enhance the user's view of
their schedule. their schedule.
Such events are also commonly known as "all-day" events. Such events are also commonly known as "all-day" events.
4.2.5. locations 4.2.5. locations
skipping to change at page 16, line 25 skipping to change at page 16, line 25
o locationTypes: "String[Boolean]" (optional) o locationTypes: "String[Boolean]" (optional)
A set of one or more location types that describe this location. A set of one or more location types that describe this location.
All types MUST be from the Location Types Registry as defined in All types MUST be from the Location Types Registry as defined in
[RFC4589]. The set is represented as a map, with the keys being [RFC4589]. The set is represented as a map, with the keys being
the location types. The value for each key in the map MUST be the location types. The value for each key in the map MUST be
true. true.
o relativeTo: "String" (optional) o relativeTo: "String" (optional)
The relation type of this location to the JSCalendar object. Specifies the relation between this location and the time of the
JSCalendar object. This is primarily to allow events representing
travel to specify the location of departure (at the start of the
event) and location of arrival (at the end); this is particularly
important if these locations are in different time zones, as a
client may wish to highlight this information for the user.
This MUST be either one of the following values, an IANA- This MUST be one of the following values, a value registered in
registered value, or a vendor-specific value. Any value the the IANA JSCalendar Enum Registry, or a vendor-specific value.
client or server doesn't understand should be treated the same as Any value the client or server doesn't understand should be
if this property is omitted. treated the same as if this property is omitted.
* "start": The JSCalendar object starts at this location. * "start": The event/task described by this JSCalendar object
occurs at this location at the time the event/task starts.
* "end": The JSCalendar object ends at this location. * "end": The event/task described by this JSCalendar object
occurs at this location at the time the event/task ends.
o timeZone: "String" (optional) o timeZone: "String" (optional)
A time zone for this location. See also Section 1.4.9. A time zone for this location. See also Section 1.4.9.
o coordinates: "String" (optional) o coordinates: "String" (optional)
A "geo:" URI [RFC5870] for the location. A "geo:" URI [RFC5870] for the location.
o linkIds: "Id[Boolean]" (optional) o linkIds: "Id[Boolean]" (optional)
A set of link ids for links to alternative representations of this
A set of link ids for links to alternate representations of this
location. Each key in the set MUST be the id of a Link object location. Each key in the set MUST be the id of a Link object
defined in the "links" property of this calendar object. The defined in the "links" property of this calendar object. The
value for each key in the set MUST be true. This MUST be omitted value for each key in the set MUST be true. If there are no
if none (rather than an empty set). links, this MUST be omitted (rather than specified as an empty
set).
For example, an alternative representation could be in vCard For example, an alternative representation could be in vCard
format. format.
4.2.6. virtualLocations 4.2.6. virtualLocations
Type: "Id[VirtualLocation]" (optional). Type: "Id[VirtualLocation]" (optional).
A map of ids to VirtualLocation objects, representing virtual A map of ids to VirtualLocation objects, representing virtual
locations, such as video conferences or chat rooms, associated with locations, such as video conferences or chat rooms, associated with
skipping to change at page 18, line 9 skipping to change at page 18, line 18
A Link object has the following properties: A Link object has the following properties:
o @type: "String" (mandatory) o @type: "String" (mandatory)
Specifies the type of this object. This MUST be "Link". Specifies the type of this object. This MUST be "Link".
o href: "String" (mandatory) o href: "String" (mandatory)
A URI from which the resource may be fetched. A URI from which the resource may be fetched.
This MAY be a "data:" URL, but it is recommended that the file be This MAY be a "data:" URL [RFC2397], but it is recommended that
hosted on a server to avoid embedding arbitrarily large data in the file be hosted on a server to avoid embedding arbitrarily
JSCalendar object instances. large data in JSCalendar object instances.
o cid: "String" (optional) o cid: "String" (optional)
This MUST be a valid "content-id" value according to the This MUST be a valid "content-id" value according to the
definition of Section 2 in [RFC2392]. The value MUST be unique definition of Section 2 in [RFC2392]. The value MUST be unique
within this Link object but has no meaning beyond that. It MAY be within this Link object but has no meaning beyond that. It MAY be
different from the link id for this Link object. different from the link id for this Link object.
o contentType: "String" (optional) o contentType: "String" (optional)
The content-type [RFC6838] of the resource, if known. The media type [RFC6838] of the resource, if known.
o size: "UnsignedInt" (optional) o size: "UnsignedInt" (optional)
The size, in octets, of the resource when fully decoded (i.e. the The size, in octets, of the resource when fully decoded (i.e., the
number of octets in the file the user would download), if known. number of octets in the file the user would download), if known.
o rel: "String" (optional) o rel: "String" (optional)
Identifies the relation of the linked resource to the object. If Identifies the relation of the linked resource to the object. If
set, the value MUST be a relation type from the IANA registry set, the value MUST be a relation type from the IANA registry
[LINKRELS], as established in [RFC8288]. [LINKRELS], as established in [RFC8288].
Links with a rel of "enclosure" SHOULD be considered by the client Links with a rel of "enclosure" SHOULD be considered by the client
as attachments for download. as attachments for download.
Links with a rel of "describedby" SHOULD be considered by the Links with a rel of "describedby" SHOULD be considered by the
client to be an alternate representation of the description. client to be an alternative representation of the description.
Links with a rel of "icon" SHOULD be considered by the client to Links with a rel of "icon" SHOULD be considered by the client to
be an image that it MAY use when presenting the calendar data to a be an image that it may use when presenting the calendar data to a
user. The "display" property MAY be set to indicate the purpose user. The "display" property may be set to indicate the purpose
of this image. of this image.
o display: "String" (optional) o display: "String" (optional)
Describes the intended purpose of a link to an image. If set, the Describes the intended purpose of a link to an image. If set, the
"rel" property MUST be set to "icon". The value MUST be either "rel" property MUST be set to "icon". The value MUST be one of
one of the following values, an IANA-registered value, or a the following values, a value registered in the IANA JSCalendar
vendor-specific value: Enum Registry, or a vendor-specific value:
* "badge": an image inline with the title of the object. * "badge": an image meant to be displayed alongside the title of
the object.
* "graphic": a full image replacement for the object itself. * "graphic": a full image replacement for the object itself.
* "fullsize": an image that is used to enhance the object. * "fullsize": an image that is used to enhance the object.
* "thumbnail": a smaller variant of "fullsize" to be used when * "thumbnail": a smaller variant of "fullsize" to be used when
space for the image is constrained. space for the image is constrained.
o title: "String" (optional) o title: "String" (optional)
skipping to change at page 19, line 51 skipping to change at page 20, line 15
In contrast to keywords, categories typically are structured. For In contrast to keywords, categories typically are structured. For
example, a vendor owning the domain "example.com" might define the example, a vendor owning the domain "example.com" might define the
categories "http://example.com/categories/sports/american-football"" categories "http://example.com/categories/sports/american-football""
and "http://example.com/categories/music/r-b". and "http://example.com/categories/music/r-b".
4.2.11. color 4.2.11. color
Type: "String" (optional). Type: "String" (optional).
A color clients MAY use when displaying this calendar object. The A color clients MAY use when displaying this calendar object. The
value is a case-insensitive color name taken from the set of names value is a color name taken from the set of names defined in
defined in Section 4.3 of CSS Color Module Level 3 [COLORS], or an Section 4.3 of CSS Color Module Level 3 [COLORS], or an RGB value in
RGB value in hexadecimal notation, as defined in Section 4.2.1 of CSS hexadecimal notation, as defined in Section 4.2.1 of CSS Color Module
Color Module Level 3. Level 3.
4.3. Recurrence Properties 4.3. Recurrence Properties
Some events and tasks occur at regular, or indeed irregular, Some events and tasks occur at regular or irregular intervals.
intervals. Rather than having to copy the data for every occurrence, Rather than having to copy the data for every occurrence there can be
you can instead have a master event with a recurrence rule generating a master event with a recurrence rule, and/or overrides that add
the occurrences, and/or overrides that add extra dates or exceptions extra dates or exceptions to the rule.
to the rule.
4.3.1. recurrenceId 4.3.1. recurrenceId
Type: "LocalDateTime" (optional). Type: "LocalDateTime" (optional).
If present, this JSCalendar object represents one occurrence of a If present, this JSCalendar object represents one occurrence of a
recurring JSCalendar object. If present the "recurrenceRules" and recurring JSCalendar object. If present the "recurrenceRules" and
"recurrenceOverrides" properties MUST NOT be present. "recurrenceOverrides" properties MUST NOT be present.
The value is a date-time either produced by the "recurrenceRules" of The value is a date-time either produced by the "recurrenceRules" of
skipping to change at page 20, line 40 skipping to change at page 20, line 52
Defines a set of recurrence rules (repeating patterns) for recurring Defines a set of recurrence rules (repeating patterns) for recurring
calendar objects. calendar objects.
A JSEvent recurs by applying the recurrence rules to the "start" A JSEvent recurs by applying the recurrence rules to the "start"
date-time. date-time.
A JSTask recurs by applying the recurrence rules to the "start" date- A JSTask recurs by applying the recurrence rules to the "start" date-
time, if defined, otherwise it recurs by the "due" date-time, if time, if defined, otherwise it recurs by the "due" date-time, if
defined. If the task defines neither a "start" nor "due" date-time, defined. If the task defines neither a "start" nor "due" date-time,
its "recurrenceRules" property value MUST be null. it MUST NOT define a "recurrenceRules" property.
If multiple recurrence rules are given, each rule is to be applied If multiple recurrence rules are given, each rule is to be applied
and then the union of the results used, ignoring any duplicates. and then the union of the results used, ignoring any duplicates.
A RecurrenceRule object is a JSON object mapping of a RECUR value A RecurrenceRule object is a JSON object mapping of a RECUR value
type in iCalendar [RFC5545] [RFC7529] and has the same semantics. It type in iCalendar [RFC5545] [RFC7529] and has the same semantics. It
has the following properties: has the following properties:
o @type: "String" (mandatory) o @type: "String" (mandatory)
skipping to change at page 21, line 38 skipping to change at page 21, line 49
The interval of iteration periods at which the recurrence repeats. The interval of iteration periods at which the recurrence repeats.
If included, it MUST be an integer >= 1. If included, it MUST be an integer >= 1.
This is the INTERVAL part from iCalendar. This is the INTERVAL part from iCalendar.
o rscale: "String" (optional, default: "gregorian") o rscale: "String" (optional, default: "gregorian")
The calendar system in which this recurrence rule operates, in The calendar system in which this recurrence rule operates, in
lowercase. This MUST be either a CLDR-registered calendar system lowercase. This MUST be either a CLDR-registered calendar system
name, or a non-standard, experimental calendar system name name [CLDR], or a vendor-specific value.
prefixed with the characters "x-".
This is the RSCALE part from iCalendar RSCALE [RFC7529], converted This is the RSCALE part from iCalendar RSCALE [RFC7529], converted
to lowercase. to lowercase.
o skip: "String" (optional, default: "omit") o skip: "String" (optional, default: "omit")
The behaviour to use when the expansion of the recurrence produces The behaviour to use when the expansion of the recurrence produces
invalid dates. This property only has an effect if the frequency invalid dates. This property only has an effect if the frequency
is "yearly" or "monthly". It MUST be one of the following values: is "yearly" or "monthly". It MUST be one of the following values:
skipping to change at page 23, line 5 skipping to change at page 23, line 16
converted to lowercase. converted to lowercase.
* nthOfPeriod: "Int" (optional) * nthOfPeriod: "Int" (optional)
If present, rather than representing every occurrence of the If present, rather than representing every occurrence of the
weekday defined in the "day" property, it represents only a weekday defined in the "day" property, it represents only a
specific instance within the recurrence period. The value can specific instance within the recurrence period. The value can
be positive or negative, but MUST NOT be zero. A negative be positive or negative, but MUST NOT be zero. A negative
integer means nth-last of period. integer means nth-last of period.
This is the ordinal part of the BYDAY value in iCalendar (e.g. This is the ordinal part of the BYDAY value in iCalendar (e.g.,
1 or -3). 1 or -3).
o byMonthDay: "Int[]" (optional) o byMonthDay: "Int[]" (optional)
Days of the month on which to repeat. Valid values are between 1 Days of the month on which to repeat. Valid values are between 1
and the maximum number of days any month may have in the calendar and the maximum number of days any month may have in the calendar
given by the "rscale" property, and the negative values of these given by the "rscale" property, and the negative values of these
numbers. For example, in the Gregorian calendar valid values are numbers. For example, in the Gregorian calendar valid values are
1 to 31 and -31 to -1. Negative values offset from the end of the 1 to 31 and -31 to -1. Negative values offset from the end of the
month. The array MUST have at least one entry if included. month. The array MUST have at least one entry if included.
This is the BYMONTHDAY part in iCalendar. This is the BYMONTHDAY part in iCalendar.
o byMonth: "String[]" (optional) o byMonth: "String[]" (optional)
The months in which to repeat. Each entry is a string The months in which to repeat. Each entry is a string
representation of a number, starting from "1" for the first month representation of a number, starting from "1" for the first month
in the calendar (e.g. "1" means January with the Gregorian in the calendar (e.g., "1" means January with the Gregorian
calendar), with an optional "L" suffix (see [RFC7529]) for leap calendar), with an optional "L" suffix (see [RFC7529]) for leap
months (this MUST be uppercase, e.g. "3L"). The array MUST have months (this MUST be uppercase, e.g., "3L"). The array MUST have
at least one entry if included. at least one entry if included.
This is the BYMONTH part from iCalendar. This is the BYMONTH part from iCalendar.
o byYearDay: "Int[]" (optional) o byYearDay: "Int[]" (optional)
The days of the year on which to repeat. Valid values are between The days of the year on which to repeat. Valid values are between
1 and the maximum number of days any year may have in the calendar 1 and the maximum number of days any year may have in the calendar
given by the "rscale" property, and the negative values of these given by the "rscale" property, and the negative values of these
numbers. For example, in the Gregorian calendar valid values are numbers. For example, in the Gregorian calendar valid values are
skipping to change at page 26, line 44 skipping to change at page 27, line 6
year (if frequency is yearly). Negative numbers means nth year (if frequency is yearly). Negative numbers means nth
last occurrence within that period. last occurrence within that period.
* byHour: the date-time has the given hour value. * byHour: the date-time has the given hour value.
* byMinute: the date-time has the given minute value. * byMinute: the date-time has the given minute value.
* bySecond: the date-time has the given second value. * bySecond: the date-time has the given second value.
If a skip property is defined and is not "omit", there may be If a skip property is defined and is not "omit", there may be
candidates that do not correspond to valid dates (e.g. 31st candidates that do not correspond to valid dates (e.g., 31st
February in the Gregorian calendar). In this case, the February in the Gregorian calendar). In this case, the
properties MUST be considered in the order above and: properties MUST be considered in the order above and:
1. After applying the byMonth filter, if the candidate's month 1. After applying the byMonth filter, if the candidate's month
is invalid for the given year increment it (if skip is is invalid for the given year, increment it (if skip is
"forward") or decrement it (if skip is "backward") until a "forward") or decrement it (if skip is "backward") until a
valid month is found, incrementing/decrementing the year as valid month is found, incrementing/decrementing the year as
well if you pass through the beginning/end of the year. This well if passing through the beginning/end of the year. This
only applies to calendar systems with leap months. only applies to calendar systems with leap months.
2. After applying the byMonthDay filter, if the day of the month 2. After applying the byMonthDay filter, if the day of the month
is invalid for the given month and year, change the date to is invalid for the given month and year, change the date to
the first day of the next month (if skip == "forward") or the the first day of the next month (if skip is "forward") or the
last day of the current month (if skip == "backward"). last day of the current month (if skip is "backward").
3. If any valid date produced after applying the skip is already 3. If any valid date produced after applying the skip is already
a candidate, eliminate the duplicate. (For example after a candidate, eliminate the duplicate. (For example after
adjusting, 30th February and 31st February would both become adjusting, 30th February and 31st February would both become
the same "real" date, so one is eliminated as a duplicate.) the same "real" date, so one is eliminated as a duplicate.)
3. If a bySetPosition property is included, this is now applied to 3. If a bySetPosition property is included, this is now applied to
the ordered list of remaining dates. This property specifies the the ordered list of remaining dates. This property specifies the
indexes of date-times to keep; all others should be eliminated. indexes of date-times to keep; all others should be eliminated.
Negative numbers are indexes from the end of the list, with -1 Negative numbers are indexes from the end of the list, with -1
being the last item. being the last item.
4. Any date-times before the start date of the event are eliminated 4. Any date-times before the start date of the event are eliminated
(see below for why this might be needed). (see below for why this might be needed).
5. If a skip property is included and is not "omit", eliminate any 5. If a skip property is included and is not "omit", eliminate any
date-times that have already been produced by previous iterations date-times that have already been produced by previous iterations
of the algorithm. (This is not possible if skip == "omit".) of the algorithm. (This is not possible if skip is "omit".)
6. If further dates are required (we have not reached the until 6. If further dates are required (we have not reached the until
date, or count limit) skip the next (interval - 1) sets of date, or count limit) skip the next (interval - 1) sets of
candidates, then continue from step 1. candidates, then continue from step 1.
When determining the set of occurrence dates for an event or task, When determining the set of occurrence dates for an event or task,
the following extra rules must be applied: the following extra rules must be applied:
1. The initial date-time to which the rule is applied (the "start" 1. The initial date-time to which the rule is applied (the "start"
date-time for events; the "start" or "due" date-time for tasks) date-time for events; the "start" or "due" date-time for tasks)
skipping to change at page 30, line 25 skipping to change at page 30, line 36
The priority is specified as an integer in the range 0 to 9. A value The priority is specified as an integer in the range 0 to 9. A value
of 0 specifies an undefined priority. A value of 1 is the highest of 0 specifies an undefined priority. A value of 1 is the highest
priority. A value of 2 is the second highest priority. Subsequent priority. A value of 2 is the second highest priority. Subsequent
numbers specify a decreasing ordinal priority. A value of 9 is the numbers specify a decreasing ordinal priority. A value of 9 is the
lowest priority. Other integer values are reserved for future use. lowest priority. Other integer values are reserved for future use.
4.4.2. freeBusyStatus 4.4.2. freeBusyStatus
Type: "String" (optional, default: "busy"). Type: "String" (optional, default: "busy").
Specifies how this property should be treated when calculating free- Specifies how this calendar object should be treated when calculating
busy state. This MUST be one of the following values, an IANA- free-busy state. This MUST be one of the following values, a value
registered value, or a vendor-specific value: registered in the IANA JSCalendar Enum Registry, or a vendor-specific
value:
o "free": The object should be ignored when calculating whether the o "free": The object should be ignored when calculating whether the
user is busy. user is busy.
o "busy": The object should be included when calculating whether the o "busy": The object should be included when calculating whether the
user is busy. user is busy.
4.4.3. privacy 4.4.3. privacy
Type: "String" (optional, default: "public"). Type: "String" (optional, default: "public").
skipping to change at page 30, line 50 skipping to change at page 31, line 13
with other users. The privacy property allows the object owner to with other users. The privacy property allows the object owner to
indicate that it should not be shared, or should only have the time indicate that it should not be shared, or should only have the time
information shared but the details withheld. Enforcement of the information shared but the details withheld. Enforcement of the
restrictions indicated by this property are up to the API via which restrictions indicated by this property are up to the API via which
this object is accessed. this object is accessed.
This property MUST NOT affect the information sent to scheduled This property MUST NOT affect the information sent to scheduled
participants; it is only interpreted when the object is shared as participants; it is only interpreted when the object is shared as
part of a shared calendar. part of a shared calendar.
The value MUST be either one of the following values, an IANA- The value MUST be one of the following values, a value registered in
registered value, or a vendor-specific value. Any value the client the IANA JSCalendar Enum Registry, or a vendor-specific value. Any
or server doesn't understand should be preserved but treated as value the client or server doesn't understand should be preserved but
equivalent to "private". treated as equivalent to "private".
o "public": The full details of the object are visible to those whom o "public": The full details of the object are visible to those whom
the object's calendar is shared with. the object's calendar is shared with.
o "private": The details of the object are hidden; only the basic o "private": The details of the object are hidden; only the basic
time and metadata is shared. The following properties MAY be time and metadata is shared. The following properties MAY be
shared, any other properties MUST NOT be shared: shared, any other properties MUST NOT be shared:
* @type * @type
skipping to change at page 32, line 12 skipping to change at page 32, line 18
o "secret": The object is hidden completely (as though it did not o "secret": The object is hidden completely (as though it did not
exist) when the calendar this object is in is shared. exist) when the calendar this object is in is shared.
4.4.4. replyTo 4.4.4. replyTo
Type: "String[String]" (optional). Type: "String[String]" (optional).
Represents methods by which participants may submit their RSVP Represents methods by which participants may submit their RSVP
response to the organizer of the calendar object. The keys in the response to the organizer of the calendar object. The keys in the
property value are the available methods and MUST only contain ASCII property value are the available methods and MUST only contain ASCII
alphanumeric characters (A-Za-z0-9). The value is a URI to use that alphanumeric characters (A-Za-z0-9). The value is a URI for the
method. Future methods may be defined in future specifications and method specified in the key. Future methods may be defined in future
registered with IANA; a calendar client MUST ignore any method it specifications and registered with IANA; a calendar client MUST
does not understand, but MUST preserve the method key and URI. This ignore any method it does not understand, but MUST preserve the
property MUST be omitted if no method is defined (rather than an method key and URI. This property MUST be omitted if no method is
empty object). If this property is set, the "participants" property defined (rather than being specified as an empty object). If this
of this calendar object MUST contain at least one participant. property is set, the "participants" property of this calendar object
MUST contain at least one participant.
The following methods are defined: The following methods are defined:
o "imip": The organizer accepts an iMIP [RFC6047] response at this o "imip": The organizer accepts an iMIP [RFC6047] response at this
email address. The value MUST be a "mailto:" URI. email address. The value MUST be a "mailto:" URI.
o "web": Opening this URI in a web browser will provide the user o "web": Opening this URI in a web browser will provide the user
with a page where they can submit a reply to the organizer. with a page where they can submit a reply to the organizer.
o "other": The organizer is identified by this URI but the method o "other": The organizer is identified by this URI the method for
how to submit the RSVP is undefined. submitting the response is undefined.
4.4.5. participants 4.4.5. participants
Type: "Id[Participant]" (optional). Type: "Id[Participant]" (optional).
A map of participant ids to participants, describing their A map of participant ids to participants, describing their
participation in the calendar object. participation in the calendar object.
If this property is set, then the "replyTo" property of this calendar If this property is set, then the "replyTo" property of this calendar
object MUST define at least one reply method. object MUST define at least one reply method.
skipping to change at page 32, line 44 skipping to change at page 33, line 4
A map of participant ids to participants, describing their A map of participant ids to participants, describing their
participation in the calendar object. participation in the calendar object.
If this property is set, then the "replyTo" property of this calendar If this property is set, then the "replyTo" property of this calendar
object MUST define at least one reply method. object MUST define at least one reply method.
A Participant object has the following properties: A Participant object has the following properties:
o @type: "String" (mandatory) o @type: "String" (mandatory)
Specifies the type of this object. This MUST be "Participant". Specifies the type of this object. This MUST be "Participant".
o name: "String" (optional) o name: "String" (optional)
The display name of the participant (e.g. "Joe Bloggs"). The display name of the participant (e.g., "Joe Bloggs").
o email: "String" (optional) o email: "String" (optional)
The email address for the participant. The email address for the participant.
o sendTo: "String[String]" (optional) o sendTo: "String[String]" (optional)
Represents methods by which the participant may receive the Represents methods by which the participant may receive the
invitation and updates to the calendar object. invitation and updates to the calendar object.
The keys in the property value are the available methods and MUST The keys in the property value are the available methods and MUST
only contain ASCII alphanumeric characters (A-Za-z0-9). The value only contain ASCII alphanumeric characters (A-Za-z0-9). The value
is a URI to use that method. Future methods may be defined in is a URI for the method specified in the key. Future methods may
future specifications and registered with IANA; a calendar client be defined in future specifications and registered with IANA; a
MUST ignore any method it does not understand, but MUST preserve calendar client MUST ignore any method it does not understand, but
the method key and URI. This property MUST be omitted if no MUST preserve the method key and URI. This property MUST be
method is defined (rather than an empty object). omitted if no method is defined (rather than being specified as an
empty object).
The following methods are defined: The following methods are defined:
* "imip": The participant accepts an iMIP [RFC6047] request at * "imip": The participant accepts an iMIP [RFC6047] request at
this email address. The value MUST be a "mailto:" URI. It MAY this email address. The value MUST be a "mailto:" URI. It MAY
be different from the value of the participant's "email" be different from the value of the participant's "email"
property. property.
* "other": The participant is identified by this URI but the * "other": The participant is identified by this URI but the
method how to submit the invitation or update is undefined. method for submitting the invitation is undefined.
o kind: "String" (optional) o kind: "String" (optional)
What kind of entity this participant is, if known. What kind of entity this participant is, if known.
This MUST be either one of the following values, an IANA- This MUST be one of the following values, a value registered in
registered value, or a vendor-specific value. Any value the the IANA JSCalendar Enum Registry, or a vendor-specific value.
client or server doesn't understand should be treated the same as Any value the client or server doesn't understand should be
if this property is omitted. treated the same as if this property is omitted.
* "individual": a single person * "individual": a single person
* "group": a collection of people invited as a whole * "group": a collection of people invited as a whole
* "location": a physical location that needs to be scheduled,
e.g., a conference room
* "resource": a non-human resource, e.g. a projector * "resource": a non-human resource other than a location, such as
a projector
* "location": a physical location involved in the calendar object
that needs to be scheduled, e.g. a conference room.
o roles: "String[Boolean]" (mandatory) o roles: "String[Boolean]" (mandatory)
A set of roles that this participant fulfills. A set of roles that this participant fulfills.
At least one role MUST be specified for the participant. The keys At least one role MUST be specified for the participant. The keys
in the set MUST be either one of the following values, an IANA- in the set MUST be one of the following values, a value registered
registered value, or a vendor-specific value: in the IANA JSCalendar Enum Registry, or a vendor-specific value:
* "owner": The participant is an owner of the object. This * "owner": The participant is an owner of the object. This
signifies they have permission to make changes to it that signifies they have permission to make changes to it that
affect the other participants. Non-owner participants may only affect the other participants. Non-owner participants may only
change properties that just affect themself (for example change properties that just affect themself (for example
setting their own alerts or changing their rsvp status). setting their own alerts or changing their rsvp status).
* "attendee": The participant is expected to attend. * "attendee": The participant is expected to attend.
* "optional": The participant is invited but not required. * "optional": The participant is invited but not required.
skipping to change at page 34, line 42 skipping to change at page 35, line 4
o locationId: "String" (optional) o locationId: "String" (optional)
The location at which this participant is expected to be The location at which this participant is expected to be
attending. attending.
If the value does not correspond to any location id in the If the value does not correspond to any location id in the
"locations" property of the JSCalendar object, this MUST be "locations" property of the JSCalendar object, this MUST be
treated the same as if the participant's locationId were omitted. treated the same as if the participant's locationId were omitted.
o language: "String" (optional) o language: "String" (optional)
The language tag as defined in [RFC5646] that best describes the The language tag as defined in [RFC5646] that best describes the
participant's preferred language, if known. participant's preferred language, if known.
o participationStatus: "String" (optional, default: "needs-action") o participationStatus: "String" (optional, default: "needs-action")
The participation status, if any, of this participant. The participation status, if any, of this participant.
The value MUST be either one of the following values, an IANA- The value MUST be one of the following values, a value registered
registered value, or a vendor-specific value: in the IANA JSCalendar Enum Registry, or a vendor-specific value:
* "needs-action": No status yet set by the participant. * "needs-action": No status yet set by the participant.
* "accepted": The invited participant will participate. * "accepted": The invited participant will participate.
* "declined": The invited participant will not participate. * "declined": The invited participant will not participate.
* "tentative": The invited participant may participate. * "tentative": The invited participant may participate.
* "delegated": The invited participant has delegated their * "delegated": The invited participant has delegated their
skipping to change at page 35, line 31 skipping to change at page 35, line 40
o expectReply: "Boolean" (optional, default: false) o expectReply: "Boolean" (optional, default: false)
If true, the organizer is expecting the participant to notify them If true, the organizer is expecting the participant to notify them
of their participation status. of their participation status.
o scheduleAgent: "String" (optional, default: "server") o scheduleAgent: "String" (optional, default: "server")
Who is responsible for sending scheduling messages with this Who is responsible for sending scheduling messages with this
calendar object to the participant. calendar object to the participant.
The value MUST be either one of the following values, an IANA- The value MUST be one of the following values, a value registered
registered value, or a vendor-specific value: in the IANA JSCalendar Enum Registry, or a vendor-specific value:
* "server": The calendar server will send the scheduling * "server": The calendar server will send the scheduling
messages. messages.
* "client": The calendar client will send the scheduling * "client": The calendar client will send the scheduling
messages. messages.
* "none": No scheduling messages are to be sent to this * "none": No scheduling messages are to be sent to this
participant. participant.
skipping to change at page 36, line 23 skipping to change at page 36, line 33
o invitedBy: "String" (optional) o invitedBy: "String" (optional)
The participant id of the participant who invited this one, if The participant id of the participant who invited this one, if
known. known.
o delegatedTo: "String[Boolean]" (optional) o delegatedTo: "String[Boolean]" (optional)
A set of participant ids that this participant has delegated their A set of participant ids that this participant has delegated their
participation to. Each key in the set MUST be the id of a participation to. Each key in the set MUST be the id of a
participant. The value for each key in the set MUST be true. participant. The value for each key in the set MUST be true. If
This MUST be omitted if none (rather than an empty set). there are no delegates, this MUST be omitted (rather than
specified as an empty set).
o delegatedFrom: "String[Boolean]" (optional) o delegatedFrom: "String[Boolean]" (optional)
A set of participant ids that this participant is acting as a A set of participant ids that this participant is acting as a
delegate for. Each key in the set MUST be the id of a delegate for. Each key in the set MUST be the id of a
participant. The value for each key in the set MUST be true. participant. The value for each key in the set MUST be true. If
This MUST be omitted if none (rather than an empty set). there are no delegators, this MUST be omitted (rather than
specified as an empty set).
o memberOf: "String[Boolean]" (optional) o memberOf: "String[Boolean]" (optional)
A set of group participants that were invited to this calendar A set of group participants that were invited to this calendar
object, which caused this participant to be invited due to their object, which caused this participant to be invited due to their
membership of the group(s). Each key in the set MUST be the id of membership in the group(s). Each key in the set MUST be the id of
a participant. The value for each key in the set MUST be true. a participant. The value for each key in the set MUST be true.
This MUST be omitted if none (rather than an empty set). If there are no groups, this MUST be omitted (rather than
specified as an empty set).
o linkIds: "String[Boolean]" (optional) o linkIds: "String[Boolean]" (optional)
A set of links to more information about this participant, for A set of links to more information about this participant, for
example in vCard format. The keys in the set MUST be the id of a example in vCard format. The keys in the set MUST be the id of a
Link object in the calendar object's "links" property. The value Link object in the calendar object's "links" property. The value
for each key in the set MUST be true. This MUST be omitted if for each key in the set MUST be true. If there are no links, this
none (rather than an empty set). MUST be omitted (rather than specified as an empty set).
o progress: "String" (optional). This is only allowed if the o progress: "String" (optional). This is only allowed if the
Participant is part of a JSTask. It represents the progress of Participant is part of a JSTask. It represents the progress of
the participant for this task, if known. This property MUST NOT the participant for this task, if known. This property MUST NOT
be set if the "participationStatus" of this participant is any be set if the "participationStatus" of this participant is any
value other than "accepted". See Section 5.2.4 for allowed values value other than "accepted". See Section 5.2.4 for allowed values
and semantics. and semantics.
o progressUpdated: "UTCDateTime" (optional). Specifies the date- o progressUpdated: "UTCDateTime" (optional). Specifies the date-
time the progress property was last set on this participant. This time the progress property was last set on this participant. This
skipping to change at page 37, line 39 skipping to change at page 38, line 4
display or send to the user for this calendar object. display or send to the user for this calendar object.
An Alert Object has the following properties: An Alert Object has the following properties:
o @type: "String" (mandatory) o @type: "String" (mandatory)
Specifies the type of this object. This MUST be "Alert". Specifies the type of this object. This MUST be "Alert".
o trigger: "OffsetTrigger|AbsoluteTrigger|UnknownTrigger" o trigger: "OffsetTrigger|AbsoluteTrigger|UnknownTrigger"
(mandatory) (mandatory)
Defines when to trigger the alert. New types may be defined in Defines when to trigger the alert. New types may be defined in
future RFCs. future documents.
An *OffsetTrigger* object has the following properties: An *OffsetTrigger* object has the following properties:
* @type: "String" (mandatory) * @type: "String" (mandatory)
Specifies the type of this object. This MUST be Specifies the type of this object. This MUST be
"OffsetTrigger". "OffsetTrigger".
* offset: "SignedDuration" (mandatory). * offset: "SignedDuration" (mandatory).
skipping to change at page 38, line 38 skipping to change at page 38, line 49
Specifies the type of this object. This MUST be Specifies the type of this object. This MUST be
"AbsoluteTrigger". "AbsoluteTrigger".
* when: "UTCDateTime" (mandatory). * when: "UTCDateTime" (mandatory).
Defines a specific UTC date-time when the alert is triggered. Defines a specific UTC date-time when the alert is triggered.
An *UnknownTrigger* object is an object that contains a *@type* An *UnknownTrigger* object is an object that contains a *@type*
property whose value is not recognized (i.e., not "OffsetTrigger" property whose value is not recognized (i.e., not "OffsetTrigger"
or "AbsoluteTrigger"), plus zero or more other properties. This or "AbsoluteTrigger"), plus zero or more other properties. This
is for compatibility with client extensions and future RFCs. is for compatibility with client extensions and future
Implementations SHOULD NOT trigger for trigger types they do not specifications. Implementations SHOULD NOT trigger for trigger
understand, but MUST preserve them. types they do not understand, but MUST preserve them.
o acknowledged: "UTCDateTime" (optional) o acknowledged: "UTCDateTime" (optional)
This records when an alert was last acknowledged. This is set This records when an alert was last acknowledged. This is set
when the user has dismissed the alert; other clients that sync when the user has dismissed the alert; other clients that sync
this property SHOULD automatically dismiss or suppress duplicate this property SHOULD automatically dismiss or suppress duplicate
alerts (alerts with the same alert id that triggered on or before alerts (alerts with the same alert id that triggered on or before
this date-time). this date-time).
For a recurring calendar object, the "acknowledged" property of For a recurring calendar object, the "acknowledged" property of
skipping to change at page 39, line 16 skipping to change at page 39, line 28
the user sees them, for example email based alerts. For those the user sees them, for example email based alerts. For those
kinds of alerts, this property SHOULD be set immediately when the kinds of alerts, this property SHOULD be set immediately when the
alert is triggered and the action successfully carried out. alert is triggered and the action successfully carried out.
o relatedTo: "String[Relation]" (optional) o relatedTo: "String[Relation]" (optional)
Relates this alert to other alerts in the same JSCalendar object. Relates this alert to other alerts in the same JSCalendar object.
If the user wishes to snooze an alert, the application SHOULD If the user wishes to snooze an alert, the application SHOULD
create an alert to trigger after snoozing. All snooze alerts create an alert to trigger after snoozing. All snooze alerts
SHOULD set a relation to the identifier of the original alert. SHOULD set a relation to the identifier of the original alert.
The Relation object SHOULD set the "parent" relation type, but MAY The Relation object SHOULD set the "parent" relation type.
be empty.
o action: "String" (optional, default: "display") o action: "String" (optional, default: "display")
Describes how to alert the user. Describes how to alert the user.
The value MUST be at most one of the following values, an IANA- The value MUST be at most one of the following values, a value
registered value, or a vendor-specific value: registered in the IANA JSCalendar Enum Registry, or a vendor-
specific value:
* "display": The alert should be displayed as appropriate for the * "display": The alert should be displayed as appropriate for the
current device and user context. current device and user context.
* "email": The alert should trigger an email sent out to the * "email": The alert should trigger an email sent out to the
user, notifying about the alert. This action is typically only user, notifying about the alert. This action is typically only
appropriate for server implementations. appropriate for server implementations.
4.6. Multilingual Properties 4.6. Multilingual Properties
4.6.1. localizations 4.6.1. localizations
Type: "String[PatchObject]" (optional). Type: "String[PatchObject]" (optional).
A map of [RFC5646] language tags to patch objects, which localize the A map of language tags [RFC5646] to patch objects, which localize the
calendar object into the locale of the respective language tag. calendar object into the locale of the respective language tag.
See the description of PatchObject (Section 1.4.8) for the structure See the description of PatchObject (Section 1.4.8) for the structure
of the PatchObject. The patches are applied to the top-level of the PatchObject. The patches are applied to the top-level
calendar object. In addition, the "locale" property of the patched calendar object. In addition, the "locale" property of the patched
object is set to the language tag. All pointers for patches MUST end object is set to the language tag. All pointers for patches MUST end
with one of the following suffixes; any patch that does not follow with one of the following suffixes; any patch that does not follow
this MUST be ignored unless otherwise specified in a future RFC: this MUST be ignored unless otherwise specified in a future RFC:
o title o title
skipping to change at page 40, line 35 skipping to change at page 40, line 47
Identifies the time zone the object is scheduled in, or null for Identifies the time zone the object is scheduled in, or null for
floating time. This is either a name from the IANA Time Zone floating time. This is either a name from the IANA Time Zone
Database [TZDB] or the id of a custom time zone from the "timeZones" Database [TZDB] or the id of a custom time zone from the "timeZones"
property (see Section 1.4.9). If omitted, this MUST be presumed to property (see Section 1.4.9). If omitted, this MUST be presumed to
be null (i.e., floating time). be null (i.e., floating time).
4.7.2. timeZones 4.7.2. timeZones
Type: "String[TimeZone]" (optional). Type: "String[TimeZone]" (optional).
Maps identifiers of custom time zones to their time zone definition. Maps identifiers of custom time zones to their time zone definitions.
The following restrictions apply for each key in the map: The following restrictions apply for each key in the map:
o It MUST start with the "/" character (ASCII decimal 47; also see o It MUST start with the "/" character (ASCII decimal 47; also see
Sections 3.2.19 of [RFC5545] and 3.6. of [RFC7808] for discussion Sections 3.2.19 of [RFC5545] and 3.6. of [RFC7808] for discussion
of the forward slash character in time zone identifiers). of the forward slash character in time zone identifiers).
o It MUST be a valid "paramtext" value as specified in Section 3.1. o It MUST be a valid "paramtext" value as specified in Section 3.1.
of [RFC5545]. of [RFC5545].
o At least one other property in the same JSCalendar object MUST o At least one other property in the same JSCalendar object MUST
reference a time zone using this identifier (i.e. orphaned time reference a time zone using this identifier (i.e., orphaned time
zones are not allowed). zones are not allowed).
An identifier need only be unique to this JSCalendar object. An identifier need only be unique to this JSCalendar object.
A TimeZone object maps a VTIMEZONE component from iCalendar [RFC5545] A TimeZone object maps a VTIMEZONE component from iCalendar [RFC5545]
and the semantics are as defined there. A valid time zone MUST and the semantics are as defined there. A valid time zone MUST
define at least one transition rule in the "standard" or "daylight" define at least one transition rule in the "standard" or "daylight"
property. Its properties are: property. Its properties are:
o @type: "String" (mandatory) o @type: "String" (mandatory)
skipping to change at page 43, line 25 skipping to change at page 43, line 39
discontinuity in the event's time zone, for example a change from discontinuity in the event's time zone, for example a change from
standard time to daylight-savings time. Leap seconds MUST NOT be standard time to daylight-savings time. Leap seconds MUST NOT be
considered when computing an exact duration. When computing an exact considered when computing an exact duration. When computing an exact
duration, the greatest order time components MUST be added first, duration, the greatest order time components MUST be added first,
that is, the number of days MUST be added first, followed by the that is, the number of days MUST be added first, followed by the
number of hours, number of minutes, and number of seconds. number of hours, number of minutes, and number of seconds.
Fractional seconds MUST be added last. These semantics match the Fractional seconds MUST be added last. These semantics match the
iCalendar DURATION value type ([RFC5545], Section 3.3.6). iCalendar DURATION value type ([RFC5545], Section 3.3.6).
A JSEvent MAY involve start and end locations that are in different A JSEvent MAY involve start and end locations that are in different
time zones (e.g. a trans-continental flight). This can be expressed time zones (e.g., a trans-continental flight). This can be expressed
using the "relativeTo" and "timeZone" properties of the JSEvent's using the "relativeTo" and "timeZone" properties of the JSEvent's
Location objects (see Section 4.2.5). Location objects (see Section 4.2.5).
5.1.3. status 5.1.3. status
Type: "String" (optional, default: "confirmed"). Type: "String" (optional, default: "confirmed").
The scheduling status (Section 4.4) of a JSEvent. If set, it MUST be The scheduling status (Section 4.4) of a JSEvent. If set, it MUST be
one of the following values, an IANA-registered value, or a vendor- one of the following values, a value registered in the IANA
specific value: JSCalendar Enum Registry, or a vendor-specific value:
o "confirmed": Indicates the event is definitely happening. o "confirmed": Indicates the event is definitely happening.
o "cancelled": Indicates the event has been cancelled. o "cancelled": Indicates the event has been cancelled.
o "tentative": Indicates the event may happen. o "tentative": Indicates the event may happen.
5.2. JSTask Properties 5.2. JSTask Properties
In addition to the common JSCalendar object properties (Section 4) a In addition to the common JSCalendar object properties (Section 4) a
skipping to change at page 44, line 37 skipping to change at page 45, line 5
is "completed". is "completed".
o "failed": if at least one "progress" property value of a o "failed": if at least one "progress" property value of a
participant is "failed". participant is "failed".
o "in-process": if at least one "progress" property value of a o "in-process": if at least one "progress" property value of a
participant is "in-process". participant is "in-process".
o "needs-action": If none of the other criteria match. o "needs-action": If none of the other criteria match.
If set, it MUST be one of the following values, an IANA-registered If set, it MUST be one of the following values, a value registered in
value, or a vendor-specific value: the IANA JSCalendar Enum Registry, or a vendor-specific value:
o "needs-action": Indicates the task needs action. o "needs-action": Indicates the task needs action.
o "in-process": Indicates the task is in process. o "in-process": Indicates the task is in process.
o "completed": Indicates the task is completed. o "completed": Indicates the task is completed.
o "failed": Indicates the task failed. o "failed": Indicates the task failed.
o "cancelled": Indicates the task was cancelled. o "cancelled": Indicates the task was cancelled.
skipping to change at page 49, line 47 skipping to change at page 50, line 19
"duration": "PT30M", "duration": "PT30M",
"recurrenceRules": [{ "recurrenceRules": [{
"@type": "RecurrenceRule", "@type": "RecurrenceRule",
"frequency": "daily" "frequency": "daily"
}] }]
} }
6.8. Event with multiple locations and localization 6.8. Event with multiple locations and localization
This example illustrates an event that happens at both a physical and This example illustrates an event that happens at both a physical and
a virtual location. Fans can see a live convert on premises or a virtual location. Fans can see a live concert on premises or
online. The event title and descriptions are localized. online. The event title and descriptions are localized.
{ {
"...": "", "...": "",
"title": "Live from Music Bowl: The Band", "title": "Live from Music Bowl: The Band",
"description": "Go see the biggest music event ever!", "description": "Go see the biggest music event ever!",
"locale": "en", "locale": "en",
"start": "2018-07-04T17:00:00", "start": "2018-07-04T17:00:00",
"timeZone": "America/New_York", "timeZone": "America/New_York",
"duration": "PT3H", "duration": "PT3H",
"locations": { "locations": {
"c0503d30-8c50-4372-87b5-7657e8e0fedd": { "c0503d30-8c50-4372-87b5-7657e8e0fedd": {
"@type": "Location", "@type": "Location",
"name": "The Music Bowl", "name": "The Music Bowl",
"description": "Music Bowl, Central Park, New York", "description": "Music Bowl, Central Park, New York",
"coordinates": "geo:40.7829,73.9654" "coordinates": "geo:40.7829,-73.9654"
} }
}, },
"virtualLocations": { "virtualLocations": {
"6f3696c6-1e07-47d0-9ce1-f50014b0041a": { "6f3696c6-1e07-47d0-9ce1-f50014b0041a": {
"@type": "VirtualLocation", "@type": "VirtualLocation",
"name": "Free live Stream from Music Bowl", "name": "Free live Stream from Music Bowl",
"uri": "https://stream.example.com/the_band_2018" "uri": "https://stream.example.com/the_band_2018"
} }
}, },
"localizations": { "localizations": {
skipping to change at page 53, line 17 skipping to change at page 54, line 17
"2018-03-08T09:00:00": { "2018-03-08T09:00:00": {
"participants/dG9tQGZvb2Jhci5xlLmNvbQ/participationStatus": "participants/dG9tQGZvb2Jhci5xlLmNvbQ/participationStatus":
"declined" "declined"
} }
} }
} }
7. Security Considerations 7. Security Considerations
Calendaring and scheduling information is very privacy-sensitive. Calendaring and scheduling information is very privacy-sensitive.
The transmission of such information must be careful to protect it The transmission of such information must be done carefully to
from possible threats, such as eavesdropping, replay, message protect it from possible threats, such as eavesdropping, replay,
insertion, deletion, modification, and man-in-the-middle attacks. message insertion, deletion, modification, and man-in-the-middle
This document just defines the data format; such considerations are attacks. This document just defines the data format; such
primarily the concern of the API or method of storage and considerations are primarily the concern of the API or method of
transmission of such files. storage and transmission of such files.
7.1. Expanding Recurrences 7.1. Expanding Recurrences
A recurrence rule may produce infinite occurrences of an event. A recurrence rule may produce infinite occurrences of an event.
Implementations MUST handle expansions carefully to prevent Implementations MUST handle expansions carefully to prevent
accidental or deliberate resource exhaustion. accidental or deliberate resource exhaustion.
Conversely, a recurrence rule may be specified that does not expand Conversely, a recurrence rule may be specified that does not expand
to anything. It is not always possible to tell this through static to anything. It is not always possible to tell this through static
analysis of the rule, so implementations MUST be careful to avoid analysis of the rule, so implementations MUST be careful to avoid
getting stuck in an infinite loop, or otherwise exhausting resources, getting stuck in infinite loops, or otherwise exhausting resources
searching for the next occurrence. while searching for the next occurrence.
7.2. JSON Parsing 7.2. JSON Parsing
The Security Considerations of [RFC8259] apply to the use of JSON as The Security Considerations of [RFC8259] apply to the use of JSON as
the data interchange format. the data interchange format.
As for any serialization format, parsers need to thoroughly check the As for any serialization format, parsers need to thoroughly check the
syntax of the supplied data. JSON uses opening and closing tags for syntax of the supplied data. JSON uses opening and closing tags for
several types and structures, and it is possible that the end of the several types and structures, and it is possible that the end of the
supplied data will be reached when scanning for a matching closing supplied data will be reached when scanning for a matching closing
skipping to change at page 54, line 25 skipping to change at page 55, line 25
7.3. URI Values 7.3. URI Values
Several JSCalendar properties contain URIs as values, and processing Several JSCalendar properties contain URIs as values, and processing
these properties requires extra care. Section 7 of [RFC3986] these properties requires extra care. Section 7 of [RFC3986]
discusses security risk related to URIs. discusses security risk related to URIs.
8. IANA Considerations 8. IANA Considerations
8.1. Media Type Registration 8.1. Media Type Registration
This document defines a MIME media type for use with JSCalendar data This document defines a media type for use with JSCalendar data
formatted in JSON. formatted in JSON.
Type name: application Type name: application
Subtype name: jscalendar+json Subtype name: jscalendar+json
Required parameters: type Required parameters: type
The "type" parameter conveys the type of the JSCalendar data in The "type" parameter conveys the type of the JSCalendar data in
the body part, with the value being one of "jsevent", "jstask", or the body part, with the value being one of "jsevent", "jstask", or
skipping to change at page 55, line 22 skipping to change at page 56, line 22
Additional information: Additional information:
Magic number(s): N/A Magic number(s): N/A
File extensions(s): N/A File extensions(s): N/A
Macintosh file type code(s): N/A Macintosh file type code(s): N/A
Person & email address to contact for further information: Person & email address to contact for further information:
calext@ietf.org calsify@ietf.org
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: N/A Restrictions on usage: N/A
Author: See the "Author's Address" section of this document. Author: See the "Author's Address" section of this document.
Change controller: IETF Change controller: IETF
8.2. Creation of "JSCalendar Properties" Registry 8.2. Creation of "JSCalendar Properties" Registry
skipping to change at page 56, line 49 skipping to change at page 57, line 49
collisions and encouraging the submitter to document security and collisions and encouraging the submitter to document security and
privacy considerations. For a common-use registration, the DE is privacy considerations. For a common-use registration, the DE is
expected to confirm that suitable documentation, as described in expected to confirm that suitable documentation, as described in
Section 4.6 of [RFC8126], is available to ensure interoperability. Section 4.6 of [RFC8126], is available to ensure interoperability.
This preferably takes the form of an RFC, but for simple definitions This preferably takes the form of an RFC, but for simple definitions
a description in the registry may be sufficient. The DE should also a description in the registry may be sufficient. The DE should also
verify that the property name does not conflict with work that is verify that the property name does not conflict with work that is
active or already published within the IETF. A published active or already published within the IETF. A published
specification is not required for reserved or obsolete registrations. specification is not required for reserved or obsolete registrations.
Before a period of 30 days has passed, the DE will either approve or The DE will either approve or deny the registration request and
deny the registration request and publish a notice of the decision to publish a notice of the decision to the Calext WG mailing list or its
the Calext WG mailing list or its successor, as well as inform IANA. successor, as well as inform IANA. A denial notice must be justified
A denial notice must be justified by an explanation, and, in the by an explanation, and, in the cases where it is possible, concrete
cases where it is possible, concrete suggestions on how the request suggestions on how the request can be modified so as to become
can be modified so as to become acceptable should be provided. acceptable should be provided.
If the DE does not respond within 30 days, the registrant may request
the IESG take action to process the request in a timely manner.
8.2.4. Change Procedures 8.2.4. Change Procedures
Once a JSCalendar property has been published by the IANA, the change Once a JSCalendar property has been published by the IANA, the change
controller may request a change to its definition. The same controller may request a change to its definition. The same
procedure that would be appropriate for the original registration procedure that would be appropriate for the original registration
request is used to process a change request. request is used to process a change request.
JSCalendar property registrations may not be deleted; properties that JSCalendar property registrations may not be deleted; properties that
are no longer believed appropriate for use can be declared obsolete are no longer believed appropriate for use can be declared obsolete
skipping to change at page 57, line 33 skipping to change at page 58, line 30
requested only when there are serious omissions or errors in the requested only when there are serious omissions or errors in the
published specification, as such changes may cause interoperability published specification, as such changes may cause interoperability
issues. When review is required, a change request may be denied if issues. When review is required, a change request may be denied if
it renders entities that were valid under the previous definition it renders entities that were valid under the previous definition
invalid under the new definition. invalid under the new definition.
The owner of a JSCalendar property may pass responsibility to another The owner of a JSCalendar property may pass responsibility to another
person or agency by informing the IANA; this can be done without person or agency by informing the IANA; this can be done without
discussion or review. discussion or review.
The IESG may reassign responsibility for a JSCalendar property. The
most common case of this will be to enable changes to be made to a
registration where the author of the registration has died, moved out
of contact, or is otherwise unable to make changes that are important
to the community.
8.2.5. JMAP Properties Registry Template 8.2.5. JMAP Properties Registry Template
o Property Name: The name of the property. The property name MUST o Property Name: The name of the property. The property name MUST
NOT already be registered for any of the objects listed in NOT already be registered for any of the object types listed in
Context. Objects not listed in Context MAY already have the "Property Context" field of this registration. Other object
registered a different property with the same name. types MAY already have registered a different property with the
same name.
o Property Type: The type of this property, using type signatures as o Property Type: The type of this property, using type signatures as
specified in Section 1.3. The property type MUST be registed in specified in Section 1.3. The property type MUST be registed in
the Type Registry. the Type Registry.
o Property Context: A comma-separated list of JSCalendar object o Property Context: A comma-separated list of JSCalendar object
types this property is allowed on. types this property is allowed on.
o Reference or Description: A brief description or RFC number and o Reference or Description: A brief description or RFC number and
section reference where the property is specified (omitted for section reference where the property is specified (omitted for
skipping to change at page 72, line 44 skipping to change at page 73, 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. Informative References 10. References
[COLORS] "CSS Color Module", <https://www.w3.org/TR/css-color-3/>. 10.1. Normative References
[LINKRELS] [CLDR] "Unicode Common Locale Data Repository",
"IANA Link Relation Types", <http://cldr.unicode.org/>.
<https://www.iana.org/assignments/link-relations/link-
relations.xhtml>.
[MIME] "IANA Media Types", <https://www.iana.org/assignments/ [COLORS] "CSS Color Module", <https://www.w3.org/TR/css-color-3/>.
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>.
[RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397,
DOI 10.17487/RFC2397, August 1998,
<https://www.rfc-editor.org/info/rfc2397>.
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:
Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002,
<https://www.rfc-editor.org/info/rfc3339>. <https://www.rfc-editor.org/info/rfc3339>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005,
<https://www.rfc-editor.org/info/rfc3986>.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
Unique IDentifier (UUID) URN Namespace", RFC 4122,
DOI 10.17487/RFC4122, July 2005,
<https://www.rfc-editor.org/info/rfc4122>.
[RFC4589] Schulzrinne, H. and H. Tschofenig, "Location Types [RFC4589] Schulzrinne, H. and H. Tschofenig, "Location Types
Registry", RFC 4589, DOI 10.17487/RFC4589, July 2006, Registry", RFC 4589, DOI 10.17487/RFC4589, July 2006,
<https://www.rfc-editor.org/info/rfc4589>. <https://www.rfc-editor.org/info/rfc4589>.
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data
Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006, Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006,
<https://www.rfc-editor.org/info/rfc4648>. <https://www.rfc-editor.org/info/rfc4648>.
[RFC4791] Daboo, C., Desruisseaux, B., and L. Dusseault,
"Calendaring Extensions to WebDAV (CalDAV)", RFC 4791,
DOI 10.17487/RFC4791, March 2007,
<https://www.rfc-editor.org/info/rfc4791>.
[RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and [RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and
Scheduling Core Object Specification (iCalendar)", Scheduling Core Object Specification (iCalendar)",
RFC 5545, DOI 10.17487/RFC5545, September 2009, RFC 5545, DOI 10.17487/RFC5545, September 2009,
<https://www.rfc-editor.org/info/rfc5545>. <https://www.rfc-editor.org/info/rfc5545>.
[RFC5546] Daboo, C., Ed., "iCalendar Transport-Independent
Interoperability Protocol (iTIP)", RFC 5546,
DOI 10.17487/RFC5546, December 2009,
<https://www.rfc-editor.org/info/rfc5546>.
[RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying
Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646, Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646,
September 2009, <https://www.rfc-editor.org/info/rfc5646>. September 2009, <https://www.rfc-editor.org/info/rfc5646>.
[RFC5870] Mayrhofer, A. and C. Spanring, "A Uniform Resource [RFC5870] Mayrhofer, A. and C. Spanring, "A Uniform Resource
Identifier for Geographic Locations ('geo' URI)", Identifier for Geographic Locations ('geo' URI)",
RFC 5870, DOI 10.17487/RFC5870, June 2010, RFC 5870, DOI 10.17487/RFC5870, June 2010,
<https://www.rfc-editor.org/info/rfc5870>. <https://www.rfc-editor.org/info/rfc5870>.
[RFC6047] Melnikov, A., Ed., "iCalendar Message-Based
Interoperability Protocol (iMIP)", RFC 6047,
DOI 10.17487/RFC6047, December 2010,
<https://www.rfc-editor.org/info/rfc6047>.
[RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type
Specifications and Registration Procedures", BCP 13, Specifications and Registration Procedures", BCP 13,
RFC 6838, DOI 10.17487/RFC6838, January 2013, RFC 6838, DOI 10.17487/RFC6838, January 2013,
<https://www.rfc-editor.org/info/rfc6838>. <https://www.rfc-editor.org/info/rfc6838>.
[RFC6901] Bryan, P., Ed., Zyp, K., and M. Nottingham, Ed., [RFC6901] Bryan, P., Ed., Zyp, K., and M. Nottingham, Ed.,
"JavaScript Object Notation (JSON) Pointer", RFC 6901, "JavaScript Object Notation (JSON) Pointer", RFC 6901,
DOI 10.17487/RFC6901, April 2013, DOI 10.17487/RFC6901, April 2013,
<https://www.rfc-editor.org/info/rfc6901>. <https://www.rfc-editor.org/info/rfc6901>.
[RFC7265] Kewisch, P., Daboo, C., and M. Douglass, "jCal: The JSON
Format for iCalendar", RFC 7265, DOI 10.17487/RFC7265, May
2014, <https://www.rfc-editor.org/info/rfc7265>.
[RFC7493] Bray, T., Ed., "The I-JSON Message Format", RFC 7493, [RFC7493] Bray, T., Ed., "The I-JSON Message Format", RFC 7493,
DOI 10.17487/RFC7493, March 2015, DOI 10.17487/RFC7493, March 2015,
<https://www.rfc-editor.org/info/rfc7493>. <https://www.rfc-editor.org/info/rfc7493>.
[RFC7529] Daboo, C. and G. Yakushev, "Non-Gregorian Recurrence Rules
in the Internet Calendaring and Scheduling Core Object
Specification (iCalendar)", RFC 7529,
DOI 10.17487/RFC7529, May 2015,
<https://www.rfc-editor.org/info/rfc7529>.
[RFC7808] Douglass, M. and C. Daboo, "Time Zone Data Distribution
Service", RFC 7808, DOI 10.17487/RFC7808, March 2016,
<https://www.rfc-editor.org/info/rfc7808>.
[RFC7986] Daboo, C., "New Properties for iCalendar", RFC 7986,
DOI 10.17487/RFC7986, October 2016,
<https://www.rfc-editor.org/info/rfc7986>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>. <https://www.rfc-editor.org/info/rfc8126>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
Interchange Format", STD 90, RFC 8259, Interchange Format", STD 90, RFC 8259,
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
[LINKRELS]
"IANA Link Relation Types",
<https://www.iana.org/assignments/link-relations/link-
relations.xhtml>.
[MIME] "IANA Media Types", <https://www.iana.org/assignments/
media-types/media-types.xhtml>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005,
<https://www.rfc-editor.org/info/rfc3986>.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
Unique IDentifier (UUID) URN Namespace", RFC 4122,
DOI 10.17487/RFC4122, July 2005,
<https://www.rfc-editor.org/info/rfc4122>.
[RFC4791] Daboo, C., Desruisseaux, B., and L. Dusseault,
"Calendaring Extensions to WebDAV (CalDAV)", RFC 4791,
DOI 10.17487/RFC4791, March 2007,
<https://www.rfc-editor.org/info/rfc4791>.
[RFC5546] Daboo, C., Ed., "iCalendar Transport-Independent
Interoperability Protocol (iTIP)", RFC 5546,
DOI 10.17487/RFC5546, December 2009,
<https://www.rfc-editor.org/info/rfc5546>.
[RFC6047] Melnikov, A., Ed., "iCalendar Message-Based
Interoperability Protocol (iMIP)", RFC 6047,
DOI 10.17487/RFC6047, December 2010,
<https://www.rfc-editor.org/info/rfc6047>.
[RFC7265] Kewisch, P., Daboo, C., and M. Douglass, "jCal: The JSON
Format for iCalendar", RFC 7265, DOI 10.17487/RFC7265, May
2014, <https://www.rfc-editor.org/info/rfc7265>.
[RFC7529] Daboo, C. and G. Yakushev, "Non-Gregorian Recurrence Rules
in the Internet Calendaring and Scheduling Core Object
Specification (iCalendar)", RFC 7529,
DOI 10.17487/RFC7529, May 2015,
<https://www.rfc-editor.org/info/rfc7529>.
[RFC7808] Douglass, M. and C. Daboo, "Time Zone Data Distribution
Service", RFC 7808, DOI 10.17487/RFC7808, March 2016,
<https://www.rfc-editor.org/info/rfc7808>.
[RFC7986] Daboo, C., "New Properties for iCalendar", RFC 7986,
DOI 10.17487/RFC7986, October 2016,
<https://www.rfc-editor.org/info/rfc7986>.
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. 141 change blocks. 
328 lines changed or deleted 348 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/