idnits 2.17.1 draft-ietf-calext-jscalendar-07.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 (September 20, 2018) is 2045 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) -- Looks like a reference, but probably isn't: '1' on line 2420 -- Looks like a reference, but probably isn't: '2' on line 2423 -- Looks like a reference, but probably isn't: '3' on line 2425 Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 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: March 24, 2019 September 20, 2018 7 JSCalendar: A JSON representation of calendar data 8 draft-ietf-calext-jscalendar-07 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 to the widely deployed iCalendar data format and to be unambiguous, 16 extendable and simple to process. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on March 24, 2019. 35 Copyright Notice 37 Copyright (c) 2018 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 53 1.1. Relation to the iCalendar format . . . . . . . . . . . . 4 54 1.2. Notational Conventions . . . . . . . . . . . . . . . . . 5 55 2. JSCalendar objects . . . . . . . . . . . . . . . . . . . . . 5 56 2.1. JSEvent . . . . . . . . . . . . . . . . . . . . . . . . . 5 57 2.2. JSTask . . . . . . . . . . . . . . . . . . . . . . . . . 5 58 2.3. JSGroup . . . . . . . . . . . . . . . . . . . . . . . . . 6 59 3. Structure of JSCalendar objects . . . . . . . . . . . . . . . 6 60 3.1. Type signatures . . . . . . . . . . . . . . . . . . . . . 6 61 3.2. Data Types . . . . . . . . . . . . . . . . . . . . . . . 7 62 3.2.1. UTCDate . . . . . . . . . . . . . . . . . . . . . . . 7 63 3.2.2. LocalDate . . . . . . . . . . . . . . . . . . . . . . 7 64 3.2.3. Duration . . . . . . . . . . . . . . . . . . . . . . 7 65 3.2.4. PatchObject . . . . . . . . . . . . . . . . . . . . . 8 66 3.2.5. Identifiers . . . . . . . . . . . . . . . . . . . . . 8 67 3.2.6. Normalization and equivalence . . . . . . . . . . . . 8 68 3.3. Custom property extensions and values . . . . . . . . . . 9 69 4. Common JSCalendar properties . . . . . . . . . . . . . . . . 9 70 4.1. Metadata properties . . . . . . . . . . . . . . . . . . . 9 71 4.1.1. @type . . . . . . . . . . . . . . . . . . . . . . . . 9 72 4.1.2. uid . . . . . . . . . . . . . . . . . . . . . . . . . 10 73 4.1.3. relatedTo . . . . . . . . . . . . . . . . . . . . . . 10 74 4.1.4. prodId . . . . . . . . . . . . . . . . . . . . . . . 11 75 4.1.5. created . . . . . . . . . . . . . . . . . . . . . . . 11 76 4.1.6. updated . . . . . . . . . . . . . . . . . . . . . . . 11 77 4.1.7. sequence . . . . . . . . . . . . . . . . . . . . . . 12 78 4.1.8. method . . . . . . . . . . . . . . . . . . . . . . . 12 79 4.2. What and where properties . . . . . . . . . . . . . . . . 12 80 4.2.1. title . . . . . . . . . . . . . . . . . . . . . . . . 12 81 4.2.2. description . . . . . . . . . . . . . . . . . . . . . 12 82 4.2.3. descriptionContentType . . . . . . . . . . . . . . . 12 83 4.2.4. locations . . . . . . . . . . . . . . . . . . . . . . 12 84 4.2.5. virtualLocations . . . . . . . . . . . . . . . . . . 13 85 4.2.6. links . . . . . . . . . . . . . . . . . . . . . . . . 14 86 4.2.7. locale . . . . . . . . . . . . . . . . . . . . . . . 15 87 4.2.8. keywords . . . . . . . . . . . . . . . . . . . . . . 15 88 4.2.9. categories . . . . . . . . . . . . . . . . . . . . . 15 89 4.2.10. color . . . . . . . . . . . . . . . . . . . . . . . . 16 90 4.3. Recurrence properties . . . . . . . . . . . . . . . . . . 16 91 4.3.1. recurrenceRule . . . . . . . . . . . . . . . . . . . 16 92 4.3.2. recurrenceOverrides . . . . . . . . . . . . . . . . . 21 93 4.3.3. excluded . . . . . . . . . . . . . . . . . . . . . . 22 94 4.4. Sharing and scheduling properties . . . . . . . . . . . . 22 95 4.4.1. priority . . . . . . . . . . . . . . . . . . . . . . 22 96 4.4.2. freeBusyStatus . . . . . . . . . . . . . . . . . . . 22 97 4.4.3. privacy . . . . . . . . . . . . . . . . . . . . . . . 23 98 4.4.4. replyTo . . . . . . . . . . . . . . . . . . . . . . . 24 99 4.4.5. participants . . . . . . . . . . . . . . . . . . . . 25 100 4.5. Alerts properties . . . . . . . . . . . . . . . . . . . . 27 101 4.5.1. useDefaultAlerts . . . . . . . . . . . . . . . . . . 27 102 4.5.2. alerts . . . . . . . . . . . . . . . . . . . . . . . 28 103 4.6. Multilingual properties . . . . . . . . . . . . . . . . . 29 104 4.6.1. localizations . . . . . . . . . . . . . . . . . . . . 29 105 5. Type-specific JSCalendar properties . . . . . . . . . . . . . 30 106 5.1. JSEvent properties . . . . . . . . . . . . . . . . . . . 30 107 5.1.1. start . . . . . . . . . . . . . . . . . . . . . . . . 30 108 5.1.2. timeZone . . . . . . . . . . . . . . . . . . . . . . 30 109 5.1.3. duration . . . . . . . . . . . . . . . . . . . . . . 30 110 5.1.4. isAllDay . . . . . . . . . . . . . . . . . . . . . . 31 111 5.1.5. status . . . . . . . . . . . . . . . . . . . . . . . 31 112 5.2. JSTask properties . . . . . . . . . . . . . . . . . . . . 31 113 5.2.1. due . . . . . . . . . . . . . . . . . . . . . . . . . 31 114 5.2.2. start . . . . . . . . . . . . . . . . . . . . . . . . 32 115 5.2.3. timeZone . . . . . . . . . . . . . . . . . . . . . . 32 116 5.2.4. estimatedDuration . . . . . . . . . . . . . . . . . . 32 117 5.2.5. statusUpdatedAt . . . . . . . . . . . . . . . . . . . 32 118 5.2.6. isAllDay . . . . . . . . . . . . . . . . . . . . . . 32 119 5.2.7. progress . . . . . . . . . . . . . . . . . . . . . . 33 120 5.2.8. status . . . . . . . . . . . . . . . . . . . . . . . 33 121 5.3. JSGroup properties . . . . . . . . . . . . . . . . . . . 34 122 5.3.1. entries . . . . . . . . . . . . . . . . . . . . . . . 34 123 5.3.2. source . . . . . . . . . . . . . . . . . . . . . . . 35 124 6. Conversion from and to iCalendar . . . . . . . . . . . . . . 35 125 6.1. JSEvent . . . . . . . . . . . . . . . . . . . . . . . . . 35 126 6.2. JSTask . . . . . . . . . . . . . . . . . . . . . . . . . 36 127 6.3. JSGroup . . . . . . . . . . . . . . . . . . . . . . . . . 38 128 6.4. Common properties . . . . . . . . . . . . . . . . . . . . 38 129 6.5. Locations and participants . . . . . . . . . . . . . . . 40 130 6.6. Unknown properties . . . . . . . . . . . . . . . . . . . 43 131 7. JSCalendar object examples . . . . . . . . . . . . . . . . . 43 132 7.1. Simple event . . . . . . . . . . . . . . . . . . . . . . 43 133 7.2. Simple task . . . . . . . . . . . . . . . . . . . . . . . 44 134 7.3. Simple group . . . . . . . . . . . . . . . . . . . . . . 44 135 7.4. All-day event . . . . . . . . . . . . . . . . . . . . . . 44 136 7.5. Task with a due date . . . . . . . . . . . . . . . . . . 45 137 7.6. Event with end time-zone . . . . . . . . . . . . . . . . 45 138 7.7. Floating-time event (with recurrence) . . . . . . . . . . 46 139 7.8. Event with multiple locations and localization . . . . . 46 140 7.9. Recurring event with overrides . . . . . . . . . . . . . 47 141 7.10. Recurring event with participants . . . . . . . . . . . . 48 142 8. Security Considerations . . . . . . . . . . . . . . . . . . . 50 143 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50 144 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 50 145 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 50 146 11.1. Normative References . . . . . . . . . . . . . . . . . . 50 147 11.2. Informative References . . . . . . . . . . . . . . . . . 52 148 11.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 53 149 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 53 151 1. Introduction 153 This document defines a data model for calendar event and task 154 objects, or groups of such objects, in electronic calendar 155 applications and systems. It aims to be unambiguous, extendable and 156 simple to process. 158 The key design considerations for this data model are as follows: 160 o The attributes of the calendar entry represented must be described 161 as a simple key-value pair, reducing complexity of its 162 representation. 164 o The data model should avoid all ambiguities and make it difficult 165 to make mistakes during implementation. 167 o Most of the initial set of attributes should be taken from the 168 iCalendar data format ([RFC5545], also see Section 1.1), but the 169 specification should add new attributes or value types, or not 170 support existing ones, where appropriate. Conversion between the 171 data formats need not fully preserve semantic meaning. 173 o Extensions, such as new properties and components, MUST NOT lead 174 to requiring an update to this document. 176 The representation of this data model is defined in the I-JSON format 177 [RFC7493], which is a strict subset of the JavaScript Object Notation 178 (JSON) Data Interchange Format [RFC8259]. Using JSON mostly is a 179 pragmatic choice: its widespread use should help to speed up 180 JSCalendar adoption and a wide range of production-ready JSON 181 implementations allows to decrease interoperability issues. 183 1.1. Relation to the iCalendar format 185 The iCalendar data format [RFC5545], a widely deployed interchange 186 format for calendaring and scheduling data, has served calendaring 187 vendors for a long while, but contains some ambiguities and pitfalls 188 that can not be overcome without backward-incompatible changes. 190 For example, iCalendar defines various formats for local times, UTC 191 time and dates, which confuses new users. Other sources for errors 192 are the requirement for custom time-zone definitions within a single 193 calendar component, as well as the iCalendar format itself; the 194 latter causing interoperability issues due to misuse of CR LF 195 terminated strings, line continuations and subtle differences between 196 iCalendar parsers. Lastly, up until recently the iCalendar format 197 did not allow to express the difference between two calendar 198 components, which results in verbose exchanges during scheduling. 200 Some of these issues were addressed by the jCal [RFC7265] format, 201 which is a direct mapping between iCalendar and JSON. However, it 202 did not attempt to extend or update iCalendar semantics. 204 1.2. Notational Conventions 206 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 207 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 208 document are to be interpreted as described in [RFC2119]. 210 The underlying format used for this specification is JSON. 211 Consequently, the terms "object" and "array" as well as the four 212 primitive types (strings, numbers, booleans, and null) are to be 213 interpreted as described in Section 1 of[RFC8259]. 215 Some examples in this document contain "partial" JSON documents used 216 for illustrative purposes. In these examples, three periods "..." 217 are used to indicate a portion of the document that has been removed 218 for compactness. 220 2. JSCalendar objects 222 This section describes the calendar object types specified by 223 JSCalendar. 225 2.1. JSEvent 227 MIME type: "application/calendar+json;type=jsevent" 229 A JSEvent represents a scheduled amount of time on a calendar, 230 typically a meeting, appointment, reminder or anniversary. Multiple 231 participants may partake in the event at multiple locations. 233 The @type (Section 4.1.1) property value MUST be "jsevent". 235 2.2. JSTask 237 MIME type: "application/calendar+json;type=jstask" 239 A JSTask represents an action-item, assignment, to-do or work item . 241 The @type (Section 4.1.1) property value MUST be "jstask". 243 A JSTask may start and be due at certain points in time, may take 244 some estimated time to complete and may recur; none of which is 245 required. This notably differs from JSEvent (Section 2.1) which is 246 required to start at a certain point in time and typically takes some 247 non-zero duration to complete. 249 2.3. JSGroup 251 MIME type: "application/calendar+json;type=jsgroup" 253 A JSGroup is a collection of JSEvent (Section 2.1) and JSTask 254 (Section 2.2) objects. Typically, objects are grouped by topic (e.g. 255 by keywords) or calendar membership. 257 The @type (Section 4.1.1) property value MUST be "jsgroup". 259 3. Structure of JSCalendar objects 261 A JSCalendar object is a JSON object, which MUST be valid I-JSON (a 262 stricter subset of JSON), as specified in [RFC8259]. Property names 263 and values are case-sensitive. 265 The object has a collection of properties, as specified in the 266 following sections. Unless otherwise specified, all properties are 267 mandatory. Optional properties may have a default value, if 268 explicitly specified in the property definition. 270 3.1. Type signatures 272 Types signatures are given for all JSON objects in this document. 273 The following conventions are used: 275 o "Boolean|String": The value is either a JSON "Boolean" value, or a 276 JSON "String" value. 278 o "Foo": Any name that is not a native JSON type means an object for 279 which the properties (and their types) are defined elsewhere 280 within this document. 282 o "Foo[]": An array of objects of type "Foo". 284 o "String[Foo]": A JSON "Object" being used as a map (associative 285 array), where all the values are of type "Foo". 287 3.2. Data Types 289 In addition to the standard JSON data types, the following data types 290 are used in this specification: 292 3.2.1. UTCDate 294 This is a string in [RFC3339] "date-time" format, with the further 295 restrictions that any letters MUST be in upper-case, the time 296 component MUST be included and the time MUST be in UTC. Fractional 297 second values MUST NOT be included unless non-zero and MUST NOT have 298 trailing zeros, to ensure there is only a single representation for 299 each date-time. 301 For example "2010-10-10T10:10:10.003Z" is OK, but 302 "2010-10-10T10:10:10.000Z" is invalid and MUST be encoded as 303 "2010-10-10T10:10:10Z". 305 In common notation, it should be of the form "YYYY-MM-DDTHH:MM:SSZ". 307 3.2.2. LocalDate 309 This is a date-time string _with no time-zone/offset information_. 310 It is otherwise in the same format as UTCDate: "YYYY-MM-DDTHH:MM:SS". 311 The time-zone to associate the LocalDate with comes from an 312 associated property, or if no time-zone is associated it defines 313 _floating time_. Floating date-times are not tied to any specific 314 time-zone. Instead, they occur in every timezone at the same _wall- 315 clock_ time (as opposed to the same instant point in time). 317 3.2.3. Duration 319 A duration is represented by a subset of ISO8601 duration format, as 320 specified by the following ABNF: 322 dur-secfrac = "." 1*DIGIT 323 dur-second = 1*DIGIT [dur-secfrac] "S" 324 dur-minute = 1*DIGIT "M" [dur-second] 325 dur-hour = 1*DIGIT "H" [dur-minute] 326 dur-time = "T" (dur-hour / dur-minute / dur-second) 327 dur-day = 1*DIGIT "D" 328 dur-week = 1*DIGIT "W" 330 duration = "P" (dur-day [dur-time] / dur-time / dur-week) 332 In addition, the duration MUST NOT include fractional second values 333 unless the fraction is non-zero. 335 3.2.4. PatchObject 337 A *PatchObject* is of type "String[*|null]", and represents an 338 unordered set of patches on a JSON object. The keys are a path in a 339 subset of [RFC6901] JSON pointer format, with an implicit leading "/" 340 (i.e. prefix each key with "/" before applying the JSON pointer 341 evaluation algorithm). 343 A patch within a PatchObject is only valid, if all of the following 344 conditions apply: 346 1. The pointer MUST NOT reference inside an array (i.e. it MUST NOT 347 insert/delete from an array; the array MUST be replaced in its 348 entirety instead). 350 2. When evaluating a path, all parts prior to the last (i.e. the 351 value after the final slash) MUST exist. 353 3. There MUST NOT be two patches in the PatchObject where the 354 pointer of one is the prefix of the pointer of the other, e.g. 355 "alerts/foo/offset" and "alerts". 357 The value associated with each pointer is either: 359 o "null": Remove the property from the patched object. If not 360 present in the parent, this a no-op. 362 o Anything else: The value to replace the inherited property on the 363 patch object with (if present) or add to the property (if not 364 present). 366 Implementations MUST reject a PatchObject if any of its patches are 367 invalid. 369 3.2.5. Identifiers 371 If not noted otherwise, properties and object keys that define 372 identifiers MUST be string values, MUST be at least 1 character in 373 length and maximum 256 octets in size, and MUST only contain 374 characters from the "URL and Filename safe" Base 64 Alphabet, as 375 defined in section 5 of [RFC4648]. This is the ASCII alphanumeric 376 characters (A-Za-z0-9), hyphen (-), and underscore (_). 378 3.2.6. Normalization and equivalence 380 JSCalendar aims to provide unambiguous definitions for value types 381 and properties, but does not define a general normalization or 382 equivalence method for JSCalendar objects and types. This is because 383 the notion of equivalence might range from byte-level equivalence to 384 semantic equivalence, depending on the respective use case (for 385 example, the CalDAV protocol [RFC4791] requires octet equivalence of 386 the encoded calendar object to determine ETag equivalence). 388 Normalization of JSCalendar objects is hindered because of the 389 following reasons: 391 o Custom JSCalendar properties may contain arbitrary JSON values, 392 including arrays. However, equivalence of arrays might or might 393 not depend on the order of elements, depending on the respective 394 property definition. 396 o Several JSCalendar property values are defined as URIs and MIME 397 types, but normalization of these types is inherently protocol and 398 scheme-specific, depending on the use-case of the equivalence 399 definition (see section 6 of [RFC3986]). 401 Considering this, the definition of equivalence and normalization is 402 left to client and server implementations and to be negotiated by a 403 calendar exchange protocol or defined by another RFC. 405 3.3. Custom property extensions and values 407 Vendors MAY add additional properties to the calendar object to 408 support their custom features. The names of these properties MUST be 409 prefixed with a domain name controlled by the vendor to avoid 410 conflict, e.g. "example.com/customprop". 412 Some JSCalendar properties allow vendor-specific value extensions. 413 If so, vendor specific values MUST be prefixed with a domain name 414 controlled by the vendor, e.g. "example.com/customrel", unless 415 otherwise noted. 417 4. Common JSCalendar properties 419 This section describes the properties that are common to the various 420 JSCalendar object types. Specific JSCalendar object types may only 421 support a subset of these properties. The object type definitions in 422 Section 5 describe the set of supported properties per type. 424 4.1. Metadata properties 426 4.1.1. @type 428 Type: "String" 429 Specifies the type which this object represents. This MUST be one of 430 the following values, registered in a future RFC, or a vendor- 431 specific value: 433 o "jsevent": a JSCalendar event (Section 2.1). 435 o "jstask": a JSCalendar task (Section 2.2). 437 o "jsgroup": a JSCalendar group (Section 2.3). 439 A valid JSCalendar object MUST include this property. 441 4.1.2. uid 443 Type: "String" 445 A globally unique identifier, used to associate the object as the 446 same across different systems, calendars and views. The value of 447 this property MUST be unique across _all_ JSCalendar objects, even if 448 they are of different type. [RFC4122] describes a range of 449 established algorithms to generate universally unique identifiers 450 (UUID), and the random or pseudo-random version is recommended to 451 use. 453 For compatibility with [RFC5545] UIDs, implementations MUST be able 454 to receive and persist values of at least 255 octets for this 455 property, but they MUST NOT truncate values in the middle of a UTF-8 456 multi-octet sequence. 458 A valid JSCalendar object MUST include this property. 460 4.1.3. relatedTo 462 Type: "String[Relation]" (optional) 464 Relates the object to other JSCalendar objects. This is represented 465 as a map of the uids of the related objects to information about the 466 relation. 468 A *Relation* object has the following properties: 470 o *relation*: "String[]" Describes how the linked object is related 471 to this object. 473 Strings in the array MUST be one of the following values, defined 474 in a future specification or a vendor-specific value. There MUST 475 NOT be duplicate strings in the array. 477 * "first": The linked object is the first in the series this 478 object is part of. 480 * "next": The linked object is the next in the series this object 481 is part of. 483 * "child": The linked object is a subpart of this object. 485 * "parent": This object is part of the overall linked object. 487 If an object is split to make a "this and future" change to a 488 recurrence, the original object MUST be truncated to end at the 489 previous occurrence before this split, and a new object created to 490 represent all the objects after the split. A "relation=["next"]" 491 relatedTo property MUST be set on the original object with the uid of 492 the new object. A "relation=["first"]" relatedTo property with the 493 UID of the first object in the series MUST be set on the new object. 494 Clients can then follow these UIDs to get the complete set of objects 495 if the user wishes to modify them all at once. 497 4.1.4. prodId 499 Type: "String" (optional) 501 The identifier for the product that created the JSCalendar object. 503 The vendor of the implementation SHOULD ensure that this is a 504 globally unique identifier, using some technique such as an FPI 505 value, as defined in [ISO.9070.1991]. It MUST only use characters of 506 an iCalendar TEXT data value (see section 3.3.11 in [RFC5545]). 508 This property SHOULD NOT be used to alter the interpretation of an 509 JSCalendar object beyond the semantics specified in this document. 510 For example, it is not to be used to further the understanding of 511 non-standard properties. 513 4.1.5. created 515 Type: "UTCDate" (optional) 517 The date and time this object was initially created. 519 4.1.6. updated 521 Type: "UTCDate" 523 The date and time the data in this object was last modified. 525 4.1.7. sequence 527 Type: "Number" (optional, default:"0") 529 Initially zero, this MUST be a non-negative integer that is 530 monotonically incremented each time a change is made to the object. 532 4.1.8. method 534 Type: "String" (optional) 536 The iTIP ([RFC5546]) method, in lower-case. Used for scheduling. 538 4.2. What and where properties 540 4.2.1. title 542 Type: "String" (optional, default:"") 544 A short summary of the object. 546 4.2.2. description 548 Type: "String" (optional, default:"") 550 A longer-form text description of the object. The content is 551 formatted according to the *descriptionContentType* property. 553 4.2.3. descriptionContentType 555 Type: "String" (optional, default:"text/plain") 557 Describes the media type ([RFC6838]) of the contents of the 558 "description" property. Media types MUST be sub-types of type 559 "text", and SHOULD be "text/plain" or "text/html" ([MIME]). They MAY 560 define parameters and the "charset" parameter MUST be "utf-8", if 561 specified. Descriptions of type "text/html" MAY contain "cid" URLs 562 ([RFC2392]) to reference links in the calendar object by use of the 563 *cid* property of the *Link* object. 565 4.2.4. locations 567 Type: "String[Location]" (optional) 569 A map of location ids to Location objects, representing locations 570 associated with the object. A location id MUST be unique to this 571 object; a UUID is a practical choice. 573 A *Location* object has the following properties. It must define at 574 least one other property than *rel*. 576 o *name*: "String" (optional, default:"") The human-readable name of 577 the location. 579 o *description*: "String" (optional) Human-readable, plain-text 580 instructions for accessing this location. This may be an address, 581 set of directions, door access code, etc. 583 o *rel*: "String" (optional) The relation type of this location to 584 the JSCalendar object. 586 This MUST be either one of the following values, registered in a 587 future RFC, or a vendor-specific value. Any value the client or 588 server doesn't understand should be treated the same as if this 589 property is omitted. 591 * "start": The JSCalendar object starts at this location. 593 * "end": The JSCalendar object ends at this location. 595 o *timeZone*: "String" (optional) A time-zone for this location. 597 If omitted, the *timeZone* from the JSCalendar object MUST be 598 presumed when a time-zone is needed in relation to this location. 600 o *coordinates*: "String" (optional) An [RFC5870] "geo:" URI for the 601 location. 603 o *linkIds*: "String[]" (optional) A list of ids for links to 604 alternate representations of this location. 606 For example, an alternative representation could be in vCard 607 format. 609 4.2.5. virtualLocations 611 Type: "String[VirtualLocation]" (optional) 613 A map of ids to VirtualLocation objects, representing virtual 614 locations, such as video conferences or chat rooms, associated with 615 the object. A virtual location id MUST be unique to this object; a 616 UUID is a practical choice. 618 A *VirtualLocation* object has the following properties. 620 o *name*: "String" (optional, default:"") The human-readable name of 621 the virtual location. 623 o *description*: "String" (optional) Human-readable plain-text 624 instructions for accessing this location. This may be an address, 625 set of directions, door access code, etc. 627 o *uri*: "String" A URI that represents how to connect to this 628 virtual location. 630 This may be a telephone number (represented as 631 "tel:+1-555-555-555") for a teleconference, a web address for 632 online chat, or any custom URI. 634 4.2.6. links 636 Type: "String[Link]" (optional) 638 A map of link ids to Link objects, representing external resources 639 associated with the object. A link id MUST be unique to this 640 calendar object; a UUID is a practical choice. 642 A *Link* object has the following properties: 644 o *href*: "String" A URI from which the resource may be fetched. 646 This MAY be a "data:" URL, but it is recommended that the file be 647 hosted on a server to avoid embedding arbitrarily large data in 648 JSCalendar object instances. 650 o *cid* "String" (optional) This MUST be a valid "content-id" value 651 according to the definition of section 2 in [RFC2392]. The 652 identifier MUST be unique within this JSCalendar object but has no 653 meaning beyond that. Specifically, it MAY be different from the 654 link identifier in the enclosing *links* property. 656 o *type*: "String" (optional) The content-type [RFC6838] of the 657 resource, if known. 659 o *size*: "Number" (optional) The size, in bytes, of the resource 660 when fully decoded (i.e. the number of bytes in the file the user 661 would download), if known. 663 o *rel*: "String" (optional) Identifies the relation of the linked 664 resource to the object. If set, the value MUST be a registered 665 relation type (see [RFC8288] and IANA Link Relations [1]). 667 Links with a rel of "enclosure" SHOULD be considered by the client 668 as attachments for download. 670 Links with a rel of "describedby" SHOULD be considered by the 671 client to be an alternate representation of the description. 673 Links with a rel of "icon" SHOULD be considered by the client to 674 be an image that it MAY use when presenting the calendar data to a 675 user. The *display* property MAY be set to indicate the purpose 676 of this image. 678 o *display*: "String" (optional) Describes the intended purpose of a 679 link to an image. If set, the *rel* property MUST be set to 680 "icon". The value MUST be either one of the following values, 681 registered in a future RFC, or a vendor-specific value: 683 * "badge": an image inline with the title of the object 685 * "graphic": a full image replacement for the object itself 687 * "fullsize": an image that is used to enhance the object 689 * "thumbnail": a smaller variant of "fullsize " to be used when 690 space for the image is constrained 692 o *title*: "String" (optional) A human-readable plain-text 693 description of the resource. 695 4.2.7. locale 697 Type: "String" (optional) 699 The [RFC5646] language tag that best describes the locale used for 700 the calendar object, if known. 702 4.2.8. keywords 704 Type: "String[Boolean]" (optional) 706 A set of keywords or tags that relate to the object. The set is 707 represented as a map, with the keys being the keywords. The value 708 for each key in the map MUST be "true". 710 4.2.9. categories 712 Type: "String[Boolean]" (optional) 713 A set of categories that relate to the calendar object. The set is 714 represented as a map, with the keys being the categories specified as 715 URIs. The value for each key in the map MUST be "true". 717 In contrast to *keywords*, categories typically are structured. For 718 example, a vendor owning the domain "example.com" might define the 719 categories "http://example.com/categories/sports/american-football"" 720 and "http://example.com/categories/music/r-b". 722 4.2.10. color 724 Type: "String" (optional) 726 Specifies a color clients MAY use when displaying this calendar 727 object. The value is a case-insensitive color name taken from the 728 CSS3 set of names, defined in Section 4.3 of W3C.REC- 729 css3-color-20110607 [2] or a CSS3 RGB color hex value. 731 4.3. Recurrence properties 733 4.3.1. recurrenceRule 735 Type: "Recurrence" 737 Defines a recurrence rule (repeating pattern) for recurring calendar 738 objects. 740 A *Recurrence* object is a JSON object mapping of a RECUR value type 741 in iCalendar, see [RFC5545] and[RFC7529]. A JSEvent recurs by 742 applying the recurrence rule (and *recurrenceOverrides*) to the 743 *start* date/time. A JSTask recurs by applying the recurrence rule 744 (and *recurrenceOverrides*) to its *start* date/time, if defined. If 745 the task does not define a start date-time, it recurs by its *due* 746 date-time. If it neither defines a start or due date-time, it MUST 747 NOT define a *recurrenceRule*. 749 A Recurrence object has the following properties: 751 o *frequency*: "String" This MUST be one of the following values: 753 * "yearly" 755 * "monthly" 757 * "weekly" 759 * "daily" 760 * "hourly" 762 * "minutely" 764 * "secondly" 766 To convert from iCalendar, simply lower-case the FREQ part. 768 o *interval*: "Number"(optional, default:"1") The INTERVAL part from 769 iCal. If included, it MUST be an integer "x >= 1". 771 o *rscale*: "String"(optional, default:""gregorian"") The RSCALE 772 part from iCalendar RSCALE [RFC7529], converted to lower-case. 774 o *skip*: "String"(optional, default:""omit"") The SKIP part from 775 iCalendar RSCALE [RFC7529], converted to lower-case. 777 o *firstDayOfWeek*: "String"(optional, default:""mo"") The WKST part 778 from iCalendar, represented as a lower-case abbreviated two-letter 779 English day of the week. If included, it MUST be one of the 780 following values: ""mo"|"tu"|"we"|"th"|"fr"|"sa"|"su"". 782 o *byDay*: "NDay[]" (optional) An *NDay* object has the following 783 properties: 785 * *day*: "String" The day-of-the-week part of the BYDAY value in 786 iCalendar, lower-cased. MUST be one of the following values: 787 ""mo"|"tu"|"we"|"th"|"fr"|"sa"|"su"". 789 * *nthOfPeriod*: "Number" (optional) The ordinal part of the 790 BYDAY value in iCalendar (e.g. ""+1"" or ""-3""). If present, 791 rather than representing every occurrence of the weekday 792 defined in the *day* property of this *NDay*, it represents 793 only a specific instance within the recurrence period. The 794 value can be positive or negative, but MUST NOT be zero. A 795 negative integer means nth-last of period. 797 o *byMonthDay*: "Number[]" (optional) The BYMONTHDAY part from 798 iCalendar. The array MUST have at least one entry if included. 800 o *byMonth*: "String[]" (optional) The BYMONTH part from iCalendar. 801 Each entry is a string representation of a number, starting from 802 "1" for the first month in the calendar (e.g. ""1" " means 803 ""January"" with Gregorian calendar), with an optional ""L"" 804 suffix (see [RFC7529]) for leap months (this MUST be upper-case, 805 e.g. ""3L""). The array MUST have at least one entry if included. 807 o *byYearDay*: "Number[]"(optional) The BYYEARDAY part from 808 iCalendar. The array MUST have at least one entry if included. 810 o *byWeekNo*: "Number[]"(optional) The BYWEEKNO part from iCalendar. 811 The array MUST have at least one entry if included. 813 o *byHour*: "Number[]"(optional) The BYHOUR part from iCalendar. 814 The array MUST have at least one entry if included. 816 o *byMinute*: "Number[]"(optional) The BYMINUTE part from iCalendar. 817 The array MUST have at least one entry if included. 819 o *bySecond*: "Number[]"(optional) The BYSECOND part from iCalendar. 820 The array MUST have at least one entry if included. 822 o *bySetPosition*: "Number[]"(optional) The BYSETPOS part from 823 iCalendar. The array MUST have at least one entry if included. 825 o *count*: "Number"(optional) The COUNT part from iCalendar. This 826 MUST NOT be included if an *until* property is specified. 828 o *until*: "LocalDate"(optional) The UNTIL part from iCalendar. 829 This MUST NOT be included if a *count* property is specified. 830 Note, as in iCalendar, this date is presumed to be in the time- 831 zone specified in *timeZone*. It is not a UTC time. 833 A recurrence rule specifies a set of set of date-times for recurring 834 calendar objects. A recurrence rule has the following semantics: 836 1. A set of candidates is generated. This is every second within a 837 period defined by the frequency property: 839 * *yearly*: every second from midnight on the 1st January 840 (inclusive) to midnight the following 1st January (exclusive) 842 * *monthly*: every second from midnight on the 1st of a month 843 (inclusive) to midnight on the 1st of the following month 844 (exclusive) 846 * *weekly*: every second from midnight (inclusive) on the first 847 day of the week (as defined by the firstDayOfWeek property, or 848 Monday if omitted), to midnight 7 days later (exclusive). 850 * *daily*: every second from midnight at the start of the day 851 (inclusive) to midnight at the end of the day (exclusive). 853 * *hourly*: every second from the beginning of the hour 854 (inclusive) to the beginning of the next hour (exclusive). 856 * *minutely*: every second from the beginning of the minute 857 (inclusive) to the beginning of the next minute (exclusive). 859 * *secondly*: the second itself, only. 861 2. Each date-time candidate is compared against all of the byX 862 properties of the rule except bySetPosition. If any property in 863 the rule does not match the date-time, it is eliminated. Each 864 byX property is an array; the date-time matches the property if 865 it matches any of the values in the array. The properties have 866 the following semantics: 868 * *byMonth*: the date-time is in the given month. 870 * *byMonthDay*: the date-time is on the given day of the month. 871 Negative numbers mean the nth last day of the month. 873 * *byDay*: the date-time is on the given day of the week. If 874 the day is prefixed by a number, it is the nth occurrence of 875 that day of the week within the month (if frequency is 876 monthly) or year (if frequency is yearly). Negative numbers 877 means nth last occurrence within that period. 879 * *byYearDay*: the date-time is on the nth day of year. 880 Negative numbers mean the nth last day of the year. 882 * *byWeekNo*: the date-time is in the nth week of the year. 883 Negative numbers mean the nth last week of the year. This 884 corresponds to weeks according to week numbering as defined in 885 ISO.8601.2004, with a week defined as a seven day period, 886 starting on the firstDayOfWeek property value or Monday if 887 omitted. Week number one of the calendar year is the first 888 week that contains at least four days in that calendar year. 890 * *byHour*: the date-time has the given hour value. 892 * *byMinute*: the date-time has the given minute value. 894 * *bySecond*: the date-time has the given second value. 896 3. If a bySetPosition property is included, this is now applied to 897 the ordered list of remaining dates (this property specifies the 898 indexes of date-times to keep; all others should be eliminated. 899 Negative numbers are indexes from the end of the list, with -1 900 being the list item). 902 4. Any date-times before the start date of the event are eliminated 903 (see below for why this might be needed). 905 5. If further dates are required (we have not reached the until 906 date, or count limit) skip the next (interval - 1) sets of 907 candidates, then continue from step 1. 909 When determining the set of occurrence dates for an event or task, 910 the following extra rules must be applied: 912 1. The start date-time is always the first occurrence in the 913 expansion (and is counted if the recurrence is limited by a 914 "count" property), even if it would normally not match the rule. 916 2. The first set of candidates to consider is that which would 917 contain the start date-time. This means the first set may 918 include candidates before the start; such candidates are 919 eliminated from the results in step (4) as outlined before. 921 3. The following properties MUST be implicitly added to the rule 922 under the given conditions: 924 * If frequency > "secondly" and no bySecond property: Add a 925 bySecond property with the sole value being the seconds value 926 of the start date-time. 928 * If frequency > "minutely" and no byMinute property: Add a 929 byMinute property with the sole value being the minutes value 930 of the start date-time. 932 * If frequency > "hourly" and no byHour property: Add a byHour 933 property with the sole value being the hours value of the 934 start date-time. 936 * If frequency is "weekly" and no byDay property: Add a byDay 937 property with the sole value being the day-of-the-week of the 938 start date-time. 940 * If frequency is "monthly" and no byDay property and no 941 byMonthDay property: Add a byMonthDay property with the sole 942 value being the day-of-the-month of the start date-time. 944 * If frequency is "yearly" and no byYearDay property: 946 + if there are no byMonth or byWeekNo properties, and either 947 there is a byMonthDay property or there is no byDay 948 property: Add a byMonth property with the sole value being 949 the month of the start date-time. 951 + if there is no byMonthDay, byWeekNo or byDay properties: 952 Add a byMonthDay property with the sole value being the 953 day-of-the-month of the start date-time. 955 + if there is a byWeekNo property and no byMonthDay or byDay 956 properties: Add a byDay property with the sole value being 957 the day-of-the-week of the start date-time. 959 4.3.2. recurrenceOverrides 961 Type: "LocalDate[PatchObject]" (optional) 963 A map of the recurrence-ids (the date-time of the start of the 964 occurrence) to an object of patches to apply to the generated 965 occurrence object. 967 If the recurrence-id does not match an expanded start date from a 968 recurrence rule, it is to be treated as an additional occurrence 969 (like an RDATE from iCalendar). The patch object may often be empty 970 in this case. 972 If the patch object defines the *excluded* property to be "true", 973 then the recurring calendar object does not occur at the recurrence- 974 id date-time (like an EXDATE from iCalendar). Such a patch object 975 MUST NOT patch any other property. 977 By default, an occurrence inherits all properties from the main 978 object except the start (or due) date-time, which is shifted to the 979 new start time of the LocalDate key. However, individual properties 980 of the occurrence can be modified by a patch, or multiple patches. 981 It is valid to patch the start property value, and this patch takes 982 precedence over the LocalDate key. Both the LocalDate key as well as 983 the patched start date-time may occur before the original JSCalendar 984 object's start or due date. 986 A pointer in the PatchObject MUST NOT start with one of the following 987 prefixes; any patch with such a key MUST be ignored: 989 o @type 991 o uid 993 o relatedTo 995 o prodId 997 o method 998 o isAllDay 1000 o recurrenceRule 1002 o recurrenceOverrides 1004 o replyTo 1006 4.3.3. excluded 1008 Type: "Boolean" (optional, default:"false") 1010 Defines if this object is an overridden, excluded instance of a 1011 recurring JSCalendar object (also see Section 4.3.2). If this 1012 property value is "true", this calendar object instance MUST be 1013 treated as if not existent. 1015 4.4. Sharing and scheduling properties 1017 4.4.1. priority 1019 Type: "Number" (optional, default:"0") 1021 Specifies a priority for the calendar object. This may be used as 1022 part of scheduling systems to help resolve conflicts for a time 1023 period. 1025 The priority is specified as an integer in the range 0 to 9. A value 1026 of 0 specifies an undefined priority. A value of 1 is the highest 1027 priority. A value of 2 is the second highest priority. Subsequent 1028 numbers specify a decreasing ordinal priority. A value of 9 is the 1029 lowest priority. Other integer values are reserved for future use. 1031 4.4.2. freeBusyStatus 1033 Type: "String"(optional, default:"busy") 1035 Specifies how this property should be treated when calculating free- 1036 busy state. The value MUST be one of: 1038 o ""free"": The object should be ignored when calculating whether 1039 the user is busy. 1041 o ""busy"": The object should be included when calculating whether 1042 the user is busy. 1044 4.4.3. privacy 1046 Type: "String"(optional, default:"public") 1048 Calendar objects are normally collected together and may be shared 1049 with other users. The privacy property allows the object owner to 1050 indicate that it should not be shared, or should only have the time 1051 information shared but the details withheld. Enforcement of the 1052 restrictions indicated by this property are up to the 1053 implementations. 1055 This property MUST NOT affect the information sent to scheduled 1056 participants; it is only interpreted when the object is shared as 1057 part of a shared calendar. 1059 The value MUST be either one of the following values, registered in a 1060 future RFC, or a vendor-specific value. Vendor specific values MUST 1061 be prefixed with a domain name controlled by the vendor, e.g. 1062 "example.com/topsecret". Any value the client or server doesn't 1063 understand should be preserved but treated as equivalent to 1064 "private". 1066 o "public": The full details of the object are visible to those whom 1067 the object's calendar is shared with. 1069 o "private": The details of the object are hidden; only the basic 1070 time and metadata is shared. Implementations MUST ensure the 1071 following properties are stripped when the object is accessed by a 1072 sharee: 1074 * title 1076 * description 1078 * locations 1080 * links 1082 * locale 1084 * localizations 1086 * participants 1088 * replyTo 1090 In addition, any patches in "recurrenceOverrides" whose key is 1091 prefixed with one of the above properties MUST be stripped. 1093 o "secret": The object is hidden completely (as though it did not 1094 exist) when the calendar is shared. 1096 4.4.4. replyTo 1098 Type: "String[String]" (optional) 1100 Represents methods by which participants may submit their RSVP 1101 response to the organizer of the calendar object. The keys in the 1102 property value are the available methods. The value is a URI to use 1103 that method. Future methods may be defined in future specifications; 1104 a calendar client MUST ignore any method it does not understand. 1106 The following methods are defined: 1108 o "imip": The organizer accepts an iMIP [RFC6047] response at this 1109 email address. The value MUST be a "mailto:" URI. 1111 o "other": The user may submit the RSVP using this URI. The URI 1112 MUST be a valid URI Template ([RFC6570]) in level 2 format. The 1113 template MAY contain variables that MUST be expanded from the 1114 JSCalendar object as defined in table Table 1. Calendar clients 1115 SHOULD be prepared to handle authentication requests from the 1116 respective URI and for the participant email, but this 1117 specification does not mandate any specific mechanism. 1119 +---------------+---------------------------------------------------+ 1120 | Variable | Expand to | 1121 +---------------+---------------------------------------------------+ 1122 | participantId | The participant id of the replying *Participant* | 1123 | | object. | 1124 | | | 1125 | uid | The *uid* property value of the JSCalendar | 1126 | | object. | 1127 | | | 1128 | sequence | The *sequence* property value of the JSCalendar | 1129 | | object. | 1130 | | | 1131 | recurrenceId | The recurrence-id when replying for a single | 1132 | | occurrence of a recurring JSCalendar object. The | 1133 | | LocalDate-typed value is the recurrence-id of a | 1134 | | non-overridden recurrence, or the key of a | 1135 | | recurrenceOverride of this JSCalendar object. | 1136 +---------------+---------------------------------------------------+ 1138 Table 1: replyTo URI Template variables 1140 4.4.5. participants 1142 Type: "String[Participant]" (optional) 1144 A map of participant ids to participants, describing their 1145 participation in the calendar object. A participant id MUST be a 1146 valid [RFC3986] URI and MUST be unique to this calendar object; a 1147 "mailto:" URI with the email address of the participant is a good 1148 choice. 1150 A *Participant* object has the following properties: 1152 o *name*: "String" The display name of the participant (e.g. "Joe 1153 Bloggs"). 1155 o *email*: "String" (optional) The email address for the 1156 participant. 1158 o *kind*: "String" (optional) What kind of entity this participant 1159 is, if known. 1161 This MUST be either one of the following values, registered in a 1162 future RFC, or a vendor-specific value. Any value the client or 1163 server doesn't understand should be treated the same as if this 1164 property is omitted. 1166 * "individual": a single person 1168 * "group": a collection of people invited as a whole 1170 * "resource": a non-human resource, e.g. a projector 1172 * "location": a physical location involved in the calendar object 1173 that needs to be scheduled, e.g. a conference room. 1175 o *roles*: "String[]" A list of roles that this participant 1176 fulfills. 1178 At least one value MUST be specified for the participant. This 1179 MUST be either one of the following values, registered in a future 1180 RFC, or a vendor-specific value. Any value the client or server 1181 doesn't understand should be preserved but ignored. 1183 * "owner": The participant is an owner of the object. 1185 * "attendee": The participant is an attendee of the calendar 1186 object. 1188 * "chair": The participant is in charge of the calendar object 1189 when it occurs. 1191 o *locationId*: "String" (optional) The location at which this 1192 participant is expected to be attending. 1194 If the value does not correspond to any location id in the 1195 *locations* property of the instance, this MUST be treated the 1196 same as if the participant's locationId were omitted. 1198 o *rsvpResponse*: "String"(optional, default:"needs-action") The 1199 RSVP response, if any, of this participant. 1201 The value MUST be either one of the following values, registered 1202 in a future RFC, or a vendor-specific value: 1204 * "needs-action": No status yet set by the participant. 1206 * "accepted": The invited participant will participate. 1208 * "declined": The invited participant will not participate. 1210 * "tentative": The invited participant may participate. 1212 o *participation*: "String"(optional, default:"required") The 1213 required participation of this participant. 1215 The value MUST be either one of the following values, registered 1216 in a future RFC, or a vendor-specific value. Any value the client 1217 or server doesn't understand should be treated the same as 1218 "required". 1220 * "non-participant": Indicates a participant who is copied for 1221 information purposes only. 1223 * "optional": Indicates a participant whose participation is 1224 optional. 1226 * "required": Indicates a participant whose participation is 1227 required. 1229 o *rsvpWanted*: "Boolean"(optional, default:"false") If true, the 1230 organizer is expecting the participant to notify them of their 1231 status. 1233 o *scheduleSequence*: "Number"(optional, default:"0") The sequence 1234 number of the last response from the participant. If defined, 1235 this MUST be a non-negative integer. 1237 This can be used to determine whether the participant has sent a 1238 new RSVP following significant changes to the calendar object, and 1239 to determine if future responses are responding to a current or 1240 older view of the data. 1242 o *scheduleUpdated*: "UTCDate" (optional) The *updated* property of 1243 the last iMIP response from the participant. 1245 This can be compared to the *updated* timestamp in future iMIP 1246 responses to determine if the response is older or newer than the 1247 current data. 1249 o *invitedBy*: "String" (optional) The participant id of the 1250 participant who invited this one, if known. 1252 o *delegatedTo*: "String[]" (optional) A list of participant ids of 1253 participants that this participant has delegated their 1254 participation to. This MUST be omitted if none (rather than an 1255 empty array). 1257 o *delegatedFrom*: "String[]" (optional) A list of participant ids 1258 that this participant is acting as a delegate for. This MUST be 1259 omitted if none (rather than an empty array). 1261 o *memberOf*: "String[]" (optional) A list of group participants 1262 that were invited to this calendar object, which caused this 1263 participant to be invited due to their membership of the group(s). 1264 This MUST be omitted if none (rather than an empty array). 1266 o *linkIds*: "String[]" (optional) Links to more information about 1267 this participant, for example in vCard format. 1269 4.5. Alerts properties 1271 4.5.1. useDefaultAlerts 1273 Type: "Boolean" (optional, default:"false") 1275 If "true", use the user's default alerts and ignore the value of the 1276 *alerts* property. Fetching user defaults is dependent on the API 1277 from which this JSCalendar object is being fetched, and is not 1278 defined in this specification. If an implementation cannot determine 1279 the user's default alerts, or none are set, it MUST process the 1280 alerts property as if useDefaultAlerts is set to "false". 1282 4.5.2. alerts 1284 Type: "String[Alert]" (optional) 1286 A map of alert ids to Alert objects, representing alerts/reminders to 1287 display or send the user for this calendar object. The id MUST be 1288 unique to this calendar object; a UUID is a practical choice. 1290 An *Alert* Object has the following properties: 1292 o *relativeTo*: "String" (optional, default:"before-start") 1293 Specifies where the offset is relative to for the alarm to 1294 trigger. The value MUST be one of: 1296 * "before-start" 1298 * "after-start" 1300 * "before-end" 1302 * "after-end" 1304 o *offset*: "Duration" The offset from the start and end/due of the 1305 calendar object to fire the alert. If the calendar object does 1306 not define a time-zone, the user's default time-zone SHOULD be 1307 used when determining the offset, if known. Otherwise, the time- 1308 zone to use is implementation specific. 1310 o *acknowledged*: "UTCDate" (optional) 1312 When the user has permanently dismissed the alert the client MUST 1313 set this to the current time in UTC. Other clients which sync 1314 this property can then automatically dismiss or suppress duplicate 1315 alerts (alerts with the same alert id that triggered on or before 1316 this date-time). 1318 For a recurring calendar object, the *acknowledged* property of 1319 the parent object MUST be updated, unless the alert is already 1320 overridden in *recurrenceOverrides*. 1322 o *snoozed*: "UTCDate" (optional) 1324 If the user temporarily dismisses the alert, this is the UTC date- 1325 time after which it should trigger again. Setting this property 1326 on an instance of a recurring calendar object MUST update the 1327 alarm on the master object, unless the respective instance already 1328 is defined in "recurrenceOverrides". It MUST NOT generate an 1329 override for the sole use of snoozing an alarm. 1331 o *action*: "String" (optional, default:"display") Describes how to 1332 alert the user. 1334 The value MUST be at most one of the following values, registered 1335 in a future RFC, or a vendor-specific value: 1337 * "display": The alert should be displayed as appropriate for the 1338 current device and user context. 1340 * "email": The alert should trigger an email sent out to the 1341 user, notifying about the alert. This action is typically only 1342 appropriate for server implementations. 1344 4.6. Multilingual properties 1346 4.6.1. localizations 1348 Type: "String[PatchObject]" (optional) 1350 A map of [RFC5646] language tags to patch objects, which localize the 1351 calendar object into the locale of the respective language tag. 1353 See the description of PatchObject (Section 3.2.4) for the structure 1354 of the PatchObject. The patches are applied to the top-level object. 1355 In addition to all the restrictions on patches specified there, the 1356 pointer also MUST NOT start with one of the following prefixes; any 1357 patch with a such a key MUST be ignored: 1359 o @type 1361 o due 1363 o duration 1365 o freeBusyStatus 1367 o localization 1369 o method 1371 o participants 1373 o prodId 1375 o progress 1377 o relatedTo 1378 o sequence 1380 o start 1382 o status 1384 o timeZone 1386 o uid 1388 o useDefaultAlerts 1390 Note that this specification does not define how to maintain validity 1391 of localized content. For example, a client application changing a 1392 JSCalendar object's title property might also need to update any 1393 localizations of this property. Client implementations SHOULD 1394 provide the means to manage localizations, but how to achieve this is 1395 specific to the application's workflow and requirements. 1397 5. Type-specific JSCalendar properties 1399 5.1. JSEvent properties 1401 In addition to the common JSCalendar object properties (Section 4) a 1402 JSEvent has the following properties: 1404 5.1.1. start 1406 Type: "LocalDate" e.g. "2015-09-02T00:00:00" 1408 The date/time the event would start in the event's time-zone. 1410 A valid JSEvent MUST include this property. 1412 5.1.2. timeZone 1414 Type: "String|null" (optional, default:"null") 1416 The IANA Time Zone Database [3] name for the time-zone the event is 1417 scheduled in, or "null" for floating time. If omitted, this MUST be 1418 presumed to be "null" (i.e. floating time). 1420 5.1.3. duration 1422 Type: "Duration", e.g. "P2DT3H" (optional, default: "P0D") 1424 The zero or positive duration of the event in absolute time (i.e. in 1425 UTC time; ignoring DST shifts). To get the end date in the event 1426 time-zone, convert start into UTC, then add the duration, then 1427 convert the result into the appropriate time-zone. 1429 A JSEvent MAY be end in a different time-zone (e.g. a plane flight 1430 crossing time-zones). In this case, the JSEvent MUST specify the end 1431 time-zone in a *location* property value that defines its *rel* to be 1432 "end" and the end time-zone in its *timeZone* property. 1434 5.1.4. isAllDay 1436 Type: "Boolean" (optional, default:"false") 1438 Specifies if the event an all day event, such as a birthday or public 1439 holiday. 1441 If *isAllDay* is true, then the following restrictions apply: 1443 o the *start* property MUST have a time component of "T00:00:00". 1445 o the *duration* property MUST only include a day component. 1447 Note that all-day events MAY be bound to a specific time-zone, as 1448 defined by the *timeZone* property. 1450 5.1.5. status 1452 Type: "String" (optional, default:"confirmed") 1454 The scheduling status (Section 4.4) of a JSEvent. If set, it MUST be 1455 one of: 1457 o "confirmed": Indicates the event is definite. 1459 o "cancelled": Indicates the event is cancelled. 1461 o "tentative": Indicates the event is tentative. 1463 5.2. JSTask properties 1465 In addition to the common JSCalendar object properties (Section 4) a 1466 JSTask has the following properties: 1468 5.2.1. due 1470 Type: "LocalDate" (optional) e.g. "2015-09-02T00:00:00" 1472 The date/time the task is due in the task's time-zone. 1474 5.2.2. start 1476 Type: "LocalDate" (optional) e.g. "2015-09-02T00:00:00" 1478 The date/time the task should start in the task's time-zone. 1480 5.2.3. timeZone 1482 Type: "String|null" (optional, default:"null") 1484 The IANA Time Zone Database name for the time-zone the task is 1485 scheduled in, or "null" for floating time. If omitted, this MUST be 1486 presumed to be "null" (i.e. floating time). 1488 5.2.4. estimatedDuration 1490 Type: "Duration" (optional), e.g. "P2DT3H" 1492 Specifies the estimated positive duration of time the task takes to 1493 complete. 1495 5.2.5. statusUpdatedAt 1497 Type: "UTCDate" (optional), e.g. "2016-06-13T12:00:00Z" 1499 Specifies the date/time the task status properties was last updated. 1501 If the task is recurring and has future instances, a client may want 1502 to keep track of the last status update timestamp of a specific task 1503 recurrence, but leave other instances unchanged. One way to achieve 1504 this is by overriding the statusUpdatedAt property in the task 1505 *recurrenceOverrides*. However, this could produce a long list of 1506 timestamps for regularly recurring tasks. An alternative approach is 1507 to split the JSTask into a current, single instance of JSTask with 1508 this instance status update time and a future recurring instance. 1509 Also see the definition of the *relatedTo* on splitting. 1511 5.2.6. isAllDay 1513 Type: "Boolean" (optional, default:"false") 1515 Specifies if the task is an all day task. 1517 If *isAllDay* is true, then the *start* and *due* properties MUST 1518 have a time component of "T00:00:00". Note that the 1519 *estimatedDuration* property MAY contain a non-zero time duration. 1520 All-day tasks MAY be bound to a specific time-zone, as defined by the 1521 *timeZone* property. 1523 5.2.7. progress 1525 In addition to the common properties of a *Participant* object 1526 (Section 4.4.5), a Participant within a JSTask supports the following 1527 property: 1529 o *progress*: "ParticipantProgress" (optional) The progress of the 1530 participant for this task, if known. This property MUST NOT be 1531 set if the *rsvpResponse* of this participant is any other value 1532 but "accepted". 1534 A *ParticipantProgress* object has the following properties: 1536 o *status*: "String" Describes the completion status of the 1537 participant's progress. 1539 The value MUST be at most one of the following values, registered 1540 in a future RFC, or a vendor-specific value: 1542 * "completed": The participant completed their task. 1544 * "in-process": The participant has started this task. 1546 * "failed": The participant failed to complete their task. 1548 o *timestamp*: "UTCDate" Describes the last time when the 1549 participant progress got updated. 1551 5.2.8. status 1553 Type: "String" 1555 Defines the overall status of this task. If omitted, the default 1556 status (Section 4.4) of a JSTask is defined as follows (in order of 1557 evaluation): 1559 o "completed": if all the *ParticipantProgress* status of the task 1560 participants is "completed". 1562 o "failed": if at least one *ParticipantProgress* status of the task 1563 participants is "failed". 1565 o "in-process": if at least one *ParticipantProgress* status of the 1566 task participants is "in-process". 1568 o "needs-action": If none of the other criteria match. 1570 If set, it MUST be one of: 1572 o "needs-action": Indicates the task needs action. 1574 o "completed": Indicates the task is completed. 1576 o "in-process": Indicates the task is in process. 1578 o "cancelled": Indicates the task is cancelled. 1580 o "pending": Indicates the task has been created and accepted for 1581 processing, but not yet started. 1583 o "failed": Indicates the task failed. 1585 5.3. JSGroup properties 1587 JSGroup supports the following JSCalendar properties (Section 4): 1589 o @type 1591 o uid 1593 o created 1595 o updated 1597 o categories 1599 o keywords 1601 o name 1603 o description 1605 o color 1607 o links 1609 as well as the following JSGroup-specific properties: 1611 5.3.1. entries 1613 Type: "String[JSTask|JSEvent]" 1615 A collection of group members. This is represented as a map of the 1616 *uid* property value to the JSCalendar object member having that uid. 1617 Implementations MUST ignore entries of unknown type. 1619 5.3.2. source 1621 Type: "String" (optional) 1623 The source from which updated versions of this group may be retrieved 1624 from. The value MUST be a URI. 1626 6. Conversion from and to iCalendar 1628 This section specifies which JSCalendar properties can be mapped from 1629 and to iCalendar format. Implementations SHOULD follow these 1630 conversion guidelines. Still, JSCalendar does not restrict itself to 1631 iCalendar and conversion between these two formats MAY be lossy. 1633 6.1. JSEvent 1635 The iCalendar counterpart to *JSEvent* is the VEVENT component type 1636 [RFC5545]. A VEVENT component that is a direct child of a VCALENDAR 1637 component is equivalent to a standalone JSEvent. A VEVENT component 1638 *within* a VEVENT maps to the entries of the JSEvent 1639 *recurrenceOverrides* property. 1641 +----------+--------------------------------------------------------+ 1642 | Property | iCalendar counterpart | 1643 +----------+--------------------------------------------------------+ 1644 | isAllDay | True, if the type of the DTSTART property in iCalendar | 1645 | | is DATE. When translating from JSCalendar the | 1646 | | iCalendar DTSTART property is of DATE value type, if | 1647 | | the *isAllDay* property is set to true and the | 1648 | | *timeZone* property is null. | 1649 | | | 1650 | start | Corresponds to the DTSTART property in iCalendar. Note | 1651 | | that time-zone information is stored separately in | 1652 | | JSEvent. | 1653 | | | 1654 | timeZone | Corresponds to the TZID part of the DTSTART property | 1655 | | in iCalendar. If the event has a different end time- | 1656 | | zone to start time-zone, this should be added as a | 1657 | | JSCalendar *location* with just a *timeZone* property | 1658 | | and "rel="end"". | 1659 | | | 1660 | duration | Corresponds to the DURATION or DSTART+DTEND properties | 1661 | | in iCalendar. | 1662 +----------+--------------------------------------------------------+ 1664 Table 2: Translation between JSEvent and iCalendar 1666 6.2. JSTask 1668 The iCalendar counterpart to *JSTask* is the VTODO component type 1669 [RFC5545]. A VTODO component that is a direct child of a VCALENDAR 1670 component is equivalent to a standalone JSTask. A VTODO component 1671 *within* a master VTODO maps to the entries of the JSTask 1672 *recurrenceOverrides* property. 1674 +-------------------+-----------------------------------------------+ 1675 | Property | iCalendar counterpart | 1676 +-------------------+-----------------------------------------------+ 1677 | isAllDay | True, if the type of the DTSTART property in | 1678 | | iCalendar is DATE. When translating from | 1679 | | JSCalendar the iCalendar DTSTART property is | 1680 | | of DATE value type, if the *isAllDay* | 1681 | | property is set to true and the *timeZone* | 1682 | | property is null. | 1683 | | | 1684 | due | Corresponds to the DUE and DTSTART+DURATION | 1685 | | properties in iCalendar. When mapping | 1686 | | iCalendar VTODOs with DTSTART+DURATION, the | 1687 | | due date is the result of adding DURATION to | 1688 | | DTSTART in the DTSTART time-zone. | 1689 | | | 1690 | start | Corresponds to the DTSTART property in | 1691 | | iCalendar. | 1692 | | | 1693 | timeZone | Corresponds to the TZID part of the | 1694 | | DTSTART/DUE properties in iCalendar. If the | 1695 | | task has a different end time-zone to start | 1696 | | or due time-zone, this should be added as a | 1697 | | JSCalendar *location* with just a *timeZone* | 1698 | | property and "rel="end"". | 1699 | | | 1700 | estimatedDuration | Corresponds to the ESTIMATED-DURATION | 1701 | | iCalendar property in the RFC draft | 1702 | | [draft-apthorp-ical-tasks]. | 1703 | | | 1704 | statusUpdatedAt | Maps to the COMPLETED iCalendar property. The | 1705 | | JSTask status property MUST have value | 1706 | | "completed". | 1707 | | | 1708 | progress | Corresponds to the PARTSTAT and COMPLETED | 1709 | | properties in iCalendar, including the | 1710 | | definitions in the RFC draft | 1711 | | [draft-apthorp-ical-tasks]. | 1712 | | | 1713 | status | Corresponds to the STATUS property in | 1714 | | iCalendar, including the definitions in the | 1715 | | RFC draft [draft-apthorp-ical-tasks]. | 1716 +-------------------+-----------------------------------------------+ 1718 Table 3: Translation between JSTask and iCalendar 1720 6.3. JSGroup 1722 A JSGroup converts to a iCalendar VCALENDAR containing VEVENT or 1723 VTODO components. 1725 +----------+--------------------------------------------------------+ 1726 | Property | iCalendar counterpart | 1727 +----------+--------------------------------------------------------+ 1728 | entries | The VEVENT and VTODO components within a top-level | 1729 | | VCALENDAR component. | 1730 | | | 1731 | source | Corresponds to the SOURCE property in iCalendar. | 1732 +----------+--------------------------------------------------------+ 1734 Table 4: Translation between JSGroup and iCalendar 1736 6.4. Common properties 1738 +------------------------+------------------------------------------+ 1739 | Property | iCalendar counterpart | 1740 +------------------------+------------------------------------------+ 1741 | alerts | An *Alert* corresponds to the VALARM | 1742 | | component in iCalendar, where the | 1743 | | *action* is determined by the iCalendar | 1744 | | ACTION property value (e.g., both | 1745 | | "DISPLAY" and "AUDIO" actions map to a | 1746 | | JSCalendar *display* action, and | 1747 | | similarly for "EMAIL"). The | 1748 | | *relativeTo* and *offset* properties | 1749 | | corresponds to the iCalendar TRIGGER | 1750 | | property. | 1751 | | | 1752 | categories | Corresponds to the CONCEPT property in | 1753 | | iCalendar, see in the RFC draft | 1754 | | [draft-ietf-calext-ical-relations]. | 1755 | | | 1756 | color | Corresponds to the COLOR property in | 1757 | | iCalendar, as specified in [RFC7986]. | 1758 | | | 1759 | created | Corresponds to the CREATED property in | 1760 | | iCalendar. | 1761 | | | 1762 | description | Corresponds to the DESCRIPTION property | 1763 | | and its ALTREP parameters in iCalendar. | 1764 | | | 1765 | descriptionContentType | Implementation-specific. | 1766 | | | 1767 | freeBusyStatus | Corresponds to the TRANSP property in | 1768 | | iCalendar. | 1769 | | | 1770 | keywords | Corresponds to the CATEGORIES property | 1771 | | in iCalendar, as specified in [RFC7986]. | 1772 | | | 1773 | links | Corresponds to the ATTACH ([RFC5545]) or | 1774 | | IMAGE ([RFC7986]) properties with a URI | 1775 | | value type set to the link "href". | 1776 | | ([RFC7986]). The *type* property | 1777 | | corresponds to the FMTTYPE parameter, | 1778 | | the *size* property to the SIZE | 1779 | | parameter. Mapping all other properties | 1780 | | is implementation-specific. | 1781 | | | 1782 | locale | Corresponds to the LANGUAGE parameter in | 1783 | | iCalendar, which is added to individual | 1784 | | properties. When converting from | 1785 | | iCalendar, one language must be picked | 1786 | | as the main locale for the object, and | 1787 | | all properties in other languages moved | 1788 | | to the localizations JSEvent property. | 1789 | | | 1790 | localizations | Implementation-specific. | 1791 | | | 1792 | locations | See Section 6.5. | 1793 | | | 1794 | method | Corresponds to the METHOD property of | 1795 | | the embedding VCALENDAR in iCalendar. | 1796 | | | 1797 | participants | See Section 6.5. | 1798 | | | 1799 | priority | Corresponds to the PRIORITY property in | 1800 | | iCalendar. | 1801 | | | 1802 | privacy | Corresponds to the CLASS property in | 1803 | | iCalendar. | 1804 | | | 1805 | prodId | Corresponds to the PRODID property in | 1806 | | iCalendar. | 1807 | | | 1808 | recurrenceOverrides | Corresponds to the RDATE and EXDATE | 1809 | | properties in iCalendar, plus VEVENT | 1810 | | (for JSEvent) or VTODO (for JSTask) | 1811 | | instances with a recurrence-id. | 1812 | | | 1813 | recurrenceRule | Corresponds to the RRULE property in | 1814 | | iCalendar. See the property definition | 1815 | | at section Section 4.3.1 how to map a | 1816 | | RRULE value. | 1817 | | | 1818 | relatedTo | Corresponds to the RELATED-TO property | 1819 | | in iCalendar. | 1820 | | | 1821 | replyTo | An iCalendar ORGANIZER with one of the | 1822 | | mapped URIs as value. If URIs are | 1823 | | defined for both the "imip" and "other" | 1824 | | type, it is recommended to map the | 1825 | | "imip" value to the calendar address | 1826 | | value of the ORGANIZER. | 1827 | | | 1828 | sequence | Corresponds to the SEQUENCE property in | 1829 | | iCalendar. | 1830 | | | 1831 | status | Corresponds to the STATUS property in | 1832 | | iCalendar (converted to lower-case). | 1833 | | | 1834 | title | Corresponds to the SUMMARY property in | 1835 | | iCalendar. | 1836 | | | 1837 | uid | Corresponds to the UID property in | 1838 | | iCalendar. | 1839 | | | 1840 | updated | Corresponds to the DTSTAMP and LAST- | 1841 | | MODIFIED properties in iCalendar. (These | 1842 | | are only different in the iTIP case, and | 1843 | | the difference is not actually useful.) | 1844 +------------------------+------------------------------------------+ 1846 Table 5: Translation between JSCalendar and iCalendar 1848 6.5. Locations and participants 1850 Both JSCalendar participants and locations have counterparts in 1851 iCalendar but provide richer representation. 1853 The following table outlines translation of JSCalendar participants. 1854 Where iCalendar has distinct properties for ORGANIZER and ATTENDEE, 1855 these are merged in JSCalendar into the Participant object type. 1857 +---------------+---------------------------------------------------+ 1858 | Property | iCalendar counterpart | 1859 +---------------+---------------------------------------------------+ 1860 | delegatedFrom | the DELEGATED-FROM parameter | 1861 | | | 1862 | delegatedTo | the DELEGATED-TO parameter | 1863 | | | 1864 | email | the value of the ORGANIZER or ATTENDEE property | 1865 | | | 1866 | kind | the CUTYPE parameter | 1867 | | | 1868 | linkIds | Implementation-specific. | 1869 | | | 1870 | locationId | Implementation-specific. When mapping from | 1871 | | iCalendar to JSCalendar this may be the | 1872 | | JSCalendar identifier of a CONFERENCE property | 1873 | | that has the MODERATOR feature defined in its | 1874 | | FEATURE parameter values. If multiple such | 1875 | | CONFERENCE properties are defined in iCalendar, | 1876 | | then the one with the most interactive features | 1877 | | is chosen. | 1878 | | | 1879 | memberOf | the MEMBER parameter | 1880 | | | 1881 | name | the CN parameter | 1882 | | | 1883 | participation | Maps to the standard iCalendar ROLE parameter | 1884 | | values REQ-PARTICIPANT, OPT-PARTICIPANT and NON- | 1885 | | PARTICIPANT. | 1886 | | | 1887 | roles | The "chair" role maps to the standard iCalendar | 1888 | | ROLE parameter value "chair", with an implicit | 1889 | | participant of value "required". The mapping of | 1890 | | non-required chairs and other roles is | 1891 | | implementation-specific, but using "x-name" | 1892 | | parameter values is recommended. | 1893 | | | 1894 | rsvpResponse | the PARTSTAT parameter | 1895 | | | 1896 | the | scheduleSequence | 1897 | DELEGATED-TO | | 1898 | parameter | | 1899 | | | 1900 | the SEQUENCE | scheduleUpdated | 1901 | property of | | 1902 | the | | 1903 | participant's | | 1904 | latest iMIP | | 1905 | message | | 1906 | | | 1907 | the DTSTAMP | 1908 | property of | 1909 | the | 1910 | participant's | 1911 | latest iMIP | 1912 | message | 1913 +---------------+---------------------------------------------------+ 1915 Table 6: Translation of Participant between JSCalendar and iCalendar 1917 The iCalendar counterpart for JSCalendar Location objects is the 1918 iCalendar [RFC5545] LOCATION property, or implementation-specific. 1920 +-------------+-----------------------------------------------------+ 1921 | Property | iCalendar counterpart | 1922 +-------------+-----------------------------------------------------+ 1923 | name | Corresponds to the LOCATION property value. | 1924 | | | 1925 | description | Implementation-specific. | 1926 | | | 1927 | rel | Implementation-specific. | 1928 | | | 1929 | timeZone | Implementation-specific. | 1930 | | | 1931 | coordinates | Implementation-specific. Consider using a GEO | 1932 | | iCalendar property, along with one LOCATION. | 1933 | | | 1934 | uri | Corresponds to the LOCATION ALTREP parameter. | 1935 | | | 1936 | linkIds | Implementation-specific. | 1937 +-------------+-----------------------------------------------------+ 1939 Table 7: Translation of Location between JSCalendar and iCalendar 1941 The iCalendar counterpart for JSCalendar VirtualLocation objects is 1942 the iCalendar [RFC7986] CONFERENCE property, or implementation- 1943 specific. 1945 +--------------+--------------------------------------------------+ 1946 | Property | iCalendar counterpart | 1947 +--------------+--------------------------------------------------+ 1948 | name | Corresponds to the CONFERENCE LABEL parameter. | 1949 | | | 1950 | description | Implementation-specific. | 1951 | | | 1952 | uri | Corresponds to the CONFERENCE property value. | 1953 +--------------+--------------------------------------------------+ 1955 Table 8: Translation of VirtualLocation between JSCalendar and 1956 iCalendar 1958 6.6. Unknown properties 1960 Both JSCalendar and iCalendar calendar objects may contain properties 1961 that are not expressible in the other format. This specification 1962 does not mandate how to preserve these properties. Instead, it 1963 leaves negotiation on how to treat unknown properties to client and 1964 server implementations and their protocol used to exchange calendar 1965 objects. 1967 Two notable options to represent and preserve arbitrary iCalendar 1968 object properties in JSCalendar are: 1970 o *JCal*: Define iCalendar properties in JCal format ([RFC7265]) in 1971 a vendor-specific property of the JCalendar object. The JCal- 1972 formatted value may either only contain iCalendar properties that 1973 were not mapped to JSCalendar properties, or contain the complete 1974 iCalendar object representation. 1976 o *Alternate link*: Define an alternate link (Section 4.2.6) value 1977 pointing to the iCalendar representation of the JSCalendar object. 1978 E.g. the alternative representation of a VEVENT would be 1979 represented as a link with rel "alternate" and type "text/ 1980 calendar;component=VEVENT". 1982 7. JSCalendar object examples 1984 The following examples illustrate several aspects of the JSCalendar 1985 data model and format. The examples may omit mandatory or additional 1986 properties, which is indicated by a placeholder property with key 1987 "...". While most of the examples use calendar event objects, they 1988 are also illustrative for tasks. 1990 7.1. Simple event 1992 This example illustrates a simple one-time event. It specifies a 1993 one-time event that begins on January 15, 2018 at 1pm New York local 1994 time and ends after 1 hour. 1996 { 1997 "@type": "jsevent", 1998 "uid": "2a358cee-6489-4f14-a57f-c104db4dc2f1", 1999 "updated": "2018-01-15T18:00:00Z", 2000 "title": "Some event", 2001 "start": "2018-01-15T13:00:00", 2002 "timeZone": "America/New_York", 2003 "duration": "PT1H" 2004 } 2006 7.2. Simple task 2008 This example illustrates a simple task for a plain to-do item. 2010 { 2011 "@type": "jstask", 2012 "uid": "2a358cee-6489-4f14-a57f-c104db4dc2f2", 2013 "updated": "2018-01-15T18:00:00Z", 2014 "title": "Do something" 2015 } 2017 7.3. Simple group 2019 This example illustrates a simple calendar object group that contains 2020 an event and a task. 2022 { 2023 "@type": "jsgroup", 2024 "uid": "2a358cee-6489-4f14-a57f-c104db4dc343", 2025 "updated": "2018-01-15T18:00:00Z", 2026 "name": "A simple group", 2027 "entries": [ 2028 { 2029 "@type": "jsevent", 2030 "uid": "2a358cee-6489-4f14-a57f-c104db4dc2f1", 2031 "updated": "2018-01-15T18:00:00Z", 2032 "title": "Some event", 2033 "start": "2018-01-15T13:00:00", 2034 "timeZone": "America/New_York", 2035 "duration": "PT1H" 2036 }, 2037 { 2038 "@type": "jstask", 2039 "uid": "2a358cee-6489-4f14-a57f-c104db4dc2f2", 2040 "updated": "2018-01-15T18:00:00Z", 2041 "title": "Do something" 2042 } 2043 ] 2044 } 2046 7.4. All-day event 2048 This example illustrates an event for an international holiday. It 2049 specifies an all-day event on April 1 that occurs every year since 2050 the year 1900. 2052 { 2053 "...": "", 2054 "title": "April Fool's Day", 2055 "isAllDay": true, 2056 "start": "1900-04-01T00:00:00", 2057 "duration": "P1D", 2058 "recurrenceRule": { 2059 "frequency": "yearly" 2060 } 2061 } 2063 7.5. Task with a due date 2065 This example illustrates a task with a due date. It is a reminder to 2066 buy groceries before 6pm Vienna local time on January 19, 2018. The 2067 calendar user expects to need 1 hour for shopping. 2069 { 2070 "...": "", 2071 "title": "Buy groceries", 2072 "due": "2018-01-19T18:00:00", 2073 "timeZone": "Europe/Vienna", 2074 "estimatedDuration": "PT1H" 2075 } 2077 7.6. Event with end time-zone 2079 This example illustrates the use of end time-zones by use of an 2080 international flight. The flight starts on April 1, 2018 at 9am in 2081 Berlin local time. The duration of the flight is scheduled at 10 2082 hours 30 minutes. The time at the flights destination is in the same 2083 time-zone as Tokyo. Calendar clients could use the end time-zone to 2084 display the arrival time in Tokyo local time and highlight the time- 2085 zone difference of the flight. The location names can serve as input 2086 for navigation systems. 2088 { 2089 "...": "", 2090 "title": "Flight XY51 to Tokyo", 2091 "start": "2018-04-01T09:00:00", 2092 "timeZone": "Europe/Berlin", 2093 "duration": "PT10H30M", 2094 "locations": { 2095 "2a358cee-6489-4f14-a57f-c104db4dc2f1": { 2096 "rel": "start", 2097 "name": "Frankfurt Airport (FRA)" 2098 }, 2099 "c2c7ac67-dc13-411e-a7d4-0780fb61fb08": { 2100 "rel": "end", 2101 "name": "Narita International Airport (NRT)", 2102 "timeZone": "Asia/Tokyo" 2103 } 2104 } 2105 } 2107 7.7. Floating-time event (with recurrence) 2109 This example illustrates the use of floating-time. Since January 1, 2110 2018, a calendar user blocks 30 minutes every day to practice Yoga at 2111 7am local time, in whatever time-zone the user is located on that 2112 date. 2114 { 2115 "...": "", 2116 "title": "Yoga", 2117 "start": "2018-01-01T07:00:00", 2118 "duration": "PT30M", 2119 "recurrenceRule": { 2120 "frequency": "daily" 2121 } 2122 } 2124 7.8. Event with multiple locations and localization 2126 This example illustrates an event that happens at both a physical and 2127 a virtual location. Fans can see a live convert on premises or 2128 online. The event title and descriptions are localized. (Note: the 2129 localization of the event description contains an UTF-8 encoded 2130 German Umlaut. This character may have been replaced with ASCII 2131 characters in the plain-text rendering of this RFC document) 2132 { 2133 "...": "", 2134 "title": "Live from Music Bowl: The Band", 2135 "description": "Go see the biggest music event ever!", 2136 "locale": "en", 2137 "start": "2018-07-04T17:00:00", 2138 "timeZone": "America/New_York", 2139 "duration": "PT3H", 2140 "locations": { 2141 "c0503d30-8c50-4372-87b5-7657e8e0fedd": { 2142 "name": "The Music Bowl", 2143 "description": "Music Bowl, Central Park, New York", 2144 "coordinates": "geo:40.7829,73.9654" 2145 } 2146 }, 2147 "virtualLocations": { 2148 "6f3696c6-1e07-47d0-9ce1-f50014b0041a": { 2149 "name": "Free live Stream from Music Bowl", 2150 "uri": "https://stream.example.com/the_band_2018" 2151 } 2152 }, 2153 "localizations": { 2154 "de": { 2155 "title": "Live von der Music Bowl: The Band!", 2156 "description": "Schau dir das groesste Musikereignis an!", 2157 "virtualLocations/6f3696c6-1e07-47d0-9ce1-f50014b0041a/name": 2158 "Gratis Live-Stream aus der Music Bowl" 2159 } 2160 } 2161 } 2163 7.9. Recurring event with overrides 2165 This example illustrates the use of recurrence overrides. A math 2166 course at a University is held for the first time on January 8, 2018 2167 at 9am London time and occurs every week until June 25, 2018. Each 2168 lecture lasts for one hour and 30 minutes and is located at the 2169 Mathematics department. This event has exceptional occurrences: at 2170 the last occurrence of the course is an exam, which lasts for 2 hours 2171 and starts at 10am. Also, the location of the exam differs from the 2172 usual location. On April 2 no course is held. On January 5 at 2pm 2173 is an optional introduction course, that occurs before the first 2174 regular lecture. 2176 { 2177 "...": "", 2178 "title": "Calculus I", 2179 "start": "2018-01-08T09:00:00", 2180 "timeZone": "Europe/London", 2181 "duration": "PT1H30M", 2182 "locations": { 2183 "2a358cee-6489-4f14-a57f-c104db4dc2f1": { 2184 "title": "Math lab room 1", 2185 "description": "Math Lab I, Department of Mathematics" 2186 } 2187 }, 2188 "recurrenceRule": { 2189 "frequency": "weekly", 2190 "until": "2018-06-25T09:00:00" 2191 }, 2192 "recurrenceOverrides": { 2193 "2018-01-05T14:00:00": { 2194 "title": "Introduction to Calculus I (optional)" 2195 }, 2196 "2018-04-02T09:00:00": { 2197 "excluded": "true" 2198 }, 2199 "2018-06-25T09:00:00": { 2200 "title": "Calculus I Exam", 2201 "start": "2018-06-25T10:00:00", 2202 "duration": "PT2H", 2203 "locations": { 2204 "2a358cee-6489-4f14-a57f-c104db4dc2f1": { 2205 "title": "Big Auditorium", 2206 "description": "Big Auditorium, Other Road" 2207 } 2208 } 2209 } 2210 } 2211 } 2213 7.10. Recurring event with participants 2215 This example illustrates scheduled events. A team meeting occurs 2216 every week since January 8, 2018 at 9am Johannesburg time. The event 2217 owner also chairs the event. Participants meet in a virtual meeting 2218 room. An attendee has accepted the invitation, but on March 8, 2018 2219 he is unavailable and declined participation for this occurrence. 2221 { 2222 "...": "", 2223 "title": "FooBar team meeting", 2224 "start": "2018-01-08T09:00:00", 2225 "timeZone": "Africa/Johannesburg", 2226 "duration": "PT1H", 2227 "locations": { 2228 "2a358cee-6489-4f14-a57f-c104db4dc2f1": { 2229 "title": "ChatMe meeting room", 2230 "rel": "virtual", 2231 "features": [ 2232 "audio", 2233 "chat", 2234 "video" 2235 ], 2236 "uri": "https://chatme.example.com?id=1234567" 2237 } 2238 }, 2239 "recurrenceRule": { 2240 "frequency": "weekly" 2241 }, 2242 "replyTo": { 2243 "imip": "zoe@foobar.example.com" 2244 }, 2245 "participants": { 2246 "tom@foobar.example.com": { 2247 "name": "Tom Tool", 2248 "email": "tom@foobar.example.com", 2249 "rsvpResponse": "accepted", 2250 "roles": [ 2251 "attendee" 2252 ] 2253 }, 2254 "zoe@foobar.example.com": { 2255 "name": "Zoe Zelda", 2256 "email": "zoe@foobar.example.com", 2257 "rsvpResponse": "accepted", 2258 "roles": [ 2259 "owner", 2260 "chair" 2261 ] 2262 }, 2263 "...": "" 2264 }, 2265 "recurrenceOverrides": { 2266 "2018-03-08T09:00:00": { 2267 "participants/tom@foobar.example.com/rsvpResponse": "declined" 2268 } 2269 } 2270 } 2272 8. Security Considerations 2274 The use of JSON as a format does have its own inherent security risks 2275 as discussed in Section 12 of [RFC8259]. Even though JSON is 2276 considered a safe subset of JavaScript, it should be kept in mind 2277 that a flaw in the parser processing JSON could still impose a 2278 threat, which doesn't arise with conventional iCalendar data. 2280 With this in mind, a parser for JSON data aware of the security 2281 implications should be used for the format described in this 2282 document. For example, the use of JavaScript's "eval()" function is 2283 considered an unacceptable security risk, as described in Section 12 2284 of[RFC8259]. A native parser with full awareness of the JSON format 2285 should be preferred. 2287 9. IANA Considerations 2289 This document amends the "application/calendar" MIME media type 2290 defined in [RFC7265]. 2292 New optional parameter: "type" with value being one of "jsevent", 2293 "jstask", "jsgroup". The parameter MUST NOT occur more than once. 2295 10. Acknowledgments 2297 The authors would like to thank the members of CalConnect for their 2298 valuable contributions. This specification originated from the work 2299 of the API technical committee of CalConnect, the Calendaring and 2300 Scheduling Consortium. 2302 11. References 2304 11.1. Normative References 2306 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2307 Requirement Levels", BCP 14, RFC 2119, 2308 DOI 10.17487/RFC2119, March 1997, 2309 . 2311 [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource 2312 Locators", RFC 2392, DOI 10.17487/RFC2392, August 1998, 2313 . 2315 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 2316 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 2317 . 2319 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 2320 Resource Identifier (URI): Generic Syntax", STD 66, 2321 RFC 3986, DOI 10.17487/RFC3986, January 2005, 2322 . 2324 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 2325 Unique IDentifier (UUID) URN Namespace", RFC 4122, 2326 DOI 10.17487/RFC4122, July 2005, 2327 . 2329 [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data 2330 Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006, 2331 . 2333 [RFC4791] Daboo, C., Desruisseaux, B., and L. Dusseault, 2334 "Calendaring Extensions to WebDAV (CalDAV)", RFC 4791, 2335 DOI 10.17487/RFC4791, March 2007, 2336 . 2338 [RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and 2339 Scheduling Core Object Specification (iCalendar)", 2340 RFC 5545, DOI 10.17487/RFC5545, September 2009, 2341 . 2343 [RFC5546] Daboo, C., Ed., "iCalendar Transport-Independent 2344 Interoperability Protocol (iTIP)", RFC 5546, 2345 DOI 10.17487/RFC5546, December 2009, 2346 . 2348 [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying 2349 Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646, 2350 September 2009, . 2352 [RFC5870] Mayrhofer, A. and C. Spanring, "A Uniform Resource 2353 Identifier for Geographic Locations ('geo' URI)", 2354 RFC 5870, DOI 10.17487/RFC5870, June 2010, 2355 . 2357 [RFC6047] Melnikov, A., Ed., "iCalendar Message-Based 2358 Interoperability Protocol (iMIP)", RFC 6047, 2359 DOI 10.17487/RFC6047, December 2010, 2360 . 2362 [RFC6570] Gregorio, J., Fielding, R., Hadley, M., Nottingham, M., 2363 and D. Orchard, "URI Template", RFC 6570, 2364 DOI 10.17487/RFC6570, March 2012, 2365 . 2367 [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type 2368 Specifications and Registration Procedures", BCP 13, 2369 RFC 6838, DOI 10.17487/RFC6838, January 2013, 2370 . 2372 [RFC6901] Bryan, P., Ed., Zyp, K., and M. Nottingham, Ed., 2373 "JavaScript Object Notation (JSON) Pointer", RFC 6901, 2374 DOI 10.17487/RFC6901, April 2013, 2375 . 2377 [RFC7265] Kewisch, P., Daboo, C., and M. Douglass, "jCal: The JSON 2378 Format for iCalendar", RFC 7265, DOI 10.17487/RFC7265, May 2379 2014, . 2381 [RFC7493] Bray, T., Ed., "The I-JSON Message Format", RFC 7493, 2382 DOI 10.17487/RFC7493, March 2015, 2383 . 2385 [RFC7529] Daboo, C. and G. Yakushev, "Non-Gregorian Recurrence Rules 2386 in the Internet Calendaring and Scheduling Core Object 2387 Specification (iCalendar)", RFC 7529, 2388 DOI 10.17487/RFC7529, May 2015, 2389 . 2391 [RFC7986] Daboo, C., "New Properties for iCalendar", RFC 7986, 2392 DOI 10.17487/RFC7986, October 2016, 2393 . 2395 [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data 2396 Interchange Format", STD 90, RFC 8259, 2397 DOI 10.17487/RFC8259, December 2017, 2398 . 2400 [RFC8288] Nottingham, M., "Web Linking", RFC 8288, 2401 DOI 10.17487/RFC8288, October 2017, 2402 . 2404 11.2. Informative References 2406 [draft-apthorp-ical-tasks] 2407 "Task Extensions to iCalendar", 2408 . 2410 [draft-ietf-calext-ical-relations] 2411 "Support for iCalendar Relationships", 2412 . 2415 [MIME] "IANA Media Types", . 2418 11.3. URIs 2420 [1] https://www.iana.org/assignments/link-relations/link- 2421 relations.xhtml 2423 [2] https://www.w3.org/TR/2011/REC-css3-color-20110607/#svg-color 2425 [3] http://www.iana.org/time-zones 2427 Authors' Addresses 2429 Neil Jenkins 2430 FastMail 2431 PO Box 234 2432 Collins St West 2433 Melbourne VIC 8007 2434 Australia 2436 Email: neilj@fastmailteam.com 2437 URI: https://www.fastmail.com 2439 Robert Stepanek 2440 FastMail 2441 PO Box 234 2442 Collins St West 2443 Melbourne VIC 8007 2444 Australia 2446 Email: rsto@fastmailteam.com 2447 URI: https://www.fastmail.com