idnits 2.17.1 draft-ietf-calext-eventpub-extensions-16.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 : ---------------------------------------------------------------------------- ** There are 2 instances of too long lines in the document, the longest one being 15 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC5545, updated by this document, for RFC5378 checks: 2005-10-26) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 16, 2020) is 1282 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) ** Obsolete normative reference: RFC 2426 (Obsoleted by RFC 6350) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Douglass 3 Internet-Draft Spherical Cow Group 4 Updates: 5545 (if approved) October 16, 2020 5 Intended status: Standards Track 6 Expires: April 19, 2021 8 Event Publishing Extensions to iCalendar 9 draft-ietf-calext-eventpub-extensions-16 11 Abstract 13 This specification updates RFC5545 by introducing a number of new 14 iCalendar properties and components which are of particular use for 15 event publishers and in social networking. 17 This specification also defines a new STRUCTURED-DATA property for 18 iCalendar RFC5545 to allow for data that is directly pertinent to an 19 event or task to be included with the calendar data. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on April 19, 2021. 38 Copyright Notice 40 Copyright (c) 2020 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (https://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 56 1.1. Conventions Used in This Document . . . . . . . . . . . . 3 57 1.2. Terms Used in This Document . . . . . . . . . . . . . . . 3 58 2. Components and properties . . . . . . . . . . . . . . . . . . 4 59 3. Typed References . . . . . . . . . . . . . . . . . . . . . . 4 60 3.1. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 5 61 3.1.1. Piano Concert Performance . . . . . . . . . . . . . . 5 62 3.1.2. Itineraries . . . . . . . . . . . . . . . . . . . . . 6 63 3.1.2.1. Reserving facilities . . . . . . . . . . . . . . 6 64 4. Modifications to Calendar Components . . . . . . . . . . . . 6 65 5. New Property Parameters . . . . . . . . . . . . . . . . . . . 7 66 5.1. Loctype . . . . . . . . . . . . . . . . . . . . . . . . . 8 67 5.2. Restype . . . . . . . . . . . . . . . . . . . . . . . . . 8 68 5.3. Order . . . . . . . . . . . . . . . . . . . . . . . . . . 9 69 5.4. Schema . . . . . . . . . . . . . . . . . . . . . . . . . 10 70 5.5. Derived . . . . . . . . . . . . . . . . . . . . . . . . . 11 71 6. New Properties . . . . . . . . . . . . . . . . . . . . . . . 12 72 6.1. Participant Type . . . . . . . . . . . . . . . . . . . . 12 73 6.2. Calendar Address . . . . . . . . . . . . . . . . . . . . 14 74 6.3. Styled-Description . . . . . . . . . . . . . . . . . . . 15 75 6.4. Structured-Location . . . . . . . . . . . . . . . . . . . 17 76 6.5. Structured-Resource . . . . . . . . . . . . . . . . . . . 19 77 6.6. Structured-Data . . . . . . . . . . . . . . . . . . . . . 21 78 7. New Components . . . . . . . . . . . . . . . . . . . . . . . 24 79 7.1. Participant . . . . . . . . . . . . . . . . . . . . . . . 24 80 7.2. Schedulable Participant . . . . . . . . . . . . . . . . . 26 81 8. Extended examples . . . . . . . . . . . . . . . . . . . . . . 27 82 8.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . 27 83 8.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . 28 84 9. Security Considerations . . . . . . . . . . . . . . . . . . . 28 85 9.1. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 28 86 9.2. Malicious Content . . . . . . . . . . . . . . . . . . . . 29 87 9.3. HTML Content . . . . . . . . . . . . . . . . . . . . . . 29 88 10. Privacy Considerations . . . . . . . . . . . . . . . . . . . 29 89 10.1. Tracking . . . . . . . . . . . . . . . . . . . . . . . . 29 90 10.2. Revealing Locations . . . . . . . . . . . . . . . . . . 29 91 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 92 11.1. Additional iCalendar Registrations . . . . . . . . . . . 30 93 11.1.1. Properties . . . . . . . . . . . . . . . . . . . . . 30 94 11.1.2. Parameters . . . . . . . . . . . . . . . . . . . . . 30 95 11.1.3. Components . . . . . . . . . . . . . . . . . . . . . 30 96 11.2. New Registration Tables . . . . . . . . . . . . . . . . 31 97 11.2.1. Participant Types . . . . . . . . . . . . . . . . . 31 98 11.2.2. Resource Types . . . . . . . . . . . . . . . . . . . 31 99 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 31 100 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 32 101 13.1. Normative References . . . . . . . . . . . . . . . . . . 32 102 13.2. Informative References . . . . . . . . . . . . . . . . . 33 103 Appendix A. Open issues . . . . . . . . . . . . . . . . . . . . 33 104 Appendix B. Change log . . . . . . . . . . . . . . . . . . . . . 33 105 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 36 107 1. Introduction 109 The currently existing iCalendar standard [RFC5545] lacks useful 110 methods for referencing additional, external information relating to 111 calendar components. Additionally there is no standard way to 112 provide rich text descriptions or meta-data associated with the 113 event. 115 Current practice is to embed this information as links in the 116 description or to add non-standard properties as defined in [RFC5545] 117 section 3.8.8.2. 119 This document updates [RFC5545] to define a number of properties and 120 a component referencing such external information that can provide 121 additional information about an iCalendar component. The intent is 122 to allow interchange of such information between applications or 123 systems (e.g., between clients, between client and server, and 124 between servers). Formats such as vCard [RFC2426] are likely to be 125 most useful to the receivers of such events as they may be used in 126 other applications - such as address books. 128 1.1. Conventions Used in This Document 130 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 131 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 132 "OPTIONAL" in this document are to be interpreted as described in BCP 133 14 [RFC2119] [RFC8174] when, and only when, they appear in all 134 capitals, as shown here. 136 1.2. Terms Used in This Document 138 Event: When the word 'event' is used (perhaps with a capitalised 'E' 139 we are referring to gatherings, formal or informal. For example a 140 sports event, a party or a concert. 142 Social Calendaring: Historically, calendar data and scheduling has 143 been heavily biased towards meetings in a corporate environment. 144 Some of the features defined in this document are to support a 145 more informal, i.e. social, model. For example, we may want to 146 record who is participating in a public event. 148 2. Components and properties 150 Previous extensions to the calendaring standards have been largely 151 restricted to the addition of properties or parameters. This is 152 partly because iCalendar libraries had trouble handling components 153 nested deeper than those defined in [RFC5545]. 155 In a break with this 'tradition' this specification defines 156 PARTICIPANT as a component rather than a property. This is a better 157 match for the way [W3C.REC-xml-20081126] and JSON [RFC8259] handle 158 such structures and allows richer definitions. 160 It also allows for the addition of extra properties inside the 161 component and resolves some of the problems of trying to add detailed 162 information as a parameter. 164 Many people or groups may participate in an event. The PARTICIPANT 165 component provides such detailed information. Participants may act 166 as attendees to the event (or derived events) or may just provide a 167 reference - perhaps for mailing lists. 169 3. Typed References 171 The properties defined here can all reference external meta-data 172 which may be used by applications to provide further information to 173 users. By providing type information as parameters, clients and 174 servers are able to discover interesting references and make use of 175 them, perhaps for indexing or the presenting of additional related 176 information for the user. 178 As always, clients should exercise caution in following references to 179 external data. 181 The [RFC5545] LOCATION property provides only an unstructured single 182 text value for specifying the location where an event (or task) will 183 occur. This is inadequate for use cases where structured location 184 information (e.g. address, region, country, postal code) is required 185 or preferred, and limits widespread adoption of iCalendar in those 186 settings. 188 Using STRUCTURED-LOCATION, rich information about multiple locations 189 can be communicated, for example, address, region, country, postal 190 code as well as other information such as parking availability, 191 nearby restaurants and the venue. Servers and clients can retrieve 192 the objects when storing the event and use them to index by 193 geographic location. 195 When a calendar client receives a calendar component it can search 196 the set of supplied properties looking for those of particular 197 interest. The TYPE and FMTTYPE parameters, if supplied, can be used 198 to help the selection. 200 The PARTICIPANT component is designed to handle common use cases in 201 event publication. It is generally important to provide information 202 about the organizers of such events. Sponsors wish to be referenced 203 in a prominent manner. In social calendaring it is often important 204 to identify the active participants in the event, for example a 205 school sports team, and the inactive participants, for example the 206 parents. 208 The PARTICIPANT component can also be used to provide useful extra 209 data about an attendee. For example a LOCATION property inside the 210 PARTICIPANT gives the actual location of a remote attendee. (But see 211 the note about privacy.) 213 3.1. Use Cases 215 The main motivation for these properties has been event publication 216 but there are opportunities for use elsewhere. The following use 217 cases will describe some possible scenarios. 219 3.1.1. Piano Concert Performance 221 In putting together a concert there are many participants: piano 222 tuner, performer, stage hands etc. In addition there are sponsors 223 and various contacts to be provided. There will also be a number of 224 related locations. A number of events can be created, all of which 225 relate to the performance in different ways. 227 There may be an iTip [RFC5546] meeting request for the piano tuner 228 who will arrive before the performance. Other members of staff may 229 also receive meeting requests. 231 An event can also be created for publication which will have a 232 PARTICIPANT component for the pianist providing a reference to vCard 233 [RFC2426] information about the performer. This event would also 234 hold information about parking, local subway stations and the venue 235 itself. In addition, there may be sponsorship information for 236 sponsors of the event and perhaps paid sponsorship properties 237 essentially advertising local establishments. 239 3.1.2. Itineraries 241 These additions also provide opportunities for the travel industry. 242 When booking a flight the PARTICIPANT component can be used to 243 provide references to businesses at the airports and to car hire 244 businesses at the destination. 246 The embedded location information can guide the traveler at the 247 airport or to their final destination. The contact information can 248 provide detailed information about the booking agent, the airlines, 249 car hire companies and the hotel. 251 3.1.2.1. Reserving facilities 253 For a meeting, the size of a room and the equipment needed depends to 254 some extent on the number of attendees actually in the room. 256 A meeting may have 10 attendees none of which are co-located. The 257 current ATTENDEE property does not allow for the addition of such 258 meta-data. The PARTICIPANT component allows attendees to specify 259 their location. 261 4. Modifications to Calendar Components 263 The following changes to the syntax defined in iCalendar [RFC5545] 264 are made here. New elements are defined in subsequent sections. 266 ; Addition of PARTICIPANT as a valid component 267 eventc = "BEGIN" ":" "VEVENT" CRLF 268 eventprop *alarmc *participantc 269 "END" ":" "VEVENT" CRLF 271 ; Addition of properties STYLED-DESCRIPTION, STRUCTURED-DATA, 272 ; STRUCTURED-LOCATION, STRUCTURED-RESOURCE 273 eventprop =/ *( 274 ; 275 ; The following are OPTIONAL, 276 ; and MAY occur more than once. 277 ; 278 styleddescription / strucloc / strucres / sdataprop 279 ; 280 ) 282 ; Addition of PARTICIPANT as a valid component 283 todoc = "BEGIN" ":" "VTODO" CRLF 284 todoprop *alarmc *participantc 285 "END" ":" "VTODO" CRLF 287 ; Addition of properties STYLED-DESCRIPTION, STRUCTURED-DATA, 288 ; STRUCTURED-LOCATION, STRUCTURED-RESOURCE 289 todoprop =/ *( 290 ; 291 ; The following are OPTIONAL, 292 ; and MAY occur more than once. 293 ; 294 styleddescription / strucloc / strucres / sdataprop 295 ; 296 ) 298 ; Addition of PARTICIPANT as a valid component 299 journalc = "BEGIN" ":" "VJOURNAL" CRLF 300 jourprop *participantc 301 "END" ":" "VJOURNAL" CRLF 303 ; Addition of properties STYLED-DESCRIPTION, STRUCTURED-DATA 304 jourprop =/ *( 305 ; 306 ; The following are OPTIONAL, 307 ; and MAY occur more than once. 308 ; 309 styleddescription / sdataprop 310 ; 311 ) 313 ; Addition of PARTICIPANT as a valid component 314 freebusyc = "BEGIN" ":" "VFREEBUSY" CRLF 315 fbprop *participantc 316 "END" ":" "VFREEBUSY" CRLF 318 ; Addition of property STYLED-DESCRIPTION 319 fbprop =/ *( 320 ; 321 ; The following are OPTIONAL, 322 ; and MAY occur more than once. 323 ; 324 styleddescription 325 ; 326 ) 328 5. New Property Parameters 330 This specification makes use of the LABEL parameter which is defined 331 in [RFC7986] 333 5.1. Loctype 335 Parameter name: LOCTYPE 337 Purpose: To specify the type(s) of a location. 339 Format Definition: 341 This parameter is defined by the following notation: 343 loctypeparam = "LOCTYPE" "=" quoted-string 344 *("," quoted-string) 346 Description: This parameter MAY be specified on STRUCTURED-LOCATION 347 and provides a way to differentiate multiple properties. For 348 example, it allows event producers to provide location information 349 for the venue and the parking. 351 Multiple values may be used if the location has multiple purposes, 352 for example a hotel and a restaurant. 354 Values for this parameter are taken from the values defined in 355 [RFC4589] section 3. New location types SHOULD be registered in 356 the manner laid down in section 5 of that specification. 358 5.2. Restype 360 Parameter name: RESTYPE 362 Purpose: To specify the type of resource. 364 Format Definition: 366 This parameter is defined by the following notation: 368 restypeparam = "RESTYPE" "=" restypevalue CRLF 370 restypevalue = ("ROOM" 371 / "PROJECTOR" 372 / "REMOTE-CONFERENCE-AUDIO" 373 / "REMOTE-CONFERENCE-VIDEO" 374 / iana-token) ; Other IANA-registered 375 ; values 377 Description: This parameter MAY be specified on STRUCTURED-RESOURCE 378 and provides a way to differentiate multiple properties. 380 The registered values are described below. New resource types 381 SHOULD be registered in the manner laid down in this 382 specification. 384 ROOM: A room for the event/meeting. 386 PROJECTOR: Projection equipment. 388 REMOTE-CONFERENCE-AUDIO: Audio remote conferencing facilities. 390 REMOTE-CONFERENCE-VIDEO: Video remote conferencing facilities. 392 5.3. Order 394 Parameter name: ORDER 396 Purpose: To define ordering for the associated property. 398 Format Definition: 400 This parameter is defined by the following notation: 402 orderparam = "ORDER" "=" integer ;Must be greater than or equal to 1 404 Description: The ORDER parameter is OPTIONAL and is used to indicate 405 the relative ordering of the corresponding instance of a property. 406 Its value MUST be an integer greater than or equal to 1 that 407 specifies the order with 1 being the first in the ordering. 409 When the parameter is absent, the default MUST be to interpret the 410 property instance as being ordered last, that is, the property 411 will appear after any other instances of the same property with 412 any value of ORDER. 414 When any ORDER parameters have the same value all the associated 415 properties appear as a group within which there is no defined 416 order. 418 Note that the value of this parameter is to be interpreted only in 419 relation to values assigned to other corresponding instances of 420 the same property in the same entity. 422 This parameter MUST NOT be applied to a property that does not 423 allow multiple instances. 425 Example uses: The ORDER may be applied to the PARTICIPANT-TYPE 426 property to indicate the relative importance of the participant, 427 for example as a sponsor or a performer. For example, ORDER=1 428 could define the principal performer or soloist. 430 5.4. Schema 432 Parameter Name: SCHEMA 434 Purpose: To specify the schema used for the content of a 435 "STRUCTURED-DATA" property value. 437 Format Definition: 439 This parameter is defined by the following notation: 441 schemaparam = "SCHEMA" "=" DQUOTE uri DQUOTE 443 Description: This property parameter SHOULD be specified on 444 "STRUCTURED-DATA" properties. When present it provides 445 identifying information about the nature of the content of the 446 corresponding "STRUCTURED-DATA" property value. This can be used 447 to supplement the media type information provided by the "FMTTYPE" 448 parameter on the corresponding property. 450 Example: 452 STRUCTURED-DATA;FMTTYPE=application/ld+json; 453 SCHEMA="https://schema.org/FlightReservation"; 454 ENCODING=BASE64;VALUE=BINARY:ICAgIDxzY3JpcHQgdHlwZT0iYXBwb 455 GljYXRpb24vbGQranNvbiI+CiAgICB7CiAgICAgICJAY29 456 udGV4dCI6ICJodHRwOi8vc2NoZW1hLm9yZyIsCiAgICAgICJAdHlwZSI 457 6ICJGbGlnaHRSZXNlcnZhdGlvbiIsCiAgICAgICJyZXNlcnZhdGlvbkl 458 kIjogIlJYSjM0UCIsCiAgICAgICJyZXNlcnZhdGlvblN0YXR1cyI6ICJ 459 odHRwOi8vc2NoZW1hLm9yZy9SZXNlcnZhdGlvbkNvbmZpcm1lZCIsCiA 460 gICAgICJwYXNzZW5nZXJQcmlvcml0eVN0YXR1cyI6ICJGYXN0IFRyYWN 461 rIiwKICAgICAgInBhc3NlbmdlclNlcXVlbmNlTnVtYmVyIjogIkFCQzE 462 yMyIsCiAgICAgICJzZWN1cml0eVNjcmVlbmluZyI6ICJUU0EgUHJlQ2h 463 lY2siLAogICAgICAidW5kZXJOYW1lIjogewogICAgICAgICJAdHlwZSI 464 6ICJQZXJzb24iLAogICAgICAgICJuYW1lIjogIkV2YSBHcmVlbiIKICA 465 gICAgfSwKICAgICAgInJlc2VydmF0aW9uRm9yIjogewogICAgICAgICJ 466 AdHlwZSI6ICJGbGlnaHQiLAogICAgICAgICJmbGlnaHROdW1iZXIiOiA 467 iVUExMTAiLAogICAgICAgICJwcm92aWRlciI6IHsKICAgICAgICAgICJ 468 AdHlwZSI6ICJBaXJsaW5lIiwKICAgICAgICAgICJuYW1lIjogIkNvbnR 469 pbmVudGFsIiwKICAgICAgICAgICJpYXRhQ29kZSI6ICJDTyIsCiAgICA 470 gICAgICAiYm9hcmRpbmdQb2xpY3kiOiAiaHR0cDovL3NjaGVtYS5vcmc 471 vWm9uZUJvYXJkaW5nUG9saWN5IgogICAgICAgIH0sCiAgICAgICAgInN 472 lbGxlciI6IHsKICAgICAgICAgICJAdHlwZSI6ICJBaXJsaW5lIiwKICA 473 gICAgICAgICJuYW1lIjogIlVuaXRlZCIsCiAgICAgICAgICAiaWF0YUN 474 vZGUiOiAiVUEiCiAgICAgICAgfSwKICAgICAgICAiZGVwYXJ0dXJlQWl 475 ycG9ydCI6IHsKICAgICAgICAgICJAdHlwZSI6ICJBaXJwb3J0IiwKICA 476 gICAgICAgICJuYW1lIjogIlNhbiBGcmFuY2lzY28gQWlycG9ydCIsCiA 477 gICAgICAgICAiaWF0YUNvZGUiOiAiU0ZPIgogICAgICAgIH0sCiAgICA 478 gICAgImRlcGFydHVyZVRpbWUiOiAiMjAxNy0wMy0wNFQyMDoxNTowMC0 479 wODowMCIsCiAgICAgICAgImFycml2YWxBaXJwb3J0IjogewogICAgICA 480 gICAgIkB0eXBlIjogIkFpcnBvcnQiLAogICAgICAgICAgIm5hbWUiOiA 481 iSm9obiBGLiBLZW5uZWR5IEludGVybmF0aW9uYWwgQWlycG9ydCIsCiA 482 gICAgICAgICAiaWF0YUNvZGUiOiAiSkZLIgogICAgICAgIH0sCiAgICA 483 gICAgImFycml2YWxUaW1lIjogIjIwMTctMDMtMDVUMDY6MzA6MDAtMDU 484 6MDAiCiAgICAgIH0KICAgIH0KICAgIDwvc2NyaXB0Pg== 486 5.5. Derived 488 Parameter Name: DERIVED 490 Purpose: To specify that the value of the associated property is 491 derived from some other property value or values. 493 Format Definition: 495 This parameter is defined by the following notation: 497 derivedparam = "DERIVED" "=" ("TRUE" / "FALSE") 498 ; Default is FALSE 500 Description: This property parameter MAY be specified on any 501 property when the value is derived from some other property or 502 properties. When present with a value of TRUE clients MUST NOT 503 update the property. 505 As an example, if a STYLED-DESCRIPTION property is present with 506 FMTTYPE="application/rtf" then there may be an additional STYLED- 507 DESCRIPTION property with FMTTYPE="text/html" and DERIVED=TRUE and 508 a value created from the rtf value. 510 Example: 512 STYLED-DESCRIPTION;FMTTYPE=text/html; 513 DERIVED=TRUE:... 515 6. New Properties 517 6.1. Participant Type 519 Property name: PARTICIPANT-TYPE 521 Purpose: To specify the type of participant. 523 Value type: The value type for this property is TEXT. The allowable 524 values are defined below. 526 Property Parameters: Non-standard parameters can be specified on 527 this property. 529 Conformance: This property MUST be specified once within a 530 PARTICIPANT component. 532 Description: This property defines the type of participation in 533 events or tasks. Participants can be individuals or 534 organizations, for example a soccer team, the spectators, or the 535 musicians. 537 Format Definition: 539 This property is defined by the following notation: 541 participanttype = "PARTICIPANT-TYPE" partvalueparam ":" 542 partvalue CRLF 544 partvalue = ("ACTIVE" 545 / "INACTIVE" 546 / "SPONSOR" 547 / "CONTACT" 548 / "BOOKING-CONTACT" 549 / "EMERGENCY-CONTACT" 550 / "PUBLICITY-CONTACT" 551 / "PLANNER-CONTACT" 552 / "PERFORMER" 553 / "SPEAKER" 554 / iana-token) ; Other IANA-registered 555 ; values 557 partvalueparam = *( 558 ; the following is OPTIONAL 559 ; and MAY occur more than once 560 ; 561 (";" other-param) 562 ) 564 Example: 566 The following is an example of this property: 568 PARTICIPANT-TYPE:SPEAKER 570 The registered values for the PARTICIPANT-TYPE property have the 571 meanings described here: 573 ACTIVE: A participant taking an active role - for example a team 574 member. 576 INACTIVE: A participant taking an inactive role - for example an 577 audience member. 579 SPONSOR: A sponsor of the event. The ORDER parameter may be used 580 with this participant type to define the relative order of 581 multiple sponsors. 583 CONTACT: Contact information for the event. The ORDER parameter may 584 be used with this participant type to define the relative order of 585 multiple contacts. 587 BOOKING-CONTACT: Contact information for reservations or payment 589 EMERGENCY-CONTACT: Contact in case of emergency 591 PUBLICITY-CONTACT: Contact for publicity 593 PLANNER-CONTACT: Contact for the event planner or organizer 595 PERFORMER: A performer - for example the soloist or the accompanist. 596 The ORDER parameter may be used with this participant type to 597 define the relative order of multiple performers. For example, 598 ORDER=1 could define the principal performer or soloist. 600 SPEAKER: Speaker at an event 602 6.2. Calendar Address 604 Property name: CALENDAR-ADDRESS 606 Purpose: To specify the calendar address for a participant. 608 Value type: CAL-ADDRESS 610 Property Parameters: IANA, non-standard, language, calendar user 611 type, group or list membership, participation role, participation 612 status, RSVP expectation, delegatee, delegator, sent by, common 613 name, or directory entry reference property parameters can be 614 specified on this property. 616 Additionally the schedule agent and schedule status parameters as 617 defined in [RFC6638] may be specified. 619 Conformance: This property MAY be specified once within a 620 PARTICIPANT component. 622 Description: This property provides a calendar user address for the 623 participant. If there is an ATTENDEE property with the same value 624 then the participant is schedulable. 626 If there is a related ATTENDEE proeprty then all parameters must 627 be applied in that property. 629 Format Definition: 631 This property is defined by the following notation: 633 calendaraddress = "CALENDAR-ADDRESS" caladdressparam ":" 634 cal-address CRLF 636 caladdressparam = *( 637 ; 638 ; The following are OPTIONAL, 639 ; but MUST NOT occur more than once. 640 ; 641 (";" cutypeparam) / (";" memberparam) / 642 (";" roleparam) / (";" partstatparam) / 643 (";" rsvpparam) / (";" deltoparam) / 644 (";" delfromparam) / (";" sentbyparam) / 645 (";" cnparam) / (";" dirparam) / 646 (";" languageparam) / 647 (";" scheduleagentparam) / 648 (";" schedulestatusparam) / 649 ; 650 ; The following is OPTIONAL, 651 ; and MAY occur more than once. 652 ; 653 (";" other-param) 654 ; 655 ) 657 6.3. Styled-Description 659 Property name: STYLED-DESCRIPTION 661 Purpose: This property provides for one or more rich-text 662 descriptions to replace that provided by the DESCRIPTION property. 664 Value type: There is no default value type for this property. The 665 value type can be set to URI or TEXT. Other text-based value 666 types can be used when defined in the future. Clients MUST ignore 667 any properties with value types they do not understand. 669 Property Parameters: IANA, non-standard, id, alternate text 670 representation, format type, derived and language property 671 parameters can be specified on this property. 673 Conformance: The property can be specified multiple times in the 674 "VEVENT", "VTODO", "VJOURNAL", "VFREEBUSY", "PARTICIPANT", or 675 "VALARM" calendar components. 677 If it does appear more than once there MUST be exactly one 678 instance of the property with no DERIVED parameter or 679 DERIVED=FALSE. All others MUST have DERIVED=TRUE. 681 Additionally, if there is one or more STYLED-DESCRIPTION property 682 then the DESCRIPTION property should be either absent or have the 683 parameter DERIVED=TRUE. 685 Description: This property supports rich-text descriptions, for 686 example HTML. Event publishers typically wish to provide more and 687 better formatted information about the event. 689 This property is used in the "VEVENT" and "VTODO" to capture 690 lengthy textual descriptions associated with the activity. This 691 property is used in the "VJOURNAL" calendar component to capture 692 one or more textual journal entries. This property is used in the 693 "VALARM" calendar component to capture the display text for a 694 DISPLAY category of alarm, and to capture the body text for an 695 EMAIL category of alarm. In the PARTICIPANT component it provides 696 a detailed description of the participant. 698 VALUE=TEXT is used to provide rich-text inline as the property 699 value. 701 VALUE=URI is used to provide a link to rich-text content which is 702 expected to be displayed inline as part of the event. 704 In either case the DESCRIPTION property should be absent or 705 contain a plain text rendering of the styled text. 707 Applications MAY attempt to guess the media type of the resource 708 via inspection of its content if and only if the media type of the 709 resource is not given by the "FMTTYPE" parameter. If the media 710 type remains unknown, calendar applications SHOULD treat it as 711 type "text/html" and process the content as defined in 712 [W3C.REC-html51-20171003] 714 Multiple STYLED-DESCRIPTION properties may be used to provide 715 different formats or different language variants. However all but 716 one MUST have DERIVED=TRUE. 718 Format Definition: 720 This property is defined by the following notation: 722 styleddescription = "STYLED-DESCRIPTION" styleddescparam ":" 723 styleddescval CRLF 725 styleddescparam = *( 726 ; The following is REQUIRED, 727 ; but MUST NOT occur more than once. 728 ; 729 (";" "VALUE" "=" ("URI" / "TEXT")) / 730 ; 731 ; The following are OPTIONAL, 732 ; but MUST NOT occur more than once. 733 ; 734 (";" altrepparam) / (";" languageparam) / 735 (";" fmttypeparam) / (";" derivedparam) / 736 ; 737 ; the following is OPTIONAL 738 ; and MAY occur more than once 739 ; 740 (";" other-param) 741 ) 743 styleddescval = ( uri / text ) 744 ;Value MUST match value type 746 Example: 748 The following is an example of this property. It points to an html 749 description. 751 STYLED-DESCRIPTION;VALUE=URI:http://example.org/desc001.html 753 6.4. Structured-Location 755 Property name: STRUCTURED-LOCATION 757 Purpose: This property provides a typed reference to external 758 information about the location of an event or optionally a plain 759 text typed value. 761 Value type: There is no default value type for this property. The 762 value type can be set to URI or TEXT. 764 Property Parameters: IANA, non-standard, label, loctype, related or 765 format type parameters can be specified on this property. 767 The LABEL parameter is defined in [RFC7986] 769 Conformance: This property MAY be specified zero or more times in 770 any iCalendar component. 772 Description: There may be a number of locations associated with an 773 event. This provides detailed information about these locations. 775 When used in a component the value of this property provides 776 information about the event venue or of related services such as 777 parking, dining, stations etc.. 779 When a LABEL parameter is supplied the language of the label 780 SHOULD match that of the content and of the LANGUAGE parameter if 781 present. 783 Use of the related parameter: This allows a location to define the 784 start and/or end timezone of the associated component. If a 785 location is specified with a RELATED parameter then the affected 786 DTSTART or DTEND properties MUST be specified as floating DATE- 787 TIME value. 789 If the RELATED parameter is present with a value of START, then 790 the "DTSTART" property MUST be present in the associated "VEVENT" 791 or "VTODO" calendar component. 793 For an event, if the RELATED parameter is present with a value of 794 END, then the "DTEND" property or the "DTSTART" and "DURATION " 795 properties MUST be present in the associated "VEVENT" calendar 796 component. 798 For a to-do with a RELATED value of END, then either the "DUE" 799 property or the "DTSTART" and "DURATION " properties MUST be 800 present in the associated "VTODO" calendar component. 802 If there is a location specified with RELATED=START and no 803 location is specified with RELATED=END then the event is assumed 804 to start and end in the same timezone. 806 Format Definition: 808 This property is defined by the following notation: 810 strucloc = "STRUCTURED-LOCATION" struclocparam ":" 811 struclocval CRLF 813 struclocparam = *( 814 ; The following is REQUIRED, 815 ; but MUST NOT occur more than once. 816 ; 817 (";" "VALUE" "=" ("URI" / "TEXT")) / 818 ; 819 ; the following are OPTIONAL 820 ; but MUST NOT occur more than once 821 ; 822 (";" fmttypeparam) / 823 (";" labelparam) / 824 (";" languageparam) / 825 (";" trigrelparam) / 826 (";" loctypeparam) / 827 ; 828 ; the following is OPTIONAL 829 ; and MAY occur more than once 830 ; 831 (";" other-param) 832 ) 834 struclocval = ( uri / text ) 835 ;Value MUST match value type 837 Example: 839 The following is an example of this property. It points to a venue. 841 STRUCTURED-LOCATION;LABEL="The venue"; 842 VALUE=URI: 843 http://dir.example.com/venues/big-hall.vcf 845 6.5. Structured-Resource 847 Property name: STRUCTURED-RESOURCE 849 Purpose: This property provides a typed reference to external 850 information about a resource or optionally a plain text typed 851 value. Typically a resource is anything that might be required or 852 used by a calendar entity and possibly has a directory entry. 854 Value type: There is no default value type for this property. The 855 value type can be set to URI or TEXT. 857 Property Parameters: IANA, non-standard, label, restype or format 858 type parameters can be specified on this property. 860 The LABEL parameter is defined in [RFC7986] 862 Conformance: The property can be specified multiple times in the 863 "VEVENT" or "VTODO" calendar components. 865 Description: When used in a component the value of this property 866 provides information about resources used for the event such as 867 rooms, projectors, conferencing capabilities. 869 Such resources may be a room or a projector. This RESTYPE value 870 registry provides a place in which resource types may be 871 registered for use by scheduling services. 873 When a LABEL parameter is supplied the language of the label must 874 match that of the content and of the LANGUAGE parameter if 875 present. 877 Format Definition: 879 This property is defined by the following notation: 881 strucres = "STRUCTURED-RESOURCE" strucresparam ":" 882 strucresval CRLF 884 strucresparam = *( 885 ; The following is REQUIRED, 886 ; but MUST NOT occur more than once. 887 ; 888 (";" "VALUE" "=" ("URI" / "TEXT")) / 889 ; 890 ; the following are OPTIONAL 891 ; but MUST NOT occur more than once 892 ; 893 (";" fmttypeparam) / 894 (";" labelparam) / 895 (";" languageparam) / 896 (";" restypeparam) / 897 ; 898 ; the following is OPTIONAL 899 ; and MAY occur more than once 900 ; 901 (";" other-param) 902 ) 904 strucresval = ( uri / text ) 905 ;Value MUST match value type 907 Example: 909 The following is an example of this property. It refers to a 910 projector. 912 STRUCTURED-RESOURCE;value=uri;restype="projector": 913 http://dir.example.com/projectors/3d.vcf 915 6.6. Structured-Data 917 Property Name: STRUCTURED-DATA 919 Purpose: This property specifies ancillary data associated with the 920 calendar component. 922 Value Type: TEXT, BINARY or URI 924 Property Parameters: IANA, non-standard, inline encoding, and value 925 data type property parameters can be specified on this property. 927 The format type and schema parameters can be specified on this 928 property and are RECOMMENDED for text or inline binary encoded 929 content information. 931 Conformance: This property can be specified multiple times in an 932 iCalendar object. Typically it would be used in "VEVENT", 933 "VTODO", or "VJOURNAL" calendar components. 935 Description: The existing properties in iCalendar cover key elements 936 of events and tasks such as start time, end time, location, 937 summary, etc. However, different types of events often have other 938 specific "fields" that it is useful to include in the calendar 939 data. For example, an event representing an airline flight could 940 include the airline, flight number, departure and arrival airport 941 codes, check-in and gate-closing times etc. As another example, a 942 sporting event might contain information about the type of sport, 943 the home and away teams, the league the teams are in, information 944 about nearby parking, etc. 946 This property is used to specify ancillary data in some structured 947 format either directly (inline) as a "TEXT" or "BINARY" value, or 948 as a link via a "URI" value. 950 Rather than define new iCalendar properties for the variety of 951 event types that might occur, it would be better to leverage 952 existing schemas for such data. For example, schemas available at 953 https://schema.org include different event types. By using 954 standard schemas, interoperability can be improved between 955 calendar clients and non-calendaring systems that wish to generate 956 or process the data. 958 This property allows the direct inclusion of ancillary data whose 959 schema is defined elsewhere. This property also includes 960 parameters to clearly identify the type of the schema being used 961 so that clients can quickly and easily spot what is relevant 962 within the calendar data and present that to users or process it 963 within the calendaring system. 965 iCalendar does support an "ATTACH" property which can be used to 966 include documents or links to documents within the calendar data. 967 However, that property does not allow data to be included as a 968 "TEXT" value (a feature that "STRUCTURED-DATA" does allow), plus 969 attachments are often treated as "opaque" data to be processed by 970 some other system rather than the calendar client. Thus the 971 existing "ATTACH" property is not sufficient to cover the specific 972 needs of inclusion of schema data. Extending the "ATTACH" 973 property to support a new value type would likely cause 974 interoperability problems. Additionally some implementations 975 manage attachments by stripping them out and replacing with a link 976 to the resource. Thus a new property to support inclusion of 977 schema data is warranted. 979 Format Definition: 981 This property is defined by the following notation: 983 sdataprop = "STRUCTURED-DATA" sdataparam 984 ( 985 ";" "VALUE" "=" "TEXT" 986 ":" text 987 ) / 988 ( 989 ";" "ENCODING" "=" "BASE64" 990 ";" "VALUE" "=" "BINARY" 991 ":" binary 992 ) / 993 ( 994 ";" "VALUE" "=" "URI" 995 ":" uri 996 ) 997 CRLF 999 sdataparam = *( 1000 ; 1001 ; The following is OPTIONAL for a URI value, 1002 ; REQUIRED for a TEXT or BINARY value, 1003 ; and MUST NOT occur more than once. 1004 ; 1005 (";" fmttypeparam) / 1006 (";" schemaparam) / 1007 ; 1008 ; The following is OPTIONAL, 1009 ; and MAY occur more than once. 1010 ; 1011 (";" other-param) 1012 ; 1013 ) 1015 Example: The following is an example of this property: 1017 STRUCTURED-DATA;FMTTYPE=application/ld+json; 1018 SCHEMA="https://schema.org/SportsEvent"; 1019 VALUE=TEXT:{\n 1020 "@context": "http://schema.org"\,\n 1021 "@type": "SportsEvent"\,\n 1022 "homeTeam": "Pittsburgh Pirates"\,\n 1023 "awayTeam": "San Francisco Giants"\n 1024 }\n 1026 7. New Components 1028 7.1. Participant 1030 Component name: PARTICIPANT 1032 Purpose: This component provides information about a participant in 1033 an event or task. 1035 Conformance: This component can be specified multiple times in a 1036 "VEVENT", "VTODO", "VJOURNAL", or "VFREEBUSY" calendar component. 1038 Description: This component provides information about a participant 1039 in a calendar component. A participant may be an attendee in a 1040 scheduling sense and the ATTENDEE property may be specified in 1041 addition. Participants can be individuals or organizations, for 1042 example a soccer team, the spectators, or the musicians. 1044 STRUCTURED-DATA properties if present may refer to external 1045 definitions of the participant - such as a vCard. 1047 The CALENDAR-ADDRESS property if present will provide a cal- 1048 address. If an ATTENDEE property has the same value the 1049 participant is considered schedulable. The PARTICIPANT component 1050 can be used to contain additional meta-data related to the 1051 attendee. 1053 Format Definition: 1055 This component is defined by the following notation: 1057 participantc = "BEGIN" ":" "PARTICIPANT" CRLF 1058 partprop 1059 "END" ":" "PARTICIPANT" CRLF 1061 partprop = *( 1062 ; 1063 ; The following are REQUIRED, 1064 ; but MUST NOT occur more than once. 1065 ; 1066 participanttype / uid / 1067 ; 1068 ; The following are OPTIONAL, 1069 ; but MUST NOT occur more than once. 1070 ; 1071 created / description / dtstamp / geo / last-mod / 1072 priority / seq / status / calendaraddress / 1073 summary / url / 1074 ; 1075 ; The following are OPTIONAL, 1076 ; and MAY occur more than once. 1077 ; 1078 attach / categories / comment / 1079 contact / location / rstatus / related / 1080 resources / strucloc / strucres / styleddescription / 1081 sdataprop / iana-prop 1082 ; 1083 ) 1085 Note: When the PRIORITY is supplied it defines the ordering of 1086 PARTICIPANT components with the same value for the TYPE parameter. 1088 Privacy Issues: When a LOCATION is supplied it provides information 1089 about the location of a participant at a given time or times. 1090 This may represent an unacceptable privacy risk for some 1091 participants. User agents MUST NOT broadcast this information 1092 without the participant's express permission. For further 1093 comments see Section 10 1095 Example: 1097 The following is an example of this component. It contains a 1098 STRUCTURED-DATA property which points to a vCard providing 1099 information about the event participant. 1101 BEGIN:PARTICIPANT 1102 PARTICIPANT-TYPE:PERFORMER 1103 STRUCTURED-DATA;VALUE=URI:http://dir.example.com/vcard/aviolinist.vcf 1104 END:PARTICIPANT 1106 Example: 1108 The following is an example for the primary contact. 1110 BEGIN: PARTICIPANT 1111 STRUCTURED-DATA;VALUE=URI; 1112 http://dir.example.com/vcard/contacts/contact1.vcf 1113 PARTICIPANT-TYPE:CONTACT 1114 DESCRIPTION:A contact 1115 END:PARTICIPANT 1117 7.2. Schedulable Participant 1119 A PARTICIPANT component may represent someone or something that needs 1120 to be scheduled as defined for ATTENDEE in [RFC5545] and [RFC5546]. 1121 The PARTICIPANT component may also represent someone or something 1122 that is NOT to receive scheduling messages. 1124 For backwards compatibility wuth existing clients and servers when 1125 used to schedule events and tasks the ATTENDEE property MUST be used 1126 to specify the sheduling parameters as defined for that property. 1128 For other, future uses the CALENDAR-ADDRESS property MUST be used to 1129 specify those parameters. 1131 A PARTICIPANT component is defined to be schedulable if 1133 o It contains a CALENDAR-ADDRESS property 1135 o That property value is the same as the value for an ATTENDEE 1136 property. 1138 If both of these conditions apply then the participant defined by the 1139 value of the URL property will take part in scheduling operations as 1140 defined in [RFC5546]. 1142 An appropriate use for the PARTICIPANT component in scheduling would 1143 be to store SEQUENCE and DTSTAMP properties associated with replies 1144 from each ATTENDEE. A LOCATION property within the PARTICIPANT 1145 component might allow better selection of meeting times when 1146 participants are in different timezones. 1148 8. Extended examples 1150 The following are some examples of the use of the properties defined 1151 in this specification. They include additional properties defined in 1152 [RFC7986] which includes IMAGE. 1154 8.1. Example 1 1156 The following is an example of a VEVENT describing a concert. It 1157 includes location information for the venue itself as well as 1158 references to parking and restaurants. 1160 BEGIN:VEVENT 1161 CREATED:20200215T145739Z 1162 DESCRIPTION: Piano Sonata No 3\n 1163 Piano Sonata No 30 1164 DTSTAMP:20200215T145739Z 1165 DTSTART;TZID=America/New_York:20200315T150000Z 1166 DTEND;TZID=America/New_York:20200315T163000Z 1167 LAST-MODIFIED:20200216T145739Z 1168 SUMMARY:Beethoven Piano Sonatas 1169 UID:123456 1170 STRUCTURED-LOCATION;LABEL="The venue";VALUE=URI: 1171 http://dir.example.com/venues/big-hall.vcf 1172 STRUCTURED-LOCATION;LABEL="Parking for the venue";VALUE=URI: 1173 http://dir.example.com/venues/parking.vcf 1174 IMAGE;VALUE=URI;DISPLAY=BADGE;FMTTYPE=image/png:h 1175 ttp://example.com/images/concert.png 1176 BEGIN:PARTICIPANT 1177 PARTICIPANT-TYPE:SPONSOR 1178 UID:dG9tQGZvb2Jhci5xlLmNvbQ 1179 STRUCTURED-DATA;VALUE=URI:http://example.com/sponsor.vcf 1180 END:PARTICIPANT 1181 BEGIN:PARTICIPANT 1182 PARTICIPANT-TYPE:PERFORMER: 1183 UID:em9lQGZvb2GFtcGxlLmNvbQ 1184 STRUCTURED-DATA;VALUE=URI:http://www.example.com/people/johndoe.vcf 1185 END:PARTICIPANT 1186 END:VEVENT 1188 8.2. Example 2 1190 The following is an example of a VEVENT describing a meeting. One of 1191 the attendees is a remote participant. 1193 BEGIN:VEVENT 1194 CREATED:20200215T145739Z 1195 DTSTAMP:20200215T145739Z 1196 DTSTART;TZID=America/New_York:20200315T150000Z 1197 DTEND;TZID=America/New_York:20200315T163000Z 1198 LAST-MODIFIED:20200216T145739Z 1199 SUMMARY:Conference planning 1200 UID:123456 1201 ORGANIZER:mailto:a@example.com 1202 ATTENDEE;PARTSTAT=ACCEPTED;CN=A:mailto:a@example.com 1203 ATTENDEE;RSVP=TRUE;CN=B:mailto:b@example.com 1204 BEGIN:PARTICIPANT 1205 PARTICIPANT-TYPE:ACTIVE: 1206 UID:v39lQGZvb2GFtcGxlLmNvbQ 1207 STRUCTURED-DATA;VALUE=URI:http://www.example.com/people/b.vcf 1208 LOCATION:At home 1209 END:PARTICIPANT 1210 END:VEVENT 1212 9. Security Considerations 1214 This specification extends [RFC5545] and makes further use of 1215 possibly linked data. While calendar data is not unique in this 1216 regard it is worth reminding implementors of some of the dangers and 1217 safeguards. 1219 9.1. URIs 1221 See [RFC3986] for a discussion of the security considerations 1222 relating to URIs. 1224 Fetching remote resources carries inherent risks. Connections must 1225 only be allowed on well known ports, using allowed protocols 1226 (generally just HTTP/HTTPS on their default ports). The URL must be 1227 resolved externally and not allowed to access internal resources. 1228 Connecting to an external source reveals IP (and therefore generally 1229 location) information. 1231 A maliciously constructed iCalendar object may contain a very large 1232 number of URIs. In the case of published calendars with a large 1233 number of subscribers, such objects could be widely distributed. 1234 Implementations should be careful to limit the automatic fetching of 1235 linked resources to reduce the risk of this being an amplification 1236 vector for a denial-of-service attack. 1238 9.2. Malicious Content 1240 For the "STRUCTURED-DATA" property, servers need to be aware that a 1241 client could attack underlying storage by sending extremely large 1242 values and could attack processing time by uploading a recurring 1243 event with a large number of overrides and then repeatedly adding, 1244 updating, and deleting structured data. 1246 Malicious content could be introduced into the calendar server by way 1247 of the "STRUCTURED-DATA" property, and propagated to many end users 1248 via scheduling. Servers SHOULD check this property for malicious or 1249 inappropriate content. Upon detecting such content, servers SHOULD 1250 remove the property, 1252 9.3. HTML Content 1254 When processing HTML content, applications need to be aware of the 1255 many security and privacy issues, as described in the IANA 1256 considerations section of [W3C.REC-html51-20171003] 1258 10. Privacy Considerations 1260 10.1. Tracking 1262 Properties with a "URI" value type can expose their users to privacy 1263 leaks as any network access of the URI data can be tracked. Clients 1264 SHOULD NOT automatically download data referenced by the URI without 1265 explicit instruction from users. 1267 To help alleviate some of the concerns protocols and services could 1268 provide proxy services for downloading referenced data. 1270 10.2. Revealing Locations 1272 The addition of location information to the new participant component 1273 provides information about the location of participants at a given 1274 time. This information MUST NOT be distributed to other participants 1275 without that participants express permission. 1277 The same may be true of other information contained in the 1278 participant component. In general, revealing only as much as is 1279 absolutely necessary should be the approach 1280 For example, there may be some privacy considerations relating to the 1281 ORDER parameter, as it provides an indication of the organizer's 1282 perception of the relative importance of other participants. 1284 11. IANA Considerations 1286 11.1. Additional iCalendar Registrations 1288 11.1.1. Properties 1290 This document defines the following new iCalendar properties to be 1291 added to the registry defined in Section 8.2.3 of [RFC5545]: 1293 +---------------------+---------+----------------------+ 1294 | Property | Status | Reference | 1295 +---------------------+---------+----------------------+ 1296 | CALENDAR-ADDRESS | Current | RFCXXXX, Section 6.2 | 1297 | PARTICIPANT-TYPE | Current | RFCXXXX, Section 6.1 | 1298 | STRUCTURED-DATA | Current | RFCXXXX, Section 6.6 | 1299 | STYLED-DESCRIPTION | Current | RFCXXXX, Section 6.3 | 1300 | STRUCTURED-LOCATION | Current | RFCXXXX, Section 6.4 | 1301 | STRUCTURED-RESOURCE | Current | RFCXXXX, Section 6.5 | 1302 +---------------------+---------+----------------------+ 1304 11.1.2. Parameters 1306 This document defines the following new iCalendar property parameters 1307 to be added to the registry defined in Section 8.2.4 of [RFC5545]: 1309 +--------------------+---------+----------------------+ 1310 | Property Parameter | Status | Reference | 1311 +--------------------+---------+----------------------+ 1312 | LOCTYPE | Current | RFCXXXX, Section 5.1 | 1313 | ORDER | Current | RFCXXXX, Section 5.3 | 1314 | RESTYPE | Current | RFCXXXX, Section 5.2 | 1315 | SCHEMA | Current | RFCXXXX, Section 5.4 | 1316 +--------------------+---------+----------------------+ 1318 11.1.3. Components 1320 This document defines the following new iCalendar components to be 1321 added to the registry defined in Section 8.3.1 of [RFC5545]: 1323 +-------------+---------+----------------------+ 1324 | Component | Status | Reference | 1325 +-------------+---------+----------------------+ 1326 | PARTICIPANT | Current | RFCXXXX, Section 7.1 | 1327 +-------------+---------+----------------------+ 1329 11.2. New Registration Tables 1331 This section defines new registration tables for PARTICIPANT-TYPE and 1332 RESTYPE values. These tables are updated using the same approaches 1333 laid down in Section 8.2.1 of [RFC5545] 1335 11.2.1. Participant Types 1337 The following table has been used to initialize the participant types 1338 registry. 1340 +-------------------+---------+----------------------+ 1341 | Participant Type | Status | Reference | 1342 +-------------------+---------+----------------------+ 1343 | ACTIVE | Current | RFCXXXX, Section 6.1 | 1344 | INACTIVE | Current | RFCXXXX, Section 6.1 | 1345 | SPONSOR | Current | RFCXXXX, Section 6.1 | 1346 | CONTACT | Current | RFCXXXX, Section 6.1 | 1347 | BOOKING-CONTACT | Current | RFCXXXX, Section 6.1 | 1348 | EMERGENCY-CONTACT | Current | RFCXXXX, Section 6.1 | 1349 | PUBLICITY-CONTACT | Current | RFCXXXX, Section 6.1 | 1350 | PLANNER-CONTACT | Current | RFCXXXX, Section 6.1 | 1351 | PERFORMER | Current | RFCXXXX, Section 6.1 | 1352 | SPEAKER | Current | RFCXXXX, Section 6.1 | 1353 +-------------------+---------+----------------------+ 1355 11.2.2. Resource Types 1357 The following table has been used to initialize the resource types 1358 registry. 1360 +-------------------------+---------+----------------------+ 1361 | Resource Type | Status | Reference | 1362 +-------------------------+---------+----------------------+ 1363 | PROJECTOR | Current | RFCXXXX, Section 5.2 | 1364 | ROOM | Current | RFCXXXX, Section 5.2 | 1365 | REMOTE-CONFERENCE-AUDIO | Current | RFCXXXX, Section 5.2 | 1366 | REMOTE-CONFERENCE-VIDEO | Current | RFCXXXX, Section 5.2 | 1367 +-------------------------+---------+----------------------+ 1369 12. Acknowledgements 1371 The author would like to thank Chuck Norris of eventful.com for his 1372 work which led to the development of this RFC. 1374 The author would also like to thank the members of CalConnect, The 1375 Calendaring and Scheduling Consortium, the Event Publication 1376 technical committee and the following individuals for contributing 1377 their ideas and support: 1379 Cyrus Daboo, John Haug, Dan Mendell, Ken Murchison, Scott Otis. 1381 13. References 1383 13.1. Normative References 1385 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1386 Requirement Levels", BCP 14, RFC 2119, 1387 DOI 10.17487/RFC2119, March 1997, 1388 . 1390 [RFC2426] Dawson, F. and T. Howes, "vCard MIME Directory Profile", 1391 RFC 2426, DOI 10.17487/RFC2426, September 1998, 1392 . 1394 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 1395 Resource Identifier (URI): Generic Syntax", STD 66, 1396 RFC 3986, DOI 10.17487/RFC3986, January 2005, 1397 . 1399 [RFC4589] Schulzrinne, H. and H. Tschofenig, "Location Types 1400 Registry", RFC 4589, DOI 10.17487/RFC4589, July 2006, 1401 . 1403 [RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and 1404 Scheduling Core Object Specification (iCalendar)", 1405 RFC 5545, DOI 10.17487/RFC5545, September 2009, 1406 . 1408 [RFC5546] Daboo, C., Ed., "iCalendar Transport-Independent 1409 Interoperability Protocol (iTIP)", RFC 5546, 1410 DOI 10.17487/RFC5546, December 2009, 1411 . 1413 [RFC6638] Daboo, C. and B. Desruisseaux, "Scheduling Extensions to 1414 CalDAV", RFC 6638, DOI 10.17487/RFC6638, June 2012, 1415 . 1417 [RFC7986] Daboo, C., "New Properties for iCalendar", RFC 7986, 1418 DOI 10.17487/RFC7986, October 2016, 1419 . 1421 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 1422 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 1423 May 2017, . 1425 [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data 1426 Interchange Format", STD 90, RFC 8259, 1427 DOI 10.17487/RFC8259, December 2017, 1428 . 1430 [W3C.REC-html51-20171003] 1431 Faulkner, S., Eicholz, A., Leithead, T., and A. Danilo, 1432 "HTML 5.1 2nd Edition", World Wide Web Consortium 1433 Recommendation REC-html51-20171003, October 2017, 1434 . 1436 [W3C.REC-xml-20081126] 1437 Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., and 1438 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth 1439 Edition)", World Wide Web Consortium Recommendation REC- 1440 xml-20081126, November 2008, 1441 . 1443 13.2. Informative References 1445 [iana-property-registry] 1446 "IANA iCalendar Element Registries", 1447 . 1450 Appendix A. Open issues 1452 None at the moment 1454 Appendix B. Change log 1456 To be deleted on publication 1458 calext-v16 2019-10-09 MD 1460 o Make LOCTYPE multi-valued. 1462 o Add all ATTENDEE scheduling parameters to CALENDAR-ADDRESS. 1464 calext-v15 2019-10-08 MD 1466 o Address various DICUSS points. 1468 calext-v14 2019-06-11 MD 1470 o Definition of event and social calendaring. 1472 o Remove redefinition of SOURCE - use STRUCTURED-DATA. 1474 calext-v13 2019-05-26 MD 1476 o Respond to various issues. 1478 calext-v12 2019-02-28 MD 1480 o Fix styled-description example. Respond to various AD issues. 1481 Some typos. 1483 calext-v11 2019-02-27 MD 1485 o Add DERIVED parameter for styled-description, RELATED parameter 1486 for structured-location 1488 calext-v09 2018-08-30 MD 1490 o Sorted out inconsistencies in refs to 5546 1492 calext-v08 2018-07-06 MD 1494 o Add some text for equal ORDER values 1496 o Switched scheduleaddress to calendaraddress in participant abnf. 1497 Also added more properties 1499 o Fixed PARTICIPANT abnf 1501 calext-v04 2017-10-11 MD 1503 o Change SCHEDULE-ADDRESS to CALENDAR-ADDRESS 1505 o Explicitly broaden scope of SOURCE 1507 o Add initial registry for RESTYPE and move new tables into separate 1508 section. 1510 o Fix PARTTYPE/PARTICIPANT-TYPE inconsistency 1512 calext-v03 2017-10-09 MD 1514 o Mostly typographical and other minor changes 1516 calext-v02 2017-04-20 MD 1518 o Add SCHEDULE-ADDRESS property 1520 o PARTICIPANT becomes a component rather than a property. Turn many 1521 of the former parameters into properties. 1523 o Use existing ATTENDEE property for scheduling. 1525 calext-v01 2017-02-18 MD 1527 o Change ASSOCIATE back to PARTICIPANT 1529 o PARTICIPANT becomes a component rather than a property. Turn many 1530 of the former parameters into properties. 1532 calext-v00 2016-08-?? MD 1534 o Name changed - taken up by calext working group 1536 v06 2016-06-26 MD 1538 o Fix up abnf 1540 o change ref to ietf from daboo 1542 o take out label spec - use Cyrus spec 1544 v05 2016-06-14 MD 1546 o Remove GROUP and HASH. they can be dealt with elsewhere if desired 1548 o Change ORDER to integer >= 1. 1550 o Incorporate Structured-Data into this specification. 1552 v04 2014-02-01 MD 1554 o Added updates attribute. 1556 o Minor typos. 1558 o Resubmitted mostly to refresh the draft. 1560 v03 2013-03-06 MD 1562 o Replace PARTICIPANT with ASSOCIATE plus related changes. 1564 o Added section showing modifications to components. 1566 o Replace ID with GROUP and modify HASH. 1568 o Replace TITLE param with LABEL. 1570 o Fixed STYLED-DESCRIPTION in various ways, correct example. 1572 v02 2012-11-02 MD 1574 o Collapse sections with description of properties and the use cases 1575 into a section with sub-sections. 1577 o New section to describe relating properties. 1579 o Remove idref and upgrade hash to have the reference 1581 o No default value types on properties.. 1583 v01 2012-10-18 MD Many changes. 1585 o SPONSOR and STRUCTURED-CONTACT are now in PARTICIPANT 1587 o Add a STRUCTURED-RESOURCE property 1589 o STYLED-DESCRIPTION to handle rich text 1591 o Much more... 1593 2011-01-07 1595 o Remove MEDIA - it's going in the Cyrus RFC 1597 o Rename EXTENDED-... to STRUCTURED-... 1599 o Add TYPE parameter to SPONSOR 1601 v00 2007-10-19 MD Initial version 1603 Author's Address 1605 Michael Douglass 1606 Spherical Cow Group 1607 226 3rd Street 1608 Troy, NY 12180 1609 USA 1611 Email: mdouglass@sphericalcowgroup.com 1612 URI: http://sphericalcowgroup.com