idnits 2.17.1 draft-ietf-calext-jscalendar-25.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 24, 2020) is 1522 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'Alert' is mentioned on line 2746, but not defined == Missing Reference: 'Boolean' is mentioned on line 2962, but not defined == Missing Reference: 'Link' is mentioned on line 2873, but not defined == Missing Reference: 'PatchObject' is mentioned on line 2937, but not defined == Missing Reference: 'Location' is mentioned on line 2887, but not defined == Missing Reference: 'Participant' is mentioned on line 2909, but not defined == Missing Reference: 'Relation' is mentioned on line 2946, but not defined == Missing Reference: 'String' is mentioned on line 2977, but not defined == Missing Reference: 'TimeZone' is mentioned on line 3008, but not defined == Missing Reference: 'VirtualLocation' is mentioned on line 3036, but not defined -- Possible downref: Non-RFC (?) normative reference: ref. 'CLDR' -- Possible downref: Non-RFC (?) normative reference: ref. 'COLORS' -- Possible downref: Non-RFC (?) normative reference: ref. 'TZDB' Summary: 0 errors (**), 0 flaws (~~), 11 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Calendaring extensions N. Jenkins 3 Internet-Draft R. Stepanek 4 Intended status: Standards Track Fastmail 5 Expires: August 27, 2020 February 24, 2020 7 JSCalendar: A JSON representation of calendar data 8 draft-ietf-calext-jscalendar-25 10 Abstract 12 This specification defines a data model and JSON representation of 13 calendar data that can be used for storage and data exchange in a 14 calendaring and scheduling environment. It aims to be an alternative 15 and, over time, successor to the widely deployed iCalendar data 16 format, and to be unambiguous, extendable, and simple to process. In 17 contrast to the jCal format, which is also JSON-based, JSCalendar is 18 not a direct mapping from iCalendar, but defines the data model 19 independently and expands semantics where appropriate. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on August 27, 2020. 38 Copyright Notice 40 Copyright (c) 2020 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (https://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 56 1.1. Motivation and Relation to iCalendar and jCal . . . . . . 5 57 1.2. Notational Conventions . . . . . . . . . . . . . . . . . 6 58 1.3. Type Signatures . . . . . . . . . . . . . . . . . . . . . 6 59 1.4. Data Types . . . . . . . . . . . . . . . . . . . . . . . 7 60 1.4.1. Int . . . . . . . . . . . . . . . . . . . . . . . . . 7 61 1.4.2. UnsignedInt . . . . . . . . . . . . . . . . . . . . . 7 62 1.4.3. UTCDateTime . . . . . . . . . . . . . . . . . . . . . 7 63 1.4.4. LocalDateTime . . . . . . . . . . . . . . . . . . . . 7 64 1.4.5. Duration . . . . . . . . . . . . . . . . . . . . . . 7 65 1.4.6. SignedDuration . . . . . . . . . . . . . . . . . . . 8 66 1.4.7. Id . . . . . . . . . . . . . . . . . . . . . . . . . 8 67 1.4.8. PatchObject . . . . . . . . . . . . . . . . . . . . . 9 68 1.4.9. Time Zones . . . . . . . . . . . . . . . . . . . . . 9 69 1.4.10. Relation . . . . . . . . . . . . . . . . . . . . . . 9 70 2. JSCalendar Objects . . . . . . . . . . . . . . . . . . . . . 10 71 2.1. JSEvent . . . . . . . . . . . . . . . . . . . . . . . . . 10 72 2.2. JSTask . . . . . . . . . . . . . . . . . . . . . . . . . 11 73 2.3. JSGroup . . . . . . . . . . . . . . . . . . . . . . . . . 11 74 3. Structure of JSCalendar Objects . . . . . . . . . . . . . . . 11 75 3.1. Normalization and Equivalence . . . . . . . . . . . . . . 11 76 3.2. Vendor-specific Property Extensions and Values . . . . . 12 77 4. Common JSCalendar Properties . . . . . . . . . . . . . . . . 12 78 4.1. Metadata Properties . . . . . . . . . . . . . . . . . . . 12 79 4.1.1. @type . . . . . . . . . . . . . . . . . . . . . . . . 12 80 4.1.2. uid . . . . . . . . . . . . . . . . . . . . . . . . . 13 81 4.1.3. relatedTo . . . . . . . . . . . . . . . . . . . . . . 13 82 4.1.4. prodId . . . . . . . . . . . . . . . . . . . . . . . 13 83 4.1.5. created . . . . . . . . . . . . . . . . . . . . . . . 14 84 4.1.6. updated . . . . . . . . . . . . . . . . . . . . . . . 14 85 4.1.7. sequence . . . . . . . . . . . . . . . . . . . . . . 14 86 4.1.8. method . . . . . . . . . . . . . . . . . . . . . . . 14 87 4.2. What and Where Properties . . . . . . . . . . . . . . . . 14 88 4.2.1. title . . . . . . . . . . . . . . . . . . . . . . . . 14 89 4.2.2. description . . . . . . . . . . . . . . . . . . . . . 15 90 4.2.3. descriptionContentType . . . . . . . . . . . . . . . 15 91 4.2.4. showWithoutTime . . . . . . . . . . . . . . . . . . . 15 92 4.2.5. locations . . . . . . . . . . . . . . . . . . . . . . 15 93 4.2.6. virtualLocations . . . . . . . . . . . . . . . . . . 17 94 4.2.7. links . . . . . . . . . . . . . . . . . . . . . . . . 17 95 4.2.8. locale . . . . . . . . . . . . . . . . . . . . . . . 19 96 4.2.9. keywords . . . . . . . . . . . . . . . . . . . . . . 19 97 4.2.10. categories . . . . . . . . . . . . . . . . . . . . . 19 98 4.2.11. color . . . . . . . . . . . . . . . . . . . . . . . . 20 99 4.3. Recurrence Properties . . . . . . . . . . . . . . . . . . 20 100 4.3.1. recurrenceId . . . . . . . . . . . . . . . . . . . . 20 101 4.3.2. recurrenceRules . . . . . . . . . . . . . . . . . . . 20 102 4.3.3. recurrenceOverrides . . . . . . . . . . . . . . . . . 28 103 4.3.4. excluded . . . . . . . . . . . . . . . . . . . . . . 30 104 4.4. Sharing and Scheduling Properties . . . . . . . . . . . . 30 105 4.4.1. priority . . . . . . . . . . . . . . . . . . . . . . 30 106 4.4.2. freeBusyStatus . . . . . . . . . . . . . . . . . . . 30 107 4.4.3. privacy . . . . . . . . . . . . . . . . . . . . . . . 30 108 4.4.4. replyTo . . . . . . . . . . . . . . . . . . . . . . . 32 109 4.4.5. participants . . . . . . . . . . . . . . . . . . . . 32 110 4.5. Alerts Properties . . . . . . . . . . . . . . . . . . . . 37 111 4.5.1. useDefaultAlerts . . . . . . . . . . . . . . . . . . 37 112 4.5.2. alerts . . . . . . . . . . . . . . . . . . . . . . . 37 113 4.6. Multilingual Properties . . . . . . . . . . . . . . . . . 39 114 4.6.1. localizations . . . . . . . . . . . . . . . . . . . . 39 115 4.7. Time Zone Properties . . . . . . . . . . . . . . . . . . 40 116 4.7.1. timeZone . . . . . . . . . . . . . . . . . . . . . . 40 117 4.7.2. timeZones . . . . . . . . . . . . . . . . . . . . . . 40 118 5. Type-specific JSCalendar Properties . . . . . . . . . . . . . 43 119 5.1. JSEvent Properties . . . . . . . . . . . . . . . . . . . 43 120 5.1.1. start . . . . . . . . . . . . . . . . . . . . . . . . 43 121 5.1.2. duration . . . . . . . . . . . . . . . . . . . . . . 43 122 5.1.3. status . . . . . . . . . . . . . . . . . . . . . . . 43 123 5.2. JSTask Properties . . . . . . . . . . . . . . . . . . . . 44 124 5.2.1. due . . . . . . . . . . . . . . . . . . . . . . . . . 44 125 5.2.2. start . . . . . . . . . . . . . . . . . . . . . . . . 44 126 5.2.3. estimatedDuration . . . . . . . . . . . . . . . . . . 44 127 5.2.4. progress . . . . . . . . . . . . . . . . . . . . . . 44 128 5.2.5. progressUpdated . . . . . . . . . . . . . . . . . . . 45 129 5.3. JSGroup Properties . . . . . . . . . . . . . . . . . . . 45 130 5.3.1. entries . . . . . . . . . . . . . . . . . . . . . . . 46 131 5.3.2. source . . . . . . . . . . . . . . . . . . . . . . . 46 132 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 46 133 6.1. Simple event . . . . . . . . . . . . . . . . . . . . . . 46 134 6.2. Simple task . . . . . . . . . . . . . . . . . . . . . . . 47 135 6.3. Simple group . . . . . . . . . . . . . . . . . . . . . . 47 136 6.4. All-day event . . . . . . . . . . . . . . . . . . . . . . 48 137 6.5. Task with a due date . . . . . . . . . . . . . . . . . . 48 138 6.6. Event with end time-zone . . . . . . . . . . . . . . . . 49 139 6.7. Floating-time event (with recurrence) . . . . . . . . . . 49 140 6.8. Event with multiple locations and localization . . . . . 50 141 6.9. Recurring event with overrides . . . . . . . . . . . . . 51 142 6.10. Recurring event with participants . . . . . . . . . . . . 52 143 7. Security Considerations . . . . . . . . . . . . . . . . . . . 54 144 7.1. Expanding Recurrences . . . . . . . . . . . . . . . . . . 54 145 7.2. JSON Parsing . . . . . . . . . . . . . . . . . . . . . . 54 146 7.3. URI Values . . . . . . . . . . . . . . . . . . . . . . . 55 147 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55 148 8.1. Media Type Registration . . . . . . . . . . . . . . . . . 55 149 8.2. Creation of "JSCalendar Properties" Registry . . . . . . 56 150 8.2.1. Preliminary Community Review . . . . . . . . . . . . 57 151 8.2.2. Submit Request to IANA . . . . . . . . . . . . . . . 57 152 8.2.3. Designated Expert Review . . . . . . . . . . . . . . 57 153 8.2.4. Change Procedures . . . . . . . . . . . . . . . . . . 58 154 8.2.5. JMAP Properties Registry Template . . . . . . . . . . 58 155 8.2.6. Initial Contents for the JSCalendar Properties 156 Registry . . . . . . . . . . . . . . . . . . . . . . 59 157 8.3. Creation of "JSCalendar Types" Registry . . . . . . . . . 66 158 8.3.1. JMAP Types Registry Template . . . . . . . . . . . . 66 159 8.3.2. Initial Contents for the JSCalendar Types Registry . 66 160 8.4. Creation of "JSCalendar Enum Values" Registry . . . . . . 68 161 8.4.1. JMAP Enum Property Template . . . . . . . . . . . . . 68 162 8.4.2. JMAP Enum Value Template . . . . . . . . . . . . . . 68 163 8.4.3. Initial Contents for the JSCalendar Enum Registry . . 68 164 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 73 165 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 73 166 10.1. Normative References . . . . . . . . . . . . . . . . . . 73 167 10.2. Informative References . . . . . . . . . . . . . . . . . 75 168 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 76 170 1. Introduction 172 This document defines a data model for calendar event and task 173 objects, or groups of such objects, in electronic calendar 174 applications and systems. It aims to be unambiguous, extendable and 175 simple to process. 177 The key design considerations for this data model are as follows: 179 o The attributes of the calendar entry represented must be described 180 as simple key-value pairs. Simple events are simple to represent; 181 complex events can be modelled accurately. 183 o Wherever possible, there should be only one way to express the 184 desired semantics, reducing complexity. 186 o The data model should avoid ambiguities, which often lead to 187 interoperability issues between implementations. 189 o The data model should be compatible with the iCalendar data format 190 [RFC5545] [RFC7986] and extensions, but the specification should 191 add new attributes where the iCalendar format currently lacks 192 expressivity, and drop seldom-used, obsolete, or redundant 193 properties. This means translation with no loss of semantics 194 should be easy with most common iCalendar files. 196 o Extensions, such as new properties and components, generally do 197 not require updates to this document. 199 The representation of this data model is defined in the I-JSON format 200 [RFC7493], which is a strict subset of the JavaScript Object Notation 201 (JSON) Data Interchange Format [RFC8259]. Using JSON is mostly a 202 pragmatic choice: its widespread use makes JSCalendar easier to 203 adopt, and the ready availability of production-ready JSON 204 implementations eliminates a whole category of parser-related 205 interoperability issues, which iCalendar has often suffered from. 207 1.1. Motivation and Relation to iCalendar and jCal 209 The iCalendar data format [RFC5545], a widely deployed interchange 210 format for calendaring and scheduling data, has served calendaring 211 vendors for a long while, but contains some ambiguities and pitfalls 212 that can not be overcome without backward-incompatible changes. 214 Sources of implementation errors include the following: 216 o iCalendar defines various formats for local times, UTC time, and 217 dates. 219 o iCalendar requires custom time zone definitions within a single 220 calendar component. 222 o iCalendar's definition of recurrence rules is ambiguous and has 223 resulted in differing understandings even between experienced 224 calendar developers. 226 o The iCalendar format itself causes interoperability issues due to 227 misuse of CRLF-terminated strings, line continuations, and subtle 228 differences among iCalendar parsers. 230 In recent years, many new products and services have appeared that 231 wish to use a JSON representation of calendar data within their APIs. 232 The JSON format for iCalendar data, jCal [RFC7265], is a direct 233 mapping between iCalendar and JSON. In its effort to represent full 234 iCalendar semantics, it inherits all the same pitfalls and uses a 235 complicated JSON structure unlike most common JSON data 236 representations. 238 As a consequence, since the standardization of jCal, the majority of 239 implementations and service providers either kept using iCalendar, or 240 came up with their own proprietary JSON representations, which are 241 incompatible with each other and often suffer from common pitfalls, 242 such as storing event start times in UTC (which become incorrect if 243 the timezone's rules change in the future). JSCalendar meets the 244 demand for JSON-formatted calendar data that is free of such known 245 problems and provides a standard representation as an alternative to 246 the proprietary formats. 248 1.2. Notational Conventions 250 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 251 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 252 "OPTIONAL" in this document are to be interpreted as described in BCP 253 14 [RFC2119] [RFC8174] when, and only when, they appear in all 254 capitals, as shown here. 256 The underlying format used for this specification is JSON. 257 Consequently, the terms "object" and "array" as well as the four 258 primitive types (strings, numbers, booleans, and null) are to be 259 interpreted as described in Section 1 of [RFC8259]. 261 Some examples in this document contain "partial" JSON documents used 262 for illustrative purposes. In these examples, three periods "..." 263 are used to indicate a portion of the document that has been removed 264 for compactness. 266 1.3. Type Signatures 268 Type signatures are given for all JSON values in this document. The 269 following conventions are used: 271 o "*" - The type is undefined (the value could be any type, although 272 permitted values may be constrained by the context of this value). 274 o "String" - The JSON string type. 276 o "Number" - The JSON number type. 278 o "Boolean" - The JSON boolean type. 280 o "A[B]" - A JSON object where the keys are all of type "A", and the 281 values are all of type "B". 283 o "A[]" - An array of values of type "A". 285 o "A|B" - The value is either of type "A" or of type "B". 287 Other types may also be given, with their representations defined 288 elsewhere in this document. 290 1.4. Data Types 292 In addition to the standard JSON data types, the following data types 293 are used in this specification: 295 1.4.1. Int 297 Where "Int" is given as a data type, it means an integer in the range 298 -2^53+1 <= value <= 2^53-1, the safe range for integers stored in a 299 floating-point double, represented as a JSON "Number". 301 1.4.2. UnsignedInt 303 Where "UnsignedInt" is given as a data type, it means an integer in 304 the range 0 <= value <= 2^53-1, represented as a JSON "Number". 306 1.4.3. UTCDateTime 308 This is a string in [RFC3339] "date-time" format, with the further 309 restrictions that any letters MUST be in uppercase, the time 310 component MUST be included and the time offset MUST be the character 311 "Z". Fractional second values MUST NOT be included unless non-zero 312 and MUST NOT have trailing zeros, to ensure there is only a single 313 representation for each date-time. 315 For example "2010-10-10T10:10:10.003Z" is OK, but 316 "2010-10-10T10:10:10.000Z" is invalid and MUST be encoded as 317 "2010-10-10T10:10:10Z". 319 1.4.4. LocalDateTime 321 This is a date-time string with no time zone/offset information. It 322 is otherwise in the same format as UTCDateTime, including fractional 323 seconds. For example "2006-01-02T15:04:05" and 324 "2006-01-02T15:04:05.003" are both valid. The time zone to associate 325 the LocalDateTime with comes from an associated property, or if no 326 time zone is associated it defines *floating time*. Floating date- 327 times are not tied to any specific time zone. Instead, they occur in 328 each time zone at the given wall-clock time (as opposed to the same 329 instant point in time). 331 1.4.5. Duration 333 Where Duration is given as a type, it means a length of time 334 represented by a subset of ISO8601 duration format, as specified by 335 the following ABNF: 337 dur-secfrac = "." 1*DIGIT 338 dur-second = 1*DIGIT [dur-secfrac] "S" 339 dur-minute = 1*DIGIT "M" [dur-second] 340 dur-hour = 1*DIGIT "H" [dur-minute] 341 dur-time = "T" (dur-hour / dur-minute / dur-second) 342 dur-day = 1*DIGIT "D" 343 dur-week = 1*DIGIT "W" 345 duration = "P" (dur-day [dur-time] / dur-time / dur-week) 347 In addition, the duration MUST NOT include fractional second values 348 unless the fraction is non-zero. 350 1.4.6. SignedDuration 352 A SignedDuration represents a length of time that may be positive or 353 negative and is typically used to express the offset of a point in 354 time relative to an associated time. It is represented as a 355 Duration, optionally preceded by a sign character. It is specified 356 by the following ABNF: 358 signed-duration = ["+" / "-"] duration 360 A negative sign indicates a point in time at or before the associated 361 time, a positive or no sign a time at or after the associated time. 363 1.4.7. Id 365 Where "Id" is given as a data type, it means a "String" of at least 1 366 and a maximum of 255 octets in size, and it MUST only contain 367 characters from the "URL and Filename Safe" base64url alphabet, as 368 defined in Section 5 of [RFC4648], excluding the pad character ("="). 369 This means the allowed characters are the ASCII alphanumeric 370 characters ("A-Za-z0-9"), hyphen ("-"), and underscore ("_"). 372 Unless otherwise specified, Ids are arbitrary and only have meaning 373 within the object where they are being used. Ids need not be unique 374 among different objects. For example, two JSEvent objects might use 375 the same ids in their respective "links" properties. Or within the 376 same JSEvent object the same Id could appear in the "participants" 377 and "alerts" properties. These situations do not imply any semantic 378 connections among the objects. 380 Nevertheless, a UUID is typically a good choice. 382 1.4.8. PatchObject 384 A PatchObject is of type "String[*]", and represents an unordered set 385 of patches on a JSON object. Each key is a path represented in a 386 subset of JSON pointer format [RFC6901]. The paths have an implicit 387 leading "/", so each key is prefixed with "/" before applying the 388 JSON pointer evaluation algorithm. 390 A patch within a PatchObject is only valid if all of the following 391 conditions apply: 393 1. The pointer MUST NOT insert/delete from an array; the array MUST 394 be replaced in its entirety instead. 396 2. When evaluating a path, all parts prior to the last (i.e., the 397 value after the final slash) MUST exist. 399 3. There MUST NOT be two patches in the PatchObject where the 400 pointer of one is a prefix of the pointer of the other, e.g., 401 "alerts/foo/offset" and "alerts". 403 The value associated with each pointer is either: 405 o null: Remove the property at the given path from the patched 406 object. If the property is not present in the object, this a no- 407 op. 409 o Anything else: Set the value for the property to this value (this 410 may be a replacement or addition to the object being patched). 412 Implementations MUST reject in its entirety a PatchObject if any of 413 its patches is invalid. Implementations MUST NOT apply partial 414 patches. 416 1.4.9. Time Zones 418 By default, time zones in JSCalendar are identified by their names in 419 the IANA Time Zone Database [TZDB], and the zone rules of the 420 respective zone records apply. 422 Implementations MAY embed the definitions of custom time zones in the 423 "timeZones" property (see Section 4.7.2). 425 1.4.10. Relation 427 A Relation object defines the relation to other objects, using a 428 possibly empty set of relation types. The object that defines this 429 relation is the linking object, while the other object is the linked 430 object. The Relation object has the following properties: 432 o @type: "String" (mandatory) 434 Specifies the type of this object. This MUST be "Relation". 436 o relation: "String[Boolean]" (optional, default: empty Object) 438 Describes how the linked object is related to the linking object. 439 The relation is defined as a set of relation types. If empty, the 440 relationship between the two objects is unspecified. 442 Keys in the set MUST be one of the following values, or specified 443 in the property definition where the Relation object is used, or a 444 value registered in the IANA JSCalendar Enum Registry, or a 445 vendor-specific value: 447 * "first": The linked object is the first in a series the linking 448 object is part of. 450 * "next": The linked object is the next in a series the linking 451 object is part of. 453 * "child": The linked object is a subpart of the linking object. 455 * "parent": The linking object is a subpart of the linked object. 457 The value for each key in the set MUST be true. 459 2. JSCalendar Objects 461 This section describes the calendar object types specified by 462 JSCalendar. 464 2.1. JSEvent 466 Media type: "application/jscalendar+json;type=jsevent" 468 A JSEvent represents a scheduled amount of time on a calendar, 469 typically a meeting, appointment, reminder or anniversary. It is 470 required to start at a certain point in time and typically has a non- 471 zero duration. Multiple participants may partake in the event at 472 multiple locations. 474 The @type (Section 4.1.1) property value MUST be "jsevent". 476 2.2. JSTask 478 Media type: "application/jscalendar+json;type=jstask" 480 A JSTask represents an action-item, assignment, to-do or work item. 481 It may start and be due at certain points in time, may take some 482 estimated time to complete, and may recur, none of which is required. 484 The @type (Section 4.1.1) property value MUST be "jstask". 486 2.3. JSGroup 488 Media type: "application/jscalendar+json;type=jsgroup" 490 A JSGroup is a collection of JSEvent (Section 2.1) and/or JSTask 491 (Section 2.2) objects. Typically, objects are grouped by topic 492 (e.g., by keywords) or calendar membership. 494 The @type (Section 4.1.1) property value MUST be "jsgroup". 496 3. Structure of JSCalendar Objects 498 A JSCalendar object is a JSON object, which MUST be valid I-JSON (a 499 stricter subset of JSON), as specified in [RFC8259]. Property names 500 and values are case-sensitive. 502 The object has a collection of properties, as specified in the 503 following sections. Properties are specified as being either 504 mandatory or optional. Optional properties may have a default value, 505 if explicitly specified in the property definition. 507 3.1. Normalization and Equivalence 509 JSCalendar aims to provide unambiguous definitions for value types 510 and properties, but does not define a general normalization or 511 equivalence method for JSCalendar objects and types. This is because 512 the notion of equivalence might range from byte-level equivalence to 513 semantic equivalence, depending on the respective use case (for 514 example, the CalDAV protocol [RFC4791] requires octet equivalence of 515 the encoded calendar object to determine ETag equivalence). 517 Normalization of JSCalendar objects is hindered because of the 518 following reasons: 520 o Custom JSCalendar properties may contain arbitrary JSON values, 521 including arrays. However, equivalence of arrays might or might 522 not depend on the order of elements, depending on the respective 523 property definition. 525 o Several JSCalendar property values are defined as URIs and media 526 types, but normalization of these types is inherently protocol- 527 and scheme-specific, depending on the use-case of the equivalence 528 definition (see Section 6 of [RFC3986]). 530 Considering this, the definition of equivalence and normalization is 531 left to client and server implementations and to be negotiated by a 532 calendar exchange protocol or defined elsewhere. 534 3.2. Vendor-specific Property Extensions and Values 536 Vendors MAY add additional properties to the calendar object to 537 support their custom features. The names of these properties MUST be 538 prefixed with a domain name controlled by the vendor to avoid 539 conflict, e.g., "example.com/customprop". 541 Some JSCalendar properties allow vendor-specific value extensions. 542 Such vendor-specific values MUST be prefixed with a domain name 543 controlled by the vendor, e.g., "example.com/customrel". 545 Vendors are strongly encouraged to register any new property values 546 or extensions that are useful to other systems as well, rather than 547 use a vendor-specific prefix. 549 4. Common JSCalendar Properties 551 This section describes the properties that are common to the various 552 JSCalendar object types. Specific JSCalendar object types may only 553 support a subset of these properties. The object type definitions in 554 Section 5 describe the set of supported properties per type. 556 4.1. Metadata Properties 558 4.1.1. @type 560 Type: "String" (mandatory). 562 Specifies the type which this object represents. This MUST be one of 563 the following values: 565 o "jsevent": a JSCalendar event (Section 2.1). 567 o "jstask": a JSCalendar task (Section 2.2). 569 o "jsgroup": a JSCalendar group (Section 2.3). 571 4.1.2. uid 573 Type: "String" (mandatory). 575 A globally unique identifier, used to associate the object as the 576 same across different systems, calendars and views. The value of 577 this property MUST be unique across all JSCalendar objects, even if 578 they are of different type. [RFC4122] describes a range of 579 established algorithms to generate universally unique identifiers 580 (UUID). UUID version 4, described in Section 4.4 of [RFC4122], is 581 RECOMMENDED. 583 For compatibility with [RFC5545] UIDs, implementations MUST be able 584 to receive and persist values of at least 255 octets for this 585 property, but they MUST NOT truncate values in the middle of a UTF-8 586 multi-octet sequence. 588 4.1.3. relatedTo 590 Type: "String[Relation]" (optional). 592 Relates the object to other JSCalendar objects. This is represented 593 as a map of the UIDs of the related objects to information about the 594 relation. 596 If an object is split to make a "this and future" change to a 597 recurrence, the original object MUST be truncated to end at the 598 previous occurrence before this split, and a new object created to 599 represent all the occurrences after the split. A "next" relation 600 MUST be set on the original object's relatedTo property for the UID 601 of the new object. A "first" relation for the UID of the first 602 object in the series MUST be set on the new object. Clients can then 603 follow these UIDs to get the complete set of objects if the user 604 wishes to modify them all at once. 606 4.1.4. prodId 608 Type: "String" (optional). 610 The identifier for the product that last updated the JSCalendar 611 object. This should be set whenever the data in the object is 612 modified (i.e., whenever the "updated" property is set). 614 The vendor of the implementation SHOULD ensure that this is a 615 globally unique identifier, using some technique such as an FPI 616 value, as defined in [ISO.9070.1991]. It MUST only use characters of 617 an iCalendar TEXT data value (see Section 3.3.11 of [RFC5545]). 619 This property SHOULD NOT be used to alter the interpretation of a 620 JSCalendar object beyond the semantics specified in this document. 621 For example, it is not to be used to further the understanding of 622 non-standard properties, a practice that is knows to cause long-term 623 interoperability problems. 625 4.1.5. created 627 Type: "UTCDateTime" (optional). 629 The date and time this object was initially created. 631 4.1.6. updated 633 Type: "UTCDateTime" (mandatory). 635 The date and time the data in this object was last modified (or its 636 creation date/time if not modified since). 638 4.1.7. sequence 640 Type: "UnsignedInt" (optional, default: 0). 642 Initially zero, this MUST be incremented by one every time a change 643 is made to the object, except if the change only modifies the 644 "participants" property (see Section 4.4.5). 646 This is used as part of iTIP [RFC5546] to know which version of the 647 object a scheduling message relates to. 649 4.1.8. method 651 Type: "String" (optional). 653 The iTIP [RFC5546] method, in lowercase. This MUST only be present 654 if the JSCalendar object represents an iTIP scheduling message. 656 4.2. What and Where Properties 658 4.2.1. title 660 Type: "String" (optional, default: empty String). 662 A short summary of the object. 664 4.2.2. description 666 Type: "String" (optional, default: empty String). 668 A longer-form text description of the object. The content is 669 formatted according to the "descriptionContentType" property. 671 4.2.3. descriptionContentType 673 Type: "String" (optional, default: "text/plain"). 675 Describes the media type [RFC6838] of the contents of the 676 "description" property. Media types MUST be sub-types of type 677 "text", and SHOULD be "text/plain" or "text/html" [MIME]. They MAY 678 include parameters and the "charset" parameter value MUST be "utf-8", 679 if specified. Descriptions of type "text/html" MAY contain "cid" 680 URLs [RFC2392] to reference links in the calendar object by use of 681 the "cid" property of the Link object. 683 4.2.4. showWithoutTime 685 Type: "Boolean" (optional, default: false). 687 Indicates that the time is not important to display to the user when 688 rendering this calendar object. An example of this is an event that 689 conceptually occurs all day or across multiple days, such as "New 690 Year's Day" or "Italy Vacation". While the time component is 691 important for free-busy calculations and checking for scheduling 692 clashes, calendars may choose to omit displaying it and/or display 693 the object separately to other objects to enhance the user's view of 694 their schedule. 696 Such events are also commonly known as "all-day" events. 698 4.2.5. locations 700 Type: "Id[Location]" (optional). 702 A map of location ids to Location objects, representing locations 703 associated with the object. 705 A Location object has the following properties. It MUST have at 706 least one property other than the "relativeTo" property. 708 o @type: "String" (mandatory) 710 Specifies the type of this object. This MUST be "Location". 712 o name: "String" (optional) 714 The human-readable name of the location. 716 o description: "String" (optional) 718 Human-readable, plain-text instructions for accessing this 719 location. This may be an address, set of directions, door access 720 code, etc. 722 o locationTypes: "String[Boolean]" (optional) 724 A set of one or more location types that describe this location. 725 All types MUST be from the Location Types Registry as defined in 726 [RFC4589]. The set is represented as a map, with the keys being 727 the location types. The value for each key in the map MUST be 728 true. 730 o relativeTo: "String" (optional) 732 Specifies the relation between this location and the time of the 733 JSCalendar object. This is primarily to allow events representing 734 travel to specify the location of departure (at the start of the 735 event) and location of arrival (at the end); this is particularly 736 important if these locations are in different time zones, as a 737 client may wish to highlight this information for the user. 739 This MUST be one of the following values, a value registered in 740 the IANA JSCalendar Enum Registry, or a vendor-specific value. 741 Any value the client or server doesn't understand should be 742 treated the same as if this property is omitted. 744 * "start": The event/task described by this JSCalendar object 745 occurs at this location at the time the event/task starts. 747 * "end": The event/task described by this JSCalendar object 748 occurs at this location at the time the event/task ends. 750 o timeZone: "String" (optional) 752 A time zone for this location. See also Section 1.4.9. 754 o coordinates: "String" (optional) 756 A "geo:" URI [RFC5870] for the location. 758 o linkIds: "Id[Boolean]" (optional) 759 A set of link ids for links to alternative representations of this 760 location. Each key in the set MUST be the id of a Link object 761 defined in the "links" property of this calendar object. The 762 value for each key in the set MUST be true. If there are no 763 links, this MUST be omitted (rather than specified as an empty 764 set). 766 For example, an alternative representation could be in vCard 767 format. 769 4.2.6. virtualLocations 771 Type: "Id[VirtualLocation]" (optional). 773 A map of ids to VirtualLocation objects, representing virtual 774 locations, such as video conferences or chat rooms, associated with 775 the object. 777 A VirtualLocation object has the following properties. 779 o @type: "String" (mandatory) 781 Specifies the type of this object. This MUST be 782 "VirtualLocation". 784 o name: "String" (optional, default: empty String) 786 The human-readable name of the virtual location. 788 o description: "String" (optional) 790 Human-readable plain-text instructions for accessing this 791 location. This may be an address, set of directions, door access 792 code, etc. 794 o uri: "String" (mandatory) 796 A URI that represents how to connect to this virtual location. 798 This may be a telephone number (represented using the "tel:" 799 scheme, e.g., "tel:+1-555-555-555") for a teleconference, a web 800 address for online chat, or any custom URI. 802 4.2.7. links 804 Type: "Id[Link]" (optional). 806 A map of link ids to Link objects, representing external resources 807 associated with the object. 809 A Link object has the following properties: 811 o @type: "String" (mandatory) 813 Specifies the type of this object. This MUST be "Link". 815 o href: "String" (mandatory) 817 A URI from which the resource may be fetched. 819 This MAY be a "data:" URL [RFC2397], but it is recommended that 820 the file be hosted on a server to avoid embedding arbitrarily 821 large data in JSCalendar object instances. 823 o cid: "String" (optional) 825 This MUST be a valid "content-id" value according to the 826 definition of Section 2 in [RFC2392]. The value MUST be unique 827 within this Link object but has no meaning beyond that. It MAY be 828 different from the link id for this Link object. 830 o contentType: "String" (optional) 832 The media type [RFC6838] of the resource, if known. 834 o size: "UnsignedInt" (optional) 836 The size, in octets, of the resource when fully decoded (i.e., the 837 number of octets in the file the user would download), if known. 839 o rel: "String" (optional) 841 Identifies the relation of the linked resource to the object. If 842 set, the value MUST be a relation type from the IANA registry 843 [LINKRELS], as established in [RFC8288]. 845 Links with a rel of "enclosure" SHOULD be considered by the client 846 as attachments for download. 848 Links with a rel of "describedby" SHOULD be considered by the 849 client to be an alternative representation of the description. 851 Links with a rel of "icon" SHOULD be considered by the client to 852 be an image that it may use when presenting the calendar data to a 853 user. The "display" property may be set to indicate the purpose 854 of this image. 856 o display: "String" (optional) 858 Describes the intended purpose of a link to an image. If set, the 859 "rel" property MUST be set to "icon". The value MUST be one of 860 the following values, a value registered in the IANA JSCalendar 861 Enum Registry, or a vendor-specific value: 863 * "badge": an image meant to be displayed alongside the title of 864 the object. 866 * "graphic": a full image replacement for the object itself. 868 * "fullsize": an image that is used to enhance the object. 870 * "thumbnail": a smaller variant of "fullsize" to be used when 871 space for the image is constrained. 873 o title: "String" (optional) 875 A human-readable plain-text description of the resource. 877 4.2.8. locale 879 Type: "String" (optional). 881 The language tag as defined in [RFC5646] that best describes the 882 locale used for the text in the calendar object, if known. 884 4.2.9. keywords 886 Type: "String[Boolean]" (optional). 888 A set of keywords or tags that relate to the object. The set is 889 represented as a map, with the keys being the keywords. The value 890 for each key in the map MUST be true. 892 4.2.10. categories 894 Type: "String[Boolean]" (optional). 896 A set of categories that relate to the calendar object. The set is 897 represented as a map, with the keys being the categories specified as 898 URIs. The value for each key in the map MUST be true. 900 In contrast to keywords, categories typically are structured. For 901 example, a vendor owning the domain "example.com" might define the 902 categories "http://example.com/categories/sports/american-football"" 903 and "http://example.com/categories/music/r-b". 905 4.2.11. color 907 Type: "String" (optional). 909 A color clients MAY use when displaying this calendar object. The 910 value is a color name taken from the set of names defined in 911 Section 4.3 of CSS Color Module Level 3 [COLORS], or an RGB value in 912 hexadecimal notation, as defined in Section 4.2.1 of CSS Color Module 913 Level 3. 915 4.3. Recurrence Properties 917 Some events and tasks occur at regular or irregular intervals. 918 Rather than having to copy the data for every occurrence there can be 919 a master event with a recurrence rule, and/or overrides that add 920 extra dates or exceptions to the rule. 922 4.3.1. recurrenceId 924 Type: "LocalDateTime" (optional). 926 If present, this JSCalendar object represents one occurrence of a 927 recurring JSCalendar object. If present the "recurrenceRules" and 928 "recurrenceOverrides" properties MUST NOT be present. 930 The value is a date-time either produced by the "recurrenceRules" of 931 the master event, or added as a key to the "recurrenceOverrides" 932 property of the master event. 934 4.3.2. recurrenceRules 936 Type: "RecurrenceRule[]" (optional). 938 Defines a set of recurrence rules (repeating patterns) for recurring 939 calendar objects. 941 A JSEvent recurs by applying the recurrence rules to the "start" 942 date-time. 944 A JSTask recurs by applying the recurrence rules to the "start" date- 945 time, if defined, otherwise it recurs by the "due" date-time, if 946 defined. If the task defines neither a "start" nor "due" date-time, 947 it MUST NOT define a "recurrenceRules" property. 949 If multiple recurrence rules are given, each rule is to be applied 950 and then the union of the results used, ignoring any duplicates. 952 A RecurrenceRule object is a JSON object mapping of a RECUR value 953 type in iCalendar [RFC5545] [RFC7529] and has the same semantics. It 954 has the following properties: 956 o @type: "String" (mandatory) 958 Specifies the type of this object. This MUST be "RecurrenceRule". 960 o frequency: "String" (mandatory) 962 The time span covered by each iteration of this recurrence rule 963 (see Section 4.3.2.1 for full semantics). This MUST be one of the 964 following values: 966 * "yearly" 968 * "monthly" 970 * "weekly" 972 * "daily" 974 * "hourly" 976 * "minutely" 978 * "secondly" 980 This is the FREQ part from iCalendar, converted to lowercase. 982 o interval: "UnsignedInt" (optional, default: 1) 984 The interval of iteration periods at which the recurrence repeats. 985 If included, it MUST be an integer >= 1. 987 This is the INTERVAL part from iCalendar. 989 o rscale: "String" (optional, default: "gregorian") 991 The calendar system in which this recurrence rule operates, in 992 lowercase. This MUST be either a CLDR-registered calendar system 993 name [CLDR], or a vendor-specific value. 995 This is the RSCALE part from iCalendar RSCALE [RFC7529], converted 996 to lowercase. 998 o skip: "String" (optional, default: "omit") 1000 The behaviour to use when the expansion of the recurrence produces 1001 invalid dates. This property only has an effect if the frequency 1002 is "yearly" or "monthly". It MUST be one of the following values: 1004 * "omit" 1006 * "backward" 1008 * "forward" 1010 This is the SKIP part from iCalendar RSCALE [RFC7529], converted 1011 to lowercase. 1013 o firstDayOfWeek: "String" (optional, default: "mo") 1015 The day on which the week is considered to start, represented as a 1016 lowercase abbreviated two-letter English day of the week. If 1017 included, it MUST be one of the following values: 1019 * "mo" 1021 * "tu" 1023 * "we" 1025 * "th" 1027 * "fr" 1029 * "sa" 1031 * "su" 1033 This is the WKST part from iCalendar. 1035 o byDay: "NDay[]" (optional) 1037 Days of the week on which to repeat. An *NDay* object has the 1038 following properties: 1040 * day: "String" (mandatory) 1042 A day of the week on which to repeat; the allowed values are 1043 the same as for the "firstDayOfWeek" RecurrenceRule property. 1045 This is the day-of-the-week of the BYDAY part in iCalendar, 1046 converted to lowercase. 1048 * nthOfPeriod: "Int" (optional) 1050 If present, rather than representing every occurrence of the 1051 weekday defined in the "day" property, it represents only a 1052 specific instance within the recurrence period. The value can 1053 be positive or negative, but MUST NOT be zero. A negative 1054 integer means nth-last of period. 1056 This is the ordinal part of the BYDAY value in iCalendar (e.g., 1057 1 or -3). 1059 o byMonthDay: "Int[]" (optional) 1061 Days of the month on which to repeat. Valid values are between 1 1062 and the maximum number of days any month may have in the calendar 1063 given by the "rscale" property, and the negative values of these 1064 numbers. For example, in the Gregorian calendar valid values are 1065 1 to 31 and -31 to -1. Negative values offset from the end of the 1066 month. The array MUST have at least one entry if included. 1068 This is the BYMONTHDAY part in iCalendar. 1070 o byMonth: "String[]" (optional) 1072 The months in which to repeat. Each entry is a string 1073 representation of a number, starting from "1" for the first month 1074 in the calendar (e.g., "1" means January with the Gregorian 1075 calendar), with an optional "L" suffix (see [RFC7529]) for leap 1076 months (this MUST be uppercase, e.g., "3L"). The array MUST have 1077 at least one entry if included. 1079 This is the BYMONTH part from iCalendar. 1081 o byYearDay: "Int[]" (optional) 1083 The days of the year on which to repeat. Valid values are between 1084 1 and the maximum number of days any year may have in the calendar 1085 given by the "rscale" property, and the negative values of these 1086 numbers. For example, in the Gregorian calendar valid values are 1087 1 to 366 and -366 to -1. Negative values offset from the end of 1088 the year. The array MUST have at least one entry if included. 1090 This is the BYYEARDAY part from iCalendar. 1092 o byWeekNo: "Int[]" (optional) 1093 Weeks of the year in which to repeat. Valid values are between 1 1094 and the maximum number of weeks any year may have in the calendar 1095 given by the "rscale" property, and the negative values of these 1096 numbers. For example, in the Gregorian calendar valid values are 1097 1 to 53 and -53 to -1. The array MUST have at least one entry if 1098 included. 1100 This is the BYWEEKNO part from iCalendar. 1102 o byHour: "UnsignedInt[]" (optional) 1104 The hours of the day in which to repeat. Valid values are 0 to 1105 23. The array MUST have at least one entry if included. This is 1106 the BYHOUR part from iCalendar. 1108 o byMinute: "UnsignedInt[]" (optional) 1110 The minutes of the hour in which to repeat. Valid values are 0 to 1111 59. The array MUST have at least one entry if included. 1113 This is the BYMINUTE part from iCalendar. 1115 o bySecond: "UnsignedInt[]" (optional) 1117 The seconds of the minute in which to repeat. Valid values are 0 1118 to 60. The array MUST have at least one entry if included. 1120 This is the BYSECOND part from iCalendar. 1122 o bySetPosition: "Int[]" (optional) 1124 The occurrences within the recurrence interval to include in the 1125 final results. Negative values offset from the end of the list of 1126 occurrences. The array MUST have at least one entry if included. 1127 This is the BYSETPOS part from iCalendar. 1129 o count: "UnsignedInt" (optional) 1131 The number of occurrences at which to range-bound the recurrence. 1132 This MUST NOT be included if an "until" property is specified. 1134 This is the COUNT part from iCalendar. 1136 o until: "LocalDateTime" (optional) 1138 The date-time at which to finish recurring. The last occurrence 1139 is on or before this date-time. This MUST NOT be included if a 1140 "count" property is specified. Note: if not specified otherwise 1141 for a specific JSCalendar object, this date is to be interpreted 1142 in the time zone specified in the JSCalendar object's "timeZone" 1143 property. 1145 This is the UNTIL part from iCalendar. 1147 4.3.2.1. Interpreting recurrence rules 1149 A recurrence rule specifies a set of date-times for recurring 1150 calendar objects. A recurrence rule has the following semantics. 1151 Note, wherever "year", "month" or "day of month" is used, this is 1152 within the calendar system given by the "rscale" property, which 1153 defaults to "gregorian" if omitted. 1155 1. A set of candidates is generated. This is every second within a 1156 period defined by the frequency property value: 1158 * "yearly": every second from midnight on the 1st day of a year 1159 (inclusive) to midnight the 1st day of the following year 1160 (exclusive). 1162 If skip is not "omit", the calendar system has leap months and 1163 there is a byMonth property, generate candidates for the leap 1164 months even if they don't occur in this year. 1166 If skip is not "omit" and there is a byMonthDay property, 1167 presume each month has the maximum number of days any month 1168 may have in this calendar system when generating candidates, 1169 even if it's more than this month actually has. 1171 * "monthly": every second from midnight on the 1st day of a 1172 month (inclusive) to midnight on the 1st of the following 1173 month (exclusive). 1175 If skip is not "omit" and there is a byMonthDay property, 1176 presume the month has the maximum number of days any month may 1177 have in this calendar system when generating candidates, even 1178 if it's more than this month actually has. 1180 * "weekly": every second from midnight (inclusive) on the first 1181 day of the week (as defined by the firstDayOfWeek property, or 1182 Monday if omitted), to midnight 7 days later (exclusive). 1184 * "daily": every second from midnight at the start of the day 1185 (inclusive) to midnight at the end of the day (exclusive). 1187 * "hourly": every second from the beginning of the hour 1188 (inclusive) to the beginning of the next hour (exclusive). 1190 * "minutely": every second from the beginning of the minute 1191 (inclusive) to the beginning of the next minute (exclusive). 1193 * "secondly": the second itself, only. 1195 2. Each date-time candidate is compared against all of the byX 1196 properties of the rule except bySetPosition. If any property in 1197 the rule does not match the date-time, it is eliminated. Each 1198 byX property is an array; the date-time matches the property if 1199 it matches any of the values in the array. The properties have 1200 the following semantics: 1202 * byMonth: the date-time is in the given month. 1204 * byWeekNo: the date-time is in the nth week of the year. 1205 Negative numbers mean the nth last week of the year. This 1206 corresponds to weeks according to week numbering as defined in 1207 ISO.8601.2004, with a week defined as a seven day period, 1208 starting on the firstDayOfWeek property value or Monday if 1209 omitted. Week number one of the calendar year is the first 1210 week that contains at least four days in that calendar year. 1212 If the date-time is not valid (this may happen when generating 1213 candidates with a skip property in effect), it is always 1214 eliminated by this property. 1216 * byYearDay: the date-time is on the nth day of year. Negative 1217 numbers mean the nth last day of the year. 1219 If the date-time is not valid (this may happen when generating 1220 candidates with a skip property in effect), it is always 1221 eliminated by this property. 1223 * byMonthDay: the date-time is on the given day of the month. 1224 Negative numbers mean the nth last day of the month. 1226 * byDay: the date-time is on the given day of the week. If the 1227 day is prefixed by a number, it is the nth occurrence of that 1228 day of the week within the month (if frequency is monthly) or 1229 year (if frequency is yearly). Negative numbers means nth 1230 last occurrence within that period. 1232 * byHour: the date-time has the given hour value. 1234 * byMinute: the date-time has the given minute value. 1236 * bySecond: the date-time has the given second value. 1238 If a skip property is defined and is not "omit", there may be 1239 candidates that do not correspond to valid dates (e.g., 31st 1240 February in the Gregorian calendar). In this case, the 1241 properties MUST be considered in the order above and: 1243 1. After applying the byMonth filter, if the candidate's month 1244 is invalid for the given year, increment it (if skip is 1245 "forward") or decrement it (if skip is "backward") until a 1246 valid month is found, incrementing/decrementing the year as 1247 well if passing through the beginning/end of the year. This 1248 only applies to calendar systems with leap months. 1250 2. After applying the byMonthDay filter, if the day of the month 1251 is invalid for the given month and year, change the date to 1252 the first day of the next month (if skip is "forward") or the 1253 last day of the current month (if skip is "backward"). 1255 3. If any valid date produced after applying the skip is already 1256 a candidate, eliminate the duplicate. (For example after 1257 adjusting, 30th February and 31st February would both become 1258 the same "real" date, so one is eliminated as a duplicate.) 1260 3. If a bySetPosition property is included, this is now applied to 1261 the ordered list of remaining dates. This property specifies the 1262 indexes of date-times to keep; all others should be eliminated. 1263 Negative numbers are indexes from the end of the list, with -1 1264 being the last item. 1266 4. Any date-times before the start date of the event are eliminated 1267 (see below for why this might be needed). 1269 5. If a skip property is included and is not "omit", eliminate any 1270 date-times that have already been produced by previous iterations 1271 of the algorithm. (This is not possible if skip is "omit".) 1273 6. If further dates are required (we have not reached the until 1274 date, or count limit) skip the next (interval - 1) sets of 1275 candidates, then continue from step 1. 1277 When determining the set of occurrence dates for an event or task, 1278 the following extra rules must be applied: 1280 1. The initial date-time to which the rule is applied (the "start" 1281 date-time for events; the "start" or "due" date-time for tasks) 1282 is always the first occurrence in the expansion (and is counted 1283 if the recurrence is limited by a "count" property), even if it 1284 would normally not match the rule. 1286 2. The first set of candidates to consider is that which would 1287 contain the initial date-time. This means the first set may 1288 include candidates before the initial date-time; such candidates 1289 are eliminated from the results in step (4) as outlined before. 1291 3. The following properties MUST be implicitly added to the rule 1292 under the given conditions: 1294 * If frequency is not "secondly" and no bySecond property: Add a 1295 bySecond property with the sole value being the seconds value 1296 of the initial date-time. 1298 * If frequency is not "secondly" or "minutely", and no byMinute 1299 property: Add a byMinute property with the sole value being 1300 the minutes value of the initial date-time. 1302 * If frequency is not "secondly", "minutely" or "hourly" and no 1303 byHour property: Add a byHour property with the sole value 1304 being the hours value of the initial date-time. 1306 * If frequency is "weekly" and no byDay property: Add a byDay 1307 property with the sole value being the day-of-the-week of the 1308 initial date-time. 1310 * If frequency is "monthly" and no byDay property and no 1311 byMonthDay property: Add a byMonthDay property with the sole 1312 value being the day-of-the-month of the initial date-time. 1314 * If frequency is "yearly" and no byYearDay property: 1316 + If there are no byMonth or byWeekNo properties, and either 1317 there is a byMonthDay property or there is no byDay 1318 property: Add a byMonth property with the sole value being 1319 the month of the initial date-time. 1321 + If there is no byMonthDay, byWeekNo or byDay properties: 1322 Add a byMonthDay property with the sole value being the 1323 day-of-the-month of the initial date-time. 1325 + If there is a byWeekNo property and no byMonthDay or byDay 1326 properties: Add a byDay property with the sole value being 1327 the day-of-the-week of the initial date-time. 1329 4.3.3. recurrenceOverrides 1331 Type: "LocalDateTime[PatchObject]" (optional). 1333 A map of the recurrence ids (the date-time produced by the recurrence 1334 rule) to an object of patches to apply to the generated occurrence 1335 object. 1337 If the recurrence id does not match a date-time from the recurrence 1338 rule (or no rule is specified), it is to be treated as an additional 1339 occurrence (like an RDATE from iCalendar). The patch object may 1340 often be empty in this case. 1342 If the patch object defines the "excluded" property value to be true, 1343 then the recurring calendar object does not occur at the recurrence 1344 id date-time (like an EXDATE from iCalendar). Such a patch object 1345 MUST NOT patch any other property. 1347 By default, an occurrence inherits all properties from the main 1348 object except the start (or due) date-time, which is shifted to match 1349 the recurrence id LocalDateTime. However, individual properties of 1350 the occurrence can be modified by a patch, or multiple patches. It 1351 is valid to patch the "start" property value, and this patch takes 1352 precedence over the value generated from the recurrence id. Both the 1353 recurrence id as well as the patched "start" date-time may occur 1354 before the original JSCalendar object's "start" or "due" date. 1356 A pointer in the PatchObject MUST be ignored if it starts with one of 1357 the following prefixes: 1359 o @type 1361 o method 1363 o privacy 1365 o prodId 1367 o recurrenceId 1369 o recurrenceOverrides 1371 o recurrenceRules 1373 o relatedTo 1375 o replyTo 1377 o uid 1379 4.3.4. excluded 1381 Type: "Boolean" (optional, default: false). 1383 Defines if this object is an overridden, excluded instance of a 1384 recurring JSCalendar object (see Section 4.3.3). If this property 1385 value is true, this calendar object instance MUST be removed from the 1386 occurrence expansion. The absence of this property or its default 1387 value false indicates that this instance MUST be included in the 1388 occurrence expansion. 1390 4.4. Sharing and Scheduling Properties 1392 4.4.1. priority 1394 Type: "Int" (optional, default: 0). 1396 Specifies a priority for the calendar object. This may be used as 1397 part of scheduling systems to help resolve conflicts for a time 1398 period. 1400 The priority is specified as an integer in the range 0 to 9. A value 1401 of 0 specifies an undefined priority, for which the treatment will 1402 vary by situation. A value of 1 is the highest priority. A value of 1403 2 is the second highest priority. Subsequent numbers specify a 1404 decreasing ordinal priority. A value of 9 is the lowest priority. 1405 Other integer values are reserved for future use. 1407 4.4.2. freeBusyStatus 1409 Type: "String" (optional, default: "busy"). 1411 Specifies how this calendar object should be treated when calculating 1412 free-busy state. This MUST be one of the following values, a value 1413 registered in the IANA JSCalendar Enum Registry, or a vendor-specific 1414 value: 1416 o "free": The object should be ignored when calculating whether the 1417 user is busy. 1419 o "busy": The object should be included when calculating whether the 1420 user is busy. 1422 4.4.3. privacy 1424 Type: "String" (optional, default: "public"). 1426 Calendar objects are normally collected together and may be shared 1427 with other users. The privacy property allows the object owner to 1428 indicate that it should not be shared, or should only have the time 1429 information shared but the details withheld. Enforcement of the 1430 restrictions indicated by this property are up to the API via which 1431 this object is accessed. 1433 This property MUST NOT affect the information sent to scheduled 1434 participants; it is only interpreted when the object is shared as 1435 part of a shared calendar. 1437 The value MUST be one of the following values, a value registered in 1438 the IANA JSCalendar Enum Registry, or a vendor-specific value. Any 1439 value the client or server doesn't understand should be preserved but 1440 treated as equivalent to "private". 1442 o "public": The full details of the object are visible to those whom 1443 the object's calendar is shared with. 1445 o "private": The details of the object are hidden; only the basic 1446 time and metadata is shared. The following properties MAY be 1447 shared, any other properties MUST NOT be shared: 1449 * @type 1451 * created 1453 * due 1455 * duration 1457 * estimatedDuration 1459 * freeBusyStatus 1461 * privacy 1463 * recurrenceOverrides. Only patches which apply to another 1464 permissible property are allowed to be shared. 1466 * sequence 1468 * showWithoutTime 1470 * start 1472 * timeZone 1473 * timeZones 1475 * uid 1477 * updated 1479 o "secret": The object is hidden completely (as though it did not 1480 exist) when the calendar this object is in is shared. 1482 4.4.4. replyTo 1484 Type: "String[String]" (optional). 1486 Represents methods by which participants may submit their RSVP 1487 response to the organizer of the calendar object. The keys in the 1488 property value are the available methods and MUST only contain ASCII 1489 alphanumeric characters (A-Za-z0-9). The value is a URI for the 1490 method specified in the key. Future methods may be defined in future 1491 specifications and registered with IANA; a calendar client MUST 1492 ignore any method it does not understand, but MUST preserve the 1493 method key and URI. This property MUST be omitted if no method is 1494 defined (rather than being specified as an empty object). If this 1495 property is set, the "participants" property of this calendar object 1496 MUST contain at least one participant. 1498 The following methods are defined: 1500 o "imip": The organizer accepts an iMIP [RFC6047] response at this 1501 email address. The value MUST be a "mailto:" URI. 1503 o "web": Opening this URI in a web browser will provide the user 1504 with a page where they can submit a reply to the organizer. 1506 o "other": The organizer is identified by this URI but the method 1507 for submitting the response is undefined. 1509 4.4.5. participants 1511 Type: "Id[Participant]" (optional). 1513 A map of participant ids to participants, describing their 1514 participation in the calendar object. 1516 If this property is set, then the "replyTo" property of this calendar 1517 object MUST define at least one reply method. 1519 A Participant object has the following properties: 1521 o @type: "String" (mandatory) 1523 Specifies the type of this object. This MUST be "Participant". 1525 o name: "String" (optional) 1527 The display name of the participant (e.g., "Joe Bloggs"). 1529 o email: "String" (optional) 1531 The email address for the participant. 1533 o sendTo: "String[String]" (optional) 1535 Represents methods by which the participant may receive the 1536 invitation and updates to the calendar object. 1538 The keys in the property value are the available methods and MUST 1539 only contain ASCII alphanumeric characters (A-Za-z0-9). The value 1540 is a URI for the method specified in the key. Future methods may 1541 be defined in future specifications and registered with IANA; a 1542 calendar client MUST ignore any method it does not understand, but 1543 MUST preserve the method key and URI. This property MUST be 1544 omitted if no method is defined (rather than being specified as an 1545 empty object). 1547 The following methods are defined: 1549 * "imip": The participant accepts an iMIP [RFC6047] request at 1550 this email address. The value MUST be a "mailto:" URI. It MAY 1551 be different from the value of the participant's "email" 1552 property. 1554 * "other": The participant is identified by this URI but the 1555 method for submitting the invitation is undefined. 1557 o kind: "String" (optional) 1559 What kind of entity this participant is, if known. 1561 This MUST be one of the following values, a value registered in 1562 the IANA JSCalendar Enum Registry, or a vendor-specific value. 1563 Any value the client or server doesn't understand should be 1564 treated the same as if this property is omitted. 1566 * "individual": a single person 1568 * "group": a collection of people invited as a whole 1569 * "location": a physical location that needs to be scheduled, 1570 e.g., a conference room 1572 * "resource": a non-human resource other than a location, such as 1573 a projector 1575 o roles: "String[Boolean]" (mandatory) 1577 A set of roles that this participant fulfills. 1579 At least one role MUST be specified for the participant. The keys 1580 in the set MUST be one of the following values, a value registered 1581 in the IANA JSCalendar Enum Registry, or a vendor-specific value: 1583 * "owner": The participant is an owner of the object. This 1584 signifies they have permission to make changes to it that 1585 affect the other participants. Non-owner participants may only 1586 change properties that just affect themself (for example 1587 setting their own alerts or changing their rsvp status). 1589 * "attendee": The participant is expected to attend. 1591 * "optional": The participant is invited but not required. 1593 * "informational": The participant is copied for informational 1594 reasons, and is not expected to attend. 1596 * "chair": The participant is in charge of the event/task when it 1597 occurs. 1599 The value for each key in the set MUST be true. It is expected 1600 that no more than one of the roles "attendee", "optional", or 1601 "informational" be present; if more than one are given, "optional" 1602 takes precedence over "informational", and "attendee" takes 1603 precedence over both. Roles that are unknown to the 1604 implementation MUST be preserved. 1606 o locationId: "String" (optional) 1608 The location at which this participant is expected to be 1609 attending. 1611 If the value does not correspond to any location id in the 1612 "locations" property of the JSCalendar object, this MUST be 1613 treated the same as if the participant's locationId were omitted. 1615 o language: "String" (optional) 1616 The language tag as defined in [RFC5646] that best describes the 1617 participant's preferred language, if known. 1619 o participationStatus: "String" (optional, default: "needs-action") 1621 The participation status, if any, of this participant. 1623 The value MUST be one of the following values, a value registered 1624 in the IANA JSCalendar Enum Registry, or a vendor-specific value: 1626 * "needs-action": No status yet set by the participant. 1628 * "accepted": The invited participant will participate. 1630 * "declined": The invited participant will not participate. 1632 * "tentative": The invited participant may participate. 1634 * "delegated": The invited participant has delegated their 1635 attendance to another participant, as specified in the 1636 delegatedTo property. 1638 o participationComment: "String" (optional) 1640 A note from the participant to explain their participation status. 1642 o expectReply: "Boolean" (optional, default: false) 1644 If true, the organizer is expecting the participant to notify them 1645 of their participation status. 1647 o scheduleAgent: "String" (optional, default: "server") 1649 Who is responsible for sending scheduling messages with this 1650 calendar object to the participant. 1652 The value MUST be one of the following values, a value registered 1653 in the IANA JSCalendar Enum Registry, or a vendor-specific value: 1655 * "server": The calendar server will send the scheduling 1656 messages. 1658 * "client": The calendar client will send the scheduling 1659 messages. 1661 * "none": No scheduling messages are to be sent to this 1662 participant. 1664 o scheduleSequence: "UnsignedInt" (optional, default: 0) 1666 The sequence number of the last response from the participant. If 1667 defined, this MUST be a non-negative integer. 1669 This can be used to determine whether the participant has sent a 1670 new RSVP following significant changes to the calendar object, and 1671 to determine if future responses are responding to a current or 1672 older view of the data. 1674 o scheduleUpdated: "UTCDateTime" (optional) 1676 The "updated" property of the last iTIP response from the 1677 participant. 1679 This can be compared to the "updated" property timestamp in future 1680 iTIP responses to determine if the response is older or newer than 1681 the current data. 1683 o invitedBy: "String" (optional) 1685 The participant id of the participant who invited this one, if 1686 known. 1688 o delegatedTo: "String[Boolean]" (optional) 1690 A set of participant ids that this participant has delegated their 1691 participation to. Each key in the set MUST be the id of a 1692 participant. The value for each key in the set MUST be true. If 1693 there are no delegates, this MUST be omitted (rather than 1694 specified as an empty set). 1696 o delegatedFrom: "String[Boolean]" (optional) 1698 A set of participant ids that this participant is acting as a 1699 delegate for. Each key in the set MUST be the id of a 1700 participant. The value for each key in the set MUST be true. If 1701 there are no delegators, this MUST be omitted (rather than 1702 specified as an empty set). 1704 o memberOf: "String[Boolean]" (optional) 1706 A set of group participants that were invited to this calendar 1707 object, which caused this participant to be invited due to their 1708 membership in the group(s). Each key in the set MUST be the id of 1709 a participant. The value for each key in the set MUST be true. 1710 If there are no groups, this MUST be omitted (rather than 1711 specified as an empty set). 1713 o linkIds: "String[Boolean]" (optional) 1715 A set of links to more information about this participant, for 1716 example in vCard format. The keys in the set MUST be the id of a 1717 Link object in the calendar object's "links" property. The value 1718 for each key in the set MUST be true. If there are no links, this 1719 MUST be omitted (rather than specified as an empty set). 1721 o progress: "String" (optional). This is only allowed if the 1722 Participant is part of a JSTask. It represents the progress of 1723 the participant for this task, if known. This property MUST NOT 1724 be set if the "participationStatus" of this participant is any 1725 value other than "accepted". See Section 5.2.4 for allowed values 1726 and semantics. 1728 o progressUpdated: "UTCDateTime" (optional). Specifies the date- 1729 time the progress property was last set on this participant. This 1730 is only allowed if the Participant is part of a JSTask. 1732 4.5. Alerts Properties 1734 4.5.1. useDefaultAlerts 1736 Type: "Boolean" (optional, default: false). 1738 If true, use the user's default alerts and ignore the value of the 1739 "alerts" property. Fetching user defaults is dependent on the API 1740 from which this JSCalendar object is being fetched, and is not 1741 defined in this specification. If an implementation cannot determine 1742 the user's default alerts, or none are set, it MUST process the 1743 alerts property as if "useDefaultAlerts" is set to false. 1745 4.5.2. alerts 1747 Type: "Id[Alert]" (optional). 1749 A map of alert ids to Alert objects, representing alerts/reminders to 1750 display or send to the user for this calendar object. 1752 An Alert Object has the following properties: 1754 o @type: "String" (mandatory) 1756 Specifies the type of this object. This MUST be "Alert". 1758 o trigger: "OffsetTrigger|AbsoluteTrigger|UnknownTrigger" 1759 (mandatory) 1760 Defines when to trigger the alert. New types may be defined in 1761 future documents. 1763 An *OffsetTrigger* object has the following properties: 1765 * @type: "String" (mandatory) 1767 Specifies the type of this object. This MUST be 1768 "OffsetTrigger". 1770 * offset: "SignedDuration" (mandatory). 1772 Defines the offset at which to trigger the alert relative to 1773 the time property defined in the "relativeTo" property of the 1774 alert. Negative durations signify alerts before the time 1775 property, positive durations signify alerts after. If the 1776 calendar object does not define a time zone, the user's default 1777 time zone SHOULD be used when determining the offset, if known. 1778 Otherwise, the time zone to use is implementation specific. 1780 * relativeTo: "String" (optional, default: "start") 1782 Specifies the time property that the alert offset is relative 1783 to. The value MUST be one of: 1785 + "start": triggers the alert relative to the start of the 1786 calendar object 1788 + "end": triggers the alert relative to the end/due time of 1789 the calendar object 1791 An *AbsoluteTrigger* object has the following properties: 1793 * @type: "String" (mandatory) 1795 Specifies the type of this object. This MUST be 1796 "AbsoluteTrigger". 1798 * when: "UTCDateTime" (mandatory). 1800 Defines a specific UTC date-time when the alert is triggered. 1802 An *UnknownTrigger* object is an object that contains a *@type* 1803 property whose value is not recognized (i.e., not "OffsetTrigger" 1804 or "AbsoluteTrigger"), plus zero or more other properties. This 1805 is for compatibility with client extensions and future 1806 specifications. Implementations SHOULD NOT trigger for trigger 1807 types they do not understand, but MUST preserve them. 1809 o acknowledged: "UTCDateTime" (optional) 1811 This records when an alert was last acknowledged. This is set 1812 when the user has dismissed the alert; other clients that sync 1813 this property SHOULD automatically dismiss or suppress duplicate 1814 alerts (alerts with the same alert id that triggered on or before 1815 this date-time). 1817 For a recurring calendar object, the "acknowledged" property of 1818 the parent object MUST be updated, unless the alert is already 1819 overridden in the "recurrenceOverrides" property. 1821 Certain kinds of alert action may not provide feedback as to when 1822 the user sees them, for example email based alerts. For those 1823 kinds of alerts, this property SHOULD be set immediately when the 1824 alert is triggered and the action successfully carried out. 1826 o relatedTo: "String[Relation]" (optional) 1828 Relates this alert to other alerts in the same JSCalendar object. 1829 If the user wishes to snooze an alert, the application SHOULD 1830 create an alert to trigger after snoozing. All snooze alerts 1831 SHOULD set a relation to the identifier of the original alert. 1832 The Relation object SHOULD set the "parent" relation type. 1834 o action: "String" (optional, default: "display") 1836 Describes how to alert the user. 1838 The value MUST be at most one of the following values, a value 1839 registered in the IANA JSCalendar Enum Registry, or a vendor- 1840 specific value: 1842 * "display": The alert should be displayed as appropriate for the 1843 current device and user context. 1845 * "email": The alert should trigger an email sent out to the 1846 user, notifying about the alert. This action is typically only 1847 appropriate for server implementations. 1849 4.6. Multilingual Properties 1851 4.6.1. localizations 1853 Type: "String[PatchObject]" (optional). 1855 A map of language tags [RFC5646] to patch objects, which localize the 1856 calendar object into the locale of the respective language tag. 1858 See the description of PatchObject (Section 1.4.8) for the structure 1859 of the PatchObject. The patches are applied to the top-level 1860 calendar object. In addition, the "locale" property of the patched 1861 object is set to the language tag. All pointers for patches MUST end 1862 with one of the following suffixes; any patch that does not follow 1863 this MUST be ignored unless otherwise specified in a future RFC: 1865 o title 1867 o description 1869 o name 1871 A patch MUST NOT have the prefix "recurrenceOverrides"; any 1872 localization of the override MUST be a patch to the localizations 1873 property inside the override instead. For example, a patch to 1874 "locations/abcd1234/title" is permissible, but a patch to "uid" or 1875 "recurrenceOverrides/2018-01-05T14:00:00/title" is not. 1877 Note that this specification does not define how to maintain validity 1878 of localized content. For example, a client application changing a 1879 JSCalendar object's title property might also need to update any 1880 localizations of this property. Client implementations SHOULD 1881 provide the means to manage localizations, but how to achieve this is 1882 specific to the application's workflow and requirements. 1884 4.7. Time Zone Properties 1886 4.7.1. timeZone 1888 Type: "String|null" (optional, default: null). 1890 Identifies the time zone the object is scheduled in, or null for 1891 floating time. This is either a name from the IANA Time Zone 1892 Database [TZDB] or the id of a custom time zone from the "timeZones" 1893 property (see Section 1.4.9). If omitted, this MUST be presumed to 1894 be null (i.e., floating time). 1896 4.7.2. timeZones 1898 Type: "String[TimeZone]" (optional). 1900 Maps identifiers of custom time zones to their time zone definitions. 1901 The following restrictions apply for each key in the map: 1903 o It MUST start with the "/" character (ASCII decimal 47; also see 1904 Sections 3.2.19 of [RFC5545] and 3.6. of [RFC7808] for discussion 1905 of the forward slash character in time zone identifiers). 1907 o It MUST be a valid "paramtext" value as specified in Section 3.1. 1908 of [RFC5545]. 1910 o At least one other property in the same JSCalendar object MUST 1911 reference a time zone using this identifier (i.e., orphaned time 1912 zones are not allowed). 1914 An identifier need only be unique to this JSCalendar object. 1916 A TimeZone object maps a VTIMEZONE component from iCalendar [RFC5545] 1917 and the semantics are as defined there. A valid time zone MUST 1918 define at least one transition rule in the "standard" or "daylight" 1919 property. Its properties are: 1921 o @type: "String" (mandatory) 1923 Specifies the type of this object. This MUST be "TimeZone". 1925 o tzId: "String" (mandatory). 1927 The TZID property from iCalendar. 1929 o lastModified: "UTCDateTime" (optional) 1931 The LAST-MODIFIED property from iCalendar. 1933 o url: "String" (optional) 1935 The TZURL property from iCalendar. 1937 o validUntil: "UTCDateTime" (optional) 1939 The TZUNTIL property from iCalendar specified in [RFC7808]. 1941 o aliases: "String[Boolean]" (optional) 1943 Maps the TZID-ALIAS-OF properties from iCalendar specified in 1944 [RFC7808] to a JSON set of aliases. The set is represented as an 1945 object, with the keys being the aliases. The value for each key 1946 in the set MUST be true. 1948 o standard: "TimeZoneRule[]" (optional) 1950 The STANDARD sub-components from iCalendar. The order MUST be 1951 preserved during conversion. 1953 o daylight: "TimeZoneRule[]" (optional). 1955 The DAYLIGHT sub-components from iCalendar. The order MUST be 1956 preserved during conversion. 1958 A TimeZoneRule object maps a STANDARD or DAYLIGHT sub-component from 1959 iCalendar, with the restriction that at most one recurrence rule is 1960 allowed per rule. It has the following properties: 1962 o @type: "String" (mandatory) 1964 Specifies the type of this object. This MUST be "TimeZoneRule". 1966 o start: "LocalDateTime" (mandatory) 1968 The DTSTART property from iCalendar. 1970 o offsetTo: "String" (mandatory) 1972 The TZOFFSETTO property from iCalendar. 1974 o offsetFrom: "String" (mandatory) 1976 The TZOFFSETFROM property from iCalendar. 1978 o recurrenceRule: "RecurrenceRule" (optional) 1980 The RRULE property mapped as specified in Section 4.3.2. During 1981 recurrence rule evaluation, the "until" property value MUST be 1982 interpreted as a local time in the UTC time zone. 1984 o recurrenceDates: "LocalDateTime[Boolean]" (optional) 1986 Maps the RDATE properties from iCalendar to a JSON set. The set 1987 is represented as an object, with the keys being the recurrence 1988 dates. The value for each key in the set MUST be true. 1990 o names: "String[Boolean]" (optional) 1992 Maps the TZNAME properties from iCalendar to a JSON set. The set 1993 is represented as an object, with the keys being the names. The 1994 value for each key in the set MUST be true. 1996 o comments: "String[]" (optional). Maps the COMMENT properties from 1997 iCalendar. The order MUST be preserved during conversion. 1999 5. Type-specific JSCalendar Properties 2001 5.1. JSEvent Properties 2003 In addition to the common JSCalendar object properties (Section 4) a 2004 JSEvent has the following properties: 2006 5.1.1. start 2008 Type: "LocalDateTime" (mandatory). 2010 The date/time the event starts in the event's time zone (as specified 2011 in the "timeZone" property, see Section 4.7.1). 2013 5.1.2. duration 2015 Type: "Duration" (optional, default: "PT0S"). 2017 The zero or positive duration of the event in the event's start time 2018 zone. 2020 Note that a duration specified using weeks or days does not always 2021 correspond to an exact multiple of 24 hours. The number of 2022 hours/minutes/seconds may vary if it overlaps a period of 2023 discontinuity in the event's time zone, for example a change from 2024 standard time to daylight-savings time. Leap seconds MUST NOT be 2025 considered when computing an exact duration. When computing an exact 2026 duration, the greatest order time components MUST be added first, 2027 that is, the number of days MUST be added first, followed by the 2028 number of hours, number of minutes, and number of seconds. 2029 Fractional seconds MUST be added last. These semantics match the 2030 iCalendar DURATION value type ([RFC5545], Section 3.3.6). 2032 A JSEvent MAY involve start and end locations that are in different 2033 time zones (e.g., a trans-continental flight). This can be expressed 2034 using the "relativeTo" and "timeZone" properties of the JSEvent's 2035 Location objects (see Section 4.2.5). 2037 5.1.3. status 2039 Type: "String" (optional, default: "confirmed"). 2041 The scheduling status (Section 4.4) of a JSEvent. If set, it MUST be 2042 one of the following values, a value registered in the IANA 2043 JSCalendar Enum Registry, or a vendor-specific value: 2045 o "confirmed": Indicates the event is definitely happening. 2047 o "cancelled": Indicates the event has been cancelled. 2049 o "tentative": Indicates the event may happen. 2051 5.2. JSTask Properties 2053 In addition to the common JSCalendar object properties (Section 4) a 2054 JSTask has the following properties: 2056 5.2.1. due 2058 Type: "LocalDateTime" (optional). 2060 The date/time the task is due in the task's time zone. 2062 5.2.2. start 2064 Type: "LocalDateTime" (optional). 2066 The date/time the task should start in the task's time zone. 2068 5.2.3. estimatedDuration 2070 Type: "Duration" (optional). 2072 Specifies the estimated positive duration of time the task takes to 2073 complete. 2075 5.2.4. progress 2077 Type: "String" (optional). 2079 Defines the progress of this task. If omitted, the default progress 2080 (Section 4.4) of a JSTask is defined as follows (in order of 2081 evaluation): 2083 o "completed": if the "progress" property value of all participants 2084 is "completed". 2086 o "failed": if at least one "progress" property value of a 2087 participant is "failed". 2089 o "in-process": if at least one "progress" property value of a 2090 participant is "in-process". 2092 o "needs-action": If none of the other criteria match. 2094 If set, it MUST be one of the following values, a value registered in 2095 the IANA JSCalendar Enum Registry, or a vendor-specific value: 2097 o "needs-action": Indicates the task needs action. 2099 o "in-process": Indicates the task is in process. 2101 o "completed": Indicates the task is completed. 2103 o "failed": Indicates the task failed. 2105 o "cancelled": Indicates the task was cancelled. 2107 5.2.5. progressUpdated 2109 Type: "UTCDateTime" (optional). 2111 Specifies the date/time the "progress" property of either the task 2112 overall (Section 5.2.4) or a specific participant (Section 4.4.5) was 2113 last updated. 2115 If the task is recurring and has future instances, a client may want 2116 to keep track of the last progress update timestamp of a specific 2117 task recurrence, but leave other instances unchanged. One way to 2118 achieve this is by overriding the progressUpdated property in the 2119 task "recurrenceOverrides" property. However, this could produce a 2120 long list of timestamps for regularly recurring tasks. An 2121 alternative approach is to split the JSTask into a current, single 2122 instance of JSTask with this instance progress update time and a 2123 future recurring instance. See also Section 4.1.3 on splitting. 2125 5.3. JSGroup Properties 2127 JSGroup supports the following common JSCalendar properties 2128 (Section 4): 2130 o @type 2132 o categories 2134 o color 2136 o created 2138 o description 2140 o descriptionContentType 2141 o keywords 2143 o links 2145 o locale 2147 o prodId 2149 o title 2151 o updated 2153 o uid 2155 In addition, the following JSGroup-specific properties are supported: 2157 5.3.1. entries 2159 Type: "String[JSTask|JSEvent]" (mandatory). 2161 A collection of group members. This is represented as a map of the 2162 "uid" property value to the JSCalendar object member having that uid. 2163 Implementations MUST ignore entries of unknown type. 2165 5.3.2. source 2167 Type: "String" (optional). 2169 The source from which updated versions of this group may be retrieved 2170 from. The value MUST be a URI. 2172 6. Examples 2174 The following examples illustrate several aspects of the JSCalendar 2175 data model and format. The examples may omit mandatory or additional 2176 properties, which is indicated by a placeholder property with key 2177 "...". While most of the examples use calendar event objects, they 2178 are also illustrative for tasks. 2180 6.1. Simple event 2182 This example illustrates a simple one-time event. It specifies a 2183 one-time event that begins on January 15, 2018 at 1pm New York local 2184 time and ends after 1 hour. 2186 { 2187 "@type": "jsevent", 2188 "uid": "2a358cee-6489-4f14-a57f-c104db4dc2f1", 2189 "updated": "2018-01-15T18:00:00Z", 2190 "title": "Some event", 2191 "start": "2018-01-15T13:00:00", 2192 "timeZone": "America/New_York", 2193 "duration": "PT1H" 2194 } 2196 6.2. Simple task 2198 This example illustrates a simple task for a plain to-do item. 2200 { 2201 "@type": "jstask", 2202 "uid": "2a358cee-6489-4f14-a57f-c104db4dc2f2", 2203 "updated": "2018-01-15T18:00:00Z", 2204 "title": "Do something" 2205 } 2207 6.3. Simple group 2209 This example illustrates a simple calendar object group that contains 2210 an event and a task. 2212 { 2213 "@type": "jsgroup", 2214 "uid": "2a358cee-6489-4f14-a57f-c104db4dc343", 2215 "updated": "2018-01-15T18:00:00Z", 2216 "name": "A simple group", 2217 "entries": { 2218 "2a358cee-6489-4f14-a57f-c104db4dc2f1": { 2219 "@type": "jsevent", 2220 "uid": "2a358cee-6489-4f14-a57f-c104db4dc2f1", 2221 "updated": "2018-01-15T18:00:00Z", 2222 "title": "Some event", 2223 "start": "2018-01-15T13:00:00", 2224 "timeZone": "America/New_York", 2225 "duration": "PT1H" 2226 }, 2227 "2a358cee-6489-4f14-a57f-c104db4dc2f2": { 2228 "@type": "jstask", 2229 "uid": "2a358cee-6489-4f14-a57f-c104db4dc2f2", 2230 "updated": "2018-01-15T18:00:00Z", 2231 "title": "Do something" 2232 } 2233 } 2234 } 2236 6.4. All-day event 2238 This example illustrates an event for an international holiday. It 2239 specifies an all-day event on April 1 that occurs every year since 2240 the year 1900. 2242 { 2243 "...": "", 2244 "title": "April Fool's Day", 2245 "showWithoutTime": true, 2246 "start": "1900-04-01T00:00:00", 2247 "duration": "P1D", 2248 "recurrenceRules": [{ 2249 "@type": "RecurrenceRule", 2250 "frequency": "yearly" 2251 }] 2252 } 2254 6.5. Task with a due date 2256 This example illustrates a task with a due date. It is a reminder to 2257 buy groceries before 6pm Vienna local time on January 19, 2018. The 2258 calendar user expects to need 1 hour for shopping. 2260 { 2261 "...": "", 2262 "title": "Buy groceries", 2263 "due": "2018-01-19T18:00:00", 2264 "timeZone": "Europe/Vienna", 2265 "estimatedDuration": "PT1H" 2266 } 2268 6.6. Event with end time-zone 2270 This example illustrates the use of end time-zones by use of an 2271 international flight. The flight starts on April 1, 2018 at 9am in 2272 Berlin local time. The duration of the flight is scheduled at 10 2273 hours 30 minutes. The time at the flights destination is in the same 2274 time-zone as Tokyo. Calendar clients could use the end time-zone to 2275 display the arrival time in Tokyo local time and highlight the time- 2276 zone difference of the flight. The location names can serve as input 2277 for navigation systems. 2279 { 2280 "...": "", 2281 "title": "Flight XY51 to Tokyo", 2282 "start": "2018-04-01T09:00:00", 2283 "timeZone": "Europe/Berlin", 2284 "duration": "PT10H30M", 2285 "locations": { 2286 "2a358cee-6489-4f14-a57f-c104db4dc2f1": { 2287 "@type": "Location", 2288 "rel": "start", 2289 "name": "Frankfurt Airport (FRA)" 2290 }, 2291 "c2c7ac67-dc13-411e-a7d4-0780fb61fb08": { 2292 "@type": "Location", 2293 "rel": "end", 2294 "name": "Narita International Airport (NRT)", 2295 "timeZone": "Asia/Tokyo" 2296 } 2297 } 2298 } 2300 6.7. Floating-time event (with recurrence) 2302 This example illustrates the use of floating-time. Since January 1, 2303 2018, a calendar user blocks 30 minutes every day to practice Yoga at 2304 7am local time, in whatever time-zone the user is located on that 2305 date. 2307 { 2308 "...": "", 2309 "title": "Yoga", 2310 "start": "2018-01-01T07:00:00", 2311 "duration": "PT30M", 2312 "recurrenceRules": [{ 2313 "@type": "RecurrenceRule", 2314 "frequency": "daily" 2315 }] 2316 } 2318 6.8. Event with multiple locations and localization 2320 This example illustrates an event that happens at both a physical and 2321 a virtual location. Fans can see a live concert on premises or 2322 online. The event title and descriptions are localized. 2324 { 2325 "...": "", 2326 "title": "Live from Music Bowl: The Band", 2327 "description": "Go see the biggest music event ever!", 2328 "locale": "en", 2329 "start": "2018-07-04T17:00:00", 2330 "timeZone": "America/New_York", 2331 "duration": "PT3H", 2332 "locations": { 2333 "c0503d30-8c50-4372-87b5-7657e8e0fedd": { 2334 "@type": "Location", 2335 "name": "The Music Bowl", 2336 "description": "Music Bowl, Central Park, New York", 2337 "coordinates": "geo:40.7829,-73.9654" 2338 } 2339 }, 2340 "virtualLocations": { 2341 "6f3696c6-1e07-47d0-9ce1-f50014b0041a": { 2342 "@type": "VirtualLocation", 2343 "name": "Free live Stream from Music Bowl", 2344 "uri": "https://stream.example.com/the_band_2018" 2345 } 2346 }, 2347 "localizations": { 2348 "de": { 2349 "title": "Live von der Music Bowl: The Band!", 2350 "description": "Schau dir das groesste Musikereignis an!", 2351 "virtualLocations/6f3696c6-1e07-47d0-9ce1-f50014b0041a/name": 2352 "Gratis Live-Stream aus der Music Bowl" 2353 } 2354 } 2355 } 2357 6.9. Recurring event with overrides 2359 This example illustrates the use of recurrence overrides. A math 2360 course at a University is held for the first time on January 8, 2018 2361 at 9am London time and occurs every week until June 25, 2018. Each 2362 lecture lasts for one hour and 30 minutes and is located at the 2363 Mathematics department. This event has exceptional occurrences: at 2364 the last occurrence of the course is an exam, which lasts for 2 hours 2365 and starts at 10am. Also, the location of the exam differs from the 2366 usual location. On April 2 no course is held. On January 5 at 2pm 2367 is an optional introduction course, that occurs before the first 2368 regular lecture. 2370 { 2371 "...": "", 2372 "title": "Calculus I", 2373 "start": "2018-01-08T09:00:00", 2374 "timeZone": "Europe/London", 2375 "duration": "PT1H30M", 2376 "locations": { 2377 "2a358cee-6489-4f14-a57f-c104db4dc2f1": { 2378 "@type": "Location", 2379 "title": "Math lab room 1", 2380 "description": "Math Lab I, Department of Mathematics" 2381 } 2382 }, 2383 "recurrenceRules": [{ 2384 "@type": "RecurrenceRule", 2385 "frequency": "weekly", 2386 "until": "2018-06-25T09:00:00" 2387 }], 2388 "recurrenceOverrides": { 2389 "2018-01-05T14:00:00": { 2390 "title": "Introduction to Calculus I (optional)" 2391 }, 2392 "2018-04-02T09:00:00": { 2393 "excluded": "true" 2394 }, 2395 "2018-06-25T09:00:00": { 2396 "title": "Calculus I Exam", 2397 "start": "2018-06-25T10:00:00", 2398 "duration": "PT2H", 2399 "locations": { 2400 "2a358cee-6489-4f14-a57f-c104db4dc2f1": { 2401 "@type": "Location", 2402 "title": "Big Auditorium", 2403 "description": "Big Auditorium, Other Road" 2404 } 2405 } 2406 } 2407 } 2408 } 2410 6.10. Recurring event with participants 2412 This example illustrates scheduled events. A team meeting occurs 2413 every week since January 8, 2018 at 9am Johannesburg time. The event 2414 owner also chairs the event. Participants meet in a virtual meeting 2415 room. An attendee has accepted the invitation, but on March 8, 2018 2416 he is unavailable and declined participation for this occurrence. 2418 { 2419 "...": "", 2420 "title": "FooBar team meeting", 2421 "start": "2018-01-08T09:00:00", 2422 "timeZone": "Africa/Johannesburg", 2423 "duration": "PT1H", 2424 "virtualLocations": { 2425 "2a358cee-6489-4f14-a57f-c104db4dc2f1": { 2426 "@type": "VirtualLocation", 2427 "name": "ChatMe meeting room", 2428 "uri": "https://chatme.example.com?id=1234567" 2429 } 2430 }, 2431 "recurrenceRules": [{ 2432 "@type": "RecurrenceRule", 2433 "frequency": "weekly" 2434 }], 2435 "replyTo": { 2436 "imip": "mailto:6489-4f14-a57f-c1@schedule.example.com" 2437 }, 2438 "participants": { 2439 "dG9tQGZvb2Jhci5xlLmNvbQ": { 2440 "@type": "Participant", 2441 "name": "Tom Tool", 2442 "email": "tom@foobar.example.com", 2443 "sendTo": { 2444 "imip": "mailto:6489-4f14-a57f-c1@calendar.example.com" 2445 }, 2446 "participationStatus": "accepted", 2447 "roles": { 2448 "attendee": true 2449 } 2450 }, 2451 "em9lQGZvb2GFtcGxlLmNvbQ": { 2452 "@type": "Participant", 2453 "name": "Zoe Zelda", 2454 "email": "zoe@foobar.example.com", 2455 "sendTo": { 2456 "imip": "mailto:zoe@foobar.example.com" 2457 }, 2458 "participationStatus": "accepted", 2459 "roles": { 2460 "owner": true, 2461 "attendee": true, 2462 "chair": true 2463 } 2464 }, 2465 "...": "" 2467 }, 2468 "recurrenceOverrides": { 2469 "2018-03-08T09:00:00": { 2470 "participants/dG9tQGZvb2Jhci5xlLmNvbQ/participationStatus": 2471 "declined" 2472 } 2473 } 2474 } 2476 7. Security Considerations 2478 Calendaring and scheduling information is very privacy-sensitive. 2479 The transmission of such information must be done carefully to 2480 protect it from possible threats, such as eavesdropping, replay, 2481 message insertion, deletion, modification, and man-in-the-middle 2482 attacks. This document just defines the data format; such 2483 considerations are primarily the concern of the API or method of 2484 storage and transmission of such files. 2486 7.1. Expanding Recurrences 2488 A recurrence rule may produce infinite occurrences of an event. 2489 Implementations MUST handle expansions carefully to prevent 2490 accidental or deliberate resource exhaustion. 2492 Conversely, a recurrence rule may be specified that does not expand 2493 to anything. It is not always possible to tell this through static 2494 analysis of the rule, so implementations MUST be careful to avoid 2495 getting stuck in infinite loops, or otherwise exhausting resources 2496 while searching for the next occurrence. 2498 7.2. JSON Parsing 2500 The Security Considerations of [RFC8259] apply to the use of JSON as 2501 the data interchange format. 2503 As for any serialization format, parsers need to thoroughly check the 2504 syntax of the supplied data. JSON uses opening and closing tags for 2505 several types and structures, and it is possible that the end of the 2506 supplied data will be reached when scanning for a matching closing 2507 tag; this is an error condition, and implementations need to stop 2508 scanning at the end of the supplied data. 2510 JSON also uses a string encoding with some escape sequences to encode 2511 special characters within a string. Care is needed when processing 2512 these escape sequences to ensure that they are fully formed before 2513 the special processing is triggered, with special care taken when the 2514 escape sequences appear adjacent to other (non-escaped) special 2515 characters or adjacent to the end of data (as in the previous 2516 paragraph). 2518 If parsing JSON into a non-textual structured data format, 2519 implementations may need to allocate storage to hold JSON string 2520 elements. Since JSON does not use explicit string lengths, the risk 2521 of denial of service due to resource exhaustion is small, but 2522 implementations may still wish to place limits on the size of 2523 allocations they are willing to make in any given context, to avoid 2524 untrusted data causing excessive memory allocation. 2526 7.3. URI Values 2528 Several JSCalendar properties contain URIs as values, and processing 2529 these properties requires extra care. Section 7 of [RFC3986] 2530 discusses security risk related to URIs. 2532 8. IANA Considerations 2534 8.1. Media Type Registration 2536 This document defines a media type for use with JSCalendar data 2537 formatted in JSON. 2539 Type name: application 2541 Subtype name: jscalendar+json 2543 Required parameters: type 2545 The "type" parameter conveys the type of the JSCalendar data in 2546 the body part, with the value being one of "jsevent", "jstask", or 2547 "jsgroup". The parameter MUST NOT occur more than once. It MUST 2548 match the value of the "@type" property of the JSON-formatted 2549 JSCalendar object in the body. 2551 Optional parameters: none 2553 Encoding considerations: Same as encoding considerations of 2554 application/json as specified in RFC8529, Section 11 [RFC8259]. 2556 Security considerations: See Section 7 of this document. 2558 Interoperability considerations: This media type provides an 2559 alternative to iCalendar, jCal and proprietary JSON-based 2560 calendaring data formats. 2562 Published specification: This specification. 2564 Applications that use this media type: Applications that currently 2565 make use of the text/calendar and application/calendar+json media 2566 types can use this as an alternative. Similarly, applications 2567 that use the application/json media type to transfer calendaring 2568 data can use this to further specify the content. 2570 Fragment identifier considerations: N/A 2572 Additional information: 2574 Magic number(s): N/A 2576 File extensions(s): N/A 2578 Macintosh file type code(s): N/A 2580 Person & email address to contact for further information: 2581 calsify@ietf.org 2583 Intended usage: COMMON 2585 Restrictions on usage: N/A 2587 Author: See the "Author's Address" section of this document. 2589 Change controller: IETF 2591 8.2. Creation of "JSCalendar Properties" Registry 2593 The IANA will create the "JSCalendar Properties" registry to allow 2594 interoperability of extensions to JSCalendar objects. 2596 This registry follows the Expert Review process ([RFC8126], 2597 Section 4.5) unless the "intended use" field is "common", in which 2598 case registration follows the Specification Required process 2599 ([RFC8126], Section 4.6). Preliminary community review for this 2600 registry is optional but strongly encouraged. 2602 A registration can have an intended use of "common", "reserved", or 2603 "obsolete". The IANA will list common-use registrations prominently 2604 and separately from those with other intended use values. 2606 A "reserved" registration reserves a property name without assigning 2607 semantics to avoid name collisions with future extensions or protocol 2608 use. 2610 An "obsolete" registration denotes a property that is no longer 2611 expected to be added by up-to-date systems. A new property has 2612 probably been defined covering the obsolete property's semantics. 2614 The JSCalendar property registration procedure is not a formal 2615 standards process but rather an administrative procedure intended to 2616 allow community comment and sanity checking without excessive time 2617 delay. It is designed to encourage vendors to document and register 2618 new properties they add for use cases not covered by the original 2619 standard, leading to increased interoperability. 2621 8.2.1. Preliminary Community Review 2623 Notice of a potential new registration SHOULD be sent to the Calext 2624 mailing list for review. This mailing list is 2625 appropriate to solicit community feedback on a proposed new property. 2627 Properties registrations must be marked with their intended use: 2628 "common", "reserved" or "obsolete". 2630 The intent of the public posting to this list is to solicit comments 2631 and feedback on the choice of the property name, the unambiguity of 2632 the specification document, and a review of any interoperability or 2633 security considerations. The submitter may submit a revised 2634 registration proposal or abandon the registration completely at any 2635 time. 2637 8.2.2. Submit Request to IANA 2639 Registration requests can be sent to . 2641 8.2.3. Designated Expert Review 2643 The primary concern of the designated expert (DE) is preventing name 2644 collisions and encouraging the submitter to document security and 2645 privacy considerations. For a common-use registration, the DE is 2646 expected to confirm that suitable documentation, as described in 2647 Section 4.6 of [RFC8126], is available to ensure interoperability. 2648 That documentation will usually be in an RFC, but simple definitions 2649 are likely to use a web/wiki page, and if a sentence or two is deemed 2650 sufficient it could be described in the registry itself. The DE 2651 should also verify that the property name does not conflict with work 2652 that is active or already published within the IETF. A published 2653 specification is not required for reserved or obsolete registrations. 2655 The DE will either approve or deny the registration request and 2656 publish a notice of the decision to the Calext WG mailing list or its 2657 successor, as well as inform IANA. A denial notice must be justified 2658 by an explanation, and, in the cases where it is possible, concrete 2659 suggestions on how the request can be modified so as to become 2660 acceptable should be provided. 2662 8.2.4. Change Procedures 2664 Once a JSCalendar property has been published by the IANA, the change 2665 controller may request a change to its definition. The same 2666 procedure that would be appropriate for the original registration 2667 request is used to process a change request. 2669 JSCalendar property registrations may not be deleted; properties that 2670 are no longer believed appropriate for use can be declared obsolete 2671 by a change to their "intended use" field; such properties will be 2672 clearly marked in the lists published by the IANA. 2674 Significant changes to a JSCalendar property's definition should be 2675 requested only when there are serious omissions or errors in the 2676 published specification, as such changes may cause interoperability 2677 issues. When review is required, a change request may be denied if 2678 it renders entities that were valid under the previous definition 2679 invalid under the new definition. 2681 The owner of a JSCalendar property may pass responsibility to another 2682 person or agency by informing the IANA; this can be done without 2683 discussion or review. 2685 8.2.5. JMAP Properties Registry Template 2687 o Property Name: The name of the property. The property name MUST 2688 NOT already be registered for any of the object types listed in 2689 the "Property Context" field of this registration. Other object 2690 types MAY already have registered a different property with the 2691 same name. 2693 o Property Type: The type of this property, using type signatures as 2694 specified in Section 1.3. The property type MUST be registed in 2695 the Type Registry. 2697 o Property Context: A comma-separated list of JSCalendar object 2698 types this property is allowed on. 2700 o Reference or Description: A brief description or RFC number and 2701 section reference where the property is specified (omitted for 2702 "reserved" property names). 2704 o Intended Use: Common, reserved, or obsolete. 2706 o Change Controller: ("IETF" for IETF-stream RFCs). 2708 8.2.6. Initial Contents for the JSCalendar Properties Registry 2710 The following table lists the initial entries of the JSCalendar 2711 Properties registry. All properties are for common-use. All RFC 2712 section references are for this document. The change controller for 2713 all these properties is "IETF". 2715 +---------------+----------------------------+------------+---------+ 2716 | Property Name | Property Type | Property | Referen | 2717 | | | Context | ce or D | 2718 | | | | escript | 2719 | | | | ion | 2720 +---------------+----------------------------+------------+---------+ 2721 | @type | String | JSEvent, | Section | 2722 | | | JSTask, | 4.1.1, | 2723 | | | JSGroup, A | Section | 2724 | | | bsoluteTri | 4.5.2, | 2725 | | | gger, | Section | 2726 | | | Alert, | 4.2.7, | 2727 | | | Link, | Section | 2728 | | | Location, | 4.2.5, | 2729 | | | OffsetTrig | Section | 2730 | | | ger, Parti | 4.4.5, | 2731 | | | cipant, Re | Section | 2732 | | | currenceRu | 4.3.2, | 2733 | | | le, | Section | 2734 | | | Relation, | 4.1.3, | 2735 | | | TimeZone, | Section | 2736 | | | VirtualLoc | 4.7.2, | 2737 | | | ation | Section | 2738 | | | | 4.2.6 | 2739 | | | | | 2740 | acknowledged | UTCDateTime | Alert | Section | 2741 | | | | 4.5.2 | 2742 | | | | | 2743 | action | String | Alert | Section | 2744 | | | | 4.5.2 | 2745 | | | | | 2746 | alerts | Id[Alert] | JSEvent, | Section | 2747 | | | JSTask | 4.5.2 | 2748 | | | | | 2749 | byDay | NDay[] | Recurrence | Section | 2750 | | | Rule | 4.3.2 | 2751 | | | | | 2752 | byHour | UnsignedInt[] | Recurrence | Section | 2753 | | | Rule | 4.3.2 | 2754 | | | | | 2755 | byMinute | UnsignedInt[] | Recurrence | Section | 2756 | | | Rule | 4.3.2 | 2757 | | | | | 2758 | byMonth | String[] | Recurrence | Section | 2759 | | | Rule | 4.3.2 | 2760 | | | | | 2761 | byMonthDay | Int[] | Recurrence | Section | 2762 | | | Rule | 4.3.2 | 2763 | | | | | 2764 | bySecond | UnsignedInt[] | Recurrence | Section | 2765 | | | Rule | 4.3.2 | 2766 | | | | | 2767 | bySetPosition | Int[] | Recurrence | Section | 2768 | | | Rule | 4.3.2 | 2769 | | | | | 2770 | byWeekNo | Int[] | Recurrence | Section | 2771 | | | Rule | 4.3.2 | 2772 | | | | | 2773 | byYearDay | Int[] | Recurrence | Section | 2774 | | | Rule | 4.3.2 | 2775 | | | | | 2776 | categories | String[Boolean] | JSEvent, | Section | 2777 | | | JSTask, | 4.2.10 | 2778 | | | JSGroup | | 2779 | | | | | 2780 | cid | String | Link | Section | 2781 | | | | 4.2.7 | 2782 | | | | | 2783 | color | String | JSEvent, | Section | 2784 | | | JSTask, | 4.2.11 | 2785 | | | JSGroup | | 2786 | | | | | 2787 | contentType | String | Link | Section | 2788 | | | | 4.2.7 | 2789 | | | | | 2790 | coordinates | String | Location | Section | 2791 | | | | 4.2.5 | 2792 | | | | | 2793 | count | UnsignedInt | Recurrence | Section | 2794 | | | Rule | 4.3.2 | 2795 | | | | | 2796 | created | UTCDateTime | JSEvent, | Section | 2797 | | | JSTask, | 4.1.5 | 2798 | | | JSGroup | | 2799 | | | | | 2800 | delegatedFrom | String[Boolean] | Participan | Section | 2801 | | | t | 4.4.5 | 2802 | | | | | 2803 | delegatedTo | String[Boolean] | Participan | Section | 2804 | | | t | 4.4.5 | 2805 | | | | | 2806 | description | String | JSEvent, | Section | 2807 | | | JSTask, | 4.2.2, | 2808 | | | Location, | Section | 2809 | | | VirtualLoc | 4.2.5, | 2810 | | | ation | Section | 2811 | | | | 4.2.6 | 2812 | | | | | 2813 | descriptionCo | String | JSEvent, | Section | 2814 | ntentType | | JSTask | 4.2.3 | 2815 | | | | | 2816 | display | String | Link | Section | 2817 | | | | 4.2.7 | 2818 | | | | | 2819 | due | LocalDateTime | JSTask | Section | 2820 | | | | 5.2.1 | 2821 | | | | | 2822 | duration | Duration | JSEvent | Section | 2823 | | | | 5.1.2 | 2824 | | | | | 2825 | email | String | Participan | Section | 2826 | | | t | 4.4.5 | 2827 | | | | | 2828 | entries | String[JSTask|JSEvent] | JSGroup | Section | 2829 | | | | 5.3.1 | 2830 | | | | | 2831 | estimatedDura | Duration | JSTask | Section | 2832 | tion | | | 5.2.3 | 2833 | | | | | 2834 | excluded | Boolean | JSEvent, | Section | 2835 | | | JSTask | 4.3.4 | 2836 | | | | | 2837 | expectReply | Boolean | Participan | Section | 2838 | | | t | 4.4.5 | 2839 | | | | | 2840 | firstDayOfWee | String | Recurrence | Section | 2841 | k | | Rule | 4.3.2 | 2842 | | | | | 2843 | freeBusyStatu | String | JSEvent, | Section | 2844 | s | | JSTask | 4.4.2 | 2845 | | | | | 2846 | frequency | String | Recurrence | Section | 2847 | | | Rule | 4.3.2 | 2848 | | | | | 2849 | href | String | Link | Section | 2850 | | | | 4.2.7 | 2851 | | | | | 2852 | interval | UnsignedInt | Recurrence | Section | 2853 | | | Rule | 4.3.2 | 2854 | | | | | 2855 | invitedBy | String | Participan | Section | 2856 | | | t | 4.4.5 | 2857 | | | | | 2858 | keywords | String[Boolean] | JSEvent, | Section | 2859 | | | JSTask, | 4.2.9 | 2860 | | | JSGroup | | 2861 | | | | | 2862 | kind | String | Participan | Section | 2863 | | | t | 4.4.5 | 2864 | | | | | 2865 | language | String | Participan | Section | 2866 | | | t | 4.4.5 | 2867 | | | | | 2868 | linkIds | Id[Boolean] | Location, | Section | 2869 | | | Participan | 4.2.5, | 2870 | | | t | Section | 2871 | | | | 4.4.5 | 2872 | | | | | 2873 | links | Id[Link] | JSGroup, | Section | 2874 | | | JSEvent, | 4.2.7 | 2875 | | | JSTask | | 2876 | | | | | 2877 | locale | String | JSGroup, | Section | 2878 | | | JSEvent, | 4.2.7 | 2879 | | | JSTask | | 2880 | | | | | 2881 | localizations | String[PatchObject] | JSEvent, | Section | 2882 | | | JSTask | 4.6.1 | 2883 | | | | | 2884 | locationId | String | Participan | Section | 2885 | | | t | 4.4.5 | 2886 | | | | | 2887 | locations | Id[Location] | JSEvent, | Section | 2888 | | | JSTask | 4.2.5 | 2889 | | | | | 2890 | locationTypes | String[Boolean] | Location | Section | 2891 | | | | 4.2.5 | 2892 | | | | | 2893 | memberOf | String[Boolean] | Participan | Section | 2894 | | | t | 4.4.5 | 2895 | | | | | 2896 | method | String | JSEvent, | Section | 2897 | | | JSTask | 4.1.8 | 2898 | | | | | 2899 | name | String | Location, | Section | 2900 | | | VirtualLoc | 4.2.5, | 2901 | | | ation, Par | Section | 2902 | | | ticipant | 4.2.6, | 2903 | | | | Section | 2904 | | | | 4.4.5 | 2905 | | | | | 2906 | offset | SignedDuration | OffsetTrig | Section | 2907 | | | ger | 4.5.2 | 2908 | | | | | 2909 | participants | Id[Participant] | JSEvent, | Section | 2910 | | | JSTask | 4.4.5 | 2911 | | | | | 2912 | participation | String | Participan | Section | 2913 | Comment | | t | 4.4.5 | 2914 | | | | | 2915 | participation | String | Participan | Section | 2916 | Status | | t | 4.4.5 | 2917 | | | | | 2918 | priority | Int | JSEvent, | Section | 2919 | | | JSTask | 4.4.1 | 2920 | | | | | 2921 | privacy | String | JSEvent, | Section | 2922 | | | JSTask | 4.4.3 | 2923 | | | | | 2924 | prodId | String | JSEvent, | Section | 2925 | | | JSTask, | 4.1.4 | 2926 | | | JSGroup | | 2927 | | | | | 2928 | progress | String | JSTask, Pa | Section | 2929 | | | rticipant | 5.2.4 | 2930 | | | | | 2931 | progressUpdat | UTCDateTime | JSTask, Pa | Section | 2932 | ed | | rticipant | 5.2.5 | 2933 | | | | | 2934 | recurrenceId | LocalDateTime | JSEvent, | Section | 2935 | | | JSTask | 4.3.1 | 2936 | | | | | 2937 | recurrenceOve | LocalDateTime[PatchObject] | JSEvent, | Section | 2938 | rrides | | JSTask | 4.3.3 | 2939 | | | | | 2940 | recurrenceRul | RecurrenceRule[] | JSEvent, | Section | 2941 | es | | JSTask | 4.3.2 | 2942 | | | | | 2943 | rel | String | Link | Section | 2944 | | | | 4.2.7 | 2945 | | | | | 2946 | relatedTo | String[Relation] | JSEvent, | Section | 2947 | | | JSTask, | 4.1.3, | 2948 | | | Alert | Section | 2949 | | | | 4.5.2 | 2950 | | | | | 2951 | relation | String[Boolean] | Relation | Section | 2952 | | | | 1.4.10 | 2953 | | | | | 2954 | relativeTo | String | OffsetTrig | Section | 2955 | | | ger, | 4.5.2, | 2956 | | | Location | Section | 2957 | | | | 4.2.5 | 2958 | | | | | 2959 | replyTo | String[String] | JSEvent, | Section | 2960 | | | JSTask | 4.4.4 | 2961 | | | | | 2962 | roles | String[Boolean] | Participan | Section | 2963 | | | t | 4.4.5 | 2964 | | | | | 2965 | rscale | String | Recurrence | Section | 2966 | | | Rule | 4.3.2 | 2967 | | | | | 2968 | scheduleAgent | String | Participan | Section | 2969 | | | t | 4.4.5 | 2970 | | | | | 2971 | scheduleSeque | UnsignedInt | Participan | Section | 2972 | nce | | t | 4.4.5 | 2973 | | | | | 2974 | scheduleUpdat | UTCDateTime | Participan | Section | 2975 | ed | | t | 4.4.5 | 2976 | | | | | 2977 | sendTo | String[String] | Participan | Section | 2978 | | | t | 4.4.5 | 2979 | | | | | 2980 | sequence | UnsignedInt | JSEvent, | Section | 2981 | | | JSTask | 4.1.7 | 2982 | | | | | 2983 | showWithoutTi | Boolean | JSEvent, | Section | 2984 | me | | JSTask | 4.2.4 | 2985 | | | | | 2986 | size | UnsignedInt | Link | Section | 2987 | | | | 4.2.7 | 2988 | | | | | 2989 | skip | String | Recurrence | Section | 2990 | | | Rule | 4.3.2 | 2991 | | | | | 2992 | source | String | JSGroup | Section | 2993 | | | | 5.3.2 | 2994 | | | | | 2995 | start | LocalDateTime | JSEvent, | Section | 2996 | | | JSTask | 5.1.1, | 2997 | | | | Section | 2998 | | | | 5.2.2 | 2999 | | | | | 3000 | status | String | JSEvent | Section | 3001 | | | | 5.1.3 | 3002 | | | | | 3003 | timeZone | String|null | JSEvent, | Section | 3004 | | | JSTask, | 4.7.1, | 3005 | | | Location | Section | 3006 | | | | 4.2.5 | 3007 | | | | | 3008 | timeZones | String[TimeZone] | JSEvent, | Section | 3009 | | | JSTask | 4.7.2 | 3010 | | | | | 3011 | title | String | JSEvent, | Section | 3012 | | | JSTask, | 4.2.1 | 3013 | | | JSGroup, | | 3014 | | | Link | | 3015 | | | | | 3016 | trigger | OffsetTrigger|AbsoluteTrig | Alert | Section | 3017 | | ger|UnknownTrigger | | 4.5.2 | 3018 | | | | | 3019 | uid | String | JSEvent, | Section | 3020 | | | JSTask, | 4.1.2 | 3021 | | | JSGroup | | 3022 | | | | | 3023 | until | LocalDateTime | Recurrence | Section | 3024 | | | Rule | 4.3.2 | 3025 | | | | | 3026 | updated | UTCDateTime | JSEvent, | Section | 3027 | | | JSTask, | 4.1.6 | 3028 | | | JSGroup | | 3029 | | | | | 3030 | uri | String | VirtualLoc | Section | 3031 | | | ation | 4.2.6 | 3032 | | | | | 3033 | useDefaultAle | Boolean | JSEvent, | Section | 3034 | rts | | JSTask | 4.5.1 | 3035 | | | | | 3036 | virtualLocati | Id[VirtualLocation] | JSEvent, | Section | 3037 | ons | | JSTask | 4.2.6 | 3038 | | | | | 3039 | when | UTCDateTime | AbsoluteTr | Section | 3040 | | | igger | 4.5.2 | 3041 +---------------+----------------------------+------------+---------+ 3042 Table 1 3044 8.3. Creation of "JSCalendar Types" Registry 3046 The IANA will create the "JSCalendar Types" registry to avoid name 3047 collisions and provide a complete reference for all data types used 3048 for JSCalendar property values. The registration process is the same 3049 as for the JSCalendar Properties registry, as defined in Section 8.2. 3051 8.3.1. JMAP Types Registry Template 3053 o Type Name: The name of the type. 3055 o Reference or Description: A brief description or RFC number and 3056 section reference where the Type is specified (may be omitted for 3057 "reserved" type names). 3059 o Intended Use: Common, reserved, or obsolete. 3061 o Change Controller: ("IETF" for IETF-stream RFCs). 3063 8.3.2. Initial Contents for the JSCalendar Types Registry 3065 The following table lists the initial entries of the JSCalendar Types 3066 registry. All properties are for common-use. All RFC section 3067 references are for this document. The change controller for all 3068 these properties is "IETF". 3070 +-----------------+--------------------------+ 3071 | Type Name | Reference or Description | 3072 +-----------------+--------------------------+ 3073 | Alert | Section 4.5.2 | 3074 | | | 3075 | Boolean | Section 1.3 | 3076 | | | 3077 | Duration | Section 1.4.5 | 3078 | | | 3079 | Id | Section 1.4.7 | 3080 | | | 3081 | Int | Section 1.4.1 | 3082 | | | 3083 | LocalDateTime | Section 1.4.4 | 3084 | | | 3085 | Link | Section 4.2.7 | 3086 | | | 3087 | Location | Section 4.2.5 | 3088 | | | 3089 | Number | Section 1.3 | 3090 | | | 3091 | Participant | Section 4.4.5 | 3092 | | | 3093 | PatchObject | Section 1.4.8 | 3094 | | | 3095 | RecurrenceRule | Section 4.3.2 | 3096 | | | 3097 | Relation | Section 1.4.10 | 3098 | | | 3099 | SignedDuration | Section 1.4.6 | 3100 | | | 3101 | String | Section 1.3 | 3102 | | | 3103 | TimeZone | Section 4.7.2 | 3104 | | | 3105 | TimeZoneRule | Section 4.7.2 | 3106 | | | 3107 | UnsignedInt | Section 1.4.2 | 3108 | | | 3109 | UTCDateTime | Section 1.4.3 | 3110 | | | 3111 | VirtualLocation | Section 4.2.6 | 3112 +-----------------+--------------------------+ 3114 Table 2 3116 8.4. Creation of "JSCalendar Enum Values" Registry 3118 The IANA will create the "JSCalendar Enum Values" registry to allow 3119 interoperable extension of semantics for properties with enumerable 3120 values. Each such property will have a subregistry of allowed 3121 values. The registration process for a new enum value or adding a 3122 new enumerable property is the same as for the JSCalendar Properties 3123 registry, as defined in Section 8.2. 3125 8.4.1. JMAP Enum Property Template 3127 This template is for adding a subregistry for a new enumerable 3128 property to the JMAP Enum registry. 3130 o Registry Name: This MUST be of the form "Enum Values for 3131 {property-name} (Context: {context})" where: 3133 {property-name} is the name(s) of the property or properties where 3134 these values may be used. This MUST be registered in the 3135 JSCalendar Properties registry. 3137 {context} is the list of allowed object types where the property 3138 or properties may appear, as registered in the JSCalendar 3139 Properties registry. This disambiguates where there may be two 3140 distinct properties with the same name in different contexts. 3142 o Change Controller: ("IETF" for properties defined in IETF-stream 3143 RFCs). 3145 o Initial Contents: The initial list of defined values for this 3146 enum, using the template defined in Section 8.4.2. 3148 8.4.2. JMAP Enum Value Template 3150 This template is for adding a new enum value to a subregistry in the 3151 JMAP Enum registry. 3153 o Enum Value: The verbatim value of the enum. 3155 o Reference or Description: A brief description or RFC number and 3156 section reference for the semantics of this value. 3158 8.4.3. Initial Contents for the JSCalendar Enum Registry 3160 For each subregistry created in this section, all RFC section 3161 references are for this document and the change controller is IETF. 3163 ------------------------------------------------------------ 3164 Enum Values for action (Context: Alert) 3166 +------------+--------------------------+ 3167 | Enum Value | Reference or Description | 3168 +------------+--------------------------+ 3169 | display | Section 4.5.2 | 3170 | | | 3171 | email | Section 4.5.2 | 3172 +------------+--------------------------+ 3174 Table 3 3176 ------------------------------------------------------------ 3178 Enum Values for display (Context: Link) 3180 +------------+--------------------------+ 3181 | Enum Value | Reference or Description | 3182 +------------+--------------------------+ 3183 | badge | Section 4.2.7 | 3184 | | | 3185 | graphic | Section 4.2.7 | 3186 | | | 3187 | fullsize | Section 4.2.7 | 3188 | | | 3189 | thumbnail | Section 4.2.7 | 3190 +------------+--------------------------+ 3192 Table 4 3194 ------------------------------------------------------------ 3196 Enum Values for freeBusyStatus (Context: JSEvent, JSTask) 3198 +------------+--------------------------+ 3199 | Enum Value | Reference or Description | 3200 +------------+--------------------------+ 3201 | free | Section 4.4.2 | 3202 | | | 3203 | busy | Section 4.4.2 | 3204 +------------+--------------------------+ 3206 Table 5 3208 ------------------------------------------------------------ 3210 Enum Values for kind (Context: Participant) 3211 +------------+--------------------------+ 3212 | Enum Value | Reference or Description | 3213 +------------+--------------------------+ 3214 | individual | Section 4.4.5 | 3215 | | | 3216 | group | Section 4.4.5 | 3217 | | | 3218 | resource | Section 4.4.5 | 3219 | | | 3220 | location | Section 4.4.5 | 3221 +------------+--------------------------+ 3223 Table 6 3225 ------------------------------------------------------------ 3227 Enum Values for participationStatus (Context: Participant) 3229 +--------------+--------------------------+ 3230 | Enum Value | Reference or Description | 3231 +--------------+--------------------------+ 3232 | needs-action | Section 4.4.5 | 3233 | | | 3234 | accepted | Section 4.4.5 | 3235 | | | 3236 | declined | Section 4.4.5 | 3237 | | | 3238 | tenative | Section 4.4.5 | 3239 | | | 3240 | delegated | Section 4.4.5 | 3241 +--------------+--------------------------+ 3243 Table 7 3245 ------------------------------------------------------------ 3247 Enum Values for privacy (Context: JSEvent, JSTask) 3248 +------------+--------------------------+ 3249 | Enum Value | Reference or Description | 3250 +------------+--------------------------+ 3251 | public | Section 4.4.3 | 3252 | | | 3253 | private | Section 4.4.3 | 3254 | | | 3255 | secret | Section 4.4.3 | 3256 +------------+--------------------------+ 3258 Table 8 3260 ------------------------------------------------------------ 3262 Enum Values for progress (Context: JSTask, Participant) 3264 +--------------+--------------------------+ 3265 | Enum Value | Reference or Description | 3266 +--------------+--------------------------+ 3267 | needs-action | Section 5.2.4 | 3268 | | | 3269 | in-process | Section 5.2.4 | 3270 | | | 3271 | completed | Section 5.2.4 | 3272 | | | 3273 | failed | Section 5.2.4 | 3274 | | | 3275 | cancelled | Section 5.2.4 | 3276 +--------------+--------------------------+ 3278 Table 9 3280 ------------------------------------------------------------ 3282 Enum Values for relation (Context: Relation) 3283 +------------+--------------------------+ 3284 | Enum Value | Reference or Description | 3285 +------------+--------------------------+ 3286 | first | Section 1.4.10 | 3287 | | | 3288 | next | Section 1.4.10 | 3289 | | | 3290 | child | Section 1.4.10 | 3291 | | | 3292 | parent | Section 1.4.10 | 3293 +------------+--------------------------+ 3295 Table 10 3297 ------------------------------------------------------------ 3299 Enum Values for relativeTo (Context: OffsetTrigger, Location) 3301 +------------+--------------------------+ 3302 | Enum Value | Reference or Description | 3303 +------------+--------------------------+ 3304 | start | Section 4.5.2 | 3305 | | | 3306 | end | Section 4.5.2 | 3307 +------------+--------------------------+ 3309 Table 11 3311 ------------------------------------------------------------ 3313 Enum Values for roles (Context: Participant) 3315 +---------------+--------------------------+ 3316 | Enum Value | Reference or Description | 3317 +---------------+--------------------------+ 3318 | owner | Section 4.4.5 | 3319 | | | 3320 | attendee | Section 4.4.5 | 3321 | | | 3322 | optional | Section 4.4.5 | 3323 | | | 3324 | informational | Section 4.4.5 | 3325 | | | 3326 | chair | Section 4.4.5 | 3327 +---------------+--------------------------+ 3329 Table 12 3331 ------------------------------------------------------------ 3333 Enum Values for scheduleAgent (Context: Participant) 3335 +------------+--------------------------+ 3336 | Enum Value | Reference or Description | 3337 +------------+--------------------------+ 3338 | server | Section 4.4.5 | 3339 | | | 3340 | client | Section 4.4.5 | 3341 | | | 3342 | none | Section 4.4.5 | 3343 +------------+--------------------------+ 3345 Table 13 3347 ------------------------------------------------------------ 3349 Enum Values for status (Context: JSEvent) 3351 +------------+--------------------------+ 3352 | Enum Value | Reference or Description | 3353 +------------+--------------------------+ 3354 | confirmed | Section 5.1.3 | 3355 | | | 3356 | cancelled | Section 5.1.3 | 3357 | | | 3358 | tentative | Section 5.1.3 | 3359 +------------+--------------------------+ 3361 Table 14 3363 9. Acknowledgments 3365 The authors would like to thank the members of CalConnect for their 3366 valuable contributions. This specification originated from the work 3367 of the API technical committee of CalConnect, the Calendaring and 3368 Scheduling Consortium. 3370 10. References 3372 10.1. Normative References 3374 [CLDR] "Unicode Common Locale Data Repository", 3375 . 3377 [COLORS] "CSS Color Module", . 3379 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3380 Requirement Levels", BCP 14, RFC 2119, 3381 DOI 10.17487/RFC2119, March 1997, 3382 . 3384 [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource 3385 Locators", RFC 2392, DOI 10.17487/RFC2392, August 1998, 3386 . 3388 [RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397, 3389 DOI 10.17487/RFC2397, August 1998, 3390 . 3392 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 3393 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 3394 . 3396 [RFC4589] Schulzrinne, H. and H. Tschofenig, "Location Types 3397 Registry", RFC 4589, DOI 10.17487/RFC4589, July 2006, 3398 . 3400 [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data 3401 Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006, 3402 . 3404 [RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and 3405 Scheduling Core Object Specification (iCalendar)", 3406 RFC 5545, DOI 10.17487/RFC5545, September 2009, 3407 . 3409 [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying 3410 Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646, 3411 September 2009, . 3413 [RFC5870] Mayrhofer, A. and C. Spanring, "A Uniform Resource 3414 Identifier for Geographic Locations ('geo' URI)", 3415 RFC 5870, DOI 10.17487/RFC5870, June 2010, 3416 . 3418 [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type 3419 Specifications and Registration Procedures", BCP 13, 3420 RFC 6838, DOI 10.17487/RFC6838, January 2013, 3421 . 3423 [RFC6901] Bryan, P., Ed., Zyp, K., and M. Nottingham, Ed., 3424 "JavaScript Object Notation (JSON) Pointer", RFC 6901, 3425 DOI 10.17487/RFC6901, April 2013, 3426 . 3428 [RFC7493] Bray, T., Ed., "The I-JSON Message Format", RFC 7493, 3429 DOI 10.17487/RFC7493, March 2015, 3430 . 3432 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 3433 Writing an IANA Considerations Section in RFCs", BCP 26, 3434 RFC 8126, DOI 10.17487/RFC8126, June 2017, 3435 . 3437 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 3438 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 3439 May 2017, . 3441 [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data 3442 Interchange Format", STD 90, RFC 8259, 3443 DOI 10.17487/RFC8259, December 2017, 3444 . 3446 [RFC8288] Nottingham, M., "Web Linking", RFC 8288, 3447 DOI 10.17487/RFC8288, October 2017, 3448 . 3450 [TZDB] "IANA Time Zone Database", 3451 . 3453 10.2. Informative References 3455 [LINKRELS] 3456 "IANA Link Relation Types", 3457 . 3460 [MIME] "IANA Media Types", . 3463 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 3464 Resource Identifier (URI): Generic Syntax", STD 66, 3465 RFC 3986, DOI 10.17487/RFC3986, January 2005, 3466 . 3468 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 3469 Unique IDentifier (UUID) URN Namespace", RFC 4122, 3470 DOI 10.17487/RFC4122, July 2005, 3471 . 3473 [RFC4791] Daboo, C., Desruisseaux, B., and L. Dusseault, 3474 "Calendaring Extensions to WebDAV (CalDAV)", RFC 4791, 3475 DOI 10.17487/RFC4791, March 2007, 3476 . 3478 [RFC5546] Daboo, C., Ed., "iCalendar Transport-Independent 3479 Interoperability Protocol (iTIP)", RFC 5546, 3480 DOI 10.17487/RFC5546, December 2009, 3481 . 3483 [RFC6047] Melnikov, A., Ed., "iCalendar Message-Based 3484 Interoperability Protocol (iMIP)", RFC 6047, 3485 DOI 10.17487/RFC6047, December 2010, 3486 . 3488 [RFC7265] Kewisch, P., Daboo, C., and M. Douglass, "jCal: The JSON 3489 Format for iCalendar", RFC 7265, DOI 10.17487/RFC7265, May 3490 2014, . 3492 [RFC7529] Daboo, C. and G. Yakushev, "Non-Gregorian Recurrence Rules 3493 in the Internet Calendaring and Scheduling Core Object 3494 Specification (iCalendar)", RFC 7529, 3495 DOI 10.17487/RFC7529, May 2015, 3496 . 3498 [RFC7808] Douglass, M. and C. Daboo, "Time Zone Data Distribution 3499 Service", RFC 7808, DOI 10.17487/RFC7808, March 2016, 3500 . 3502 [RFC7986] Daboo, C., "New Properties for iCalendar", RFC 7986, 3503 DOI 10.17487/RFC7986, October 2016, 3504 . 3506 Authors' Addresses 3508 Neil Jenkins 3509 Fastmail 3510 PO Box 234 3511 Collins St West 3512 Melbourne VIC 8007 3513 Australia 3515 Email: neilj@fastmailteam.com 3516 URI: https://www.fastmail.com 3517 Robert Stepanek 3518 Fastmail 3519 PO Box 234 3520 Collins St West 3521 Melbourne VIC 8007 3522 Australia 3524 Email: rsto@fastmailteam.com 3525 URI: https://www.fastmail.com