draft-ietf-calext-jscalendar-09.txt   draft-ietf-calext-jscalendar-10.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: May 9, 2019 November 5, 2018 Expires: May 26, 2019 November 22, 2018
JSCalendar: A JSON representation of calendar data JSCalendar: A JSON representation of calendar data
draft-ietf-calext-jscalendar-09 draft-ietf-calext-jscalendar-10
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 alternative calendaring and scheduling environment. It aims to be an alternative
to the widely deployed iCalendar data format and to be unambiguous, to the widely deployed iCalendar data format and to be unambiguous,
extendable and simple to process. extendable and simple to process.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 May 9, 2019. This Internet-Draft will expire on May 26, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 12 skipping to change at page 2, line 12
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. Relation to the iCalendar format . . . . . . . . . . . . 4 1.1. Relation to the iCalendar format . . . . . . . . . . . . 4
1.2. Notational Conventions . . . . . . . . . . . . . . . . . 5 1.2. Notational Conventions . . . . . . . . . . . . . . . . . 5
2. JSCalendar objects . . . . . . . . . . . . . . . . . . . . . 5 2. JSCalendar objects . . . . . . . . . . . . . . . . . . . . . 5
2.1. JSEvent . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1. JSEvent . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2. JSTask . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.2. JSTask . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3. JSGroup . . . . . . . . . . . . . . . . . . . . . . . . . 6 2.3. JSGroup . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Structure of JSCalendar objects . . . . . . . . . . . . . . . 6 3. Structure of JSCalendar objects . . . . . . . . . . . . . . . 6
3.1. Type signatures . . . . . . . . . . . . . . . . . . . . . 6 3.1. Type signatures . . . . . . . . . . . . . . . . . . . . . 6
3.2. Data Types . . . . . . . . . . . . . . . . . . . . . . . 7 3.2. Data Types . . . . . . . . . . . . . . . . . . . . . . . 7
3.2.1. UTCDate . . . . . . . . . . . . . . . . . . . . . . . 7 3.2.1. UTCDate . . . . . . . . . . . . . . . . . . . . . . . 7
3.2.2. LocalDate . . . . . . . . . . . . . . . . . . . . . . 7 3.2.2. LocalDate . . . . . . . . . . . . . . . . . . . . . . 7
3.2.3. Duration . . . . . . . . . . . . . . . . . . . . . . 7 3.2.3. Duration . . . . . . . . . . . . . . . . . . . . . . 7
3.2.4. PatchObject . . . . . . . . . . . . . . . . . . . . . 8 3.2.4. PatchObject . . . . . . . . . . . . . . . . . . . . . 8
3.2.5. Identifiers . . . . . . . . . . . . . . . . . . . . . 8 3.2.5. Identifiers . . . . . . . . . . . . . . . . . . . . . 8
3.2.6. Normalization and equivalence . . . . . . . . . . . . 8 3.2.6. Normalization and equivalence . . . . . . . . . . . . 9
3.3. Custom property extensions and values . . . . . . . . . . 9 3.3. Custom property extensions and values . . . . . . . . . . 9
4. Common JSCalendar properties . . . . . . . . . . . . . . . . 9 4. Common JSCalendar properties . . . . . . . . . . . . . . . . 9
4.1. Metadata properties . . . . . . . . . . . . . . . . . . . 9 4.1. Metadata properties . . . . . . . . . . . . . . . . . . . 10
4.1.1. @type . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1.1. @type . . . . . . . . . . . . . . . . . . . . . . . . 10
4.1.2. uid . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.1.2. uid . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.1.3. relatedTo . . . . . . . . . . . . . . . . . . . . . . 10 4.1.3. relatedTo . . . . . . . . . . . . . . . . . . . . . . 10
4.1.4. prodId . . . . . . . . . . . . . . . . . . . . . . . 11 4.1.4. prodId . . . . . . . . . . . . . . . . . . . . . . . 11
4.1.5. created . . . . . . . . . . . . . . . . . . . . . . . 11 4.1.5. created . . . . . . . . . . . . . . . . . . . . . . . 12
4.1.6. updated . . . . . . . . . . . . . . . . . . . . . . . 12 4.1.6. updated . . . . . . . . . . . . . . . . . . . . . . . 12
4.1.7. sequence . . . . . . . . . . . . . . . . . . . . . . 12 4.1.7. sequence . . . . . . . . . . . . . . . . . . . . . . 12
4.1.8. method . . . . . . . . . . . . . . . . . . . . . . . 12 4.1.8. method . . . . . . . . . . . . . . . . . . . . . . . 12
4.2. What and where properties . . . . . . . . . . . . . . . . 12 4.2. What and where properties . . . . . . . . . . . . . . . . 12
4.2.1. title . . . . . . . . . . . . . . . . . . . . . . . . 12 4.2.1. title . . . . . . . . . . . . . . . . . . . . . . . . 12
4.2.2. description . . . . . . . . . . . . . . . . . . . . . 12 4.2.2. description . . . . . . . . . . . . . . . . . . . . . 12
4.2.3. descriptionContentType . . . . . . . . . . . . . . . 12 4.2.3. descriptionContentType . . . . . . . . . . . . . . . 12
4.2.4. locations . . . . . . . . . . . . . . . . . . . . . . 13 4.2.4. locations . . . . . . . . . . . . . . . . . . . . . . 13
4.2.5. virtualLocations . . . . . . . . . . . . . . . . . . 14 4.2.5. virtualLocations . . . . . . . . . . . . . . . . . . 14
4.2.6. links . . . . . . . . . . . . . . . . . . . . . . . . 14 4.2.6. links . . . . . . . . . . . . . . . . . . . . . . . . 14
4.2.7. locale . . . . . . . . . . . . . . . . . . . . . . . 15 4.2.7. locale . . . . . . . . . . . . . . . . . . . . . . . 15
4.2.8. keywords . . . . . . . . . . . . . . . . . . . . . . 16 4.2.8. keywords . . . . . . . . . . . . . . . . . . . . . . 16
4.2.9. categories . . . . . . . . . . . . . . . . . . . . . 16 4.2.9. categories . . . . . . . . . . . . . . . . . . . . . 16
4.2.10. color . . . . . . . . . . . . . . . . . . . . . . . . 16 4.2.10. color . . . . . . . . . . . . . . . . . . . . . . . . 16
4.3. Recurrence properties . . . . . . . . . . . . . . . . . . 16 4.3. Recurrence properties . . . . . . . . . . . . . . . . . . 16
4.3.1. recurrenceRule . . . . . . . . . . . . . . . . . . . 16 4.3.1. recurrenceRule . . . . . . . . . . . . . . . . . . . 16
4.3.2. recurrenceOverrides . . . . . . . . . . . . . . . . . 21 4.3.2. recurrenceOverrides . . . . . . . . . . . . . . . . . 22
4.3.3. excluded . . . . . . . . . . . . . . . . . . . . . . 22 4.3.3. excluded . . . . . . . . . . . . . . . . . . . . . . 23
4.4. Sharing and scheduling properties . . . . . . . . . . . . 22 4.4. Sharing and scheduling properties . . . . . . . . . . . . 23
4.4.1. priority . . . . . . . . . . . . . . . . . . . . . . 22 4.4.1. priority . . . . . . . . . . . . . . . . . . . . . . 23
4.4.2. freeBusyStatus . . . . . . . . . . . . . . . . . . . 22 4.4.2. freeBusyStatus . . . . . . . . . . . . . . . . . . . 24
4.4.3. privacy . . . . . . . . . . . . . . . . . . . . . . . 23 4.4.3. privacy . . . . . . . . . . . . . . . . . . . . . . . 24
4.4.4. replyTo . . . . . . . . . . . . . . . . . . . . . . . 24 4.4.4. replyTo . . . . . . . . . . . . . . . . . . . . . . . 25
4.4.5. participants . . . . . . . . . . . . . . . . . . . . 24 4.4.5. participants . . . . . . . . . . . . . . . . . . . . 25
4.5. Alerts properties . . . . . . . . . . . . . . . . . . . . 28 4.5. Alerts properties . . . . . . . . . . . . . . . . . . . . 29
4.5.1. useDefaultAlerts . . . . . . . . . . . . . . . . . . 28 4.5.1. useDefaultAlerts . . . . . . . . . . . . . . . . . . 29
4.5.2. alerts . . . . . . . . . . . . . . . . . . . . . . . 28 4.5.2. alerts . . . . . . . . . . . . . . . . . . . . . . . 29
4.6. Multilingual properties . . . . . . . . . . . . . . . . . 29 4.6. Multilingual properties . . . . . . . . . . . . . . . . . 30
4.6.1. localizations . . . . . . . . . . . . . . . . . . . . 29 4.6.1. localizations . . . . . . . . . . . . . . . . . . . . 30
5. Type-specific JSCalendar properties . . . . . . . . . . . . . 30 5. Type-specific JSCalendar properties . . . . . . . . . . . . . 31
5.1. JSEvent properties . . . . . . . . . . . . . . . . . . . 30 5.1. JSEvent properties . . . . . . . . . . . . . . . . . . . 32
5.1.1. start . . . . . . . . . . . . . . . . . . . . . . . . 31 5.1.1. start . . . . . . . . . . . . . . . . . . . . . . . . 32
5.1.2. timeZone . . . . . . . . . . . . . . . . . . . . . . 31 5.1.2. timeZone . . . . . . . . . . . . . . . . . . . . . . 32
5.1.3. duration . . . . . . . . . . . . . . . . . . . . . . 31 5.1.3. duration . . . . . . . . . . . . . . . . . . . . . . 32
5.1.4. isAllDay . . . . . . . . . . . . . . . . . . . . . . 31 5.1.4. isAllDay . . . . . . . . . . . . . . . . . . . . . . 32
5.1.5. status . . . . . . . . . . . . . . . . . . . . . . . 32 5.1.5. status . . . . . . . . . . . . . . . . . . . . . . . 33
5.2. JSTask properties . . . . . . . . . . . . . . . . . . . . 32 5.2. JSTask properties . . . . . . . . . . . . . . . . . . . . 33
5.2.1. due . . . . . . . . . . . . . . . . . . . . . . . . . 32 5.2.1. due . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.2.2. start . . . . . . . . . . . . . . . . . . . . . . . . 32 5.2.2. start . . . . . . . . . . . . . . . . . . . . . . . . 33
5.2.3. timeZone . . . . . . . . . . . . . . . . . . . . . . 32 5.2.3. timeZone . . . . . . . . . . . . . . . . . . . . . . 33
5.2.4. estimatedDuration . . . . . . . . . . . . . . . . . . 33 5.2.4. estimatedDuration . . . . . . . . . . . . . . . . . . 34
5.2.5. statusUpdatedAt . . . . . . . . . . . . . . . . . . . 33 5.2.5. statusUpdatedAt . . . . . . . . . . . . . . . . . . . 34
5.2.6. isAllDay . . . . . . . . . . . . . . . . . . . . . . 33 5.2.6. isAllDay . . . . . . . . . . . . . . . . . . . . . . 34
5.2.7. progress . . . . . . . . . . . . . . . . . . . . . . 33 5.2.7. progress . . . . . . . . . . . . . . . . . . . . . . 34
5.2.8. status . . . . . . . . . . . . . . . . . . . . . . . 34 5.2.8. status . . . . . . . . . . . . . . . . . . . . . . . 35
5.3. JSGroup properties . . . . . . . . . . . . . . . . . . . 35 5.3. JSGroup properties . . . . . . . . . . . . . . . . . . . 36
5.3.1. entries . . . . . . . . . . . . . . . . . . . . . . . 35 5.3.1. entries . . . . . . . . . . . . . . . . . . . . . . . 36
5.3.2. source . . . . . . . . . . . . . . . . . . . . . . . 35 5.3.2. source . . . . . . . . . . . . . . . . . . . . . . . 36
6. Conversion from and to iCalendar . . . . . . . . . . . . . . 35 6. Conversion from and to iCalendar . . . . . . . . . . . . . . 36
6.1. JSEvent . . . . . . . . . . . . . . . . . . . . . . . . . 36 6.1. JSEvent . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.2. JSTask . . . . . . . . . . . . . . . . . . . . . . . . . 36 6.2. JSTask . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.3. JSGroup . . . . . . . . . . . . . . . . . . . . . . . . . 38 6.3. JSGroup . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.4. Common properties . . . . . . . . . . . . . . . . . . . . 38 6.4. Common properties . . . . . . . . . . . . . . . . . . . . 39
6.5. Locations and participants . . . . . . . . . . . . . . . 40 6.5. Locations and participants . . . . . . . . . . . . . . . 41
6.6. Unknown properties . . . . . . . . . . . . . . . . . . . 43 6.6. Unknown properties . . . . . . . . . . . . . . . . . . . 44
7. JSCalendar object examples . . . . . . . . . . . . . . . . . 43 7. JSCalendar object examples . . . . . . . . . . . . . . . . . 44
7.1. Simple event . . . . . . . . . . . . . . . . . . . . . . 43 7.1. Simple event . . . . . . . . . . . . . . . . . . . . . . 44
7.2. Simple task . . . . . . . . . . . . . . . . . . . . . . . 44 7.2. Simple task . . . . . . . . . . . . . . . . . . . . . . . 45
7.3. Simple group . . . . . . . . . . . . . . . . . . . . . . 44 7.3. Simple group . . . . . . . . . . . . . . . . . . . . . . 45
7.4. All-day event . . . . . . . . . . . . . . . . . . . . . . 44 7.4. All-day event . . . . . . . . . . . . . . . . . . . . . . 45
7.5. Task with a due date . . . . . . . . . . . . . . . . . . 45 7.5. Task with a due date . . . . . . . . . . . . . . . . . . 46
7.6. Event with end time zone . . . . . . . . . . . . . . . . 45 7.6. Event with end time-zone . . . . . . . . . . . . . . . . 46
7.7. Floating-time event (with recurrence) . . . . . . . . . . 46 7.7. Floating-time event (with recurrence) . . . . . . . . . . 47
7.8. Event with multiple locations and localization . . . . . 46 7.8. Event with multiple locations and localization . . . . . 47
7.9. Recurring event with overrides . . . . . . . . . . . . . 47 7.9. Recurring event with overrides . . . . . . . . . . . . . 48
7.10. Recurring event with participants . . . . . . . . . . . . 48 7.10. Recurring event with participants . . . . . . . . . . . . 49
8. Security Considerations . . . . . . . . . . . . . . . . . . . 50 8. Security Considerations . . . . . . . . . . . . . . . . . . . 51
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 51
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 50 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 51
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 50 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 51
11.1. Normative References . . . . . . . . . . . . . . . . . . 50 11.1. Normative References . . . . . . . . . . . . . . . . . . 51
11.2. Informative References . . . . . . . . . . . . . . . . . 52 11.2. Informative References . . . . . . . . . . . . . . . . . 53
11.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 53 11.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 53 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 54
1. Introduction 1. Introduction
This document defines a data model for calendar event and task This document defines a data model for calendar event and task
objects, or groups of such objects, in electronic calendar objects, or groups of such objects, in electronic calendar
applications and systems. It aims to be unambiguous, extendable and applications and systems. It aims to be unambiguous, extendable and
simple to process. simple to process.
The key design considerations for this data model are as follows: The key design considerations for this data model are as follows:
skipping to change at page 5, line 30 skipping to change at page 5, line 30
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
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. In this document, property and object definitions
are formatted like *this* and are referred to in other sections like
_this_. Verbatim text is formatted like "this".
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/calendar+json;type=jsevent" MIME type: "application/calendar+json;type=jsevent"
skipping to change at page 8, line 42 skipping to change at page 8, line 45
o Anything else: The value to replace the inherited property on the o Anything else: The value to replace the inherited property on the
patch object with (if present) or add to the property (if not patch object with (if present) or add to the property (if not
present). present).
Implementations MUST reject a PatchObject if any of its patches are Implementations MUST reject a PatchObject if any of its patches are
invalid. invalid.
3.2.5. Identifiers 3.2.5. Identifiers
If not noted otherwise, properties and object keys that define If not noted otherwise, properties and object keys that define
identifiers MUST be string values, MUST be at least 1 character in identifiers MUST be string values, MUST be at least 1 character and
length and maximum 256 octets in size, and MUST only contain maximum 256 characters in size, and MUST only contain characters from
characters from the "URL and Filename safe" Base 64 Alphabet, as the "URL and Filename safe" Base 64 Alphabet, as defined in section 5
defined in section 5 of [RFC4648]. This is the ASCII alphanumeric of [RFC4648]. This is the ASCII alphanumeric characters (A-Za-z0-9),
characters (A-Za-z0-9), hyphen (-), and underscore (_). hyphen (-), and underscore (_). Note that [RFC7493] requires string
values be encoded in UTF-8, so the maximum size of an identifier
according to this definition is 256 octets.
3.2.6. Normalization and equivalence 3.2.6. Normalization and equivalence
JSCalendar aims to provide unambiguous definitions for value types JSCalendar aims to provide unambiguous definitions for value types
and properties, but does not define a general normalization or and properties, but does not define a general normalization or
equivalence method for JSCalendar objects and types. This is because equivalence method for JSCalendar objects and types. This is because
the notion of equivalence might range from byte-level equivalence to the notion of equivalence might range from byte-level equivalence to
semantic equivalence, depending on the respective use case (for semantic equivalence, depending on the respective use case (for
example, the CalDAV protocol [RFC4791] requires octet equivalence of example, the CalDAV protocol [RFC4791] requires octet equivalence of
the encoded calendar object to determine ETag equivalence). the encoded calendar object to determine ETag equivalence).
skipping to change at page 12, line 37 skipping to change at page 12, line 43
Type: "String" (optional, default:"") Type: "String" (optional, default:"")
A short summary of the object. A short summary of the object.
4.2.2. description 4.2.2. description
Type: "String" (optional, default:"") Type: "String" (optional, default:"")
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 MUST be "utf-8", if define parameters and the "charset" parameter MUST be "utf-8", if
specified. Descriptions of type "text/html" MAY contain "cid" URLs specified. Descriptions of type "text/html" MAY contain "cid" URLs
([RFC2392]) to reference links in the calendar object by use of the ([RFC2392]) to reference links in the calendar object by use of the
*cid* property of the *Link* object. _cid_ property of the _Link_ object.
4.2.4. locations 4.2.4. locations
Type: "String[Location]" (optional) Type: "String[Location]" (optional)
A map of location ids to Location objects, representing locations A map of location ids to Location objects, representing locations
associated with the object. A location id MUST be unique to this associated with the object. A location id MUST be unique to this
object; a UUID is a practical choice. object; a UUID is a practical choice.
A *Location* object has the following properties. It must define at A *Location* object has the following properties. It must define at
least one other property than *rel*. least one other property than _rel_.
o *name*: "String" (optional, default:"") The human-readable name of o *name*: "String" (optional, default:"") The human-readable name of
the location. the location.
o *description*: "String" (optional) Human-readable, plain-text o *description*: "String" (optional) Human-readable, plain-text
instructions for accessing this location. This may be an address, instructions for accessing this location. This may be an address,
set of directions, door access code, etc. set of directions, door access code, etc.
o *rel*: "String" (optional) The relation type of this location to o *rel*: "String" (optional) The relation type of this location to
the JSCalendar object. the JSCalendar object.
skipping to change at page 13, line 43 skipping to change at page 13, line 46
* "end": The JSCalendar object ends at this location. * "end": The JSCalendar object ends at this location.
o *timeZone*: "String" (optional) A time zone for this location. o *timeZone*: "String" (optional) A time zone for this location.
o *coordinates*: "String" (optional) An [RFC5870] "geo:" URI for the o *coordinates*: "String" (optional) An [RFC5870] "geo:" URI for the
location. location.
o *linkIds*: "String[Boolean]" (optional) A set of link ids for o *linkIds*: "String[Boolean]" (optional) A set of link ids for
links to alternate representations of this location. Each key in links to alternate representations of this location. Each key in
the set MUST be the identifier of a Link object defined in the the set MUST be the identifier of a Link object defined in the
*links* property of this calendar object. The value for each key _links_ property of this calendar object. The value for each key
in the set MUST be "true". This MUST be omitted if none (rather in the set MUST be "true". This MUST be omitted if none (rather
than an empty set). than 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.5. virtualLocations 4.2.5. virtualLocations
Type: "String[VirtualLocation]" (optional) Type: "String[VirtualLocation]" (optional)
skipping to change at page 14, line 50 skipping to change at page 14, line 50
o *href*: "String" A URI from which the resource may be fetched. o *href*: "String" 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, but it is recommended that the file be
hosted on a server to avoid embedding arbitrarily large data in hosted on a server to avoid embedding arbitrarily large data in
JSCalendar object instances. JSCalendar object instances.
o *cid* "String" (optional) This MUST be a valid "content-id" value o *cid* "String" (optional) This MUST be a valid "content-id" value
according to the definition of section 2 in [RFC2392]. The according to the definition of section 2 in [RFC2392]. The
identifier MUST be unique within this JSCalendar object but has no identifier MUST be unique within this JSCalendar object but has no
meaning beyond that. Specifically, it MAY be different from the meaning beyond that. Specifically, it MAY be different from the
link identifier in the enclosing *links* property. link identifier in the enclosing _links_ property.
o *type*: "String" (optional) The content-type [RFC6838] of the o *type*: "String" (optional) The content-type [RFC6838] of the
resource, if known. resource, if known.
o *size*: "Number" (optional) The size, in bytes, of the resource o *size*: "Number" (optional) The size, in bytes, of the resource
when fully decoded (i.e. the number of bytes in the file the user when fully decoded (i.e. the number of bytes in the file the user
would download), if known. would download), if known.
o *rel*: "String" (optional) Identifies the relation of the linked o *rel*: "String" (optional, default:"enclosure") Identifies the
resource to the object. If set, the value MUST be a registered relation of the linked resource to the object. If set, the value
relation type (see [RFC8288] and IANA Link Relations [1]). MUST be a registered relation type (see [RFC8288] and IANA Link
Relations [1]).
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 alternate 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) Describes the intended purpose of a o *display*: "String" (optional) Describes the intended purpose of a
link to an image. If set, the *rel* property MUST be set to link to an image. If set, the _rel_ property MUST be set to
"icon". The value MUST be either one of the following values, "icon". The value MUST be either one of the following values,
registered in a future RFC, or a vendor-specific value: registered in a future RFC, or a vendor-specific value:
* "badge": an image inline with the title of the object * "badge": an image inline with 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
skipping to change at page 16, line 21 skipping to change at page 16, line 21
for each key in the map MUST be "true". for each key in the map MUST be "true".
4.2.9. categories 4.2.9. categories
Type: "String[Boolean]" (optional) Type: "String[Boolean]" (optional)
A set of categories that relate to the calendar object. The set is A set of categories that relate to the calendar object. The set is
represented as a map, with the keys being the categories specified as represented as a map, with the keys being the categories specified as
URIs. The value for each key in the map MUST be "true". URIs. The value for each key in the map MUST be "true".
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.10. color 4.2.10. color
Type: "String" (optional) Type: "String" (optional)
Specifies a color clients MAY use when displaying this calendar Specifies a color clients MAY use when displaying this calendar
object. The value is a case-insensitive color name taken from the object. The value is a case-insensitive color name taken from the
skipping to change at page 16, line 46 skipping to change at page 16, line 46
4.3.1. recurrenceRule 4.3.1. recurrenceRule
Type: "Recurrence" Type: "Recurrence"
Defines a recurrence rule (repeating pattern) for recurring calendar Defines a recurrence rule (repeating pattern) for recurring calendar
objects. objects.
A *Recurrence* object is a JSON object mapping of a RECUR value type A *Recurrence* object is a JSON object mapping of a RECUR value type
in iCalendar, see [RFC5545] and[RFC7529]. A JSEvent recurs by in iCalendar, see [RFC5545] and[RFC7529]. A JSEvent recurs by
applying the recurrence rule (and *recurrenceOverrides*) to the applying the recurrence rule (and _recurrenceOverrides_) to the
*start* date/time. A JSTask recurs by applying the recurrence rule _start_ date/time. A JSTask recurs by applying the recurrence rule
(and *recurrenceOverrides*) to its *start* date/time, if defined. If (and _recurrenceOverrides_) to its _start_ date/time, if defined. If
the task does not define a start date-time, it recurs by its *due* the task does not define a start date-time, it recurs by its _due_
date-time. If it neither defines a start or due date-time, it MUST date-time. If it neither defines a start or due date-time, it MUST
NOT define a *recurrenceRule*. NOT define a _recurrenceRule_.
A Recurrence object has the following properties: A Recurrence object has the following properties:
o *frequency*: "String" This MUST be one of the following values: o *frequency*: "String" This MUST be one of the following values:
* "yearly" * "yearly"
* "monthly" * "monthly"
* "weekly" * "weekly"
skipping to change at page 17, line 49 skipping to change at page 17, line 49
o *byDay*: "NDay[]" (optional) An *NDay* object has the following o *byDay*: "NDay[]" (optional) An *NDay* object has the following
properties: properties:
* *day*: "String" The day-of-the-week part of the BYDAY value in * *day*: "String" The day-of-the-week part of the BYDAY value in
iCalendar, lower-cased. MUST be one of the following values: iCalendar, lower-cased. MUST be one of the following values:
""mo"|"tu"|"we"|"th"|"fr"|"sa"|"su"". ""mo"|"tu"|"we"|"th"|"fr"|"sa"|"su"".
* *nthOfPeriod*: "Number" (optional) The ordinal part of the * *nthOfPeriod*: "Number" (optional) The ordinal part of the
BYDAY value in iCalendar (e.g. ""+1"" or ""-3""). If present, BYDAY value in iCalendar (e.g. ""+1"" or ""-3""). If present,
rather than representing every occurrence of the weekday rather than representing every occurrence of the weekday
defined in the *day* property of this *NDay*, it represents defined in the _day_ property of this _NDay_, it represents
only a specific instance within the recurrence period. The only a specific instance within the recurrence period. The
value can be positive or negative, but MUST NOT be zero. A value can be positive or negative, but MUST NOT be zero. A
negative integer means nth-last of period. negative integer means nth-last of period.
o *byMonthDay*: "Number[]" (optional) The BYMONTHDAY part from o *byMonthDay*: "Number[]" (optional) The BYMONTHDAY part from
iCalendar. The array MUST have at least one entry if included. iCalendar. The array MUST have at least one entry if included.
o *byMonth*: "String[]" (optional) The BYMONTH part from iCalendar. o *byMonth*: "String[]" (optional) The BYMONTH part from iCalendar.
Each entry is a string representation of a number, starting from Each entry is a string representation of a number, starting from
"1" for the first month in the calendar (e.g. ""1" " means "1" for the first month in the calendar (e.g. ""1" " means
skipping to change at page 18, line 34 skipping to change at page 18, line 34
o *byMinute*: "Number[]" (optional) The BYMINUTE part from o *byMinute*: "Number[]" (optional) The BYMINUTE part from
iCalendar. The array MUST have at least one entry if included. iCalendar. The array MUST have at least one entry if included.
o *bySecond*: "Number[]" (optional) The BYSECOND part from o *bySecond*: "Number[]" (optional) The BYSECOND part from
iCalendar. The array MUST have at least one entry if included. iCalendar. The array MUST have at least one entry if included.
o *bySetPosition*: "Number[]" (optional) The BYSETPOS part from o *bySetPosition*: "Number[]" (optional) The BYSETPOS part from
iCalendar. The array MUST have at least one entry if included. iCalendar. The array MUST have at least one entry if included.
o *count*: "Number" (optional) The COUNT part from iCalendar. This o *count*: "Number" (optional) The COUNT part from iCalendar. This
MUST NOT be included if an *until* property is specified. MUST NOT be included if an _until_ property is specified.
o *until*: "LocalDate" (optional) The UNTIL part from iCalendar. o *until*: "LocalDate" (optional) The UNTIL part from iCalendar.
This MUST NOT be included if a *count* property is specified. This MUST NOT be included if a _count_ property is specified.
Note, as in iCalendar, this date is presumed to be in the time Note, as in iCalendar, this date is presumed to be in the time
zone specified in *timeZone*. It is not a UTC time. zone specified in _timeZone_. It is not a UTC time.
A recurrence rule specifies a set of set of date-times for recurring A recurrence rule specifies a set of set of date-times for recurring
calendar objects. A recurrence rule has the following semantics: calendar objects. A recurrence rule has the following semantics.
Note, wherever "year", "month" or "day of month" is used, this is
within the calendar system given by the "rscale" property, which
defaults to gregorian if omitted.
1. A set of candidates is generated. This is every second within a 1. A set of candidates is generated. This is every second within a
period defined by the frequency property: period defined by the frequency property:
* *yearly*: every second from midnight on the 1st January * *yearly*: every second from midnight on the 1st day of a year
(inclusive) to midnight the following 1st January (exclusive) (inclusive) to midnight the 1st day of the following year
(exclusive).
* *monthly*: every second from midnight on the 1st of a month If skip is not "omit", the calendar system has leap months and
(inclusive) to midnight on the 1st of the following month there is a byMonth property, generate candidates for the leap
(exclusive) months even if they don't occur in this year.
If skip is not "omit" and there is a byMonthDay property,
presume each month has the maximum number of days any month
may have in this calendar system when generating candidates,
even if it's more than this month actually has.
* *monthly*: every second from midnight on the 1st day of a
month (inclusive) to midnight on the 1st of the following
month (exclusive).
If skip is not "omit" and there is a byMonthDay property,
presume the month has the maximum number of days any month may
have in this calendar system when generating candidates, even
if it's more than this month actually has.
* *weekly*: every second from midnight (inclusive) on the first * *weekly*: every second from midnight (inclusive) on the first
day of the week (as defined by the firstDayOfWeek property, or day of the week (as defined by the firstDayOfWeek property, or
Monday if omitted), to midnight 7 days later (exclusive). Monday if omitted), to midnight 7 days later (exclusive).
* *daily*: every second from midnight at the start of the day * *daily*: every second from midnight at the start of the day
(inclusive) to midnight at the end of the day (exclusive). (inclusive) to midnight at the end of the day (exclusive).
* *hourly*: every second from the beginning of the hour * *hourly*: every second from the beginning of the hour
(inclusive) to the beginning of the next hour (exclusive). (inclusive) to the beginning of the next hour (exclusive).
skipping to change at page 19, line 29 skipping to change at page 19, line 47
2. Each date-time candidate is compared against all of the byX 2. Each date-time candidate is compared against all of the byX
properties of the rule except bySetPosition. If any property in properties of the rule except bySetPosition. If any property in
the rule does not match the date-time, it is eliminated. Each the rule does not match the date-time, it is eliminated. Each
byX property is an array; the date-time matches the property if byX property is an array; the date-time matches the property if
it matches any of the values in the array. The properties have it matches any of the values in the array. The properties have
the following semantics: the following semantics:
* *byMonth*: the date-time is in the given month. * *byMonth*: the date-time is in the given month.
* *byWeekNo*: the date-time is in the nth week of the year.
Negative numbers mean the nth last week of the year. This
corresponds to weeks according to week numbering as defined in
ISO.8601.2004, with a week defined as a seven day period,
starting on the firstDayOfWeek property value or Monday if
omitted. Week number one of the calendar year is the first
week that contains at least four days in that calendar year.
If the date-time is not valid (this may happen when generating
candidates with a skip property in effect), it is always
eliminated by this property.
* *byYearDay*: the date-time is on the nth day of year.
Negative numbers mean the nth last day of the year.
If the date-time is not valid (this may happen when generating
candidates with a skip property in effect), it is always
eliminated by this property.
* *byMonthDay*: the date-time is on the given day of the month. * *byMonthDay*: the date-time is on the given day of the month.
Negative numbers mean the nth last day of the month. Negative numbers mean the nth last day of the month.
* *byDay*: the date-time is on the given day of the week. If * *byDay*: the date-time is on the given day of the week. If
the day is prefixed by a number, it is the nth occurrence of the day is prefixed by a number, it is the nth occurrence of
that day of the week within the month (if frequency is that day of the week within the month (if frequency is
monthly) or year (if frequency is yearly). Negative numbers monthly) or year (if frequency is yearly). Negative numbers
means nth last occurrence within that period. means nth last occurrence within that period.
* *byYearDay*: the date-time is on the nth day of year.
Negative numbers mean the nth last day of the year.
* *byWeekNo*: the date-time is in the nth week of the year.
Negative numbers mean the nth last week of the year. This
corresponds to weeks according to week numbering as defined in
ISO.8601.2004, with a week defined as a seven day period,
starting on the firstDayOfWeek property value or Monday if
omitted. Week number one of the calendar year is the first
week that contains at least four days in that calendar year.
* *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
candidates that do not correspond to valid dates (e.g. 31st
Februrary in the gregorian calendar). In this case, the
properties MUST be considered in the order above and:
1. After applying the byMonth filter, if the candidate's month
is invalid for the given year increment it (if skip is
"forward") or decrement it (if skip is "backward") until a
valid month is found, incrementing/decrementing the year as
well if you pass through the beginning/end of the year. This
only applies to calendar systems with leap months.
2. After applying the byMonthDay filter, if the day of the month
is invalid for the given month and year, change the date to
the first day of the next month (if skip == "forward") or the
last day of the current month (if skip == "backward").
3. If any valid date produced after applying the skip is already
a candidate, eliminate the duplicate. (For example after
adjusting, 30th Februrary and 31st February would both become
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 further dates are required (we have not reached the until 5. If a skip property is included and is not "omit", eliminate any
date-times that have already been produced by previous iterations
of the algorithm. (This is not possible if skip == "omit".)
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 start date-time is always the first occurrence in the 1. The start date-time is always the first occurrence in the
expansion (and is counted if the recurrence is limited by a expansion (and is counted if the recurrence is limited by a
"count" property), even if it would normally not match the rule. "count" property), even if it would normally not match the rule.
skipping to change at page 21, line 37 skipping to change at page 22, line 41
A map of the recurrence-ids (the date-time of the start of the A map of the recurrence-ids (the date-time of the start of the
occurrence) to an object of patches to apply to the generated occurrence) to an object of patches to apply to the generated
occurrence object. occurrence object.
If the recurrence-id does not match an expanded start date from a If the recurrence-id does not match an expanded start date from a
recurrence rule, it is to be treated as an additional occurrence recurrence rule, it is to be treated as an additional occurrence
(like an RDATE from iCalendar). The patch object may often be empty (like an RDATE from iCalendar). The patch object may often be empty
in this case. in this case.
If the patch object defines the *excluded* property to be "true", If the patch object defines the _excluded_ property to be "true",
then the recurring calendar object does not occur at the recurrence- then the recurring calendar object does not occur at the recurrence-
id date-time (like an EXDATE from iCalendar). Such a patch object id date-time (like an EXDATE from iCalendar). Such a patch object
MUST NOT patch any other property. MUST NOT patch any other property.
By default, an occurrence inherits all properties from the main By default, an occurrence inherits all properties from the main
object except the start (or due) date-time, which is shifted to the object except the start (or due) date-time, which is shifted to the
new start time of the LocalDate key. However, individual properties new start time of the LocalDate key. However, individual properties
of the occurrence can be modified by a patch, or multiple patches. of the occurrence can be modified by a patch, or multiple patches.
It is valid to patch the start property value, and this patch takes It is valid to patch the start property value, and this patch takes
precedence over the LocalDate key. Both the LocalDate key as well as precedence over the LocalDate key. Both the LocalDate key as well as
skipping to change at page 25, line 27 skipping to change at page 26, line 29
is a URI to use that method. Future methods may be defined in is a URI to use that method. Future methods may be defined in
future specifications; a calendar client MUST ignore any method it future specifications; a calendar client MUST ignore any method it
does not understand, but MUST preserve the method key and URI. does not understand, but MUST preserve the method key and URI.
This property MUST be omitted if no method is defined (rather than This property MUST be omitted if no method is defined (rather than
an empty object). 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 how to submit the invitation or update is undefined.
o *kind*: "String" (optional) What kind of entity this participant o *kind*: "String" (optional) What kind of entity this participant
is, if known. is, if known.
This MUST be either one of the following values, registered in a This MUST be either one of the following values, registered in a
future RFC, or a vendor-specific value. Any value the client or future RFC, or a vendor-specific value. Any value the client or
skipping to change at page 26, line 25 skipping to change at page 27, line 28
when it occurs. when it occurs.
The value for each key in the set MUST be "true". Roles that are The value for each key in the set MUST be "true". Roles that are
unknown to the implementation MUST be preserved and MAY be unknown to the implementation MUST be preserved and MAY be
ignored. ignored.
o *locationId*: "String" (optional) The location at which this o *locationId*: "String" (optional) The location at which this
participant is expected to be attending. participant is expected to be 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 instance, this MUST be treated the _locations_ property of the instance, this MUST be treated the
same as if the participant's locationId were omitted. same as if the participant's locationId were omitted.
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, registered The value MUST be either one of the following values, registered
in a future RFC, or a vendor-specific value: in a future RFC, or a vendor-specific value:
* "needs-action": No status yet set by the participant. * "needs-action": No status yet set by the participant.
skipping to change at page 27, line 24 skipping to change at page 28, line 27
o *scheduleSequence*: "Number" (optional, default:"0") The sequence o *scheduleSequence*: "Number" (optional, default:"0") The sequence
number of the last response from the participant. If defined, number of the last response from the participant. If defined,
this MUST be a non-negative integer. this MUST be a non-negative integer.
This can be used to determine whether the participant has sent a This can be used to determine whether the participant has sent a
new RSVP following significant changes to the calendar object, and new RSVP following significant changes to the calendar object, and
to determine if future responses are responding to a current or to determine if future responses are responding to a current or
older view of the data. older view of the data.
o *scheduleUpdated*: "UTCDate" (optional) The *updated* property of o *scheduleUpdated*: "UTCDate" (optional) The _updated_ property of
the last iMIP response from the participant. the last iMIP response from the participant.
This can be compared to the *updated* timestamp in future iMIP This can be compared to the _updated_ timestamp in future iMIP
responses to determine if the response is older or newer than the responses to determine if the response is older or newer than the
current data. current data.
o *invitedBy*: "String" (optional) The participant id of the o *invitedBy*: "String" (optional) The participant id of the
participant who invited this one, if known. participant who invited this one, if known.
o *delegatedTo*: "String[Boolean]" (optional) A set of participant o *delegatedTo*: "String[Boolean]" (optional) A set of participant
ids that this participant has delegated their participation to. ids that this participant has delegated their participation to.
Each key in the set MUST be the identifier of a participant. The Each key in the set MUST be the identifier of a participant. The
value for each key in the set MUST be "true". This MUST be value for each key in the set MUST be "true". This MUST be
skipping to change at page 28, line 8 skipping to change at page 29, line 10
o *memberOf*: "String[Boolean]" (optional) A set of group o *memberOf*: "String[Boolean]" (optional) A set of group
participants that were invited to this calendar object, which participants that were invited to this calendar object, which
caused this participant to be invited due to their membership of caused this participant to be invited due to their membership of
the group(s). Each key in the set MUST be the identifier of a the group(s). Each key in the set MUST be the identifier 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".
This MUST be omitted if none (rather than an empty set). This MUST be omitted if none (rather than an empty set).
o *linkIds*: "String[Boolean]" (optional) A set of links to more o *linkIds*: "String[Boolean]" (optional) A set of links to more
information about this participant, for example in vCard format. information about this participant, for example in vCard format.
The keys in the set MUST be the identifier of a Link object in the The keys in the set MUST be the identifier of a Link object in the
calendar object's *links* property. The value for each key in the calendar object's _links_ property. The value for each key in the
set MUST be "true". This MUST be omitted if none (rather than an set MUST be "true". This MUST be omitted if none (rather than an
empty set). empty set).
4.5. Alerts properties 4.5. Alerts properties
4.5.1. useDefaultAlerts 4.5.1. useDefaultAlerts
Type: "Boolean" (optional, default:"false") Type: "Boolean" (optional, default:"false")
If "true", use the user's default alerts and ignore the value of the If "true", use the user's default alerts and ignore the value of the
*alerts* property. Fetching user defaults is dependent on the API _alerts_ property. Fetching user defaults is dependent on the API
from which this JSCalendar object is being fetched, and is not from which this JSCalendar object is being fetched, and is not
defined in this specification. If an implementation cannot determine defined in this specification. If an implementation cannot determine
the user's default alerts, or none are set, it MUST process the the user's default alerts, or none are set, it MUST process the
alerts property as if useDefaultAlerts is set to "false". alerts property as if useDefaultAlerts is set to "false".
4.5.2. alerts 4.5.2. alerts
Type: "String[Alert]" (optional) Type: "String[Alert]" (optional)
A map of alert ids to Alert objects, representing alerts/reminders to A map of alert ids to Alert objects, representing alerts/reminders to
skipping to change at page 29, line 13 skipping to change at page 30, line 15
zone to use is implementation specific. zone to use is implementation specific.
o *acknowledged*: "UTCDate" (optional) o *acknowledged*: "UTCDate" (optional)
When the user has permanently dismissed the alert the client MUST When the user has permanently dismissed the alert the client MUST
set this to the current time in UTC. Other clients which sync set this to the current time in UTC. Other clients which sync
this property can then automatically dismiss or suppress duplicate this property can then 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
the parent object MUST be updated, unless the alert is already the parent object MUST be updated, unless the alert is already
overridden in *recurrenceOverrides*. overridden in _recurrenceOverrides_.
o *snoozed*: "UTCDate" (optional) o *snoozed*: "UTCDate" (optional)
If the user temporarily dismisses the alert, this is the UTC date- If the user temporarily dismisses the alert, this is the UTC date-
time after which it should trigger again. Setting this property time after which it should trigger again. Setting this property
on an instance of a recurring calendar object MUST update the on an instance of a recurring calendar object MUST update the
alarm on the master object, unless the respective instance already alarm on the master object, unless the respective instance already
is defined in "recurrenceOverrides". It MUST NOT generate an is defined in "recurrenceOverrides". It MUST NOT generate an
override for the sole use of snoozing an alarm. override for the sole use of snoozing an alarm.
skipping to change at page 31, line 39 skipping to change at page 32, line 43
event's time zone, for example a change from standard time to event's time zone, for example a change from standard time to
daylight-savings time. Leap seconds MUST NOT be considered when daylight-savings time. Leap seconds MUST NOT be considered when
computing an exact duration. When computing an exact duration, the computing an exact duration. When computing an exact duration, the
greatest order time components MUST be added first, that is, the greatest order time components MUST be added first, that is, the
number of days MUST be added first, followed by the number of hours, number of days MUST be added first, followed by the number of hours,
number of minutes, and number of seconds. Fractional seconds MUST be number of minutes, and number of seconds. Fractional seconds MUST be
added last. added last.
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 *rel* and *timeZone* properties of the JSEvent's *location* using the _rel_ and _timeZone_ properties of the JSEvent's _location_
objects. objects.
5.1.4. isAllDay 5.1.4. isAllDay
Type: "Boolean" (optional, default:"false") Type: "Boolean" (optional, default:"false")
Specifies if the event is an all day event, such as a birthday or Specifies if the event is an all day event, such as a birthday or
public holiday. public holiday.
If *isAllDay* is true, then the following restrictions apply: If _isAllDay_ is true, then the following restrictions apply:
o the *start* property MUST have a time component of "T00:00:00". o the _start_ property MUST have a time component of "T00:00:00".
o the *duration* property MUST NOT include non-zero time components o the _duration_ property MUST NOT include non-zero time components
(hours, minutes, or seconds). (hours, minutes, or seconds).
Note that all-day events MAY be bound to a specific time zone, as Note that all-day events MAY be bound to a specific time zone, as
defined by the *timeZone* property. defined by the _timeZone_ property.
5.1.5. status 5.1.5. 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: one of:
o "confirmed": Indicates the event is definite. o "confirmed": Indicates the event is definite.
skipping to change at page 33, line 22 skipping to change at page 34, line 22
5.2.5. statusUpdatedAt 5.2.5. statusUpdatedAt
Type: "UTCDate" (optional), e.g. "2016-06-13T12:00:00Z" Type: "UTCDate" (optional), e.g. "2016-06-13T12:00:00Z"
Specifies the date/time the task status properties was last updated. Specifies the date/time the task status properties was last updated.
If the task is recurring and has future instances, a client may want If the task is recurring and has future instances, a client may want
to keep track of the last status update timestamp of a specific task to keep track of the last status update timestamp of a specific task
recurrence, but leave other instances unchanged. One way to achieve recurrence, but leave other instances unchanged. One way to achieve
this is by overriding the statusUpdatedAt property in the task this is by overriding the statusUpdatedAt property in the task
*recurrenceOverrides*. However, this could produce a long list of _recurrenceOverrides_. However, this could produce a long list of
timestamps for regularly recurring tasks. An alternative approach is timestamps for regularly recurring tasks. An alternative approach is
to split the JSTask into a current, single instance of JSTask with to split the JSTask into a current, single instance of JSTask with
this instance status update time and a future recurring instance. this instance status update time and a future recurring instance.
Also see the definition of the *relatedTo* on splitting. Also see the definition of the _relatedTo_ on splitting.
5.2.6. isAllDay 5.2.6. isAllDay
Type: "Boolean" (optional, default:"false") Type: "Boolean" (optional, default:"false")
Specifies if the task is an all day task. Specifies if the task is an all day task.
If *isAllDay* is true, then the *start* and *due* properties MUST If _isAllDay_ is true, then the _start_ and _due_ properties MUST
have a time component of "T00:00:00". Note that the have a time component of "T00:00:00". Note that the
*estimatedDuration* property MAY contain a non-zero time duration. _estimatedDuration_ property MAY contain a non-zero time duration.
All-day tasks MAY be bound to a specific time zone, as defined by the All-day tasks MAY be bound to a specific time zone, as defined by the
*timeZone* property. _timeZone_ property.
5.2.7. progress 5.2.7. progress
In addition to the common properties of a *Participant* object In addition to the common properties of a _Participant_ object
(Section 4.4.5), a Participant within a JSTask supports the following (Section 4.4.5), a Participant within a JSTask supports the following
property: property:
o *progress*: "ParticipantProgress" (optional) The progress of the o *progress*: "ParticipantProgress" (optional) The progress of the
participant for this task, if known. This property MUST NOT be participant for this task, if known. This property MUST NOT be
set if the *participationStatus* of this participant is any other set if the _participationStatus_ of this participant is any other
value but "accepted". value but "accepted".
A *ParticipantProgress* object has the following properties: A *ParticipantProgress* object has the following properties:
o *status*: "String" Describes the completion status of the o *status*: "String" Describes the completion status of the
participant's progress. participant's progress.
The value MUST be at most one of the following values, registered The value MUST be at most one of the following values, registered
in a future RFC, or a vendor-specific value: in a future RFC, or a vendor-specific value:
skipping to change at page 34, line 28 skipping to change at page 35, line 28
participant progress got updated. participant progress got updated.
5.2.8. status 5.2.8. status
Type: "String" Type: "String"
Defines the overall status of this task. If omitted, the default Defines the overall status of this task. If omitted, the default
status (Section 4.4) of a JSTask is defined as follows (in order of status (Section 4.4) of a JSTask is defined as follows (in order of
evaluation): evaluation):
o "completed": if all the *ParticipantProgress* status of the task o "completed": if all the _ParticipantProgress_ status of the task
participants is "completed". participants is "completed".
o "failed": if at least one *ParticipantProgress* status of the task o "failed": if at least one _ParticipantProgress_ status of the task
participants is "failed". participants is "failed".
o "in-process": if at least one *ParticipantProgress* status of the o "in-process": if at least one _ParticipantProgress_ status of the
task participants is "in-process". task participants 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: If set, it MUST be one of:
o "needs-action": Indicates the task needs action. o "needs-action": Indicates the task needs action.
o "completed": Indicates the task is completed. o "completed": Indicates the task is completed.
skipping to change at page 35, line 36 skipping to change at page 36, line 36
o links o links
as well as the following JSGroup-specific properties: as well as the following JSGroup-specific properties:
5.3.1. entries 5.3.1. entries
Type: "String[JSTask|JSEvent]" Type: "String[JSTask|JSEvent]"
A collection of group members. This is represented as a map of the A collection of group members. This is represented as a map of the
*uid* property value to the JSCalendar object member having that uid. _uid_ property value to the JSCalendar object member having that uid.
Implementations MUST ignore entries of unknown type. Implementations MUST ignore entries of unknown type.
5.3.2. source 5.3.2. source
Type: "String" (optional) Type: "String" (optional)
The source from which updated versions of this group may be retrieved The source from which updated versions of this group may be retrieved
from. The value MUST be a URI. from. The value MUST be a URI.
6. Conversion from and to iCalendar 6. Conversion from and to iCalendar
This section specifies which JSCalendar properties can be mapped from This section specifies which JSCalendar properties can be mapped from
and to iCalendar format. Implementations SHOULD follow these and to iCalendar format. Implementations SHOULD follow these
conversion guidelines. Still, JSCalendar does not restrict itself to conversion guidelines. Still, JSCalendar does not restrict itself to
iCalendar and conversion between these two formats MAY be lossy. iCalendar and conversion between these two formats MAY be lossy.
6.1. JSEvent 6.1. JSEvent
The iCalendar counterpart to *JSEvent* is the VEVENT component type The iCalendar counterpart to _JSEvent_ is the VEVENT component type
[RFC5545]. A VEVENT component that is a direct child of a VCALENDAR [RFC5545]. A VEVENT component that is a direct child of a VCALENDAR
component is equivalent to a standalone JSEvent. A VEVENT component component is equivalent to a standalone JSEvent. A VEVENT component
*within* a VEVENT maps to the entries of the JSEvent within a VEVENT maps to the entries of the JSEvent
*recurrenceOverrides* property. _recurrenceOverrides_ property.
+----------+--------------------------------------------------------+ +----------+--------------------------------------------------------+
| Property | iCalendar counterpart | | Property | iCalendar counterpart |
+----------+--------------------------------------------------------+ +----------+--------------------------------------------------------+
| isAllDay | True, if the type of the DTSTART property in iCalendar | | isAllDay | True, if the type of the DTSTART property in iCalendar |
| | is DATE. When translating from JSCalendar the | | | is DATE. When translating from JSCalendar the |
| | iCalendar DTSTART property is of DATE value type, if | | | iCalendar DTSTART property is of DATE value type, if |
| | the *isAllDay* property is set to true and the | | | the _isAllDay_ property is set to true and the |
| | *timeZone* property is null. | | | _timeZone_ property is null. |
| | | | | |
| start | Corresponds to the DTSTART property in iCalendar. Note | | start | Corresponds to the DTSTART property in iCalendar. Note |
| | that time zone information is stored separately in | | | that time zone information is stored separately in |
| | JSEvent. | | | JSEvent. |
| | | | | |
| timeZone | Corresponds to the TZID part of the DTSTART property | | timeZone | Corresponds to the TZID part of the DTSTART property |
| | in iCalendar. If the event has a different end time | | | in iCalendar. If the event has a different end time |
| | zone to start time zone, this should be added as a | | | zone to start time zone, this should be added as a |
| | JSCalendar *location* with just a *timeZone* property | | | JSCalendar _location_ with just a _timeZone_ property |
| | and "rel="end"". | | | and "rel="end"". |
| | | | | |
| duration | Corresponds to the DURATION or DSTART+DTEND properties | | duration | Corresponds to the DURATION or DSTART+DTEND properties |
| | in iCalendar. | | | in iCalendar. |
+----------+--------------------------------------------------------+ +----------+--------------------------------------------------------+
Table 1: Translation between JSEvent and iCalendar Table 1: Translation between JSEvent and iCalendar
6.2. JSTask 6.2. JSTask
The iCalendar counterpart to *JSTask* is the VTODO component type The iCalendar counterpart to _JSTask_ is the VTODO component type
[RFC5545]. A VTODO component that is a direct child of a VCALENDAR [RFC5545]. A VTODO component that is a direct child of a VCALENDAR
component is equivalent to a standalone JSTask. A VTODO component component is equivalent to a standalone JSTask. A VTODO component
*within* a master VTODO maps to the entries of the JSTask within a master VTODO maps to the entries of the JSTask
*recurrenceOverrides* property. _recurrenceOverrides_ property.
+-------------------+-----------------------------------------------+ +-------------------+-----------------------------------------------+
| Property | iCalendar counterpart | | Property | iCalendar counterpart |
+-------------------+-----------------------------------------------+ +-------------------+-----------------------------------------------+
| isAllDay | True, if the type of the DTSTART property in | | isAllDay | True, if the type of the DTSTART property in |
| | iCalendar is DATE. When translating from | | | iCalendar is DATE. When translating from |
| | JSCalendar the iCalendar DTSTART property is | | | JSCalendar the iCalendar DTSTART property is |
| | of DATE value type, if the *isAllDay* | | | of DATE value type, if the _isAllDay_ |
| | property is set to true and the *timeZone* | | | property is set to true and the _timeZone_ |
| | property is null. | | | property is null. |
| | | | | |
| due | Corresponds to the DUE and DTSTART+DURATION | | due | Corresponds to the DUE and DTSTART+DURATION |
| | properties in iCalendar. When mapping | | | properties in iCalendar. When mapping |
| | iCalendar VTODOs with DTSTART+DURATION, the | | | iCalendar VTODOs with DTSTART+DURATION, the |
| | due date is the result of adding DURATION to | | | due date is the result of adding DURATION to |
| | DTSTART in the DTSTART time zone. | | | DTSTART in the DTSTART time zone. |
| | | | | |
| start | Corresponds to the DTSTART property in | | start | Corresponds to the DTSTART property in |
| | iCalendar. | | | iCalendar. |
| | | | | |
| timeZone | Corresponds to the TZID part of the | | timeZone | Corresponds to the TZID part of the |
| | DTSTART/DUE properties in iCalendar. If the | | | DTSTART/DUE properties in iCalendar. If the |
| | task has a different end time zone to start | | | task has a different end time zone to start |
| | or due time zone, this should be added as a | | | or due time zone, this should be added as a |
| | JSCalendar *location* with just a *timeZone* | | | JSCalendar _location_ with just a _timeZone_ |
| | property and "rel="end"". | | | property and "rel="end"". |
| | | | | |
| estimatedDuration | Corresponds to the ESTIMATED-DURATION | | estimatedDuration | Corresponds to the ESTIMATED-DURATION |
| | iCalendar property in the RFC draft | | | iCalendar property in the RFC draft |
| | [draft-apthorp-ical-tasks]. | | | [draft-apthorp-ical-tasks]. |
| | | | | |
| statusUpdatedAt | Maps to the COMPLETED iCalendar property. The | | statusUpdatedAt | Maps to the COMPLETED iCalendar property. The |
| | JSTask status property MUST have value | | | JSTask status property MUST have value |
| | "completed". | | | "completed". |
| | | | | |
skipping to change at page 38, line 26 skipping to change at page 39, line 26
| source | Corresponds to the SOURCE property in iCalendar. | | source | Corresponds to the SOURCE property in iCalendar. |
+----------+--------------------------------------------------------+ +----------+--------------------------------------------------------+
Table 3: Translation between JSGroup and iCalendar Table 3: Translation between JSGroup and iCalendar
6.4. Common properties 6.4. Common properties
+------------------------+------------------------------------------+ +------------------------+------------------------------------------+
| Property | iCalendar counterpart | | Property | iCalendar counterpart |
+------------------------+------------------------------------------+ +------------------------+------------------------------------------+
| alerts | An *Alert* corresponds to the VALARM | | alerts | An _Alert_ corresponds to the VALARM |
| | component in iCalendar, where the | | | component in iCalendar, where the |
| | *action* is determined by the iCalendar | | | _action_ is determined by the iCalendar |
| | ACTION property value (e.g., both | | | ACTION property value (e.g., both |
| | "DISPLAY" and "AUDIO" actions map to a | | | "DISPLAY" and "AUDIO" actions map to a |
| | JSCalendar *display* action, and | | | JSCalendar _display_ action, and |
| | similarly for "EMAIL"). The | | | similarly for "EMAIL"). The |
| | *relativeTo* and *offset* properties | | | _relativeTo_ and _offset_ properties |
| | corresponds to the iCalendar TRIGGER | | | corresponds to the iCalendar TRIGGER |
| | property. | | | property. |
| | | | | |
| categories | Corresponds to the CONCEPT property in | | categories | Corresponds to the CONCEPT property in |
| | iCalendar, see in the RFC draft | | | iCalendar, see in the RFC draft |
| | [draft-ietf-calext-ical-relations]. | | | [draft-ietf-calext-ical-relations]. |
| | | | | |
| color | Corresponds to the COLOR property in | | color | Corresponds to the COLOR property in |
| | iCalendar, as specified in [RFC7986]. | | | iCalendar, as specified in [RFC7986]. |
| | | | | |
skipping to change at page 39, line 12 skipping to change at page 40, line 12
| | | | | |
| freeBusyStatus | Corresponds to the TRANSP property in | | freeBusyStatus | Corresponds to the TRANSP property in |
| | iCalendar. | | | iCalendar. |
| | | | | |
| keywords | Corresponds to the CATEGORIES property | | keywords | Corresponds to the CATEGORIES property |
| | in iCalendar, as specified in [RFC7986]. | | | in iCalendar, as specified in [RFC7986]. |
| | | | | |
| links | Corresponds to the ATTACH ([RFC5545]) or | | links | Corresponds to the ATTACH ([RFC5545]) or |
| | IMAGE ([RFC7986]) properties with a URI | | | IMAGE ([RFC7986]) properties with a URI |
| | value type set to the link "href". | | | value type set to the link "href". |
| | ([RFC7986]). The *type* property | | | ([RFC7986]). The _type_ property |
| | corresponds to the FMTTYPE parameter, | | | corresponds to the FMTTYPE parameter, |
| | the *size* property to the SIZE | | | the _size_ property to the SIZE |
| | parameter. Mapping all other properties | | | parameter. Mapping all other properties |
| | is implementation-specific. | | | is implementation-specific. |
| | | | | |
| locale | Corresponds to the LANGUAGE parameter in | | locale | Corresponds to the LANGUAGE parameter in |
| | iCalendar, which is added to individual | | | iCalendar, which is added to individual |
| | properties. When converting from | | | properties. When converting from |
| | iCalendar, one language must be picked | | | iCalendar, one language must be picked |
| | as the main locale for the object, and | | | as the main locale for the object, and |
| | all properties in other languages moved | | | all properties in other languages moved |
| | to the localizations JSEvent property. | | | to the localizations JSEvent property. |
skipping to change at page 43, line 17 skipping to change at page 44, line 17
Both JSCalendar and iCalendar calendar objects may contain properties Both JSCalendar and iCalendar calendar objects may contain properties
that are not expressible in the other format. This specification that are not expressible in the other format. This specification
does not mandate how to preserve these properties. Instead, it does not mandate how to preserve these properties. Instead, it
leaves negotiation on how to treat unknown properties to client and leaves negotiation on how to treat unknown properties to client and
server implementations and their protocol used to exchange calendar server implementations and their protocol used to exchange calendar
objects. objects.
Two notable options to represent and preserve arbitrary iCalendar Two notable options to represent and preserve arbitrary iCalendar
object properties in JSCalendar are: object properties in JSCalendar are:
o *JCal*: Define iCalendar properties in JCal format ([RFC7265]) in o _JCal_: Define iCalendar properties in JCal format ([RFC7265]) in
a vendor-specific property of the JCalendar object. The JCal- a vendor-specific property of the JCalendar object. The JCal-
formatted value may either only contain iCalendar properties that formatted value may either only contain iCalendar properties that
were not mapped to JSCalendar properties, or contain the complete were not mapped to JSCalendar properties, or contain the complete
iCalendar object representation. iCalendar object representation.
o *Alternate link*: Define an alternate link (Section 4.2.6) value o _Alternate link_: Define an alternate link (Section 4.2.6) value
pointing to the iCalendar representation of the JSCalendar object. pointing to the iCalendar representation of the JSCalendar object.
E.g. the alternative representation of a VEVENT would be E.g. the alternative representation of a VEVENT would be
represented as a link with rel "alternate" and type "text/ represented as a link with rel "alternate" and type "text/
calendar;component=VEVENT". calendar;component=VEVENT".
7. JSCalendar object examples 7. JSCalendar object examples
The following examples illustrate several aspects of the JSCalendar The following examples illustrate several aspects of the JSCalendar
data model and format. The examples may omit mandatory or additional data model and format. The examples may omit mandatory or additional
properties, which is indicated by a placeholder property with key properties, which is indicated by a placeholder property with key
skipping to change at page 45, line 30 skipping to change at page 46, line 30
calendar user expects to need 1 hour for shopping. calendar user expects to need 1 hour for shopping.
{ {
"...": "", "...": "",
"title": "Buy groceries", "title": "Buy groceries",
"due": "2018-01-19T18:00:00", "due": "2018-01-19T18:00:00",
"timeZone": "Europe/Vienna", "timeZone": "Europe/Vienna",
"estimatedDuration": "PT1H" "estimatedDuration": "PT1H"
} }
7.6. Event with end time zone 7.6. Event with end time-zone
This example illustrates the use of end time zones by use of an This example illustrates the use of end time-zones by use of an
international flight. The flight starts on April 1, 2018 at 9am in international flight. The flight starts on April 1, 2018 at 9am in
Berlin local time. The duration of the flight is scheduled at 10 Berlin local time. The duration of the flight is scheduled at 10
hours 30 minutes. The time at the flights destination is in the same hours 30 minutes. The time at the flights destination is in the same
time zone as Tokyo. Calendar clients could use the end time zone to time-zone as Tokyo. Calendar clients could use the end time-zone to
display the arrival time in Tokyo local time and highlight the time display the arrival time in Tokyo local time and highlight the time-
zone difference of the flight. The location names can serve as input zone difference of the flight. The location names can serve as input
for navigation systems. for navigation systems.
{ {
"...": "", "...": "",
"title": "Flight XY51 to Tokyo", "title": "Flight XY51 to Tokyo",
"start": "2018-04-01T09:00:00", "start": "2018-04-01T09:00:00",
"timeZone": "Europe/Berlin", "timeZone": "Europe/Berlin",
"duration": "PT10H30M", "duration": "PT10H30M",
"locations": { "locations": {
skipping to change at page 46, line 28 skipping to change at page 47, line 28
"name": "Narita International Airport (NRT)", "name": "Narita International Airport (NRT)",
"timeZone": "Asia/Tokyo" "timeZone": "Asia/Tokyo"
} }
} }
} }
7.7. Floating-time event (with recurrence) 7.7. Floating-time event (with recurrence)
This example illustrates the use of floating-time. Since January 1, This example illustrates the use of floating-time. Since January 1,
2018, a calendar user blocks 30 minutes every day to practice Yoga at 2018, a calendar user blocks 30 minutes every day to practice Yoga at
7am local time, in whatever time zone the user is located on that 7am local time, in whatever time-zone the user is located on that
date. date.
{ {
"...": "", "...": "",
"title": "Yoga", "title": "Yoga",
"start": "2018-01-01T07:00:00", "start": "2018-01-01T07:00:00",
"duration": "PT30M", "duration": "PT30M",
"recurrenceRule": { "recurrenceRule": {
"frequency": "daily" "frequency": "daily"
} }
} }
7.8. Event with multiple locations and localization 7.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 convert on premises or
online. The event title and descriptions are localized. (Note: the online. The event title and descriptions are localized.
localization of the event description contains an UTF-8 encoded
German Umlaut. This character may have been replaced with ASCII
characters in the plain-text rendering of this RFC document)
{ {
"...": "", "...": "",
"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": {
skipping to change at page 47, line 30 skipping to change at page 48, line 31
"6f3696c6-1e07-47d0-9ce1-f50014b0041a": { "6f3696c6-1e07-47d0-9ce1-f50014b0041a": {
"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": {
"de": { "de": {
"title": "Live von der Music Bowl: The Band!", "title": "Live von der Music Bowl: The Band!",
"description": "Schau dir das groesste Musikereignis an!", "description": "Schau dir das groesste Musikereignis an!",
"virtualLocations/6f3696c6-1e07-47d0-9ce1-f50014b0041a/name": "virtualLocations/6f3696c6-1e07-47d0-9ce1-f50014b0041a/name":
"Gratis Live-Stream aus der Music Bowl" "Gratis Live-Stream aus der Music Bowl"
} }
} }
} }
7.9. Recurring event with overrides 7.9. Recurring event with overrides
This example illustrates the use of recurrence overrides. A math This example illustrates the use of recurrence overrides. A math
course at a University is held for the first time on January 8, 2018 course at a University is held for the first time on January 8, 2018
at 9am London time and occurs every week until June 25, 2018. Each at 9am London time and occurs every week until June 25, 2018. Each
lecture lasts for one hour and 30 minutes and is located at the lecture lasts for one hour and 30 minutes and is located at the
skipping to change at page 49, line 7 skipping to change at page 50, line 7
owner also chairs the event. Participants meet in a virtual meeting owner also chairs the event. Participants meet in a virtual meeting
room. An attendee has accepted the invitation, but on March 8, 2018 room. An attendee has accepted the invitation, but on March 8, 2018
he is unavailable and declined participation for this occurrence. he is unavailable and declined participation for this occurrence.
{ {
"...": "", "...": "",
"title": "FooBar team meeting", "title": "FooBar team meeting",
"start": "2018-01-08T09:00:00", "start": "2018-01-08T09:00:00",
"timeZone": "Africa/Johannesburg", "timeZone": "Africa/Johannesburg",
"duration": "PT1H", "duration": "PT1H",
"locations": { "virtualLocations": {
"2a358cee-6489-4f14-a57f-c104db4dc2f1": { "2a358cee-6489-4f14-a57f-c104db4dc2f1": {
"title": "ChatMe meeting room", "name": "ChatMe meeting room",
"rel": "virtual",
"features": [
"audio",
"chat",
"video"
],
"uri": "https://chatme.example.com?id=1234567" "uri": "https://chatme.example.com?id=1234567"
} }
}, },
"recurrenceRule": { "recurrenceRule": {
"frequency": "weekly" "frequency": "weekly"
}, },
"replyTo": { "replyTo": {
"imip": "zoe@foobar.example.com" "imip": "mailto:6489-4f14-a57f-c1@schedule.example.com"
}, },
"participants": { "participants": {
"tom@foobar.example.com": { "dG9tQGZvb2Jhci5leGFtcGxlLmNvbQ": {
"name": "Tom Tool", "name": "Tom Tool",
"email": "tom@foobar.example.com", "email": "tom@foobar.example.com",
"sendTo": {
"imip": "mailto:6489-4f14-a57f-c1@calendar.example.com"
},
"participationStatus": "accepted", "participationStatus": "accepted",
"roles": [ "roles": {
"attendee" "attendee": true
] }
}, },
"zoe@foobar.example.com": { "em9lQGZvb2Jhci5leGFtcGxlLmNvbQ": {
"name": "Zoe Zelda", "name": "Zoe Zelda",
"email": "zoe@foobar.example.com", "email": "zoe@foobar.example.com",
"sendTo": {
"imip": "mailto:zoe@foobar.example.com"
},
"participationStatus": "accepted", "participationStatus": "accepted",
"roles": [ "roles": {
"owner", "owner": true,
"chair" "attendee": true,
] "chair": true
}
}, },
"...": "" "...": ""
}, },
"recurrenceOverrides": { "recurrenceOverrides": {
"2018-03-08T09:00:00": { "2018-03-08T09:00:00": {
"participants/tom@foobar.example.com/participationStatus": "participants/dG9tQGZvb2Jhci5leGFtcGxlLmNvbQ/participationStatus":
"declined" "declined"
} }
} }
} }
8. Security Considerations 8. Security Considerations
The use of JSON as a format does have its own inherent security risks The use of JSON as a format does have its own inherent security risks
as discussed in Section 12 of [RFC8259]. Even though JSON is as discussed in Section 12 of [RFC8259]. Even though JSON is
considered a safe subset of JavaScript, it should be kept in mind considered a safe subset of JavaScript, it should be kept in mind
that a flaw in the parser processing JSON could still impose a that a flaw in the parser processing JSON could still impose a
threat, which doesn't arise with conventional iCalendar data. threat, which doesn't arise with conventional iCalendar data.
 End of changes. 90 change blocks. 
184 lines changed or deleted 241 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/