idnits 2.17.1 draft-ietf-calext-eventpub-extensions-17.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 seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). (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 (January 3, 2021) is 1203 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: 1 error (**), 0 flaws (~~), 2 warnings (==), 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 Bedework 4 Updates: 5545 (if approved) January 3, 2021 5 Intended status: Standards Track 6 Expires: July 7, 2021 8 Event Publishing Extensions to iCalendar 9 draft-ietf-calext-eventpub-extensions-17 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 July 7, 2021. 38 Copyright Notice 40 Copyright (c) 2021 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 . . . . . . . . . . . . . . . . . . . . . 5 63 3.1.2.1. Reserving facilities . . . . . . . . . . . . . . 6 64 4. Modifications to Calendar Components . . . . . . . . . . . . 6 65 5. New Property Parameters . . . . . . . . . . . . . . . . . . . 7 66 5.1. Order . . . . . . . . . . . . . . . . . . . . . . . . . . 7 67 5.2. Schema . . . . . . . . . . . . . . . . . . . . . . . . . 8 68 5.3. Derived . . . . . . . . . . . . . . . . . . . . . . . . . 9 69 6. New Properties . . . . . . . . . . . . . . . . . . . . . . . 10 70 6.1. Location Type . . . . . . . . . . . . . . . . . . . . . . 10 71 6.2. Participant Type . . . . . . . . . . . . . . . . . . . . 11 72 6.3. Resource Type . . . . . . . . . . . . . . . . . . . . . . 12 73 6.4. Calendar Address . . . . . . . . . . . . . . . . . . . . 13 74 6.5. Styled-Description . . . . . . . . . . . . . . . . . . . 14 75 6.6. Structured-Data . . . . . . . . . . . . . . . . . . . . . 16 76 7. New Components . . . . . . . . . . . . . . . . . . . . . . . 18 77 7.1. Participant . . . . . . . . . . . . . . . . . . . . . . . 18 78 7.1.1. Schedulable Participant . . . . . . . . . . . . . . . 20 79 7.2. Location . . . . . . . . . . . . . . . . . . . . . . . . 21 80 7.3. Resource . . . . . . . . . . . . . . . . . . . . . . . . 22 81 8. Extended examples . . . . . . . . . . . . . . . . . . . . . . 23 82 8.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . 24 83 8.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . 24 84 9. Security Considerations . . . . . . . . . . . . . . . . . . . 25 85 9.1. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 25 86 9.2. Malicious Content . . . . . . . . . . . . . . . . . . . . 26 87 9.3. HTML Content . . . . . . . . . . . . . . . . . . . . . . 26 88 10. Privacy Considerations . . . . . . . . . . . . . . . . . . . 26 89 10.1. Tracking . . . . . . . . . . . . . . . . . . . . . . . . 26 90 10.2. Revealing Locations . . . . . . . . . . . . . . . . . . 26 91 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 92 11.1. Additional iCalendar Registrations . . . . . . . . . . . 27 93 11.1.1. Properties . . . . . . . . . . . . . . . . . . . . . 27 94 11.1.2. Parameters . . . . . . . . . . . . . . . . . . . . . 27 95 11.1.3. Components . . . . . . . . . . . . . . . . . . . . . 27 96 11.2. New Registration Tables . . . . . . . . . . . . . . . . 28 97 11.2.1. Participant Types . . . . . . . . . . . . . . . . . 28 98 11.2.2. Resource Types . . . . . . . . . . . . . . . . . . . 28 99 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 29 100 13. Normative References . . . . . . . . . . . . . . . . . . . . 29 101 Appendix A. Open issues . . . . . . . . . . . . . . . . . . . . 30 102 Appendix B. Change log . . . . . . . . . . . . . . . . . . . . . 30 103 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 33 105 1. Introduction 107 The currently existing iCalendar standard [RFC5545] lacks useful 108 methods for referencing additional, external information relating to 109 calendar components. Additionally there is no standard way to 110 provide rich text descriptions or meta-data associated with the 111 event. 113 Current practice is to embed this information as links in the 114 description or to add non-standard properties as defined in [RFC5545] 115 section 3.8.8.2. 117 This document updates [RFC5545] to define a number of properties and 118 components referencing such external information that can provide 119 additional information about an iCalendar component. The intent is 120 to allow interchange of such information between applications or 121 systems (e.g., between clients, between client and server, and 122 between servers). Formats such as vCard [RFC2426] are likely to be 123 most useful to the receivers of such events as they may be used in 124 other applications - such as address books. 126 1.1. Conventions Used in This Document 128 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 129 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY" and 130 "OPTIONAL" in this document are to be interpreted as described in BCP 131 14 [RFC2119] [RFC8174] when, and only when, they appear in all 132 capitals, as shown here. 134 1.2. Terms Used in This Document 136 Event: When the (perhaps with a capitalised 'E') word 'event' is 137 used we are referring to gatherings, formal or informal. For 138 example a sports event, a party or a concert. 140 Social Calendaring: Historically, calendar data and scheduling has 141 been heavily biased towards meetings in a corporate environment. 142 Some of the features defined in this document are to support a 143 more informal, i.e. social, model. For example, we may want to 144 record who is participating in a public event. 146 2. Components and properties 148 Previous extensions to the calendaring standards have been largely 149 restricted to the addition of properties or parameters. This is 150 partly because iCalendar libraries had trouble handling components 151 nested deeper than those defined in [RFC5545]. 153 In a break with this 'tradition' this specification defines a number 154 of components rather than properties. This is a better match for the 155 way [W3C.REC-xml-20081126] and JSON [RFC8259] handle such structures 156 and allows richer definitions. 158 It also allows for the addition of extra properties inside the 159 components and resolves some of the problems of trying to add 160 detailed information as a parameter. 162 3. Typed References 164 The properties and components defined here can all reference external 165 meta-data which may be used by applications to provide further 166 information to users. By providing type information, clients and 167 servers are able to discover interesting references and make use of 168 them, perhaps for indexing or the presenting of additional related 169 information for the user. 171 As always, clients should exercise caution in following references to 172 external data. 174 The [RFC5545] LOCATION property provides only an unstructured single 175 text value for specifying the location where an event (or task) will 176 occur. This is inadequate for use cases where structured location 177 information (e.g. address, region, country, postal code) is required 178 or preferred, and limits widespread adoption of iCalendar in those 179 settings. 181 Using the VLOCATION component, rich information about multiple 182 locations can be communicated in a STRUCTURED-DATA property, for 183 example, address, region, country, postal code as well as other 184 information such as parking availability, nearby restaurants and the 185 venue. Servers and clients can retrieve the objects when storing the 186 event and use them to index by geographic location. 188 When a calendar client receives a calendar component it can search 189 the set of locations looking for those of particular interest. The 190 LOCATION-TYPE property and STRUCTURED-DATA FMTTYPE parameter, if 191 supplied, can be used to help the selection. 193 The PARTICIPANT component is designed to handle common use cases in 194 event publication. It is generally important to provide information 195 about the organizers of such events. Sponsors wish to be referenced 196 in a prominent manner. In social calendaring it is often important 197 to identify the active participants in the event, for example a 198 school sports team, and the inactive participants, for example the 199 parents. 201 The PARTICIPANT component can be used to provide useful extra data 202 about an attendee. For example a location inside the PARTICIPANT 203 gives the actual location of a remote attendee. (But see the note 204 about privacy.) 206 Alternatively the PARTICIPANT component can be used to provide a 207 reference - perhaps the address for mailing lists. 209 3.1. Use Cases 211 The main motivation for these changes has been event publication but 212 there are opportunities for use elsewhere. The following use cases 213 will describe some possible scenarios. 215 3.1.1. Piano Concert Performance 217 In putting together a concert there are many participants: piano 218 tuner, performer, stage hands etc. In addition there are sponsors 219 and various contacts to be provided. There will also be a number of 220 related locations. A number of events can be created, all of which 221 relate to the performance in different ways. 223 There may be an iTip [RFC5546] meeting request for the piano tuner 224 who will arrive before the performance. Other members of staff may 225 also receive meeting requests. 227 An event can also be created for publication which will have a 228 PARTICIPANT component for the pianist providing a reference to vCard 229 [RFC2426] information about the performer. This event would also 230 hold information about parking, local subway stations and the venue 231 itself. In addition, there may be sponsorship information for 232 sponsors of the event and perhaps paid sponsorship properties 233 essentially advertising local establishments. 235 3.1.2. Itineraries 237 These additions also provide opportunities for the travel industry. 238 When booking a flight the PARTICIPANT component can be used to 239 provide references to businesses at the airports and to car hire 240 businesses at the destination. 242 The embedded location information can guide the traveler at the 243 airport or to their final destination. The contact information can 244 provide detailed information about the booking agent, the airlines, 245 car hire companies and the hotel. 247 3.1.2.1. Reserving facilities 249 For a meeting, the size of a room and the equipment needed depends to 250 some extent on the number of attendees actually in the room. 252 A meeting may have many attendees none of which are co-located. The 253 current ATTENDEE property does not allow for the addition of such 254 meta-data. The PARTICIPANT component allows attendees to specify 255 their location. 257 4. Modifications to Calendar Components 259 The following changes to the syntax defined in iCalendar [RFC5545] 260 are made here. New elements are defined in subsequent sections. 262 ; Addition of PARTICIPANT, VLOCATION and VRESOURCE 263 ; as valid components 264 eventc = "BEGIN" ":" "VEVENT" CRLF 265 eventprop *alarmc *participantc *locationc *resourcec 266 "END" ":" "VEVENT" CRLF 268 ; Addition of properties STYLED-DESCRIPTION and STRUCTURED-DATA 269 eventprop =/ *styleddescription 270 *sdataprop 272 ; Addition of PARTICIPANT, VLOCATION and VRESOURCE 273 ; as valid components 274 todoc = "BEGIN" ":" "VTODO" CRLF 275 todoprop *alarmc *participantc *locationc *resourcec 276 "END" ":" "VTODO" CRLF 278 ; Addition of properties STYLED-DESCRIPTION, STRUCTURED-DATA 279 todoprop =/ *styleddescription 280 *sdataprop 282 ; Addition of PARTICIPANT, VLOCATION and VRESOURCE 283 ; as valid components 284 journalc = "BEGIN" ":" "VJOURNAL" CRLF 285 jourprop *participantc *locationc *resourcec 286 "END" ":" "VJOURNAL" CRLF 288 ; Addition of properties STYLED-DESCRIPTION, STRUCTURED-DATA 289 jourprop =/ *styleddescription 290 *sdataprop 292 ; Addition of PARTICIPANT, VLOCATION and VRESOURCE 293 ; as valid components 294 freebusyc = "BEGIN" ":" "VFREEBUSY" CRLF 295 fbprop *participantc *locationc *resourcec 296 "END" ":" "VFREEBUSY" CRLF 298 ; Addition of property STYLED-DESCRIPTION 299 fbprop =/ *styleddescription 301 5. New Property Parameters 303 5.1. Order 305 Parameter name: ORDER 307 Purpose: To define ordering for the associated property. 309 Format Definition: 311 This parameter is defined by the following notation: 313 orderparam = "ORDER" "=" integer 314 ; Must be greater than or equal to 1 316 Description: The ORDER parameter is OPTIONAL and is used to indicate 317 the relative ordering of the corresponding instance of a property. 318 Its value MUST be an integer greater than or equal to 1 that 319 specifies the order with 1 being the first in the ordering. 321 When the parameter is absent, the default MUST be to interpret the 322 property instance as being ordered last, that is, the property 323 will appear after any other instances of the same property with 324 any value of ORDER. 326 When any ORDER parameters have the same value all the associated 327 properties appear as a group within which there is no defined 328 order. 330 Note that the value of this parameter is to be interpreted only in 331 relation to values assigned to other corresponding instances of 332 the same property in the same entity. 334 This parameter MUST NOT be applied to a property that does not 335 allow multiple instances. 337 Example uses: The ORDER may be applied to the PARTICIPANT-TYPE 338 property to indicate the relative importance of the participant, 339 for example as a sponsor or a performer. For example, ORDER=1 340 could define the principal performer or soloist. 342 5.2. Schema 344 Parameter Name: SCHEMA 346 Purpose: To specify the schema used for the content of a 347 "STRUCTURED-DATA" property value. 349 Format Definition: 351 This parameter is defined by the following notation: 353 schemaparam = "SCHEMA" "=" DQUOTE uri DQUOTE 355 Description: This property parameter SHOULD be specified on 356 "STRUCTURED-DATA" properties. When present it provides 357 identifying information about the nature of the content of the 358 corresponding "STRUCTURED-DATA" property value. This can be used 359 to supplement the media type information provided by the "FMTTYPE" 360 parameter on the corresponding property. 362 Example: 364 STRUCTURED-DATA;FMTTYPE=application/ld+json; 365 SCHEMA="https://schema.org/FlightReservation"; 366 ENCODING=BASE64;VALUE=BINARY:ICAgIDxzY3JpcHQgdHlwZT0iYXBwb 367 GljYXRpb24vbGQranNvbiI+CiAgICB7CiAgICAgICJAY29 368 udGV4dCI6ICJodHRwOi8vc2NoZW1hLm9yZyIsCiAgICAgICJAdHlwZSI 369 6ICJGbGlnaHRSZXNlcnZhdGlvbiIsCiAgICAgICJyZXNlcnZhdGlvbkl 370 kIjogIlJYSjM0UCIsCiAgICAgICJyZXNlcnZhdGlvblN0YXR1cyI6ICJ 371 odHRwOi8vc2NoZW1hLm9yZy9SZXNlcnZhdGlvbkNvbmZpcm1lZCIsCiA 372 gICAgICJwYXNzZW5nZXJQcmlvcml0eVN0YXR1cyI6ICJGYXN0IFRyYWN 373 rIiwKICAgICAgInBhc3NlbmdlclNlcXVlbmNlTnVtYmVyIjogIkFCQzE 374 yMyIsCiAgICAgICJzZWN1cml0eVNjcmVlbmluZyI6ICJUU0EgUHJlQ2h 375 lY2siLAogICAgICAidW5kZXJOYW1lIjogewogICAgICAgICJAdHlwZSI 376 6ICJQZXJzb24iLAogICAgICAgICJuYW1lIjogIkV2YSBHcmVlbiIKICA 377 gICAgfSwKICAgICAgInJlc2VydmF0aW9uRm9yIjogewogICAgICAgICJ 378 AdHlwZSI6ICJGbGlnaHQiLAogICAgICAgICJmbGlnaHROdW1iZXIiOiA 379 iVUExMTAiLAogICAgICAgICJwcm92aWRlciI6IHsKICAgICAgICAgICJ 380 AdHlwZSI6ICJBaXJsaW5lIiwKICAgICAgICAgICJuYW1lIjogIkNvbnR 381 pbmVudGFsIiwKICAgICAgICAgICJpYXRhQ29kZSI6ICJDTyIsCiAgICA 382 gICAgICAiYm9hcmRpbmdQb2xpY3kiOiAiaHR0cDovL3NjaGVtYS5vcmc 383 vWm9uZUJvYXJkaW5nUG9saWN5IgogICAgICAgIH0sCiAgICAgICAgInN 384 lbGxlciI6IHsKICAgICAgICAgICJAdHlwZSI6ICJBaXJsaW5lIiwKICA 385 gICAgICAgICJuYW1lIjogIlVuaXRlZCIsCiAgICAgICAgICAiaWF0YUN 386 vZGUiOiAiVUEiCiAgICAgICAgfSwKICAgICAgICAiZGVwYXJ0dXJlQWl 387 ycG9ydCI6IHsKICAgICAgICAgICJAdHlwZSI6ICJBaXJwb3J0IiwKICA 388 gICAgICAgICJuYW1lIjogIlNhbiBGcmFuY2lzY28gQWlycG9ydCIsCiA 389 gICAgICAgICAiaWF0YUNvZGUiOiAiU0ZPIgogICAgICAgIH0sCiAgICA 390 gICAgImRlcGFydHVyZVRpbWUiOiAiMjAxNy0wMy0wNFQyMDoxNTowMC0 391 wODowMCIsCiAgICAgICAgImFycml2YWxBaXJwb3J0IjogewogICAgICA 392 gICAgIkB0eXBlIjogIkFpcnBvcnQiLAogICAgICAgICAgIm5hbWUiOiA 393 iSm9obiBGLiBLZW5uZWR5IEludGVybmF0aW9uYWwgQWlycG9ydCIsCiA 394 gICAgICAgICAiaWF0YUNvZGUiOiAiSkZLIgogICAgICAgIH0sCiAgICA 395 gICAgImFycml2YWxUaW1lIjogIjIwMTctMDMtMDVUMDY6MzA6MDAtMDU 396 6MDAiCiAgICAgIH0KICAgIH0KICAgIDwvc2NyaXB0Pg== 398 5.3. Derived 400 Parameter Name: DERIVED 402 Purpose: To specify that the value of the associated property is 403 derived from some other property value or values. 405 Format Definition: 407 This parameter is defined by the following notation: 409 derivedparam = "DERIVED" "=" ("TRUE" / "FALSE") 410 ; Default is FALSE 412 Description: This property parameter MAY be specified on any 413 property when the value is derived from some other property or 414 properties. When present with a value of TRUE clients MUST NOT 415 update the property. 417 As an example, if a STYLED-DESCRIPTION property is present with 418 FMTTYPE="application/rtf" then there may be an additional STYLED- 419 DESCRIPTION property with FMTTYPE="text/html" and DERIVED=TRUE and 420 a value created from the rtf value. 422 Example: 424 STYLED-DESCRIPTION;FMTTYPE=text/html; 425 DERIVED=TRUE:... 427 6. New Properties 429 This specification makes use of the NAME property which is defined in 430 [RFC7986] 432 6.1. Location Type 434 Property name: LOCATION-TYPE 436 Purpose: To specify the type(s) of a location. 438 Value type: The value type for this property is TEXT. The allowable 439 values are defined below. 441 Description: This property MAY be specified in VLOCATION components 442 and provides a way to differentiate multiple locations. For 443 example, it allows event producers to provide location information 444 for the venue and the parking. 446 Format Definition: 448 This property is defined by the following notation: 450 loctype = "LOCATION-TYPE" ":" text *("," text) 451 CRLF 453 Multiple values may be used if the location has multiple purposes, 454 for example a hotel and a restaurant. 456 Values for this parameter are taken from the values defined in 457 [RFC4589] section 3. New location types SHOULD be registered in 458 the manner laid down in section 5 of that specification. 460 6.2. Participant Type 462 Property name: PARTICIPANT-TYPE 464 Purpose: To specify the type of participant. 466 Value type: The value type for this property is TEXT. The allowable 467 values are defined below. 469 Property Parameters: Non-standard parameters can be specified on 470 this property. 472 Conformance: This property MUST be specified once within a 473 PARTICIPANT component. 475 Description: This property defines the type of participation in 476 events or tasks. Participants can be individuals or 477 organizations, for example a soccer team, the spectators, or the 478 musicians. 480 Format Definition: 482 This property is defined by the following notation: 484 participanttype = "PARTICIPANT-TYPE" partvalueparam ":" 485 partvalue CRLF 487 partvalue = ("ACTIVE" 488 / "INACTIVE" 489 / "SPONSOR" 490 / "CONTACT" 491 / "BOOKING-CONTACT" 492 / "EMERGENCY-CONTACT" 493 / "PUBLICITY-CONTACT" 494 / "PLANNER-CONTACT" 495 / "PERFORMER" 496 / "SPEAKER" 497 / iana-token) ; Other IANA-registered 498 ; values 500 partvalueparam = *(";" other-param) 502 Example: 504 The following is an example of this property: 506 PARTICIPANT-TYPE:SPEAKER 508 The registered values for the PARTICIPANT-TYPE property have the 509 meanings described here: 511 ACTIVE: A participant taking an active role - for example a team 512 member. 514 INACTIVE: A participant taking an inactive role - for example an 515 audience member. 517 SPONSOR: A sponsor of the event. The ORDER parameter may be used 518 with this participant type to define the relative order of 519 multiple sponsors. 521 CONTACT: Contact information for the event. The ORDER parameter may 522 be used with this participant type to define the relative order of 523 multiple contacts. 525 BOOKING-CONTACT: Contact information for reservations or payment 527 EMERGENCY-CONTACT: Contact in case of emergency 529 PUBLICITY-CONTACT: Contact for publicity 531 PLANNER-CONTACT: Contact for the event planner or organizer 533 PERFORMER: A performer - for example the soloist or the accompanist. 534 The ORDER parameter may be used with this participant type to 535 define the relative order of multiple performers. For example, 536 ORDER=1 could define the principal performer or soloist. 538 SPEAKER: Speaker at an event 540 6.3. Resource Type 542 Property name: RESOURCE-TYPE 544 Purpose: To specify the type of resource. 546 Value type: The value type for this property is TEXT. The allowable 547 values are defined below. 549 Format Definition: 551 This property is defined by the following notation: 553 restypeprop = "RESOURCE-TYPE" restypeparam ":" 554 restypevalue CRLF 556 restypevalue = ("ROOM" 557 / "PROJECTOR" 558 / "REMOTE-CONFERENCE-AUDIO" 559 / "REMOTE-CONFERENCE-VIDEO" 560 / iana-token) ; Other IANA-registered 561 ; values 563 restypeparam = *(";" other-param) 565 Description: This property MAY be specified in VRESOURCE components 566 and provides a way to differentiate multiple resources. 568 The registered values are described below. New resource types 569 SHOULD be registered in the manner laid down in this 570 specification. 572 ROOM: A room for the event/meeting. 574 PROJECTOR: Projection equipment. 576 REMOTE-CONFERENCE-AUDIO: Audio remote conferencing facilities. 578 REMOTE-CONFERENCE-VIDEO: Video remote conferencing facilities. 580 6.4. Calendar Address 582 Property name: CALENDAR-ADDRESS 584 Purpose: To specify the calendar address for a participant. 586 Value type: CAL-ADDRESS 588 Property Parameters: IANA, or non-standard property parameters can 589 be specified on this property. 591 Conformance: This property MAY be specified once within a 592 PARTICIPANT component. 594 Description: This property provides a calendar user address for the 595 participant. If there is an ATTENDEE property with the same value 596 then the participant is schedulable. 598 Format Definition: 600 This property is defined by the following notation: 602 calendaraddress = "CALENDAR-ADDRESS" caladdressparam ":" 603 cal-address CRLF 605 caladdressparam = *(";" other-param) 607 6.5. Styled-Description 609 Property name: STYLED-DESCRIPTION 611 Purpose: This property provides for one or more rich-text 612 descriptions to replace that provided by the DESCRIPTION property. 614 Value type: There is no default value type for this property. The 615 value type can be set to URI or TEXT. Other text-based value 616 types can be used when defined in the future. Clients MUST ignore 617 any properties with value types they do not understand. 619 Property Parameters: IANA, non-standard, id, alternate text 620 representation, format type, derived and language property 621 parameters can be specified on this property. 623 Conformance: The property can be specified multiple times in the 624 "VEVENT", "VTODO", "VJOURNAL", "VFREEBUSY", "PARTICIPANT", or 625 "VALARM" calendar components. 627 If it does appear more than once there MUST be exactly one 628 instance of the property with no DERIVED parameter or 629 DERIVED=FALSE. All others MUST have DERIVED=TRUE. 631 Additionally, if there is one or more STYLED-DESCRIPTION property 632 then the DESCRIPTION property should be either absent or have the 633 parameter DERIVED=TRUE. 635 Description: This property supports rich-text descriptions, for 636 example HTML. Event publishers typically wish to provide more and 637 better formatted information about the event. 639 This property is used in the "VEVENT" and "VTODO" to capture 640 lengthy textual descriptions associated with the activity. This 641 property is used in the "VJOURNAL" calendar component to capture 642 one or more textual journal entries. This property is used in the 643 "VALARM" calendar component to capture the display text for a 644 DISPLAY category of alarm, and to capture the body text for an 645 EMAIL category of alarm. In the PARTICIPANT component it provides 646 a detailed description of the participant. 648 VALUE=TEXT is used to provide rich-text inline as the property 649 value. 651 VALUE=URI is used to provide a link to rich-text content which is 652 expected to be displayed inline as part of the event. 654 In either case the DESCRIPTION property should be absent or 655 contain a plain text rendering of the styled text. 657 Applications MAY attempt to guess the media type of the resource 658 via inspection of its content if and only if the media type of the 659 resource is not given by the "FMTTYPE" parameter. If the media 660 type remains unknown, calendar applications SHOULD treat it as 661 type "text/html" and process the content as defined in 662 [W3C.REC-html51-20171003] 664 Multiple STYLED-DESCRIPTION properties may be used to provide 665 different formats or different language variants. However all but 666 one MUST have DERIVED=TRUE. 668 Format Definition: 670 This property is defined by the following notation: 672 styleddescription = "STYLED-DESCRIPTION" styleddescparam ":" 673 styleddescval CRLF 675 styleddescparam = ; the elements herein may appear in any order, 676 ; and the order is not significant. 678 (";" "VALUE" "=" ("URI" / "TEXT")) 680 [";" altrepparam] 681 [";" languageparam] 682 [";" fmttypeparam] 683 [";" derivedparam] 685 *(";" other-param) 687 styleddescval = ( uri / text ) 688 ;Value MUST match value type 690 Example: 692 The following is an example of this property. It points to an html 693 description. 695 STYLED-DESCRIPTION;VALUE=URI:http://example.org/desc001.html 697 6.6. Structured-Data 699 Property Name: STRUCTURED-DATA 701 Purpose: This property specifies ancillary data associated with the 702 calendar component. 704 Value Type: There is no default value type for this property. The 705 value type can be set to TEXT, BINARY or URI 707 Property Parameters: IANA, non-standard, inline encoding and value 708 data type property parameters can be specified on this property. 709 The format type and schema parameters can be specified on this 710 property and MUST be present for text or inline binary encoded 711 content information. 713 Conformance: This property can be specified multiple times in an 714 iCalendar object. Typically it would be used in "VEVENT", "VTODO" 715 or "VJOURNAL" calendar components. 717 Description: The existing properties in iCalendar cover key elements 718 of events and tasks such as start time, end time, location, 719 summary, etc. However, different types of events often have other 720 specific "fields" that it is useful to include in the calendar 721 data. For example, an event representing an airline flight could 722 include the airline, flight number, departure and arrival airport 723 codes, check-in and gate-closing times etc. As another example, a 724 sporting event might contain information about the type of sport, 725 the home and away teams, the league the teams are in, information 726 about nearby parking, etc. 728 This property is used to specify ancillary data in some structured 729 format either directly (inline) as a "TEXT" or "BINARY" value or 730 as a link via a "URI" value. 732 Rather than define new iCalendar properties for the variety of 733 event types that might occur, it would be better to leverage 734 existing schemas for such data. For example, schemas available at 735 https://schema.org include different event types. By using 736 standard schemas, interoperability can be improved between 737 calendar clients and non-calendaring systems that wish to generate 738 or process the data. 740 This property allows the direct inclusion of ancillary data whose 741 schema is defined elsewhere. This property also includes 742 parameters to clearly identify the type of the schema being used 743 so that clients can quickly and easily spot what is relevant 744 within the calendar data and present that to users or process it 745 within the calendaring system. 747 iCalendar does support an "ATTACH" property which can be used to 748 include documents or links to documents within the calendar data. 749 However, that property does not allow data to be included as a 750 "TEXT" value (a feature that "STRUCTURED-DATA" does allow), plus 751 attachments are often treated as "opaque" data to be processed by 752 some other system rather than the calendar client. Thus the 753 existing "ATTACH" property is not sufficient to cover the specific 754 needs of inclusion of schema data. Extending the "ATTACH" 755 property to support a new value type would likely cause 756 interoperability problems. Additionally some implementations 757 manage attachments by stripping them out and replacing with a link 758 to the resource. Thus a new property to support inclusion of 759 schema data is warranted. 761 Format Definition: 763 This property is defined by the following notation: 765 sdataprop = "STRUCTURED-DATA" sdataparam ":" 766 sdataval CRLF 768 sdataparam = ; the elements herein may appear in any order, 769 ; and the order is not significant. 771 (";" "VALUE" "=" ("BINARY" / "URI" / "TEXT")) 773 ; ENCODING is REQUIRED for VALUE=BINARY 774 [";" "ENCODING" "=" "BASE64"] 776 ; FMTTYPE and SCHEMA are OPTIONAL for a URI value, 777 ; REQUIRED for a TEXT or BINARY value, 778 [";" fmttypeparam] 779 [";" schemaparam] 781 *(";" other-param) 783 sdataval = ( binary / text /uri ) 784 ;Value MUST match value type 786 Example: The following is an example of this property: 788 STRUCTURED-DATA;FMTTYPE=application/ld+json; 789 SCHEMA="https://schema.org/SportsEvent"; 790 VALUE=TEXT:{\n 791 "@context": "http://schema.org"\,\n 792 "@type": "SportsEvent"\,\n 793 "homeTeam": "Pittsburgh Pirates"\,\n 794 "awayTeam": "San Francisco Giants"\n 795 }\n 797 7. New Components 799 7.1. Participant 801 Component name: PARTICIPANT 803 Purpose: This component provides information about a participant in 804 an event or task. 806 Conformance: This component can be specified multiple times in a 807 "VEVENT", "VTODO", "VJOURNAL" or "VFREEBUSY" calendar component. 809 Description: This component provides information about a participant 810 in a calendar component. A participant may be an attendee in a 811 scheduling sense and the ATTENDEE property may be specified in 812 addition. Participants can be individuals or organizations, for 813 example a soccer team, the spectators or the musicians. 815 STRUCTURED-DATA properties if present may refer to definitions of 816 the participant - such as a vCard. 818 The CALENDAR-ADDRESS property if present will provide a cal- 819 address. If an ATTENDEE property has the same value the 820 participant is considered schedulable. The PARTICIPANT component 821 can be used to contain additional meta-data related to the 822 attendee. 824 Format Definition: 826 This component is defined by the following notation: 828 participantc = "BEGIN" ":" "PARTICIPANT" CRLF 829 *( partprop / locationc / resourcec ) 830 "END" ":" "PARTICIPANT" CRLF 832 partprop = ; the elements herein may appear in any order, 833 ; and the order is not significant. 835 uid 836 participanttype 838 (calendaraddress) 839 (created) 840 (description) 841 (dtstamp) 842 (geo) 843 (last-mod) 844 (priority) 845 (seq) 846 (status) 847 (summary) 848 (url) 850 *attach 851 *categories 852 *comment 853 *contact 854 *location 855 *rstatus 856 *related 857 *resources 858 *strucloc 859 *strucres 860 *styleddescription 861 *sdataprop 862 *iana-prop 864 Note: When the PRIORITY is supplied it defines the ordering of 865 PARTICIPANT components with the same value for the TYPE parameter. 867 Privacy Issues: When a LOCATION is supplied it provides information 868 about the location of a participant at a given time or times. 869 This may represent an unacceptable privacy risk for some 870 participants. User agents MUST NOT broadcast this information 871 without the participant's express permission. For further 872 comments see Section 10 874 Example: 876 The following is an example of this component. It contains a 877 STRUCTURED-DATA property which points to a vCard providing 878 information about the event participant. 880 BEGIN:PARTICIPANT 881 UID: em9lQGZvb2GFtcGxlLmNvbQ 882 PARTICIPANT-TYPE:PERFORMER 883 STRUCTURED-DATA;VALUE=URI: 884 http://dir.example.com/vcard/aviolinist.vcf 885 END:PARTICIPANT 887 Example: 889 The following is an example for the primary contact. 891 BEGIN:PARTICIPANT 892 UID: em9lQGZvb2GFtcGxlLmNvbQ 893 STRUCTURED-DATA;VALUE=URI; 894 http://dir.example.com/vcard/contacts/contact1.vcf 895 PARTICIPANT-TYPE:CONTACT 896 DESCRIPTION:A contact 897 END:PARTICIPANT 899 7.1.1. Schedulable Participant 901 A PARTICIPANT component may represent someone or something that needs 902 to be scheduled as defined for ATTENDEE in [RFC5545] and [RFC5546]. 903 The PARTICIPANT component may also represent someone or something 904 that is NOT to receive scheduling messages. 906 For backwards compatibility wuth existing clients and servers when 907 used to schedule events and tasks the ATTENDEE property MUST be used 908 to specify the sheduling parameters as defined for that property. 910 For other, future uses the CALENDAR-ADDRESS property MUST be used to 911 specify those parameters. 913 A PARTICIPANT component is defined to be schedulable if 915 o It contains a CALENDAR-ADDRESS property 917 o That property value is the same as the value for an ATTENDEE 918 property. 920 If both of these conditions apply then the participant defined by the 921 value of the URL property will take part in scheduling operations as 922 defined in [RFC5546]. 924 An appropriate use for the PARTICIPANT component in scheduling would 925 be to store SEQUENCE and DTSTAMP properties associated with replies 926 from each ATTENDEE. A LOCATION property within the PARTICIPANT 927 component might allow better selection of meeting times when 928 participants are in different timezones. 930 7.2. Location 932 Component name: VLOCATION 934 Purpose: This component provides rich information about the location 935 of an event using the structured data property or optionally a 936 plain text typed value. 938 Conformance: This component can be specified multiple times in a 939 "VEVENT", "VTODO", "VJOURNAL", "VFREEBUSY" or "PARTICIPANT" 940 calendar component. 942 Description: There may be a number of locations associated with an 943 event. This component provides detailed information about a 944 location. 946 When used in a component the value of this property provides 947 information about the event venue or of related services such as 948 parking, dining, stations etc.. 950 STRUCTURED-DATA properties if present may refer to representations 951 of the location - such as a vCard. 953 Format Definition: 955 This component is defined by the following notation: 957 locationc = "BEGIN" ":" "VLOCATION" CRLF 958 locprop 959 "END" ":" "VLOCATION" CRLF 961 locprop = ; the elements herein may appear in any order, 962 ; and the order is not significant. 964 uid 966 (name) 967 (description) 968 (geo) 969 (loctype) 971 *sdataprop 972 *iana-prop 974 The NAME property is defined in [RFC7986] 976 Example: 978 The following is an example of this component. It points to a venue. 980 BEGIN:VLOCATION 981 UID:123456-abcdef-98765432 982 NAME:The venue 983 STRUCTURED-DATA;VALUE=URI: 984 http://dir.example.com/venues/big-hall.vcf 985 END:VLOCATION 987 7.3. Resource 989 Component name: VRESOURCE 991 Purpose: This component provides a typed reference to external 992 information about a resource or optionally a plain text typed 993 value. Typically a resource is anything that might be required or 994 used by a calendar entity and possibly has a directory entry. 996 Conformance: This component can be specified multiple times in a 997 "VEVENT", "VTODO", "VJOURNAL", "VFREEBUSY" or "PARTICIPANT" 998 calendar component. 1000 Description: When used in a component this component provides 1001 information about resources used for the event such as rooms, 1002 projectors, conferencing capabilities. 1004 The RESOURCE-TYPE value registry provides a place in which 1005 resource types may be registered. 1007 STRUCTURED-DATA properties if present may refer to representations 1008 of the resource - such as a vCard. 1010 Format Definition: 1012 This component is defined by the following notation: 1014 resourcec = "BEGIN" ":" "VRESOURCE" CRLF 1015 resprop 1016 "END" ":" "VRESOURCE" CRLF 1018 resprop = ; the elements herein may appear in any order, 1019 ; and the order is not significant. 1021 uid 1023 (name) 1024 (description) 1025 (geo) 1026 (restype) 1028 *sdataprop 1029 *iana-prop 1031 The NAME property is defined in [RFC7986] 1033 Example: 1035 The following is an example of this component. It refers to a 1036 projector. 1038 BEGIN:VRESOURCE 1039 UID:456789-abcdef-98765432 1040 NAME:The projector 1041 RESOURCE-TYPE:projector 1042 STRUCTURED-DATA;VALUE=URI:http://dir.example.com/projectors/3d.vcf 1043 END:VRESOURCE 1045 8. Extended examples 1047 The following are some examples of the use of the properties defined 1048 in this specification. They include additional properties defined in 1049 [RFC7986] which includes IMAGE. 1051 8.1. Example 1 1053 The following is an example of a VEVENT describing a concert. It 1054 includes location information for the venue itself as well as 1055 references to parking and restaurants. 1057 BEGIN:VEVENT 1058 CREATED:20200215T145739Z 1059 DESCRIPTION: Piano Sonata No 3\n 1060 Piano Sonata No 30 1061 DTSTAMP:20200215T145739Z 1062 DTSTART;TZID=America/New_York:20200315T150000Z 1063 DTEND;TZID=America/New_York:20200315T163000Z 1064 LAST-MODIFIED:20200216T145739Z 1065 SUMMARY:Beethoven Piano Sonatas 1066 UID:123456 1067 IMAGE;VALUE=URI;DISPLAY=BADGE;FMTTYPE=image/png:h 1068 ttp://example.com/images/concert.png 1069 BEGIN:PARTICIPANT 1070 PARTICIPANT-TYPE:SPONSOR 1071 UID:dG9tQGZvb2Jhci5xlLmNvbQ 1072 STRUCTURED-DATA;VALUE=URI:http://example.com/sponsor.vcf 1073 END:PARTICIPANT 1074 BEGIN:PARTICIPANT 1075 PARTICIPANT-TYPE:PERFORMER: 1076 UID:em9lQGZvb2GFtcGxlLmNvbQ 1077 STRUCTURED-DATA;VALUE=URI:http://www.example.com/people/johndoe.vcf 1078 END:PARTICIPANT 1079 BEGIN:VLOCATION 1080 UID:123456-abcdef-98765432 1081 NAME:The venue 1082 STRUCTURED-DATA;VALUE=URI:http://dir.example.com/venues/big-hall.vcf 1083 END:VLOCATION 1084 BEGIN:VLOCATION 1085 UID:123456-abcdef-87654321 1086 NAME:Parking for the venue 1087 STRUCTURED-DATA;VALUE=URI:http://dir.example.com/venues/parking.vcf 1088 END:VLOCATION 1089 END:VEVENT 1091 8.2. Example 2 1092 The following is an example of a VEVENT describing a meeting. One of 1093 the attendees is a remote participant. 1095 BEGIN:VEVENT 1096 CREATED:20200215T145739Z 1097 DTSTAMP:20200215T145739Z 1098 DTSTART;TZID=America/New_York:20200315T150000Z 1099 DTEND;TZID=America/New_York:20200315T163000Z 1100 LAST-MODIFIED:20200216T145739Z 1101 SUMMARY:Conference planning 1102 UID:123456 1103 ORGANIZER:mailto:a@example.com 1104 ATTENDEE;PARTSTAT=ACCEPTED;CN=A:mailto:a@example.com 1105 ATTENDEE;RSVP=TRUE;CN=B:mailto:b@example.com 1106 BEGIN:PARTICIPANT 1107 PARTICIPANT-TYPE:ACTIVE: 1108 UID:v39lQGZvb2GFtcGxlLmNvbQ 1109 STRUCTURED-DATA;VALUE=URI:http://www.example.com/people/b.vcf 1110 LOCATION:At home 1111 END:PARTICIPANT 1112 END:VEVENT 1114 9. Security Considerations 1116 This specification extends [RFC5545] and makes further use of 1117 possibly linked data. While calendar data is not unique in this 1118 regard it is worth reminding implementors of some of the dangers and 1119 safeguards. 1121 9.1. URIs 1123 See [RFC3986] for a discussion of the security considerations 1124 relating to URIs. Because of the issues discussed there and below, 1125 clients SHOULD NOT follow URIs and fetch content automatically, and 1126 should only do so at the explicit request of the user. 1128 Fetching remote resources carries inherent risks. Connections must 1129 only be allowed on well known ports, using allowed protocols 1130 (generally just HTTP/HTTPS on their default ports). The URL must be 1131 resolved externally and not allowed to access internal resources. 1132 Connecting to an external source reveals IP (and therefore generally 1133 location) information. 1135 A maliciously constructed iCalendar object may contain a very large 1136 number of URIs. In the case of published calendars with a large 1137 number of subscribers, such objects could be widely distributed. 1138 Implementations should be careful to limit the automatic fetching of 1139 linked resources to reduce the risk of this being an amplification 1140 vector for a denial-of-service attack. 1142 9.2. Malicious Content 1144 For the "STRUCTURED-DATA" property, servers need to be aware that a 1145 client could attack underlying storage by sending extremely large 1146 values and could attack processing time by uploading a recurring 1147 event with a large number of overrides and then repeatedly adding, 1148 updating and deleting structured data. 1150 Malicious content could be introduced into the calendar server by way 1151 of the "STRUCTURED-DATA" property and propagated to many end users 1152 via scheduling. Servers SHOULD check this property for malicious or 1153 inappropriate content. Upon detecting such content, servers SHOULD 1154 remove the property, 1156 9.3. HTML Content 1158 When processing HTML content, applications need to be aware of the 1159 many security and privacy issues, as described in the IANA 1160 considerations section of [W3C.REC-html51-20171003] 1162 10. Privacy Considerations 1164 10.1. Tracking 1166 Properties with a "URI" value type can expose their users to privacy 1167 leaks as any network access of the URI data can be tracked both by a 1168 network observer and by the entity hosting the remote resource. 1169 Clients SHOULD NOT automatically download data referenced by the URI 1170 without explicit instruction from users. 1172 To help alleviate some of the concerns protocols and services could 1173 provide proxy services for downloading referenced data. 1175 10.2. Revealing Locations 1177 The addition of location information to the new participant component 1178 provides information about the location of participants at a given 1179 time. This information MUST NOT be distributed to other participants 1180 without that participants express permission. Agents processing and 1181 distributing calendar data must be aware that it has the property of 1182 providing information about a future time when a given individual may 1183 be at a particular location, which could enable targeted attacks 1184 against that individual. 1186 The same may be true of other information contained in the 1187 participant component. In general, revealing only as much as is 1188 absolutely necessary should be the approach 1190 For example, there may be some privacy considerations relating to the 1191 ORDER parameter, as it provides an indication of the organizer's 1192 perception of the relative importance of other participants. 1194 11. IANA Considerations 1196 11.1. Additional iCalendar Registrations 1198 11.1.1. Properties 1200 This document defines the following new iCalendar properties to be 1201 added to the registry defined in Section 8.2.3 of [RFC5545]: 1203 +--------------------+---------+----------------------+ 1204 | Property | Status | Reference | 1205 +--------------------+---------+----------------------+ 1206 | CALENDAR-ADDRESS | Current | RFCXXXX, Section 6.4 | 1207 | LOCATION-TYPE | Current | RFCXXXX, Section 6.1 | 1208 | PARTICIPANT-TYPE | Current | RFCXXXX, Section 6.2 | 1209 | RESOURCE-TYPE | Current | RFCXXXX, Section 6.3 | 1210 | STRUCTURED-DATA | Current | RFCXXXX, Section 6.6 | 1211 | STYLED-DESCRIPTION | Current | RFCXXXX, Section 6.5 | 1212 +--------------------+---------+----------------------+ 1214 11.1.2. Parameters 1216 This document defines the following new iCalendar property parameters 1217 to be added to the registry defined in Section 8.2.4 of [RFC5545]: 1219 +--------------------+---------+----------------------+ 1220 | Property Parameter | Status | Reference | 1221 +--------------------+---------+----------------------+ 1222 | ORDER | Current | RFCXXXX, Section 5.1 | 1223 | SCHEMA | Current | RFCXXXX, Section 5.2 | 1224 +--------------------+---------+----------------------+ 1226 11.1.3. Components 1228 This document defines the following new iCalendar components to be 1229 added to the registry defined in Section 8.3.1 of [RFC5545]: 1231 +-------------+---------+----------------------+ 1232 | Component | Status | Reference | 1233 +-------------+---------+----------------------+ 1234 | PARTICIPANT | Current | RFCXXXX, Section 7.1 | 1235 | VLOCATION | Current | RFCXXXX, Section 7.2 | 1236 | VRESOURCE | Current | RFCXXXX, Section 7.3 | 1237 +-------------+---------+----------------------+ 1239 11.2. New Registration Tables 1241 This section defines new registration tables for PARTICIPANT-TYPE and 1242 RESOURCE-TYPE values. These tables are updated using the same 1243 approaches laid down in Section 8.2.1 of [RFC5545] 1245 11.2.1. Participant Types 1247 The following table has been used to initialize the participant types 1248 registry. 1250 +-------------------+---------+----------------------+ 1251 | Participant Type | Status | Reference | 1252 +-------------------+---------+----------------------+ 1253 | ACTIVE | Current | RFCXXXX, Section 6.2 | 1254 | INACTIVE | Current | RFCXXXX, Section 6.2 | 1255 | SPONSOR | Current | RFCXXXX, Section 6.2 | 1256 | CONTACT | Current | RFCXXXX, Section 6.2 | 1257 | BOOKING-CONTACT | Current | RFCXXXX, Section 6.2 | 1258 | EMERGENCY-CONTACT | Current | RFCXXXX, Section 6.2 | 1259 | PUBLICITY-CONTACT | Current | RFCXXXX, Section 6.2 | 1260 | PLANNER-CONTACT | Current | RFCXXXX, Section 6.2 | 1261 | PERFORMER | Current | RFCXXXX, Section 6.2 | 1262 | SPEAKER | Current | RFCXXXX, Section 6.2 | 1263 +-------------------+---------+----------------------+ 1265 11.2.2. Resource Types 1267 The following table has been used to initialize the resource types 1268 registry. 1270 +-------------------------+---------+----------------------+ 1271 | Resource Type | Status | Reference | 1272 +-------------------------+---------+----------------------+ 1273 | PROJECTOR | Current | RFCXXXX, Section 6.3 | 1274 | ROOM | Current | RFCXXXX, Section 6.3 | 1275 | REMOTE-CONFERENCE-AUDIO | Current | RFCXXXX, Section 6.3 | 1276 | REMOTE-CONFERENCE-VIDEO | Current | RFCXXXX, Section 6.3 | 1277 +-------------------------+---------+----------------------+ 1279 12. Acknowledgements 1281 The author would like to thank Chuck Norris of eventful.com for his 1282 work which led to the development of this RFC. 1284 The author would also like to thank the members of CalConnect, The 1285 Calendaring and Scheduling Consortium, the Event Publication 1286 technical committee and the following individuals for contributing 1287 their ideas and support: 1289 Cyrus Daboo, John Haug, Dan Mendell, Ken Murchison, Scott Otis. 1291 13. Normative References 1293 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1294 Requirement Levels", BCP 14, RFC 2119, 1295 DOI 10.17487/RFC2119, March 1997, 1296 . 1298 [RFC2426] Dawson, F. and T. Howes, "vCard MIME Directory Profile", 1299 RFC 2426, DOI 10.17487/RFC2426, September 1998, 1300 . 1302 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 1303 Resource Identifier (URI): Generic Syntax", STD 66, 1304 RFC 3986, DOI 10.17487/RFC3986, January 2005, 1305 . 1307 [RFC4589] Schulzrinne, H. and H. Tschofenig, "Location Types 1308 Registry", RFC 4589, DOI 10.17487/RFC4589, July 2006, 1309 . 1311 [RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and 1312 Scheduling Core Object Specification (iCalendar)", 1313 RFC 5545, DOI 10.17487/RFC5545, September 2009, 1314 . 1316 [RFC5546] Daboo, C., Ed., "iCalendar Transport-Independent 1317 Interoperability Protocol (iTIP)", RFC 5546, 1318 DOI 10.17487/RFC5546, December 2009, 1319 . 1321 [RFC7986] Daboo, C., "New Properties for iCalendar", RFC 7986, 1322 DOI 10.17487/RFC7986, October 2016, 1323 . 1325 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 1326 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 1327 May 2017, . 1329 [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data 1330 Interchange Format", STD 90, RFC 8259, 1331 DOI 10.17487/RFC8259, December 2017, 1332 . 1334 [W3C.REC-html51-20171003] 1335 Faulkner, S., Eicholz, A., Leithead, T., and A. Danilo, 1336 "HTML 5.1 2nd Edition", World Wide Web Consortium 1337 Recommendation REC-html51-20171003, October 2017, 1338 . 1340 [W3C.REC-xml-20081126] 1341 Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., and 1342 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth 1343 Edition)", World Wide Web Consortium Recommendation REC- 1344 xml-20081126, November 2008, 1345 . 1347 Appendix A. Open issues 1349 None at the moment 1351 Appendix B. Change log 1353 To be deleted on publication 1355 calext-v17 2021-01-03 MD 1357 o Remove STRUCTURED-LOCATION property, add VLOCATION component. 1359 o Remove STRUCTURED-RESOURCE property, add VRESOURCE component. 1361 o Make LOCATION-TYPE multi-valued property for location. 1363 o Make RESOURCE-TYPE multi-valued property for resource. 1365 o Tidy up abnf. 1367 calext-v16 2019-10-09 MD 1369 o Make LOCTYPE multi-valued. 1371 o Add all ATTENDEE scheduling parameters to CALENDAR-ADDRESS. 1373 calext-v15 2019-10-08 MD 1375 o Address various DICUSS points. 1377 calext-v14 2019-06-11 MD 1379 o Definition of event and social calendaring. 1381 o Remove redefinition of SOURCE - use STRUCTURED-DATA. 1383 calext-v13 2019-05-26 MD 1385 o Respond to various issues. 1387 calext-v12 2019-02-28 MD 1389 o Fix styled-description example. Respond to various AD issues. 1390 Some typos. 1392 calext-v11 2019-02-27 MD 1394 o Add DERIVED parameter for styled-description, RELATED parameter 1395 for structured-location 1397 calext-v09 2018-08-30 MD 1399 o Sorted out inconsistencies in refs to 5546 1401 calext-v08 2018-07-06 MD 1403 o Add some text for equal ORDER values 1405 o Switched scheduleaddress to calendaraddress in participant abnf. 1406 Also added more properties 1408 o Fixed PARTICIPANT abnf 1410 calext-v04 2017-10-11 MD 1412 o Change SCHEDULE-ADDRESS to CALENDAR-ADDRESS 1414 o Explicitly broaden scope of SOURCE 1416 o Add initial registry for RESTYPE and move new tables into separate 1417 section. 1419 o Fix PARTTYPE/PARTICIPANT-TYPE inconsistency 1420 calext-v03 2017-10-09 MD 1422 o Mostly typographical and other minor changes 1424 calext-v02 2017-04-20 MD 1426 o Add SCHEDULE-ADDRESS property 1428 o PARTICIPANT becomes a component rather than a property. Turn many 1429 of the former parameters into properties. 1431 o Use existing ATTENDEE property for scheduling. 1433 calext-v01 2017-02-18 MD 1435 o Change ASSOCIATE back to PARTICIPANT 1437 o PARTICIPANT becomes a component rather than a property. Turn many 1438 of the former parameters into properties. 1440 calext-v00 2016-08-?? MD 1442 o Name changed - taken up by calext working group 1444 v06 2016-06-26 MD 1446 o Fix up abnf 1448 o change ref to ietf from daboo 1450 o take out label spec - use Cyrus spec 1452 v05 2016-06-14 MD 1454 o Remove GROUP and HASH. they can be dealt with elsewhere if desired 1456 o Change ORDER to integer >= 1. 1458 o Incorporate Structured-Data into this specification. 1460 v04 2014-02-01 MD 1462 o Added updates attribute. 1464 o Minor typos. 1466 o Resubmitted mostly to refresh the draft. 1468 v03 2013-03-06 MD 1470 o Replace PARTICIPANT with ASSOCIATE plus related changes. 1472 o Added section showing modifications to components. 1474 o Replace ID with GROUP and modify HASH. 1476 o Replace TITLE param with LABEL. 1478 o Fixed STYLED-DESCRIPTION in various ways, correct example. 1480 v02 2012-11-02 MD 1482 o Collapse sections with description of properties and the use cases 1483 into a section with sub-sections. 1485 o New section to describe relating properties. 1487 o Remove idref and upgrade hash to have the reference 1489 o No default value types on properties.. 1491 v01 2012-10-18 MD Many changes. 1493 o SPONSOR and STRUCTURED-CONTACT are now in PARTICIPANT 1495 o Add a STRUCTURED-RESOURCE property 1497 o STYLED-DESCRIPTION to handle rich text 1499 o Much more... 1501 2011-01-07 1503 o Remove MEDIA - it's going in the Cyrus RFC 1505 o Rename EXTENDED-... to STRUCTURED-... 1507 o Add TYPE parameter to SPONSOR 1509 v00 2007-10-19 MD Initial version 1511 Author's Address 1512 Michael Douglass 1513 Bedework 1514 226 3rd Street 1515 Troy, NY 12180 1516 USA 1518 Email: mdouglass@bedework.com 1519 URI: http://bedework.com