idnits 2.17.1 draft-ietf-calext-jscalendar-02.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 (March 5, 2018) is 2237 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 2311 -- Looks like a reference, but probably isn't: '2' on line 2313 -- Looks like a reference, but probably isn't: '3' on line 2316 -- Looks like a reference, but probably isn't: '4' on line 2318 Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 5 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: September 6, 2018 March 5, 2018 7 JSCalendar: A JSON representation of calendar data 8 draft-ietf-calext-jscalendar-02 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 September 6, 2018. 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 . . . . . . . . . . . . . . . . . . . . . . . 6 62 3.2.1. UTCDate . . . . . . . . . . . . . . . . . . . . . . . 7 63 3.2.2. LocalDate . . . . . . . . . . . . . . . . . . . . . . 7 64 3.2.3. Duration . . . . . . . . . . . . . . . . . . . . . . 7 65 3.2.4. PatchObject . . . . . . . . . . . . . . . . . . . . . 7 66 3.2.5. Normalisation and equivalence . . . . . . . . . . . . 8 67 3.3. Custom property extensions and values . . . . . . . . . . 9 68 4. Common JSCalendar properties . . . . . . . . . . . . . . . . 9 69 4.1. Metadata properties . . . . . . . . . . . . . . . . . . . 9 70 4.1.1. @type . . . . . . . . . . . . . . . . . . . . . . . . 9 71 4.1.2. uid . . . . . . . . . . . . . . . . . . . . . . . . . 10 72 4.1.3. relatedTo . . . . . . . . . . . . . . . . . . . . . . 10 73 4.1.4. prodId . . . . . . . . . . . . . . . . . . . . . . . 11 74 4.1.5. created . . . . . . . . . . . . . . . . . . . . . . . 11 75 4.1.6. updated . . . . . . . . . . . . . . . . . . . . . . . 11 76 4.1.7. sequence . . . . . . . . . . . . . . . . . . . . . . 11 77 4.1.8. method . . . . . . . . . . . . . . . . . . . . . . . 11 78 4.2. What and where properties . . . . . . . . . . . . . . . . 11 79 4.2.1. title . . . . . . . . . . . . . . . . . . . . . . . . 12 80 4.2.2. description . . . . . . . . . . . . . . . . . . . . . 12 81 4.2.3. htmlDescription . . . . . . . . . . . . . . . . . . . 12 82 4.2.4. locations . . . . . . . . . . . . . . . . . . . . . . 12 83 4.2.5. links . . . . . . . . . . . . . . . . . . . . . . . . 14 84 4.2.6. locale . . . . . . . . . . . . . . . . . . . . . . . 15 85 4.2.7. keywords . . . . . . . . . . . . . . . . . . . . . . 15 86 4.2.8. categories . . . . . . . . . . . . . . . . . . . . . 16 87 4.2.9. color . . . . . . . . . . . . . . . . . . . . . . . . 16 88 4.3. Recurrence properties . . . . . . . . . . . . . . . . . . 16 89 4.3.1. recurrenceRule . . . . . . . . . . . . . . . . . . . 16 90 4.3.2. recurrenceOverrides . . . . . . . . . . . . . . . . . 18 91 4.4. Sharing and scheduling properties . . . . . . . . . . . . 19 92 4.4.1. priority . . . . . . . . . . . . . . . . . . . . . . 19 93 4.4.2. freeBusyStatus . . . . . . . . . . . . . . . . . . . 19 94 4.4.3. privacy . . . . . . . . . . . . . . . . . . . . . . . 20 95 4.4.4. replyTo . . . . . . . . . . . . . . . . . . . . . . . 21 96 4.4.5. participants . . . . . . . . . . . . . . . . . . . . 22 97 4.5. Alerts properties . . . . . . . . . . . . . . . . . . . . 25 98 4.5.1. useDefaultAlerts . . . . . . . . . . . . . . . . . . 25 99 4.5.2. alerts . . . . . . . . . . . . . . . . . . . . . . . 25 100 4.6. Multilingual properties . . . . . . . . . . . . . . . . . 28 101 4.6.1. localizations . . . . . . . . . . . . . . . . . . . . 28 102 5. Type-specific JSCalendar properties . . . . . . . . . . . . . 29 103 5.1. JSEvent properties . . . . . . . . . . . . . . . . . . . 29 104 5.1.1. start . . . . . . . . . . . . . . . . . . . . . . . . 29 105 5.1.2. timeZone . . . . . . . . . . . . . . . . . . . . . . 29 106 5.1.3. duration . . . . . . . . . . . . . . . . . . . . . . 29 107 5.1.4. isAllDay . . . . . . . . . . . . . . . . . . . . . . 29 108 5.1.5. status . . . . . . . . . . . . . . . . . . . . . . . 30 109 5.2. JSTask properties . . . . . . . . . . . . . . . . . . . . 30 110 5.2.1. due . . . . . . . . . . . . . . . . . . . . . . . . . 30 111 5.2.2. start . . . . . . . . . . . . . . . . . . . . . . . . 30 112 5.2.3. timeZone . . . . . . . . . . . . . . . . . . . . . . 30 113 5.2.4. estimatedDuration . . . . . . . . . . . . . . . . . . 31 114 5.2.5. completed . . . . . . . . . . . . . . . . . . . . . . 31 115 5.2.6. isAllDay . . . . . . . . . . . . . . . . . . . . . . 31 116 5.2.7. progress . . . . . . . . . . . . . . . . . . . . . . 31 117 5.2.8. status . . . . . . . . . . . . . . . . . . . . . . . 32 118 5.3. JSGroup properties . . . . . . . . . . . . . . . . . . . 33 119 5.3.1. entries . . . . . . . . . . . . . . . . . . . . . . . 33 120 5.3.2. source . . . . . . . . . . . . . . . . . . . . . . . 34 121 6. Conversion from and to iCalendar . . . . . . . . . . . . . . 34 122 6.1. JSEvent . . . . . . . . . . . . . . . . . . . . . . . . . 34 123 6.2. JSTask . . . . . . . . . . . . . . . . . . . . . . . . . 35 124 6.3. JSGroup . . . . . . . . . . . . . . . . . . . . . . . . . 37 125 6.4. Common properties . . . . . . . . . . . . . . . . . . . . 37 126 6.5. Locations and participants . . . . . . . . . . . . . . . 39 127 6.6. Unknown properties . . . . . . . . . . . . . . . . . . . 41 128 7. JSCalendar object examples . . . . . . . . . . . . . . . . . 41 129 7.1. Simple event . . . . . . . . . . . . . . . . . . . . . . 41 130 7.2. Simple task . . . . . . . . . . . . . . . . . . . . . . . 42 131 7.3. Simple group . . . . . . . . . . . . . . . . . . . . . . 42 132 7.4. All-day event . . . . . . . . . . . . . . . . . . . . . . 43 133 7.5. Task with a due date . . . . . . . . . . . . . . . . . . 43 134 7.6. Event with end time-zone . . . . . . . . . . . . . . . . 44 135 7.7. Floating-time event (with recurrence) . . . . . . . . . . 44 136 7.8. Event with multiple locations and localization . . . . . 45 137 7.9. Recurring event with overrides . . . . . . . . . . . . . 46 138 7.10. Recurring event with participants . . . . . . . . . . . . 47 139 8. Security Considerations . . . . . . . . . . . . . . . . . . . 48 140 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48 141 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 48 142 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 48 143 11.1. Normative References . . . . . . . . . . . . . . . . . . 48 144 11.2. Informative References . . . . . . . . . . . . . . . . . 51 145 11.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 51 147 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 51 149 1. Introduction 151 This document defines a data model for calendar event and task 152 objects, or groups of such objects, in electronic calendar 153 applications and systems. It aims to be unambiguous, extendable and 154 simple to process. 156 The key design considerations for this data model are as follows: 158 o The attributes of the calendar entry represented must be described 159 as a simple key-value pair, reducing complexity of its 160 representation. 162 o The data model should avoid all ambiguities and make it difficult 163 to make mistakes during implementation. 165 o Most of the initial set of attributes should be taken from the 166 iCalendar data format ([RFC5545], also see Section 1.1), but the 167 specification should add new attributes or value types, or not 168 support existing ones, where appropriate. Conversion between the 169 data formats need not fully preserve semantic meaning. 171 o Extensions, such as new properties and components, MUST NOT lead 172 to requiring an update to this document. 174 The representation of this data model is defined in the I-JSON format 175 [RFC7493], which is a strict subset of the JavaScript Object Notation 176 (JSON) Data Interchange Format [RFC8259]. Using JSON mostly is a 177 pragmatic choice: its widespread use should help to speed up 178 JSCalendar adoption and a wide range of production-ready JSON 179 implementations allows to decrease interoperability issues. 181 1.1. Relation to the iCalendar format 183 The iCalendar data format [RFC5545], a widely deployed interchange 184 format for calendaring and scheduling data, has served calendaring 185 vendors for a long while, but contains some ambiguities and pitfalls 186 that can not be overcome without backward-incompatible changes. 188 For example, iCalendar defines various formats for local times, UTC 189 time and dates, which confuses new users. Other sources for errors 190 are the requirement for custom time-zone definitions within a single 191 calendar component, as well as the iCalendar format itself; the 192 latter causing interoperability issues due to misuse of CR LF 193 terminated strings, line continuations and subtle differences between 194 iCalendar parsers. Lastly, up until recently the iCalendar format 195 did not allow to express the difference between two calendar 196 components, which results in verbose exchanges during scheduling. 198 Some of these issues were addressed by the jCal [RFC7265] format, 199 which is a direct mapping between iCalendar and JSON. However, it 200 did not attempt to extend or update iCalendar semantics. 202 1.2. Notational Conventions 204 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 205 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 206 document are to be interpreted as described in [RFC2119]. 208 The underlying format used for this specification is JSON. 209 Consequently, the terms "object" and "array" as well as the four 210 primitive types (strings, numbers, booleans, and null) are to be 211 interpreted as described in Section 1 of[RFC8259]. 213 Some examples in this document contain "partial" JSON documents used 214 for illustrative purposes. In these examples, three periods "..." 215 are used to indicate a portion of the document that has been removed 216 for compactness. 218 2. JSCalendar objects 220 This section describes the calendar object types specified by 221 JSCalendar. 223 2.1. JSEvent 225 MIME type: "application/calendar+json;type=jsevent" 227 A JSEvent represents a scheduled amount of time on a calendar, 228 typically a meeting, appointment, reminder or anniversary. Multiple 229 participants may partake in the event at multiple locations. 231 The @type (Section 4.1.1) property value MUST be "jsevent". 233 2.2. JSTask 235 MIME type: "application/calendar+json;type=jstask" 237 A JSTask represents an action-item, assignment, to-do or work item . 239 The @type (Section 4.1.1) property value MUST be "jstask". 241 A JSTask may start and be due at certain points in time, may take 242 some estimated time to complete and may recur; none of which is 243 required. This notably differs from JSEvent (Section 2.1) which is 244 required to start at a certain point in time and typically takes some 245 non-zero duration to complete. 247 2.3. JSGroup 249 MIME type: "application/calendar+json;type=jsgroup" 251 A JSGroup is a collection of JSEvent (Section 2.1) and JSTask 252 (Section 2.2) objects. Typically, objects are grouped by topic (e.g. 253 by keywords) or calendar membership. 255 The @type (Section 4.1.1) property value MUST be "jsgroup". 257 3. Structure of JSCalendar objects 259 A JSCalendar object is a JSON object, which MUST be valid I-JSON (a 260 stricter subset of JSON), as specified in [RFC8259]. Property names 261 and values are case-sensitive. 263 The object has a collection of properties, as specified in the 264 following sections. Unless otherwise specified, all properties are 265 optional; omitted properties MUST be treated identically to if that 266 property had the value of "null", unless otherwise specified. 268 3.1. Type signatures 270 Types signatures are given for all JSON objects in this document. 271 The following conventions are used: 273 o "Boolean|String": The value is either a JSON "Boolean" value, or a 274 JSON "String" value. 276 o "Foo": Any name that is not a native JSON type means an object for 277 which the properties (and their types) are defined elsewhere 278 within this document. 280 o "Foo[]": An array of objects of type "Foo". 282 o "String[Foo]": A JSON "Object" being used as a map (associative 283 array), where all the values are of type "Foo". 285 3.2. Data Types 287 In addition to the standard JSON data types, the following data types 288 are used in this specification: 290 3.2.1. UTCDate 292 This is a string in [RFC3339] "date-time" format, with the further 293 restrictions that any letters MUST be in upper-case, the time 294 component MUST be included and the time MUST be in UTC. Fractional 295 second values MUST NOT be included unless non-zero and MUST NOT have 296 trailing zeros, to ensure there is only a single representation for 297 each date-time. 299 For example "2010-10-10T10:10:10.003Z" is OK, but 300 "2010-10-10T10:10:10.000Z" is invalid and MUST be encoded as 301 "2010-10-10T10:10:10Z". 303 In common notation, it should be of the form "YYYY-MM-DDTHH:MM:SSZ". 305 3.2.2. LocalDate 307 This is a date-time string _with no time-zone/offset information_. 308 It is otherwise in the same format as UTCDate: "YYYY-MM-DDTHH:MM:SS". 309 The time-zone to associate the LocalDate with comes from an 310 associated property, or if no time-zone is associated it defines 311 _floating time_. Floating date-times are not tied to any specific 312 time-zone. Instead, they occur in every timezone at the same _wall- 313 clock_ time (as opposed to the same instant point in time). 315 3.2.3. Duration 317 A duration is represented by a subset of ISO8601 duration format, as 318 specified by the following ABNF: 320 dur-secfrac = "." 1*DIGIT 321 dur-second = 1*DIGIT [dur-secfrac] "S" 322 dur-minute = 1*DIGIT "M" [dur-second] 323 dur-hour = 1*DIGIT "H" [dur-minute] 324 dur-time = "T" (dur-hour / dur-minute / dur-second) 325 dur-day = 1*DIGIT "D" 327 duration = "P" (dur-day [dur-time] / dur-time) 329 In addition, the duration MUST NOT include fractional second values 330 unless the fraction is non-zero. A zero duration MUST be represented 331 as "P0D". 333 3.2.4. PatchObject 335 A *PatchObject* is of type "String[*|null]", and represents an 336 unordered set of patches on a JSON object. The keys are a path in a 337 subset of [RFC6901] JSON pointer format, with an implicit leading "/" 338 (i.e. prefix each key with "/" before applying the JSON pointer 339 evaluation algorithm). 341 A patch within a PatchObject is only valid, if all of the following 342 conditions apply: 344 1. The pointer MUST NOT reference inside an array (i.e. it MUST NOT 345 insert/delete from an array; the array MUST be replaced in its 346 entirety instead). 348 2. When evaluating a path, all parts prior to the last (i.e. the 349 value after the final slash) MUST exist. 351 3. There MUST NOT be two patches in the PatchObject where the 352 pointer of one is the prefix of the pointer of the other, e.g. 353 "alerts/1/offset" and "alerts". 355 The value associated with each pointer is either: 357 o "null": Remove the property from the patched object. If not 358 present in the parent, this a no-op. 360 o Anything else: The value to replace the inherited property on the 361 patch object with (if present) or add to the property (if not 362 present). 364 Implementations MUST reject a PatchObject if any of its patches are 365 invalid. 367 3.2.5. Normalisation and equivalence 369 JSCalendar aims to provide unambiguous definitions for value types 370 and properties, but does not define a general normalisation or 371 equivalence method for JSCalendar objects and types. This is because 372 the notion of equivalence might range from byte-level equivalence to 373 semantic equivalence, depending on the respective use case (for 374 example, the CalDAV protocol [RFC4791] requires octet equivalence of 375 the encoded calendar object to determine ETag equivalence). 377 Normalisation of JSCalendar objects is hindered because of the 378 following reasons: 380 o Custom JSCalendar properties may contain arbitrary JSON values, 381 including arrays. However, equivalence of arrays might or might 382 not depend on the order of elements, depending on the respective 383 property definition. 385 o Several JSCalendar property values are defined as URIs and MIME 386 types, but normalisation of these types is inherently protocol and 387 scheme-specific, depending on the use-case of the equivalence 388 definition (see section 6 of [RFC3986]). 390 Considering this, the definition of equivalence and normalisation is 391 left to client and server implementations and to be negotiated by a 392 calendar exchange protocol or defined by another RFC. 394 3.3. Custom property extensions and values 396 Vendors MAY add additional properties to the calendar object to 397 support their custom features. The names of these properties MUST be 398 prefixed with a domain name controlled by the vendor to avoid 399 conflict, e.g. "example.com/customprop". 401 Some JSCalendar properties allow vendor-specific value extensions. 402 If so, vendor specific values MUST be prefixed with a domain name 403 controlled by the vendor, e.g. "example.com/customrel", unless 404 otherwise noted. 406 4. Common JSCalendar properties 408 This section describes the properties that are common to the various 409 JSCalendar object types. Specific JSCalendar object types may only 410 support a subset of these properties. The object type definitions in 411 section Section 5 describe the set of supported properties per type. 413 4.1. Metadata properties 415 4.1.1. @type 417 Type: "String" 419 Specifies the type which this object represents. This MUST be one of 420 the following values, registered in a future RFC, or a vendor- 421 specific value: 423 o "jsevent": a JSCalendar event (Section 2.1). 425 o "jstask": a JSCalendar task (Section 2.2). 427 o "jsgroup": a JSCalendar group (Section 2.3). 429 A valid JSCalendar object MUST include this property. 431 4.1.2. uid 433 Type: "String" 435 A globally unique identifier, used to associate the object as the 436 same across different systems, calendars and views. The value of 437 this property MUST be unique across _all_ JSCalendar objects, even if 438 they are of different type. [RFC4122] describes a range of 439 established algorithms to generate universally unique identifiers 440 (UUID), and the random or pseudo-random version is recommended to 441 use. 443 A valid JSCalendar object MUST include this property. 445 4.1.3. relatedTo 447 Type: "String[Relation]|null" 449 Relates the object to other JSCalendar objects. This is represented 450 as a map of the uids of the related objects to information about the 451 relation. 453 A *Relation* object has the following properties: 455 o *relation*: "String[]" Describes how the linked object is related 456 to this object. 458 The strings in the array MUST each be at most one of the following 459 values, registered in a future RFC, or a vendor-specific value: 461 * "first": The linked object is the first in the series this 462 object is part of. 464 * "next": The linked object is the next in the series this object 465 is part of. 467 * "child": The linked object is a subpart of this object. 469 * "parent": This object is part of the overall linked object. 471 If an object is split to make a "this and future" change to a 472 recurrence, the original object MUST be truncated to end at the 473 previous occurrence before this split, and a new object created to 474 represent all the objects after the split. A "relation=["next"]" 475 relatedTo property MUST be set on the original object with the uid of 476 the new object. A "relation=["first"]" relatedTo property with the 477 UID of the first object in the series MUST be set on the new object. 479 Clients can then follow these UIDs to get the complete set of objects 480 if the user wishes to modify them all at once. 482 4.1.4. prodId 484 Type: "String|null" 486 The identifier for the product that created the JSCalendar object. 488 The vendor of the implementation SHOULD ensure that this is a 489 globally unique identifier, using some technique such as an FPI 490 value, as defined in [ISO.9070.1991]. 492 This property SHOULD NOT be used to alter the interpretation of an 493 JSCalendar object beyond the semantics specified in this document. 494 For example, it is not to be used to further the understanding of 495 non-standard properties. 497 4.1.5. created 499 Type: "UTCDate|null" 501 The date and time this object was initially created. 503 4.1.6. updated 505 Type: "UTCDate" 507 The date and time the data in this object was last modified. 509 4.1.7. sequence 511 Type: "Number" (Defaults to "0" if omitted) 513 Initially zero, this MUST be a non-negative integer that is 514 monotonically incremented each time a change is made to the object. 516 4.1.8. method 518 Type: "String|null" 520 The iTIP ([RFC5546]) method, in lower-case. Used for scheduling. 522 4.2. What and where properties 523 4.2.1. title 525 Type: "String" (Defaults to the empty string if omitted) 527 A short summary of the object. 529 4.2.2. description 531 Type: "String" (Defaults to the empty string if omitted) 533 A longer form description of the object. This is plain text, but a 534 client SHOULD attempt to hyperlink URLs when displaying it. 536 4.2.3. htmlDescription 538 Type: "String" (Defaults to the empty string if omitted) 540 A longer form rich-text description of the object. This is HTML text 541 [1] and allows to reference resources in the *links* property by use 542 of CID URLs (see [RFC2392]). To convert a CID URL to the *cid* 543 property value of a *Link* object, implementations MUST follow the 544 conversion described in section 2 of [RFC2392]. Implementations MAY 545 choose not to follow untrusted external CID URLs referenced in the 546 *links* property, in which case they MUST treat the *htmlDescription* 547 property as if omitted. Implementations MUST preserve the value of 548 this property, even if it contains untrusted links. 550 4.2.4. locations 552 Type: "String[Location]|null" 554 A map of location ids to Location objects, representing locations 555 associated with the object. A location id may be any string and need 556 only be unique to this object, although a UUID is a practical choice. 558 A *Location* object has the following properties. All properties are 559 optional, but every Location object MUST have at least one property: 561 o *name*: "String" The human-readable name of the location. 563 o *description*: "String" Human-readable instructions for accessing 564 this location. This may be an address, set of directions, door 565 access code, etc. 567 o *rel*: "String" The relation type of this location to the 568 JSCalendar object. 570 This MUST be either one of the following values, registered in a 571 future RFC, or a vendor-specific value. Any value the client or 572 server doesn't understand should be treated the same as "unknown". 574 * "start": The JSCalendar object starts at this location. 576 * "end": The JSCalendar object ends at this location. 578 * "virtual": This is not a physical location (e.g. this location 579 is an online chat room where people will meet). 581 * "unknown": The relation of this location to the calendar object 582 is unknown. 584 o *features*: "String[]|null" The features supported by this 585 location. 587 The strings in the array MUST each be either one of the following 588 values, registered in a future RFC, or a vendor-specific value. 589 Any value the client or server doesn't understand should be 590 ignored, but preserved. 592 The features supported by locations with rel-type "virtual" are: 594 * "audio": audio conferencing 596 * "chat": chat or instant messaging 598 * "screen": screen sharing 600 * "video": video conferencing 602 * any vendor-prefixed custom value 604 o *timeZone*: "String|null" (Defaults to "null" if omitted) A time- 605 zone for this location. 607 If "null", the *timeZone* from the JSCalendar object MUST be 608 presumed when a time-zone is needed in relation to this location. 610 o *coordinates*: "String" An [RFC5870] "geo:" URI for the location. 612 o *uri*: "String" A URI that represents how to connect to this 613 location. 615 This may be a telephone number (represented as 616 "tel:+1-555-555-555") for a teleconference, a web address for 617 online chat, or any custom URI. 619 o *linkIds*: "String[]|null" A list of ids for links to alternate 620 representations of this location. 622 For example, an alternative representation could be in vCard 623 format. If a given value does not correspond to any link id in 624 the links property of the instance, this MUST be ignored. 626 4.2.5. links 628 Type: "String[Link]|null" 630 A map of link ids to Link objects, representing external resources 631 associated with the object. A link id may be any string and need 632 only be unique to this object, although the href or a UUID are 633 practical choices. 635 A *Link* object has the following properties: 637 o *href*: "String" A URI from which the resource may be fetched. 639 This MAY be a "data:" URL, but it is recommended that the file be 640 hosted on a server to avoid embedding arbitrary large data in 641 JSCalendar object instances. 643 o *cid* "String|null" The id used within the *htmlDescription* 644 property to reference this link. 646 If not null, this MUST be a valid Content-ID MIME header value 647 (see [RFC2392]). The identifier MUST be unique within this 648 JSCalendar object but has no meaning beyond that. Specifically, 649 it MAY be different from the *Link* object identifier in the 650 enclosing *links* property. 652 o *type*: "String|null"(optional, defaults to "null") The content- 653 type [RFC6838] of the resource, if known. 655 o *size*: "Number|null"(optional, defaults to "null") The size, in 656 bytes, of the resource when fully decoded (i.e. the number of 657 bytes in the file the user would download), if known. 659 o *rel*: "String"(optional, defaults to "related") Identifies the 660 relation of the linked resource to the object. The value MUST be 661 a registered relation type (see [RFC8288] and IANA Link Relations 662 [2]). 664 Links with a rel of "enclosure" SHOULD be considered by the client 665 as attachments for download. 667 Links with a rel of "describedby" SHOULD be considered by the 668 client to be an alternate representation of the description and 669 HTML description. 671 Links with a rel of "icon" SHOULD be considered by the client to 672 be an image that it MAY use when presenting the calendar data to a 673 user. The *properties* object of this link MAY include a 674 "display" property indicating the intended purpose of this image. 675 If included, the value MUST be either one of the following values, 676 registered in a future RFC, or a vendor-specific value. 678 * "badge": an image inline with the title of the object 680 * "graphic": a full image replacement for the object itself 682 * "fullsize": an image that is used to enhance the object 684 * "thumbnail": a smaller variant of "fullsize " to be used when 685 space for the image is constrained 687 o *title*: "String|null"(optional, defaults to "null") A human- 688 readable description of the resource. 690 o *properties*: "String[String|null]|null"(optional, defaults to 691 "null") Extra metadata submitted by clients about a link. Server 692 implementations MUST preserve these properties. 694 The keys are as defined in this document, as defined in a future 695 RFC, or URIs that should be owned by the client author to avoid 696 conflicts. 698 4.2.6. locale 700 Type: "String|null" 702 The [RFC5646] language tag that best describes the locale used for 703 the calendar object, if known. 705 4.2.7. keywords 707 Type: "String[]|null" 709 A list of keywords or tags related to the object. The values are 710 free-form and do not have to follow any particular structure. 712 4.2.8. categories 714 Type: "String[]|null" 716 Specifies the categories related to the calendar object. Array 717 values MUST be URIs. In contrast to *keywords*, categories typically 718 are structured. 720 For example, a vendor owning the domain "example.com" might define 721 the categories "http://example.com/categories/sports/american- 722 football"" and "http://example.com/categories/music/r-b". 724 4.2.9. color 726 Type: "String|null" 728 Specifies a color clients MAY use when displaying this calendar 729 object. The value is a case-insensitive color name taken from the 730 CSS3 set of names, defined in Section 4.3 of W3C.REC- 731 css3-color-20110607 [3] or a CSS3 RGB color hex value. 733 4.3. Recurrence properties 735 4.3.1. recurrenceRule 737 Type: "Recurrence" 739 Defines a recurrence rule (repeating pattern) for recurring calendar 740 objects. 742 A *Recurrence* object is a JSON object mapping of a RECUR value type 743 in iCalendar, see [RFC5545] and[RFC7529]. Objects recur by applying 744 the recurrence rule (and *recurrenceOverrides*) to the *start* date/ 745 time. A JSTask (Section 2.2) without a *start* property value recurs 746 by its *due* date/time, if defined. 748 A Recurrence object has the following properties: 750 o *frequency*: "String" This MUST be one of the following values: 752 * "yearly" 754 * "monthly" 756 * "weekly" 758 * "daily" 759 * "hourly" 761 * "minutely" 763 * "secondly" 765 To convert from iCalendar, simply lower-case the FREQ part. 767 o *interval*: "Number"(optional, defaults to "1") The INTERVAL part 768 from iCal. If included, it MUST be an integer "x >= 1". 770 o *rscale*: "String"(optional, defaults to ""gregorian"") The RSCALE 771 part from iCalendar RSCALE [RFC7529], converted to lower-case. 773 o *skip*: "String"(optional, defaults to ""omit"") The SKIP part 774 from iCalendar RSCALE [RFC7529], converted to lower-case. 776 o *firstDayOfWeek*: "String"(optional, defaults to ""mo"") The WKST 777 part from iCalendar, represented as a lower-case abbreviated two- 778 letter English day of the week. If included, it MUST be one of 779 the following values: ""mo"|"tu"|"we"|"th"|"fr"|"sa"|"su"". 781 o *byDay*: "NDay[]"(optional) An *NDay* object has the following 782 properties: 784 * *day*: "String" The day-of-the-week part of the BYDAY value in 785 iCalendar, lower-cased. MUST be one of the following values: 786 ""mo"|"tu"|"we"|"th"|"fr"|"sa"|"su"". 788 * *nthOfPeriod*: "Number"(optional) The optional ordinal part of 789 the BYDAY value in iCalendar (e.g. ""+1"" or ""-3""). If 790 present, rather than representing every occurrence of the 791 weekday defined in the *day* property of this *NDay*, it 792 represents only a specific instance within the recurrence 793 period. The value can be positive or negative, but MUST NOT be 794 zero. A negative integer means nth-last of period. 796 o *byMonthDay*: "Number[]"(optional) The BYMONTHDAY part from 797 iCalendar. The array MUST have at least one entry if included. 799 o *byMonth*: "String[]"(optional) The BYMONTH part from iCalendar. 800 Each entry is a string representation of a number, starting from 801 "1" for the first month in the calendar (e.g. ""1" " means 802 ""January"" with Gregorian calendar), with an optional ""L"" 803 suffix (see [RFC7529]) for leap months (this MUST be upper-case, 804 e.g. ""3L""). The array MUST have at least one entry if included. 806 o *byYearDay*: "Number[]"(optional) The BYYEARDAY part from 807 iCalendar. The array MUST have at least one entry if included. 809 o *byWeekNo*: "Number[]"(optional) The BYWEEKNO part from iCalendar. 810 The array MUST have at least one entry if included. 812 o *byHour*: "Number[]"(optional) The BYHOUR part from iCalendar. 813 The array MUST have at least one entry if included. 815 o *byMinute*: "Number[]"(optional) The BYMINUTE part from iCalendar. 816 The array MUST have at least one entry if included. 818 o *bySecond*: "Number[]"(optional) The BYSECOND part from iCalendar. 819 The array MUST have at least one entry if included. 821 o *bySetPosition*: "Number[]"(optional) The BYSETPOS part from 822 iCalendar. The array MUST have at least one entry if included. 824 o *count*: "Number"(optional) The COUNT part from iCalendar. This 825 MUST NOT be included if an *until* property is specified. 827 o *until*: "LocalDate"(optional) The UNTIL part from iCalendar. 828 This MUST NOT be included if a *count* property is specified. 829 Note, as in iCalendar, this date is presumed to be in the time- 830 zone specified in *timeZone*. It is not a UTC time. 832 4.3.2. recurrenceOverrides 834 Type: "LocalDate[PatchObject|null]|null" 836 A map of the recurrence-ids (the date-time of the start of the 837 occurrence) to either "null", to indicate the occurrence should be 838 deleted, or an object of patches to apply to the generated occurrence 839 object. 841 If the recurrence-id does not match an expanded start date from a 842 recurrence rule, it is to be treated as an additional occurrence 843 (like an RDATE from iCalendar). The patch object may often be empty 844 in this case. 846 By default, an occurrence inherits all properties from the main 847 object except the start (or due) date-time, which is shifted to the 848 new start time. However, individual properties of the occurrence can 849 be modified by a patch, or multiple patches. 851 A pointer in the PatchObject MUST NOT start with one of the following 852 prefixes; any patch with such a key MUST be ignored: 854 o @type 856 o uid 858 o relatedTo 860 o prodId 862 o method 864 o isAllDay 866 o recurrenceRule 868 o recurrenceOverrides 870 o replyTo 872 4.4. Sharing and scheduling properties 874 4.4.1. priority 876 Type: "Number"(defaults to "0" if omitted) 878 Specifies a priority for the calendar object. This may be used as 879 part of scheduling systems to help resolve conflicts for a time 880 period. 882 The priority is specified as an integer in the range 0 to 9. A value 883 of 0 specifies an undefined priority. A value of 1 is the highest 884 priority. A value of 2 is the second highest priority. Subsequent 885 numbers specify a decreasing ordinal priority. A value of 9 is the 886 lowest priority. Other integer values are reserved for future use. 888 4.4.2. freeBusyStatus 890 Type: "String"(defaults to "busy" if omitted) 892 Specifies how this property should be treated when calculating free- 893 busy state. The value MUST be one of: 895 o ""free"": The object should be ignored when calculating whether 896 the user is busy. 898 o ""busy"": The object should be included when calculating whether 899 the user is busy. 901 4.4.3. privacy 903 Type: "String"(defaults to "public" if omitted) 905 Calendar objects are normally collected together and may be shared 906 with other users. The privacy property allows the object owner to 907 indicate that it should not be shared, or should only have the time 908 information shared but the details withheld. Enforcement of the 909 restrictions indicated by this property are up to the 910 implementations. 912 This property MUST NOT affect the information sent to scheduled 913 participants; it is only interpreted when the object is shared as 914 part of a shared calendar. 916 The value MUST be either one of the following values, registered in a 917 future RFC, or a vendor-specific value. Vendor specific values MUST 918 be prefixed with a domain name controlled by the vendor, e.g. 919 "example.com/topsecret". Any value the client or server doesn't 920 understand should be preserved but treated as equivalent to 921 "private". 923 o "public": The full details of the object are visible to those whom 924 the object's calendar is shared with. 926 o "private": The details of the object are hidden; only the basic 927 time and metadata is shared. Implementations MUST ensure the 928 following properties are stripped when the object is accessed by a 929 sharee: 931 * title 933 * description 935 * htmlDescription 937 * locations 939 * links 941 * locale 943 * localizations 945 * participants 947 * replyTo 948 In addition, any patches in "recurrenceOverrides" whose key is 949 prefixed with one of the above properties MUST be stripped. 951 o "secret": The object is hidden completely (as though it did not 952 exist) when the calendar is shared. 954 4.4.4. replyTo 956 Type: "String[String]|null" 958 Represents methods by which a participant may RSVP to the organizer 959 of the calendar object. The keys in the property value are the 960 available methods. The value is a URI to use that method. Future 961 methods may be defined in future specifications; a calendar client 962 MUST ignore any method it does not understand. 964 The following methods are defined: 966 o "imip": The organizer accepts an iMIP [RFC6047] response. The 967 value MUST be a "mailto:" URI. 969 o "web": There is a web page where the user may submit an RSVP using 970 their browser. The value MUST be an "http:" or "https:" URI 971 Template ([RFC6570]) in level 1 format. The template MAY contain 972 variables that MUST be expanded from the JSCalendar object as 973 defined in table Table 1. Calendar clients SHOULD be prepared to 974 handle authentication requests from the respective web page and 975 for the participant email, but this specification does not mandate 976 any specific mechanism. 978 +--------------+----------------------------------------------------+ 979 | Variable | Expand to | 980 +--------------+----------------------------------------------------+ 981 | email | The *email* property value of the replying | 982 | | *Participant* object. | 983 | | | 984 | uid | The *uid* property value of the JSCalendar object. | 985 | | | 986 | sequence | The *sequence* property value of the JSCalendar | 987 | | object. | 988 | | | 989 | recurrenceId | The recurrence-id when replying for a single | 990 | | occurrence of a recurring JSCalendar object. The | 991 | | value is the date-time of the non-overridden start | 992 | | as determined by expanding the *recurrenceRule* of | 993 | | the JSCalendar object. | 994 +--------------+----------------------------------------------------+ 996 Table 1: replyTo URI Template variables 998 4.4.5. participants 1000 Type: "String[Participant]|null" 1002 A map of participant ids to participants, describing their 1003 participation in the calendar object. A participant id may be any 1004 string and need only be unique to this calendar object; the email 1005 address of the participant is a good choice. 1007 A *Participant* object has the following properties. Properties are 1008 mandatory unless marked otherwise: 1010 o *name*: "String" The display name of the participant (e.g. "Joe 1011 Bloggs"). 1013 o *email*: "String" The email address for the participant. 1015 o *kind*: "String"(optional, defaults to "unknown") What kind of 1016 entity this participant is. 1018 This MUST be either one of the following values, registered in a 1019 future RFC, or a vendor-specific value. Any value the client or 1020 server doesn't understand should be treated the same as "unknown". 1022 * "individual": a single person 1024 * "group": a collection of people invited as a whole 1025 * "resource": a non-human resource, e.g. a projector 1027 * "location": a physical location involved in the calendar object 1028 that needs to be scheduled, e.g. a conference room. 1030 * "unknown": no information is available about the kind of this 1031 participant. 1033 o *roles*: "String[]" A list of roles that this participant fulfils. 1035 At least one value MUST be specified for the participant. This 1036 MUST be either one of the following values, registered in a future 1037 RFC, or a vendor-specific value. Any value the client or server 1038 doesn't understand should be preserved but ignored. 1040 * "owner": The participant is an owner of the object, and allowed 1041 to make alterations to any part of it. 1043 * "attendee": The participant is an attendee of the calendar 1044 object. Attendees are only allowed to alter their own 1045 participation. 1047 * "chair": The participant is in charge of the calendar object 1048 when it occurs. 1050 o *locationId*: "String|null"(optional, defaults to "null") The 1051 location at which this participant is expected to be attending. 1053 If the value does not correspond to any location id in the 1054 locations property of the instance, this MUST be treated the same 1055 as if the participant's locationId were specified as null. 1057 o *rsvpResponse*: "String"(optional, defaults to "needs-action") The 1058 RSVP response, if any, of this participant. 1060 The value MUST be either one of the following values, registered 1061 in a future RFC, or a vendor-specific value: 1063 * "needs-action": No status yet set by the participant. 1065 * "accepted": The invited participant will participate. 1067 * "declined": The invited participant will not participate. 1069 * "tentative": The invited participant may participate. 1071 o *participation*: "String"(optional, defaults to "required") The 1072 required participation of this participant. 1074 The value MUST be either one of the following values, registered 1075 in a future RFC, or a vendor-specific value. Any value the client 1076 or server doesn't understand should be treated the same as 1077 "required". 1079 * "non-participant": Indicates a participant who is copied for 1080 information purposes only. 1082 * "optional": Indicates a participant whose participation is 1083 optional. 1085 * "required": Indicates a participant whose participation is 1086 required. 1088 o *rsvpWanted*: "Boolean"(optional, defaults to "false") If true, 1089 the organizer is expecting the participant to notify them of their 1090 status. 1092 o *scheduleSequence*: "Number"(optional, defaults to "0") The 1093 sequence number of the last response from the participant. If 1094 defined, this MUST be a non-negative integer. 1096 This can be used to determine whether the partcipant has sent a 1097 new RSVP following significant changes to the calendar object, and 1098 to determine if future responses are responding to a current or 1099 older view of the data. 1101 o *scheduleUpdated*: "UTCDate|null"(optional, defaults to "null") 1102 The *updated* property of the last iMIP response from the 1103 participant. 1105 This can be compared to the *updated* timestamp in future iMIP 1106 responses to determine if the response is older or newer than the 1107 current data. 1109 o *invitedBy*: "String|null"(optional, defaults to "null") The 1110 participant id of the participant who invited this one, if known. 1112 o *delegatedTo*: "String[]|null"(optional, defaults to "null") A 1113 list of participant ids of participants that this participant has 1114 delegated their participation to. This MUST be omitted if none 1115 (rather than an empty array). 1117 o *delegatedFrom*: "String[]|null"(optional, defaults to "null") A 1118 list of participant ids that this participant is acting as a 1119 delegate for. This MUST be omitted if none (rather than an empty 1120 array). 1122 o *memberOf*: "String[]|null"(optional, defaults to "null") A list 1123 of group participants that were invited to this calendar object, 1124 which caused this participant to be invited due to their 1125 membership of the group(s). This MUST be omitted if none (rather 1126 than an empty array). 1128 o *linkIds*: "String[]|null"(optional, defaults to "null") Links to 1129 more information about this participant, for example in vCard 1130 format. If a given value does not correspond to any link id in 1131 the links property of the instance, this id MUST be ignored. This 1132 MUST be omitted if none (rather than an empty array). 1134 4.5. Alerts properties 1136 4.5.1. useDefaultAlerts 1138 Type: "Boolean" (defaults to "false" if omitted) 1140 If "true", use the user's default alerts and ignore the value of the 1141 *alerts* property. Fetching user defaults is dependent on the API 1142 from which this JSCalendar object is being fetched, and is not 1143 defined in this specification. If an implementation cannot determine 1144 the user's default alerts, or none are set, it MUST process the 1145 alerts property as if useDefaultAlerts is set to "false". 1147 4.5.2. alerts 1149 Type: "String[Alert]|null" 1151 A map of alert ids to Alert objects, representing alerts/reminders to 1152 display or send the user for this calendar object. An alert id may 1153 be any string and need only be unique to this calendar object, 1154 although a globally unique id is a practical choice (also see 1155 Section 4.1.2)). 1157 An *Alert* Object has the following properties: 1159 o *relativeTo*: "String" (optional, defaults to "before-start") 1160 Specifies where the offset is relative to for the alarm to 1161 trigger. The value MUST be one of: 1163 * "before-start" 1165 * "after-start" 1167 * "before-end" 1169 * "after-end" 1171 o *offset*: "Duration" The offset from the start and end/due of the 1172 calendar object to fire the alert. If the calendar object does 1173 not define a time-zone, the user's default time-zone SHOULD be 1174 used when determining the offset, if known. Otherwise, the time- 1175 zone to use is implementation specific. 1177 o *action*: "DisplayAction|EmailAction|UnknownAction" 1179 Describes how to alert the user. 1181 A *DisplayAction* means a message (which is service dependent, but 1182 SHOULD include the title and start or due time of the calendar 1183 object) SHOULD be shown to the user on any client connected to 1184 this account at the specified time. How this message is formatted 1185 (and any sound or other method of drawing the user's attention) is 1186 client specific. It has the following properties: 1188 * *type*: "String" The value MUST be "display". 1190 * *acknowledged*: "UTCDate|null " (optional) 1192 When the user has permanently dismissed the alert the client 1193 MUST set this to the current time in UTC. Other clients which 1194 sync this property can then automatically dismiss or suppress 1195 duplicate alerts (alerts with the same alert id that triggered 1196 on or before this date-time). 1198 For a recurring calendar object, the *acknowledged* property of 1199 the parent object MUST be updated, unless the alert is already 1200 overridden in *recurrenceOverrides*. 1202 * *snoozed*: "UTCDate|null" (optional) 1204 If the user temporarily dismisses the alert, this is the UTC 1205 date-time after which it should be reshown. Clients displaying 1206 this alert SHOULD hide it if the snoozed property is updated to 1207 a time in the future. When that time is reached, the alert 1208 SHOULD be reshown unless acknowledged is now after the original 1209 trigger time. 1211 Setting this property on an instance of a recurring calendar 1212 object MUST update the alarm on the master object, unless the 1213 respective instance already is defined in 1214 "recurrenceOverrides". It MUST NOT generate an override for 1215 the sole use of snoozing an alarm. 1217 * *mediaLinkIds*: "String[]|null " (optional) 1218 A list of link identifiers in the JSCalendar object *links* 1219 property. Clients SHOULD play one or more of the link contents 1220 that are supported by the client implementation and are 1221 appropriate for the given device and user context. 1223 An *EmailAction* means an email SHOULD be sent as specified in the 1224 object at the specified time. It has the following properties: 1226 * *type*: "String" The value MUST be "email". 1228 * *to*: "Emailer[]" An array of name/email objects to send the 1229 alert to. 1231 An *Emailer* object has the following properties: 1233 + name: String The name of the recipient. If not known, 1234 clients SHOULD use the empty string. 1236 + email: String The email address of the recipient. 1238 * *subject*: "String" (optional) The subject to use for the 1239 email. If omitted, this is implementation specific, but the 1240 server SHOULD try to choose an appropriate subject, e.g. by 1241 including the summary. 1243 * *textBody*: "String" (optional) The plain-text body to use for 1244 the email. If omitted, the body of the email is implementation 1245 specific, but the server SHOULD include all pertinent details 1246 about the calendar object, such as summary, location and start 1247 time. 1249 * *htmlBody*: "String" (optional) The HTML body to use for the 1250 email, with rich-media content processed as for the 1251 *htmlDescription* property of the JSCalendar object (see 1252 Section 4.2.3), e.g. all CID URLs MUST be embedded in the 1253 generated alert email HTML body, or the *htmlBody* property 1254 ignored completely. If the textBody property of this alert 1255 action is not set, the server SHOULD generate a plain-text 1256 version from the HTML body and include it in a "multipart/ 1257 alternative" MIME message. 1259 * *attachments*: "String[]|null" (optional) A list of link 1260 identifiers in the JSCalendar object links property. Included 1261 attachments SHOULD be embedded in the MIME message with the 1262 "Content-Disposition" header value set to "attachment" (see 1263 [RFC2183]). Implementations MAY refuse to include one or more 1264 attachments when building an alert email, in which case they 1265 MUST ignore the contents of the *attachments* property (e.g. 1266 they MUST NOT include a subset of attachments). 1268 An *UnknownAction* object is an object that contains a *type * 1269 property whose value is not "email" or "string", plus zero or more 1270 other properties. This is for compatibility with client 1271 extensions and future RFCs. The client or server SHOULD NOT 1272 trigger any type of alert for action types they do not understand, 1273 but MUST preserve them. 1275 4.6. Multilingual properties 1277 4.6.1. localizations 1279 Type: "String[PatchObject]|null" 1281 A map of [RFC5646] language tags to patch objects, which localise the 1282 calendar object into the locale of the respective language tag. 1284 See the description of PatchObject (Section 3.2.4) for the structure 1285 of the PatchObject. The patches are applied to the top-level object 1286 and MUST only patch the following properties: 1288 o title 1290 o description 1292 o htmlDescription 1294 o keywords 1296 o Location name 1298 o Location description 1300 o Link title 1302 o EmailAction alert subject 1304 o EmailAction alert textBody 1306 o EmailAction alert htmlBody 1308 o any Link properties entry except the "display" field 1310 o any UnknownAction alert property except the "type" field 1311 o any unknown or vendor-specific property (if not defined otherwise 1312 in a future RFC or vendor-specific extension). 1314 5. Type-specific JSCalendar properties 1316 5.1. JSEvent properties 1318 In addition to the common JSCalendar object properties (Section 4) a 1319 JSEvent has the following properties: 1321 5.1.1. start 1323 Type: "LocalDate" e.g. "2015-09-02T00:00:00" 1325 The date/time the event would start in the event's time-zone. 1327 A valid JSEvent MUST include this property. 1329 5.1.2. timeZone 1331 Type: "String|null" 1333 The IANA Time Zone Database [4] name for the time-zone the event is 1334 scheduled in, or "null" for floating time. If omitted, this MUST be 1335 presumed to be "null" (i.e. floating time). 1337 5.1.3. duration 1339 Type: "Duration", e.g. "P2DT3H" (Defaults to "P0D" if omitted) 1341 The zero or positive duration of the event in absolute time (i.e. in 1342 UTC time; ignoring DST shifts). To get the end date in the event 1343 time-zone, convert start into UTC, then add the duration, then 1344 convert the result into the appropriate time-zone. 1346 A JSEvent MAY be end in a different time-zone (e.g. a plane flight 1347 crossing time-zones). In this case, the JSEvent MUST specify the end 1348 time-zone in a *location* property value that defines its *rel* to be 1349 "end" and the end time-zone in its *timeZone* property. 1351 5.1.4. isAllDay 1353 Type: "Boolean" (optional, defaults to "false") 1355 Specifies if the event an all day event, such as a birthday or public 1356 holiday. 1358 If *isAllDay* is true, then the following restrictions apply: 1360 o the *start* property MUST have a time component of "T00:00:00". 1362 o the *duration* property MUST only include a day component. 1364 Note that all-day events MAY be bound to a specific time-zone, as 1365 defined by the *timeZone* property. 1367 5.1.5. status 1369 Type: "String" 1371 The scheduling status (Section 4.4) of a JSEvent defaults to 1372 "confirmed" if omitted. 1374 If set, it MUST be one of: 1376 o "confirmed": Indicates the event is definite. 1378 o "cancelled": Indicates the event is cancelled. 1380 o "tentative": Indicates the event is tentative. 1382 5.2. JSTask properties 1384 In addition to the common JSCalendar object properties (Section 4) a 1385 JSTask has the following properties: 1387 5.2.1. due 1389 Type: "LocalDate|null" e.g. "2015-09-02T00:00:00" 1391 The date/time the task is due in the task's time-zone. 1393 5.2.2. start 1395 Type: "LocalDate|null" e.g. "2015-09-02T00:00:00" 1397 The date/time the task should start in the task's time-zone. 1399 5.2.3. timeZone 1401 Type: "String|null" 1403 The IANA Time Zone Database name for the time-zone the task is 1404 scheduled in, or "null" for floating time. If omitted, this MUST be 1405 presumed to be "null" (i.e. floating time). 1407 5.2.4. estimatedDuration 1409 Type: "Duration|null", e.g. "P2DT3H" 1411 Specifies the estimated positive duration of time the task takes to 1412 complete. 1414 If the *start* and *due* properties are set, the estimated duration 1415 SHOULD be less than or equal to the time interval between these 1416 properties. 1418 5.2.5. completed 1420 Type: "UTCDate|null", e.g. "2016-06-13T12:00:00Z" 1422 Specifies the date/time the task was completed. 1424 If the task is recurring and has future instances, a client may want 1425 to denote a specific task recurrence as completed but leave other 1426 instances as uncompleted. One way to achieve this is by overriding 1427 the completed property in the task *recurrenceOverrides*. However, 1428 this could produce a long list of completion times for regularly 1429 recurring tasks. An alternative approach is to split the JSTask into 1430 a current, single instance of JSTask with this instance completion 1431 time and a future recurring instance. Also see the definition of the 1432 *relatedTo* on splitting. 1434 5.2.6. isAllDay 1436 Type: "Boolean" (optional, defaults to "false") 1438 Specifies if the task is an all day task. 1440 If *isAllDay* is true, then the *start* and *due* properties MUST 1441 have a time component of "T00:00:00". Note that the 1442 *estimatedDuration* property MAY contain a non-zero time duration. 1443 All-day tasks MAY be bound to a specific time-zone, as defined by the 1444 *timeZone* property. 1446 5.2.7. progress 1448 In addition to the common properties of a *Participant* object 1449 (Section 4.4.5), a Participant within a JSTask supports the following 1450 property: 1452 o *progress*: "ParticipantProgress|null" The progress of the 1453 participant for this task, if known. This property MUST be "null" 1454 if the *rsvpResponse* of this participant is any other value but 1455 "accepted". 1457 A *ParticipantProgress* object has the following properties: 1459 o *status*: "String" Describes the completion status of the 1460 participant's progress. 1462 The value MUST be at most one of the following values, registered 1463 in a future RFC, or a vendor-specific value: 1465 * "completed": The participant completed their progress. 1467 * "in-process": The participant processes this task. 1469 * "failed": The participant failed to complete their progress. 1471 o *timestamp*: "UTCDate" Describes the last time when the 1472 participant progress got updated. 1474 5.2.8. status 1476 Type: "String" 1478 If omitted, the default scheduling status (Section 4.4) of a JSTask 1479 is defined as follows (in order of evaluation): 1481 o "needs-action": if the task has no participants, or if at least 1482 one participant of the task has *rsvpResponse* set to "needs- 1483 action" (eiher explicitly or by default). 1485 o "completed": if all the *ParticipantProgress* status of the task 1486 participants is "completed". 1488 o "failed": if at least one *ParticipantProgress* status of the task 1489 participants is "failed". 1491 o "in-process": if at least one *ParticipantProgress* status of the 1492 task participants is "in-process". 1494 o "pending": If none of the other criteria match. 1496 If set, it MUST be one of: 1498 o "needs-action": Indicates the task needs action. 1500 o "completed": Indicates the task is completed. If this value is 1501 set, then the timestamp in the *completed* property MUST NOT be 1502 null. 1504 o "in-process": Indicates the task is in process. 1506 o "cancelled": Indicates the task is cancelled. 1508 o "pending": Indicates the task has been created, but not yet 1509 started. 1511 o "failed": Indicates the task failed. 1513 5.3. JSGroup properties 1515 JSGroup supports the following JSCalendar properties (Section 4): 1517 o @type 1519 o uid 1521 o created 1523 o updated 1525 o categories 1527 o keywords 1529 o name 1531 o description 1533 o htmlDescription 1535 o color 1537 o links 1539 as well as the following JSGroup-specific properties: 1541 5.3.1. entries 1543 Type: "(JSTask|JSEvent)[]|null" 1545 A list of group members. The list MAY contain multiple object types 1546 and implementations MUST ignore entries of unknown type. The 1547 property value MUST either be "null" or the list MUST NOT be empty. 1549 5.3.2. source 1551 Type: "String|null" (optional, default is "null") 1553 The source from which updated versions of this group may be retrieved 1554 from. If the value is not "null", it MUST be a URI. 1556 6. Conversion from and to iCalendar 1558 This section specifies which JSCalendar properties can be mapped from 1559 and to iCalendar format. Implementations SHOULD follow these 1560 conversion guidelines. Still, JSCalendar does not restrict itself to 1561 iCalendar and conversion between these two formats MAY be lossy. 1563 6.1. JSEvent 1565 The iCalendar counterpart to *JSEvent* is the VEVENT component type 1566 [RFC5545]. A VEVENT component that is a direct child of a VCALENDAR 1567 component is equivalent to a standalone JSEvent. A VEVENT component 1568 *within* a VEVENT maps to the entries of the JSEvent 1569 *recurrenceOverrides* property. 1571 +----------+--------------------------------------------------------+ 1572 | Property | iCalendar counterpart | 1573 +----------+--------------------------------------------------------+ 1574 | isAllDay | True, if the type of the DTSTART property in iCalendar | 1575 | | is DATE. When translating from JSCalendar the | 1576 | | iCalendar DTSTART property is of DATE value type, if | 1577 | | the *isAllDay* property is set to true and the | 1578 | | *timeZone* property is null. | 1579 | | | 1580 | start | Corresponds to the DTSTART property in iCalendar. Note | 1581 | | that time-zone information is stored separately in | 1582 | | JSEvent. | 1583 | | | 1584 | timeZone | Corresponds to the TZID part of the DTSTART property | 1585 | | in iCalendar. If the event has a different end time- | 1586 | | zone to start time-zone, this should be added as a | 1587 | | JSCalendar *location* with just a *timeZone* property | 1588 | | and "rel="end"". | 1589 | | | 1590 | duration | Corresponds to the DURATION or DSTART+DTEND properties | 1591 | | in iCalendar. | 1592 +----------+--------------------------------------------------------+ 1594 Table 2: Translation between JSEvent and iCalendar 1596 6.2. JSTask 1598 The iCalendar counterpart to *JSTask* is the VTODO component type 1599 [RFC5545]. A VTODO component that is a direct child of a VCALENDAR 1600 component is equivalent to a standalone JSTask. A VTODO component 1601 *within* a master VTODO maps to the entries of the JSTask 1602 *recurrenceOverrides* property. 1604 +-------------------+-----------------------------------------------+ 1605 | Property | iCalendar counterpart | 1606 +-------------------+-----------------------------------------------+ 1607 | isAllDay | True, if the type of the DTSTART property in | 1608 | | iCalendar is DATE. When translating from | 1609 | | JSCalendar the iCalendar DTSTART property is | 1610 | | of DATE value type, if the *isAllDay* | 1611 | | property is set to true and the *timeZone* | 1612 | | property is null. | 1613 | | | 1614 | due | Corresponds to the DUE and DTSTART+DURATION | 1615 | | properties in iCalendar. When mapping | 1616 | | iCalendar VTODOs with DTSTART+DURATION, the | 1617 | | due date is the result of adding DURATION to | 1618 | | DTSTART in the DTSTART time-zone. | 1619 | | | 1620 | start | Corresponds to the DTSTART property in | 1621 | | iCalendar. | 1622 | | | 1623 | timeZone | Corresponds to the TZID part of the | 1624 | | DTSTART/DUE properties in iCalendar. If the | 1625 | | task has a different end time-zone to start | 1626 | | or due time-zone, this should be added as a | 1627 | | JSCalendar *location* with just a *timeZone* | 1628 | | property and "rel="end"". | 1629 | | | 1630 | estimatedDuration | Corresponds to the ESTIMATED-DURATION | 1631 | | iCalendar property. *NON-STANDARD*: this | 1632 | | property is currently non-standard, see | 1633 | | [draft-apthorp-ical-tasks]. | 1634 | | | 1635 | completed | Maps to the COMPLETED iCalendar property. | 1636 | | | 1637 | progress | Corresponds to the PARTSTAT and COMPLETED | 1638 | | properties in iCalendar, including the | 1639 | | currently non-standard definitions in | 1640 | | [draft-apthorp-ical-tasks]. | 1641 | | | 1642 | status | Corresponds to the STATUS property in | 1643 | | iCalendar, including the currently non- | 1644 | | standard definitions in | 1645 | | [draft-apthorp-ical-tasks]. | 1646 +-------------------+-----------------------------------------------+ 1648 Table 3: Translation between JSTask and iCalendar 1650 6.3. JSGroup 1652 A JSGroup converts to a iCalendar VCALENDAR containing VEVENT or 1653 VTODO components. 1655 +----------+--------------------------------------------------------+ 1656 | Property | iCalendar counterpart | 1657 +----------+--------------------------------------------------------+ 1658 | entries | The VEVENT and VTODO components within a top-level | 1659 | | VCALENDAR component. | 1660 | | | 1661 | source | Corresponds to the SOURCE property in iCalendar. | 1662 +----------+--------------------------------------------------------+ 1664 Table 4: Translation between JSGroup and iCalendar 1666 6.4. Common properties 1668 +---------------------+---------------------------------------------+ 1669 | Property | iCalendar counterpart | 1670 +---------------------+---------------------------------------------+ 1671 | alerts | An *Alert* corresponds to the VALARM | 1672 | | component in iCalendar, where the *action* | 1673 | | is determined by the iCalendar ACTION | 1674 | | property value (e.g., a "DISPLAY" property | 1675 | | indicates that the JSCalendar Alert action | 1676 | | is a *DisplayAction* and similarly an | 1677 | | iCalendar "EMAIL" value for *EmailAction* | 1678 | | action). The *relativeTo* and *offset* | 1679 | | properties corresponds to the iCalendar | 1680 | | TRIGGER property. *NON-STANDARD*: The | 1681 | | iCalendar properties for JSCalendar Alert | 1682 | | actions are non-standard, see | 1683 | | [draft-daboo-valarm-extensions]. | 1684 | | | 1685 | categories | Corresponds to the STRUCTURED-CATEGORY | 1686 | | property in iCalendar, see. *NON- | 1687 | | STANDARD*: this property is currently non- | 1688 | | standard, see | 1689 | | [draft-ietf-calext-ical-relations]. | 1690 | | | 1691 | color | Corresponds to the COLOR property in | 1692 | | iCalendar, as specified in [RFC7986]. | 1693 | | | 1694 | created | Corresponds to the CREATED property in | 1695 | | iCalendar. | 1696 | | | 1697 | description | Corresponds to the DESCRIPTION property in | 1698 | | iCalendar. | 1699 | | | 1700 | htmlDescription | There is no direct equivalent in iCalendar. | 1701 | | If the *description* is empty, | 1702 | | implementations SHOUD store a plain text | 1703 | | version of *htmlDescription* in iCalendar | 1704 | | DESCRIPTION. | 1705 | | | 1706 | freeBusyStatus | Corresponds to the TRANSP property in | 1707 | | iCalendar. | 1708 | | | 1709 | keywords | Corresponds to the CATEGORIES property in | 1710 | | iCalendar, as specified in [RFC7986]. | 1711 | | | 1712 | links | Corresponds to the ATTACH ([RFC5545]) and | 1713 | | IMAGE iCalendar properties ([RFC7986]). | 1714 | | | 1715 | locale | Corresponds to the LANGUAGE parameter in | 1716 | | iCalendar, which is added to individual | 1717 | | properties. When converting from | 1718 | | iCalendar, one language must be picked as | 1719 | | the main locale for the object, and all | 1720 | | properties in other languages moved to the | 1721 | | localizations JSEvent property. | 1722 | | | 1723 | localizations | Corresponds to the LANGUAGE parameter in | 1724 | | iCalendar, which is added to individual | 1725 | | properties. When converting from | 1726 | | iCalendar, one language must be picked as | 1727 | | the main locale for the object, and all | 1728 | | properties in other languages moved to the | 1729 | | localizations JSEvent property. | 1730 | | | 1731 | locations | See Section 6.5. | 1732 | | | 1733 | method | Corresponds to the METHOD property in | 1734 | | iCalendar. | 1735 | | | 1736 | participants | See Section 6.5. | 1737 | | | 1738 | priority | Corresponds to the PRIORITY property in | 1739 | | iCalendar. | 1740 | | | 1741 | privacy | Corresponds to the CLASS property in | 1742 | | iCalendar. | 1743 | | | 1744 | prodId | Corresponds to the PRODID property in | 1745 | | iCalendar. | 1746 | | | 1747 | recurrenceOverrides | Corresponds to the RDATE and EXDATE | 1748 | | properties in iCalendar, plus VEVENT (for | 1749 | | JSEvent) or VTODO (for JSTask) instances | 1750 | | with a recurrence-id. | 1751 | | | 1752 | recurrenceRule | Corresponds to the RRULE property in | 1753 | | iCalendar. See the property definition at | 1754 | | section Section 4.3.1 how to map a RRULE | 1755 | | value. | 1756 | | | 1757 | relatedTo | Corresponds to the RELATED-TO property in | 1758 | | iCalendar. | 1759 | | | 1760 | replyTo | A *replyTo* property of type "imip" | 1761 | | corresponds to the email address of the | 1762 | | ORGANIZER property in iCalendar. There is | 1763 | | no iCalendar representation for the "web" | 1764 | | type. | 1765 | | | 1766 | sequence | Corresponds to the SEQUENCE property in | 1767 | | iCalendar. | 1768 | | | 1769 | status | Corresponds to the STATUS property in | 1770 | | iCalendar (converted to lower-case). | 1771 | | | 1772 | title | Corresponds to the SUMMARY property in | 1773 | | iCalendar. | 1774 | | | 1775 | uid | Corresponds to the UID property in | 1776 | | iCalendar. | 1777 | | | 1778 | updated | Corresponds to the DTSTAMP and LAST- | 1779 | | MODIFIED properties in iCalendar. (These | 1780 | | are only different in the iTIP case, and | 1781 | | the difference is not actually useful.) | 1782 +---------------------+---------------------------------------------+ 1784 Table 5: Translation between JSCalendar and iCalendar 1786 6.5. Locations and participants 1788 Both JSCalendar participants and locations have counterparts in 1789 iCalendar but provide richer representation. 1791 The following table outlines translation of JSCalendar participants. 1792 Where iCalendar has distinct properties for ORGANIZER and ATTENDEE, 1793 these are merged in JSCalendar into the Participant object type. 1795 +------------------+------------------------------------------------+ 1796 | Property | iCalendar counterpart | 1797 +------------------+------------------------------------------------+ 1798 | name | the CN parameter | 1799 | | | 1800 | kind | the CUTYPE parameter | 1801 | | | 1802 | rsvpResponse | the PARTSTAT parameter | 1803 | | | 1804 | role | the ORGANIZER and ATTENDEE properties. Owners | 1805 | | map to the iCalendar ORGANIZER property, where | 1806 | | mapping multiple owners to iCalendar is | 1807 | | implementation-specific but MUST be consistent | 1808 | | across mappings of the same object. | 1809 | | | 1810 | participation | the ROLE parameter | 1811 | | | 1812 | locationId | the JSCalendar identifier of a mapped | 1813 | | CONFERENCE property that has the MODERATOR | 1814 | | feature defined in its FEATURE parameter | 1815 | | values. If multiple such CONFERENCE properties | 1816 | | are defined in iCalendar, then the one with | 1817 | | the most interactive features is chosen (VIDEO | 1818 | | over AUDIO over CHAT over anything else). | 1819 | | | 1820 | rsvpWanted | the RSVP parameter | 1821 | | | 1822 | delegatedTo | the DELEGATED-TO parameter | 1823 | | | 1824 | delegatedFrom | the DELEGATED-FROM parameter | 1825 | | | 1826 | memberOf | the MEMBER parameter | 1827 | | | 1828 | scheduleSequence | the SEQUENCE property of the participant's | 1829 | | latest iMIP message | 1830 | | | 1831 | scheduleUpdated | the DTSTAMP property of the participant's | 1832 | | latest iMIP message | 1833 +------------------+------------------------------------------------+ 1835 Table 6: Translation of Participant between JSCalendar and iCalendar 1837 For JSCalendar locations, the iCalendar counterparts are the 1838 [RFC5545] LOCATION and the extended iCalendar [RFC7986] CONFERENCE 1839 properties. 1841 An iCalendar LOCATION property becomes a JSCalendar Location with 1842 just a description property. CONFERENCE property values in iCalendar 1843 map to locations with *rel* type "virtual". The location *feature* 1844 property value corresponds to the extended iCalendar FEATURE property 1845 parameter values defined in [RFC7986]. Both iCalendar PHONE and 1846 AUDIO features map to the "audio" feature and the FEED parameter 1847 value is omitted. See the mapping for *locationId* in Table 6 on how 1848 to map CONFERENCE properties that contain the MODERATOR feature. 1850 6.6. Unknown properties 1852 Both JSCalendar and iCalendar calendar objects may contain properties 1853 that are not expressible in the other format. This specification 1854 does not mandate how to preserve these properties. Instead, it 1855 leaves negotiation on how to treat unknown properties to client and 1856 server implementations and their protocol used to exchange calendar 1857 objects. 1859 Two notable options to represent and preserve arbitrary iCalendar 1860 object properties in JSCalendar are: 1862 o *JCal*: Define iCalendar properties in JCal format ([RFC7265]) in 1863 a vendor-specific property of the JCalendar object. The JCal- 1864 formatted value may either only contain iCalendar properties that 1865 were not mapped to JSCalendar properties, or contain the complete 1866 iCalendar object representation. 1868 o *Alternate link*: Define an alternate link (Section 4.2.5) value 1869 pointing to the iCalendar representation of the JSCalendar object. 1870 E.g. the alternative representation of a VEVENT would be 1871 represented as a link with rel "alternate" and type "text/ 1872 calendar;component=VEVENT". 1874 7. JSCalendar object examples 1876 The following examples illustrate several aspects of the JSCalendar 1877 data model and format. The examples may omit mandatory or additional 1878 properties, which is indicated by a placeholder property with key 1879 "...". While most of the examples use calendar event objects, they 1880 are also illustrative for tasks. 1882 7.1. Simple event 1884 This example illustrates a simple one-time event. It specifies a 1885 one-time event that begins on January 15, 2018 at 1pm New York local 1886 time and ends after 1 hour. 1888 { 1889 "@type": "jsevent", 1890 "uid": "2a358cee-6489-4f14-a57f-c104db4dc2f1", 1891 "updated": "2018-01-15T18:00:00Z", 1892 "title": "Some event", 1893 "start": "2018-01-15T13:00:00", 1894 "timeZone": "America/New_York", 1895 "duration": "PT1H" 1896 } 1898 7.2. Simple task 1900 This example illustrates a simple task for a plain to-do item. 1902 { 1903 "@type": "jstask", 1904 "uid": "2a358cee-6489-4f14-a57f-c104db4dc2f2", 1905 "updated": "2018-01-15T18:00:00Z", 1906 "title": "Do something" 1907 } 1909 7.3. Simple group 1911 This example illustrates a simple calendar object group that contains 1912 an event and a task. 1914 { 1915 "@type": "jsgroup", 1916 "uid": "2a358cee-6489-4f14-a57f-c104db4dc343", 1917 "updated": "2018-01-15T18:00:00Z", 1918 "name": "A simple group", 1919 "entries": [ 1920 { 1921 "@type": "jsevent", 1922 "uid": "2a358cee-6489-4f14-a57f-c104db4dc2f1", 1923 "updated": "2018-01-15T18:00:00Z", 1924 "title": "Some event", 1925 "start": "2018-01-15T13:00:00", 1926 "timeZone": "America/New_York", 1927 "duration": "PT1H" 1928 }, 1929 { 1930 "@type": "jstask", 1931 "uid": "2a358cee-6489-4f14-a57f-c104db4dc2f2", 1932 "updated": "2018-01-15T18:00:00Z", 1933 "title": "Do something" 1934 } 1935 ] 1936 } 1938 7.4. All-day event 1940 This example illustrates an event for an international holiday. It 1941 specifies an all-day event on April 1 that occurs every year since 1942 the year 1900. 1944 { 1945 "...": "", 1946 "title": "April Fool's Day", 1947 "isAllDay": true, 1948 "start": "1900-04-01T00:00:00", 1949 "duration": "P1D", 1950 "recurrenceRule": { 1951 "frequency": "yearly" 1952 } 1953 } 1955 7.5. Task with a due date 1957 This example illustrates a task with a due date. It is a reminder to 1958 buy groceries before 6pm Vienna local time on January 19, 2018. The 1959 calendar user expects to need 1 hour for shopping. 1961 { 1962 "...": "", 1963 "title": "Buy groceries", 1964 "due": "2018-01-19T18:00:00", 1965 "timeZone": "Europe/Vienna", 1966 "estimatedDuration": "PT1H" 1967 } 1969 7.6. Event with end time-zone 1971 This example illustrates the use of end time-zones by use of an 1972 international flight. The flight starts on April 1, 2018 at 9am in 1973 Berlin local time. The duration of the flight is scheduled at 10 1974 hours 30 minutes. The time at the flights destination is in the same 1975 time-zone as Tokyo. Calendar clients could use the end time-zone to 1976 display the arrival time in Tokyo local time and highlight the time- 1977 zone difference of the flight. 1979 { 1980 "...": "", 1981 "title": "Flight XY51 from FRA to NRT", 1982 "start": "2018-04-01T09:00:00", 1983 "timeZone": "Europe/Berlin", 1984 "duration": "PT10H30M", 1985 "locations": { 1986 "2a358cee-6489-4f14-a57f-c104db4dc2f1": { 1987 "rel": "end", 1988 "timeZone": "Asia/Tokyo" 1989 } 1990 } 1991 } 1993 7.7. Floating-time event (with recurrence) 1995 This example illustrates the use of floating-time. Since January 1, 1996 2018, a calendar user blocks 30 minutes every day to practice Yoga at 1997 7am local time, in whatever time-zone the user is located on that 1998 date. 2000 { 2001 "...": "", 2002 "title": "Yoga", 2003 "start": "2018-01-01T07:00:00", 2004 "duration": "PT30M", 2005 "recurrenceRule": { 2006 "frequency": "daily" 2007 } 2008 } 2010 7.8. Event with multiple locations and localization 2012 This example illustrates an event that happens at both a physical and 2013 a virtual location. Fans can see a live convert on premises or 2014 online. The event title and descriptions are localized. (Note: the 2015 localization of the event description contains an UTF-8 encoded 2016 German Umlaut. This character may have been replaced with ASCII 2017 characters in the plain-text rendering of this RFC document) 2019 { 2020 "...": "", 2021 "title": "Live from Music Bowl: The Band", 2022 "description": "Go see the biggest music event ever!", 2023 "locale": "en", 2024 "start": "2018-07-04T17:00:00", 2025 "timeZone": "America/New_York", 2026 "duration": "PT3H", 2027 "locations": { 2028 "9366e041-bb4c-4aa4-b249-b4657cab925c": { 2029 "name": "The Music Bowl", 2030 "description": "Music Bowl, Central Park, New York", 2031 "coordinates": "geo:40.7829,73.9654" 2032 }, 2033 "6f3696c6-1e07-47d0-9ce1-f50014b0041a": { 2034 "name": "Free live Stream from Music Bowl", 2035 "rel": "virtual", 2036 "features": [ 2037 "video", 2038 "audio", 2039 "chat" 2040 ], 2041 "uri": "https://stream.example.com/the_band_2018" 2042 } 2043 }, 2044 "localizations": { 2045 "de": { 2046 "title": "Live von der Music Bowl: The Band!", 2047 "description": "Schau dir das groesste Musikereignis an!", 2048 "locations/6f3696c6-1e07-47d0-9ce1-f50014b0041a/name": 2049 "Gratis Live-Stream aus der Music Bowl" 2050 } 2051 } 2052 } 2054 7.9. Recurring event with overrides 2056 This example illustrates the use of recurrence overrides. A math 2057 course at a University is held for the first time on January 8, 2018 2058 at 9am London time and occurs every week until June 25, 2018. Each 2059 lecture lasts for one hour and 30 minutes and is located at the 2060 Mathematics department. This event has exceptional occurrences: at 2061 the last occurrence of the course is an exam, which lasts for 2 hours 2062 and starts at 10am. Also, the location of the exam differs from the 2063 usual location. On April 2, May 7 and May 28 no course is held. 2065 { 2066 "...": "", 2067 "title": "Calculus I", 2068 "start": "2018-01-08T09:00:00", 2069 "timeZone": "Europe/London", 2070 "duration": "PT1H30M", 2071 "locations": { 2072 "2a358cee-6489-4f14-a57f-c104db4dc2f1": { 2073 "title": "Math lab room 1", 2074 "description": "Math Lab I, Department of Mathematics" 2075 } 2076 }, 2077 "recurrenceRule": { 2078 "frequency": "weekly", 2079 "until": "2018-06-25T09:00:00" 2080 }, 2081 "recurrenceOverrides": { 2082 "2018-04-02T09:00:00": null, 2083 "2018-05-07T09:00:00": null, 2084 "2018-05-28T09:00:00": null, 2085 "2018-06-25T09:00:00": { 2086 "title": "Calculus I Exam", 2087 "start": "2018-06-25T10:00:00", 2088 "duration": "PT2H", 2089 "locations": { 2090 "2a358cee-6489-4f14-a57f-c104db4dc2f1": { 2091 "title": "Big Auditorium", 2092 "description": "Big Auditorium, Other Road" 2093 } 2094 } 2095 } 2096 } 2097 } 2099 7.10. Recurring event with participants 2101 This example illustrates scheduled events. A team meeting occurs 2102 every week since January 8, 2018 at 9am Johannesburg time. The event 2103 owner also chairs the event. Participants meet in a virtual meeting 2104 room. An attendee has accepted the invitation, but on March 8, 2018 2105 he is unavailable and declined participation for this occurrence. 2107 { 2108 "...": "", 2109 "title": "FooBar team meeting", 2110 "start": "2018-01-08T09:00:00", 2111 "timeZone": "Africa/Johannesburg", 2112 "duration": "PT1H", 2113 "locations": { 2114 "2a358cee-6489-4f14-a57f-c104db4dc2f1": { 2115 "title": "ChatMe meeting room", 2116 "rel": "virtual", 2117 "features": [ 2118 "audio", 2119 "chat", 2120 "video" 2121 ], 2122 "uri": "https://chatme.example.com?id=1234567" 2123 } 2124 }, 2125 "recurrenceRule": { 2126 "frequency": "weekly" 2127 }, 2128 "replyTo": { 2129 "imip": "zoe@foobar.example.com" 2130 }, 2131 "participants": { 2132 "tom@foobar.example.com": { 2133 "name": "Tom Tool", 2134 "email": "tom@foobar.example.com", 2135 "rsvpResponse": "accepted", 2136 "roles": [ 2137 "attendee" 2138 ] 2139 }, 2140 "zoe@foobar.example.com": { 2141 "name": "Zoe Zelda", 2142 "email": "zoe@foobar.example.com", 2143 "rsvpResponse": "accepted", 2144 "roles": [ 2145 "owner", 2146 "chair" 2148 ] 2149 }, 2150 "...": "" 2151 }, 2152 "recurrenceOverrides": { 2153 "2018-03-08T09:00:00": { 2154 "participants/tom@foobar.example.com/rsvpResponse": "declined" 2155 } 2156 } 2157 } 2159 8. Security Considerations 2161 The use of JSON as a format does have its own inherent security risks 2162 as discussed in Section 12 of [RFC8259]. Even though JSON is 2163 considered a safe subset of JavaScript, it should be kept in mind 2164 that a flaw in the parser processing JSON could still impose a 2165 threat, which doesn't arise with conventional iCalendar data. 2167 With this in mind, a parser for JSON data aware of the security 2168 implications should be used for the format described in this 2169 document. For example, the use of JavaScript's "eval()" function is 2170 considered an unacceptable security risk, as described in Section 12 2171 of[RFC8259]. A native parser with full awareness of the JSON format 2172 should be preferred. 2174 9. IANA Considerations 2176 This document amends the "application/calendar" MIME media type 2177 defined in [RFC7265]. 2179 New optional parameter: "type" with value being one of "jsevent", 2180 "jstask", "jsgroup". The parameter MUST NOT occur more than once. 2182 10. Acknowledgments 2184 The authors would like to thank the members of CalConnect for their 2185 valuable contributions. This specification originated from the work 2186 of the API technical committee of CalConnect, the Calendaring and 2187 Scheduling Consortium. 2189 11. References 2191 11.1. Normative References 2193 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2194 Requirement Levels", BCP 14, RFC 2119, 2195 DOI 10.17487/RFC2119, March 1997, 2196 . 2198 [RFC2183] Troost, R., Dorner, S., and K. Moore, Ed., "Communicating 2199 Presentation Information in Internet Messages: The 2200 Content-Disposition Header Field", RFC 2183, 2201 DOI 10.17487/RFC2183, August 1997, 2202 . 2204 [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource 2205 Locators", RFC 2392, DOI 10.17487/RFC2392, August 1998, 2206 . 2208 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 2209 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 2210 . 2212 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 2213 Resource Identifier (URI): Generic Syntax", STD 66, 2214 RFC 3986, DOI 10.17487/RFC3986, January 2005, 2215 . 2217 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 2218 Unique IDentifier (UUID) URN Namespace", RFC 4122, 2219 DOI 10.17487/RFC4122, July 2005, 2220 . 2222 [RFC4791] Daboo, C., Desruisseaux, B., and L. Dusseault, 2223 "Calendaring Extensions to WebDAV (CalDAV)", RFC 4791, 2224 DOI 10.17487/RFC4791, March 2007, 2225 . 2227 [RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and 2228 Scheduling Core Object Specification (iCalendar)", 2229 RFC 5545, DOI 10.17487/RFC5545, September 2009, 2230 . 2232 [RFC5546] Daboo, C., Ed., "iCalendar Transport-Independent 2233 Interoperability Protocol (iTIP)", RFC 5546, 2234 DOI 10.17487/RFC5546, December 2009, 2235 . 2237 [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying 2238 Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646, 2239 September 2009, . 2241 [RFC5870] Mayrhofer, A. and C. Spanring, "A Uniform Resource 2242 Identifier for Geographic Locations ('geo' URI)", 2243 RFC 5870, DOI 10.17487/RFC5870, June 2010, 2244 . 2246 [RFC6047] Melnikov, A., Ed., "iCalendar Message-Based 2247 Interoperability Protocol (iMIP)", RFC 6047, 2248 DOI 10.17487/RFC6047, December 2010, 2249 . 2251 [RFC6570] Gregorio, J., Fielding, R., Hadley, M., Nottingham, M., 2252 and D. Orchard, "URI Template", RFC 6570, 2253 DOI 10.17487/RFC6570, March 2012, 2254 . 2256 [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type 2257 Specifications and Registration Procedures", BCP 13, 2258 RFC 6838, DOI 10.17487/RFC6838, January 2013, 2259 . 2261 [RFC6901] Bryan, P., Ed., Zyp, K., and M. Nottingham, Ed., 2262 "JavaScript Object Notation (JSON) Pointer", RFC 6901, 2263 DOI 10.17487/RFC6901, April 2013, 2264 . 2266 [RFC7265] Kewisch, P., Daboo, C., and M. Douglass, "jCal: The JSON 2267 Format for iCalendar", RFC 7265, DOI 10.17487/RFC7265, May 2268 2014, . 2270 [RFC7493] Bray, T., Ed., "The I-JSON Message Format", RFC 7493, 2271 DOI 10.17487/RFC7493, March 2015, 2272 . 2274 [RFC7529] Daboo, C. and G. Yakushev, "Non-Gregorian Recurrence Rules 2275 in the Internet Calendaring and Scheduling Core Object 2276 Specification (iCalendar)", RFC 7529, 2277 DOI 10.17487/RFC7529, May 2015, 2278 . 2280 [RFC7986] Daboo, C., "New Properties for iCalendar", RFC 7986, 2281 DOI 10.17487/RFC7986, October 2016, 2282 . 2284 [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data 2285 Interchange Format", STD 90, RFC 8259, 2286 DOI 10.17487/RFC8259, December 2017, 2287 . 2289 [RFC8288] Nottingham, M., "Web Linking", RFC 8288, 2290 DOI 10.17487/RFC8288, October 2017, 2291 . 2293 11.2. Informative References 2295 [draft-apthorp-ical-tasks] 2296 "Task Extensions to iCalendar", 2297 . 2299 [draft-daboo-valarm-extensions] 2300 "VALARM Extensions for iCalendar", 2301 . 2304 [draft-ietf-calext-ical-relations] 2305 "Support for iCalendar Relationships", 2306 . 2309 11.3. URIs 2311 [1] https://www.w3.org/TR/html/ 2313 [2] https://www.iana.org/assignments/link-relations/link- 2314 relations.xhtml 2316 [3] https://www.w3.org/TR/2011/REC-css3-color-20110607/#svg-color 2318 [4] http://www.iana.org/time-zones 2320 Authors' Addresses 2322 Neil Jenkins 2323 FastMail 2324 PO Box 234 2325 Collins St West 2326 Melbourne VIC 8007 2327 Australia 2329 Email: neilj@fastmailteam.com 2330 URI: https://www.fastmail.com 2331 Robert Stepanek 2332 FastMail 2333 PO Box 234 2334 Collins St West 2335 Melbourne VIC 8007 2336 Australia 2338 Email: rsto@fastmailteam.com 2339 URI: https://www.fastmail.com