draft-ietf-calext-eventpub-extensions-13.txt   draft-ietf-calext-eventpub-extensions-14.txt 
Network Working Group M. Douglass Network Working Group M. Douglass
Internet-Draft Spherical Cow Group Internet-Draft Spherical Cow Group
Updates: 5545,7986 (if approved) May 26, 2019 Updates: 5545,7986 (if approved) August 2, 2019
Intended status: Standards Track Intended status: Standards Track
Expires: November 27, 2019 Expires: February 3, 2020
Event Publishing Extensions to iCalendar Event Publishing Extensions to iCalendar
draft-ietf-calext-eventpub-extensions-13 draft-ietf-calext-eventpub-extensions-14
Abstract Abstract
This specification updates RFC5545 by introducing a number of new This specification updates RFC5545 by introducing a number of new
iCalendar properties and components which are of particular use for iCalendar properties and components which are of particular use for
event publishers and in social networking. event publishers and in social networking.
This specification also defines a new STRUCTURED-DATA property for This specification also defines a new STRUCTURED-DATA property for
iCalendar RFC5545 to allow for data that is directly pertinent to an iCalendar RFC5545 to allow for data that is directly pertinent to an
event or task to be included with the calendar data. event or task to be included with the calendar data.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 27, 2019. This Internet-Draft will expire on February 3, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 3 1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Components and properties . . . . . . . . . . . . . . . . . . 3 1.2. Terms Used in This Document . . . . . . . . . . . . . . . 3
2. Components and properties . . . . . . . . . . . . . . . . . . 4
3. Typed References . . . . . . . . . . . . . . . . . . . . . . 4 3. Typed References . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 5 3.1. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1.1. Piano Concert Performance . . . . . . . . . . . . . . 5 3.1.1. Piano Concert Performance . . . . . . . . . . . . . . 5
3.1.2. Itineraries . . . . . . . . . . . . . . . . . . . . . 5 3.1.2. Itineraries . . . . . . . . . . . . . . . . . . . . . 5
3.1.2.1. Reserving facilities . . . . . . . . . . . . . . 5 3.1.2.1. Reserving facilities . . . . . . . . . . . . . . 6
4. Modifications to Calendar Components . . . . . . . . . . . . 6 4. Modifications to Calendar Components . . . . . . . . . . . . 6
5. New Property Parameters . . . . . . . . . . . . . . . . . . . 7 5. New Property Parameters . . . . . . . . . . . . . . . . . . . 7
5.1. Loctype . . . . . . . . . . . . . . . . . . . . . . . . . 7 5.1. Loctype . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.2. Restype . . . . . . . . . . . . . . . . . . . . . . . . . 7 5.2. Restype . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.3. Order . . . . . . . . . . . . . . . . . . . . . . . . . . 8 5.3. Order . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.4. Schema . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.4. Schema . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.5. Derived . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.5. Derived . . . . . . . . . . . . . . . . . . . . . . . . . 10
6. Redefined Property SOURCE . . . . . . . . . . . . . . . . . . 10 6. New Properties . . . . . . . . . . . . . . . . . . . . . . . 11
7. New Properties . . . . . . . . . . . . . . . . . . . . . . . 12 6.1. Participant Type . . . . . . . . . . . . . . . . . . . . 11
7.1. Participant Type . . . . . . . . . . . . . . . . . . . . 12 6.2. Calendar Address . . . . . . . . . . . . . . . . . . . . 13
7.2. Calendar Address . . . . . . . . . . . . . . . . . . . . 14 6.3. Styled-Description . . . . . . . . . . . . . . . . . . . 14
7.3. Styled-Description . . . . . . . . . . . . . . . . . . . 15 6.4. Structured-Location . . . . . . . . . . . . . . . . . . . 16
7.4. Structured-Location . . . . . . . . . . . . . . . . . . . 17 6.5. Structured-Resource . . . . . . . . . . . . . . . . . . . 18
7.5. Structured-Resource . . . . . . . . . . . . . . . . . . . 19 6.6. Structured-Data . . . . . . . . . . . . . . . . . . . . . 19
7.6. Structured-Data . . . . . . . . . . . . . . . . . . . . . 20 7. New Components . . . . . . . . . . . . . . . . . . . . . . . 22
8. New Components . . . . . . . . . . . . . . . . . . . . . . . 23 7.1. Participant . . . . . . . . . . . . . . . . . . . . . . . 22
8.1. Participant . . . . . . . . . . . . . . . . . . . . . . . 23 7.2. Schedulable Participant . . . . . . . . . . . . . . . . . 24
8.2. Schedulable Participant . . . . . . . . . . . . . . . . . 25 8. Extended examples . . . . . . . . . . . . . . . . . . . . . . 25
9. Extended examples . . . . . . . . . . . . . . . . . . . . . . 26 8.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . 25
9.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . 26 8.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . 25
9.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . 26 9. Security Considerations . . . . . . . . . . . . . . . . . . . 26
10. Security Considerations . . . . . . . . . . . . . . . . . . . 27 10. Privacy Considerations . . . . . . . . . . . . . . . . . . . 26
11. Privacy Considerations . . . . . . . . . . . . . . . . . . . 27 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 11.1. Additional iCalendar Registrations . . . . . . . . . . . 27
12.1. Additional iCalendar Registrations . . . . . . . . . . . 28 11.1.1. Properties . . . . . . . . . . . . . . . . . . . . . 27
12.1.1. Properties . . . . . . . . . . . . . . . . . . . . . 28 11.1.2. Parameters . . . . . . . . . . . . . . . . . . . . . 27
12.1.2. Parameters . . . . . . . . . . . . . . . . . . . . . 28 11.1.3. Components . . . . . . . . . . . . . . . . . . . . . 27
12.1.3. Components . . . . . . . . . . . . . . . . . . . . . 28 11.2. New Registration Tables . . . . . . . . . . . . . . . . 28
12.2. New Registration Tables . . . . . . . . . . . . . . . . 29 11.2.1. Participant Types . . . . . . . . . . . . . . . . . 28
12.2.1. Participant Types . . . . . . . . . . . . . . . . . 29 11.2.2. Resource Types . . . . . . . . . . . . . . . . . . . 28
12.2.2. Resource Types . . . . . . . . . . . . . . . . . . . 29 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 29 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 29
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 30 13.1. Normative References . . . . . . . . . . . . . . . . . . 29
14.1. Normative References . . . . . . . . . . . . . . . . . . 30 13.2. Informative References . . . . . . . . . . . . . . . . . 30
14.2. Informative References . . . . . . . . . . . . . . . . . 31 Appendix A. Open issues . . . . . . . . . . . . . . . . . . . . 30
Appendix A. Open issues . . . . . . . . . . . . . . . . . . . . 31 Appendix B. Change log . . . . . . . . . . . . . . . . . . . . . 30
Appendix B. Change log . . . . . . . . . . . . . . . . . . . . . 31 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 33
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 34
1. Introduction 1. Introduction
The currently existing iCalendar standard [RFC5545] lacks useful The currently existing iCalendar standard [RFC5545] lacks useful
methods for referencing additional, external information relating to methods for referencing additional, external information relating to
calendar components. Additionally there is no standard way to calendar components. Additionally there is no standard way to
provide rich text descriptions or meta-data associated with the provide rich text descriptions or meta-data associated with the
event. event.
Current practice is to embed this information as links in the Current practice is to embed this information as links in the
skipping to change at page 3, line 38 skipping to change at page 3, line 38
other applications - such as address books. other applications - such as address books.
1.1. Conventions Used in This Document 1.1. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
1.2. Terms Used in This Document
Event: When the word 'event' is used (perhaps with a capitalised 'E'
we are referring to gatherings, formal or informal. For example a
sports event, a party or a concert.
Social Calendaring: Historically, calendar data and scheduling has
been heavily biased towards meetings in a corporate environment.
Some of the features defined in this document are to support a
more informal, i.e. social, model. For example, we may want to
record who is participating in a public event.
2. Components and properties 2. Components and properties
Previous extensions to the calendaring standards have been largely Previous extensions to the calendaring standards have been largely
restricted to the addition of properties or parameters. This is restricted to the addition of properties or parameters. This is
partly because iCalendar libraries had trouble handling components partly because iCalendar libraries had trouble handling components
nested deeper than those defined in [RFC5545]. nested deeper than those defined in [RFC5545].
In a break with this 'tradition' this specification defines In a break with this 'tradition' this specification defines
PARTICIPANT as a component rather than a property. This is a better PARTICIPANT as a component rather than a property. This is a better
match for the way [W3C.REC-xml-20081126] and JSON [RFC8259] handle match for the way [W3C.REC-xml-20081126] and JSON [RFC8259] handle
skipping to change at page 4, line 30 skipping to change at page 4, line 42
for indexing or the presenting of additional related information for for indexing or the presenting of additional related information for
the user. the user.
The [RFC5545] LOCATION property provides only an unstructured single The [RFC5545] LOCATION property provides only an unstructured single
text value for specifying the location where an event (or task) will text value for specifying the location where an event (or task) will
occur. This is inadequate for use cases where structured location occur. This is inadequate for use cases where structured location
information (e.g. address, region, country, postal code) is required information (e.g. address, region, country, postal code) is required
or preferred, and limits widespread adoption of iCalendar in those or preferred, and limits widespread adoption of iCalendar in those
settings. settings.
Using STRUCTURED-LOCATION, information about a number of interesting Using STRUCTURED-LOCATION, rich information about multiple locations
locations can be communicated, for example, address, region, country, can be communicated, for example, address, region, country, postal
postal code as well as other informations such as the parking, code as well as other information such as the parking, restaurants
restaurants and the venue. Servers and clients can retrieve the and the venue. Servers and clients can retrieve the objects when
objects when storing the event and use them to index by geographic storing the event and use them to index by geographic location.
location.
When a calendar client receives a calendar component it can search When a calendar client receives a calendar component it can search
the set of supplied properties looking for those of particular the set of supplied properties looking for those of particular
interest. The TYPE and FMTTYPE parameters, if supplied, can be used interest. The TYPE and FMTTYPE parameters, if supplied, can be used
to help the selection. to help the selection.
The PARTICIPANT component is designed to handle common use cases in The PARTICIPANT component is designed to handle common use cases in
event publication. It is generally important to provide information event publication. It is generally important to provide information
about the organizers of such events. Sponsors wish to be referenced about the organizers of such events. Sponsors wish to be referenced
in a prominent manner. In social calendaring it is often important in a prominent manner. In social calendaring it is often important
skipping to change at page 5, line 29 skipping to change at page 5, line 40
relate to the performance in different ways. relate to the performance in different ways.
There may be an iTip [RFC5546] meeting request for the piano tuner There may be an iTip [RFC5546] meeting request for the piano tuner
who will arrive before the performance. Other members of staff may who will arrive before the performance. Other members of staff may
also receive meeting requests. also receive meeting requests.
An event can also be created for publication which will have a An event can also be created for publication which will have a
PARTICIPANT component for the pianist providing a reference to VCARD PARTICIPANT component for the pianist providing a reference to VCARD
[RFC2426] information about the performer. This event would also [RFC2426] information about the performer. This event would also
hold information about parking, local subway stations and the venue hold information about parking, local subway stations and the venue
itself. In addition, there will be sponsorship information for itself. In addition, there may be sponsorship information for
sponsors of the event and perhaps paid sponsorship properties sponsors of the event and perhaps paid sponsorship properties
essentially advertising local establishments. essentially advertising local establishments.
3.1.2. Itineraries 3.1.2. Itineraries
These additions also provide opportunities for the travel industry. These additions also provide opportunities for the travel industry.
When booking a flight the PARTICIPANT component can be used to When booking a flight the PARTICIPANT component can be used to
provide references to businesses at the airports and to car hire provide references to businesses at the airports and to car hire
businesses at the destination. businesses at the destination.
The embedded location information can guide the traveller at the The embedded location information can guide the traveller at the
airport or to their final destination. The contact information can airport or to their final destination. The contact information can
provide detailed information about the booking agent, the airlines, provide detailed information about the booking agent, the airlines,
car hire companies and the hotel. car hire companies and the hotel.
3.1.2.1. Reserving facilities 3.1.2.1. Reserving facilities
For a meeting, the size of a room and the equipment needed depends to For a meeting, the size of a room and the equipment needed depends to
some extent on the number of attendees actually in the room. some extent on the number of attendees actually in the room.
A meeting may have 10 attendees non of which are co-located. The A meeting may have 10 attendees none of which are co-located. The
current ATTENDEE property does not allow for the addition of such current ATTENDEE property does not allow for the addition of such
meta-data. The PARTICIPANT property allows attendees to specify meta-data. The PARTICIPANT property allows attendees to specify
their location. their location.
4. Modifications to Calendar Components 4. Modifications to Calendar Components
The following changes to the syntax defined in iCalendar [RFC5545] The following changes to the syntax defined in iCalendar [RFC5545]
are made here. New elements are defined in subsequent sections. are made here. New elements are defined in subsequent sections.
eventc = "BEGIN" ":" "VEVENT" CRLF eventc = "BEGIN" ":" "VEVENT" CRLF
skipping to change at page 9, line 45 skipping to change at page 10, line 7
"STRUCTURED-DATA" properties. When present it provides "STRUCTURED-DATA" properties. When present it provides
identifying information about the nature of the content of the identifying information about the nature of the content of the
corresponding "STRUCTURED-DATA" property value. This can be used corresponding "STRUCTURED-DATA" property value. This can be used
to supplement the media type information provided by the "FMTTYPE" to supplement the media type information provided by the "FMTTYPE"
parameter on the corresponding property. parameter on the corresponding property.
Example: Example:
STRUCTURED-DATA;FMTTYPE=application/ld+json; STRUCTURED-DATA;FMTTYPE=application/ld+json;
SCHEMA="https://schema.org/FlightReservation"; SCHEMA="https://schema.org/FlightReservation";
ENCODING=BASE64;VALUE=BINARY:Zm9vYmFy ENCODING=BASE64;VALUE=BINARY:ICAgIDxzY3JpcHQgdHlwZT0iYXBwb
GljYXRpb24vbGQranNvbiI+CiAgICB7CiAgICAgICJAY29
udGV4dCI6ICJodHRwOi8vc2NoZW1hLm9yZyIsCiAgICAgICJAdHlwZSI
6ICJGbGlnaHRSZXNlcnZhdGlvbiIsCiAgICAgICJyZXNlcnZhdGlvbkl
kIjogIlJYSjM0UCIsCiAgICAgICJyZXNlcnZhdGlvblN0YXR1cyI6ICJ
odHRwOi8vc2NoZW1hLm9yZy9SZXNlcnZhdGlvbkNvbmZpcm1lZCIsCiA
gICAgICJwYXNzZW5nZXJQcmlvcml0eVN0YXR1cyI6ICJGYXN0IFRyYWN
rIiwKICAgICAgInBhc3NlbmdlclNlcXVlbmNlTnVtYmVyIjogIkFCQzE
yMyIsCiAgICAgICJzZWN1cml0eVNjcmVlbmluZyI6ICJUU0EgUHJlQ2h
lY2siLAogICAgICAidW5kZXJOYW1lIjogewogICAgICAgICJAdHlwZSI
6ICJQZXJzb24iLAogICAgICAgICJuYW1lIjogIkV2YSBHcmVlbiIKICA
gICAgfSwKICAgICAgInJlc2VydmF0aW9uRm9yIjogewogICAgICAgICJ
AdHlwZSI6ICJGbGlnaHQiLAogICAgICAgICJmbGlnaHROdW1iZXIiOiA
iVUExMTAiLAogICAgICAgICJwcm92aWRlciI6IHsKICAgICAgICAgICJ
AdHlwZSI6ICJBaXJsaW5lIiwKICAgICAgICAgICJuYW1lIjogIkNvbnR
pbmVudGFsIiwKICAgICAgICAgICJpYXRhQ29kZSI6ICJDTyIsCiAgICA
gICAgICAiYm9hcmRpbmdQb2xpY3kiOiAiaHR0cDovL3NjaGVtYS5vcmc
vWm9uZUJvYXJkaW5nUG9saWN5IgogICAgICAgIH0sCiAgICAgICAgInN
lbGxlciI6IHsKICAgICAgICAgICJAdHlwZSI6ICJBaXJsaW5lIiwKICA
gICAgICAgICJuYW1lIjogIlVuaXRlZCIsCiAgICAgICAgICAiaWF0YUN
vZGUiOiAiVUEiCiAgICAgICAgfSwKICAgICAgICAiZGVwYXJ0dXJlQWl
ycG9ydCI6IHsKICAgICAgICAgICJAdHlwZSI6ICJBaXJwb3J0IiwKICA
gICAgICAgICJuYW1lIjogIlNhbiBGcmFuY2lzY28gQWlycG9ydCIsCiA
gICAgICAgICAiaWF0YUNvZGUiOiAiU0ZPIgogICAgICAgIH0sCiAgICA
gICAgImRlcGFydHVyZVRpbWUiOiAiMjAxNy0wMy0wNFQyMDoxNTowMC0
wODowMCIsCiAgICAgICAgImFycml2YWxBaXJwb3J0IjogewogICAgICA
gICAgIkB0eXBlIjogIkFpcnBvcnQiLAogICAgICAgICAgIm5hbWUiOiA
iSm9obiBGLiBLZW5uZWR5IEludGVybmF0aW9uYWwgQWlycG9ydCIsCiA
gICAgICAgICAiaWF0YUNvZGUiOiAiSkZLIgogICAgICAgIH0sCiAgICA
gICAgImFycml2YWxUaW1lIjogIjIwMTctMDMtMDVUMDY6MzA6MDAtMDU
6MDAiCiAgICAgIH0KICAgIH0KICAgIDwvc2NyaXB0Pg==
5.5. Derived 5.5. Derived
Parameter Name: DERIVED Parameter Name: DERIVED
Purpose: To specify that the value of the associated property is Purpose: To specify that the value of the associated property is
derived from some other property value or values. derived from some other property value or values.
Format Definition: Format Definition:
This parameter is defined by the following notation: This parameter is defined by the following notation:
derivedparam = "DERIVED" "=" ("TRUE" / "FALSE") derivedparam = "DERIVED" "=" ("TRUE" / "FALSE")
; Default is FALSE ; Default is FALSE
Description: This property parameter can be specified on any Description: This property parameter MAY be specified on any
property when the value is derived from some other property or property when the value is derived from some other property or
properties. When present with a value of TRUE clients MUST NOT properties. When present with a value of TRUE clients MUST NOT
update the property. update the property.
As an example, if a STYLED-DESCRIPTION property is present with As an example, if a STYLED-DESCRIPTION property is present with
FMTTYPE="application/rtf" then there may be an additional STYLED- FMTTYPE="application/rtf" then there may be an additional STYLED-
DESCRIPTION property with FMTTYPE="text/html" and DERIVED=TRUE and DESCRIPTION property with FMTTYPE="text/html" and DERIVED=TRUE and
a value created from the rtf value. a value created from the rtf value.
Example: Example:
STYLED-DESCRIPTION;FMTTYPE=text/html; STYLED-DESCRIPTION;FMTTYPE=text/html;
DERIVED=TRUE:<html>... DERIVED=TRUE:<html>...
6. Redefined Property SOURCE 6. New Properties
The SOURCE property defined in [RFC7986] is redefined to allow
VALUE=TEXT and broaden its usage to any component.
Property name: SOURCE
Purpose: This property provides a reference to information about a
component such as a participant. For example, that information
may be a vcard or a plain text typed value.
For value type URI and embedded in a VEVENT or VTODO it may
provide a location from which the compoent may be refreshed.
Value type: There is no default value type for this property. It
may be set to URI as in [RFC7986]. The value type can also be set
to TEXT to indicate plain text content.
Property Parameters: Non-standard or format type parameters can be
specified on this property.
Conformance: This property can be specified once in an iCalendar
object.
Description: This property provides information about the component
in which it appears.
In a PARTICIPANT component it may provide a reference to a vcard
giving directory information.
In a VCALENDAR component this property identifies a location where
a client can retrieve updated data for the calendar. Clients
SHOULD honor any specified "REFRESH-INTERVAL" value when
periodically retrieving data. Note that this property differs
from the "URL" property in that "URL" is meant to provide an
alternative representation of the calendar data rather than the
original location of the data.
In a calendar entity component such as an event the SOURCE
property may provide a reference to the original source of the
event. This may be used by aggregators to provide a link back.
Format Definition:
This property is defined by the following notation:
source = "SOURCE" sourceparam
(
(
";" "VALUE" "=" "URI"
":" uri
) /
(
";" "VALUE" "=" "TEXT"
":" text
)
)
CRLF
sourceparam = *(
;
; the following are OPTIONAL
; but MUST NOT occur more than once
;
(";" fmttypeparam) /
;
; the following is OPTIONAL
; and MAY occur more than once
;
(";" other-param)
;
)
Example:
The following is an example referring to a VCARD.
SOURCE;FMTTYPE=text/vcard;VALUE=URL:
http://dir.example.com/vcard/contacts/contact1.vcf
7. New Properties
7.1. Participant Type 6.1. Participant Type
Property name: PARTICIPANT-TYPE Property name: PARTICIPANT-TYPE
Purpose: To specify the type of participant. Purpose: To specify the type of participant.
Value type: The value type for this property is TEXT. The allowable Value type: The value type for this property is TEXT. The allowable
values are defined below. values are defined below.
Property Parameters: Non-standard parameters can be specified on Property Parameters: Non-standard parameters can be specified on
this property. this property.
skipping to change at page 14, line 20 skipping to change at page 13, line 20
PLANNER-CONTACT: Contact for the event planner or organizer PLANNER-CONTACT: Contact for the event planner or organizer
PERFORMER: A performer - for example the soloist or the accompanist. PERFORMER: A performer - for example the soloist or the accompanist.
The ORDER parameter may be used with this participant type to The ORDER parameter may be used with this participant type to
define the relative order of multiple performers. For example, define the relative order of multiple performers. For example,
ORDER=1 could define the principal performer or soloist. ORDER=1 could define the principal performer or soloist.
SPEAKER: Speaker at an event SPEAKER: Speaker at an event
7.2. Calendar Address 6.2. Calendar Address
Property name: CALENDAR-ADDRESS Property name: CALENDAR-ADDRESS
Purpose: To specify the calendar address for a participant. Purpose: To specify the calendar address for a participant.
Value type: CAL-ADDRESS Value type: CAL-ADDRESS
Property Parameters: IANA or non-standard property parameters can be Property Parameters: IANA or non-standard property parameters can be
specified on this property. specified on this property.
skipping to change at page 15, line 5 skipping to change at page 14, line 5
calendaraddress = "CALENDAR-ADDRESS" caladdressparam ":" calendaraddress = "CALENDAR-ADDRESS" caladdressparam ":"
cal-address CRLF cal-address CRLF
caladdressparam = *( caladdressparam = *(
; the following is OPTIONAL ; the following is OPTIONAL
; and MAY occur more than once ; and MAY occur more than once
; ;
(";" other-param) (";" other-param)
) )
7.3. Styled-Description 6.3. Styled-Description
Property name: STYLED-DESCRIPTION Property name: STYLED-DESCRIPTION
Purpose: This property provides for one or more rich-text Purpose: This property provides for one or more rich-text
descriptions to replace that provided by the DESCRIPTION property. descriptions to replace that provided by the DESCRIPTION property.
Value type: There is no default value type for this property. The Value type: There is no default value type for this property. The
value type can be set to URI or TEXT. Other text-based value value type can be set to URI or TEXT. Other text-based value
types can be used when defined in the future. Clients MUST ignore types can be used when defined in the future. Clients MUST ignore
any properties with value types they do not understand. any properties with value types they do not understand.
skipping to change at page 17, line 10 skipping to change at page 16, line 10
styleddescval = ( uri / text ) styleddescval = ( uri / text )
;Value MUST match value type ;Value MUST match value type
Example: Example:
The following is an example of this property. It points to an html The following is an example of this property. It points to an html
description. description.
STYLED-DESCRIPTION;VALUE=URI:http://example.org/desc001.html STYLED-DESCRIPTION;VALUE=URI:http://example.org/desc001.html
7.4. Structured-Location 6.4. Structured-Location
Property name: STRUCTURED-LOCATION Property name: STRUCTURED-LOCATION
Purpose: This property provides a typed reference to external Purpose: This property provides a typed reference to external
information about the location of an event or optionally a plain information about the location of an event or optionally a plain
text typed value. text typed value.
Value type: There is no default value type for this property. The Value type: There is no default value type for this property. The
value type can be set to URI or TEXT. value type can be set to URI or TEXT.
skipping to change at page 19, line 5 skipping to change at page 18, line 5
;Value MUST match value type ;Value MUST match value type
Example: Example:
The following is an example of this property. It points to a venue. The following is an example of this property. It points to a venue.
STRUCTURED-LOCATION;LABEL="The venue"; STRUCTURED-LOCATION;LABEL="The venue";
VALUE=URI: VALUE=URI:
http://dir.example.com/venues/big-hall.vcf http://dir.example.com/venues/big-hall.vcf
7.5. Structured-Resource 6.5. Structured-Resource
Property name: STRUCTURED-RESOURCE Property name: STRUCTURED-RESOURCE
Purpose: This property provides a typed reference to external Purpose: This property provides a typed reference to external
information about a resource or optionally a plain text typed information about a resource or optionally a plain text typed
value. Typically a resource is anything that might be required or value. Typically a resource is anything that might be required or
used by a calendar entity and possibly has a directory entry. used by a calendar entity and possibly has a directory entry.
Value type: There is no default value type for this property. The Value type: There is no default value type for this property. The
value type can be set to URI or TEXT. value type can be set to URI or TEXT.
skipping to change at page 20, line 41 skipping to change at page 19, line 41
;Value MUST match value type ;Value MUST match value type
Example: Example:
The following is an example of this property. It refers to a The following is an example of this property. It refers to a
projector. projector.
STRUCTURED-RESOURCE;value=uri;restype="projector": STRUCTURED-RESOURCE;value=uri;restype="projector":
http://dir.example.com/projectors/3d.vcf http://dir.example.com/projectors/3d.vcf
7.6. Structured-Data 6.6. Structured-Data
Property Name: STRUCTURED-DATA Property Name: STRUCTURED-DATA
Purpose: This property specifies ancillary data associated with the Purpose: This property specifies ancillary data associated with the
calendar component. calendar component.
Value Type: TEXT, BINARY or URI Value Type: TEXT, BINARY or URI
Property Parameters: IANA, non-standard, inline encoding, and value Property Parameters: IANA, non-standard, inline encoding, and value
data type property parameters can be specified on this property. data type property parameters can be specified on this property.
skipping to change at page 22, line 4 skipping to change at page 20, line 52
iCalendar does support an "ATTACH" property which can be used to iCalendar does support an "ATTACH" property which can be used to
include documents or links to documents within the calendar data. include documents or links to documents within the calendar data.
However, that property does not allow data to be included as a However, that property does not allow data to be included as a
"TEXT" value (a feature that "STRUCTURED-DATA" does allow), plus "TEXT" value (a feature that "STRUCTURED-DATA" does allow), plus
attachments are often treated as "opaque" data to be processed by attachments are often treated as "opaque" data to be processed by
some other system rather than the calendar client. Thus the some other system rather than the calendar client. Thus the
existing "ATTACH" property is not sufficient to cover the specific existing "ATTACH" property is not sufficient to cover the specific
needs of inclusion of schema data. Extending the "ATTACH" needs of inclusion of schema data. Extending the "ATTACH"
property to support a new value type would likely cause property to support a new value type would likely cause
interoperability problems. Thus a new property to support interoperability problems. Additionally some implementations
inclusion of schema data is warranted. manage attachments by stripping them out and replacing with a link
to the resource. Thus a new property to support inclusion of
schema data is warranted.
Format Definition: Format Definition:
This property is defined by the following notation: This property is defined by the following notation:
sdataprop = "STRUCTURED-DATA" sdataparam sdataprop = "STRUCTURED-DATA" sdataparam
(":" text) / (":" text) /
( (
";" "ENCODING" "=" "BASE64" ";" "ENCODING" "=" "BASE64"
";" "VALUE" "=" "BINARY" ";" "VALUE" "=" "BINARY"
skipping to change at page 23, line 5 skipping to change at page 22, line 5
STRUCTURED-DATA;FMTTYPE=application/ld+json; STRUCTURED-DATA;FMTTYPE=application/ld+json;
SCHEMA="https://schema.org/SportsEvent"; SCHEMA="https://schema.org/SportsEvent";
VALUE=TEXT:{\n VALUE=TEXT:{\n
"@context": "http://schema.org"\,\n "@context": "http://schema.org"\,\n
"@type": "SportsEvent"\,\n "@type": "SportsEvent"\,\n
"homeTeam": "Pittsburgh Pirates"\,\n "homeTeam": "Pittsburgh Pirates"\,\n
"awayTeam": "San Francisco Giants"\n "awayTeam": "San Francisco Giants"\n
}\n }\n
8. New Components 7. New Components
8.1. Participant 7.1. Participant
Component name: PARTICIPANT Component name: PARTICIPANT
Purpose: This component provides information about a participant in Purpose: This component provides information about a participant in
an event or task. an event or task.
Conformance: This component can be specified multiple times in a Conformance: This component can be specified multiple times in a
"VEVENT", "VTODO", "VJOURNAL", or "VFREEBUSY" calendar component. "VEVENT", "VTODO", "VJOURNAL", or "VFREEBUSY" calendar component.
Description: This component provides information about a participant Description: This component provides information about a participant
in an event, task or poll. A participant may be an attendee in a in an event, task or poll. A participant may be an attendee in a
scheduling sense and the ATTENDEE property may be specified in scheduling sense and the ATTENDEE property may be specified in
addition. Participants in events can be individuals or addition. Participants in events can be individuals or
organizations, for example a soccer team, the spectators, or the organizations, for example a soccer team, the spectators, or the
musicians. musicians.
The SOURCE property if present may refer to an external definition STRUCTURED-DATA properties if present may refer to external
of the participant - such as a vcard. definitions of the participant - such as a vcard.
The CALENDAR-ADDRESS property if present will provide a cal- The CALENDAR-ADDRESS property if present will provide a cal-
address. If an ATTENDEE property has the same value the address. If an ATTENDEE property has the same value the
participant is considered schedulable. The PARTICIPANT component participant is considered schedulable. The PARTICIPANT component
can be used to contain additional meta-data related to the can be used to contain additional meta-data related to the
attendee. attendee.
Format Definition: Format Definition:
This component is defined by the following notation: This component is defined by the following notation:
skipping to change at page 24, line 22 skipping to change at page 23, line 22
; ;
; The following are REQUIRED, ; The following are REQUIRED,
; but MUST NOT occur more than once. ; but MUST NOT occur more than once.
; ;
dtstamp / participanttype / uid / dtstamp / participanttype / uid /
; ;
; The following are OPTIONAL, ; The following are OPTIONAL,
; but MUST NOT occur more than once. ; but MUST NOT occur more than once.
; ;
created / description / geo / last-mod / priority / seq / created / description / geo / last-mod / priority / seq /
source / status / calendaraddress / summary / url / status / calendaraddress / summary / url /
; ;
; The following are OPTIONAL, ; The following are OPTIONAL,
; and MAY occur more than once. ; and MAY occur more than once.
; ;
attach / categories / comment / attach / categories / comment /
contact / location / rstatus / related / contact / location / rstatus / related /
resources / strucloc / strucres / styleddescription / resources / strucloc / strucres / styleddescription /
iana-prop sdataprop / iana-prop
; ;
) )
Note: When the PRIORITY is supplied it defines the ordering of Note: When the PRIORITY is supplied it defines the ordering of
PARTICIPANT components with the same value for the TYPE parameter. PARTICIPANT components with the same value for the TYPE parameter.
Privacy Issues: When a LOCATION is supplied it provides information Privacy Issues: When a LOCATION is supplied it provides information
about the location of a participant at a given time or times. about the location of a participant at a given time or times.
This may represent an unacceptable privacy risk for some This may represent an unacceptable privacy risk for some
participants. User agents MUST NOT include this information participants. User agents MUST NOT include this information
without informing the participant. without informing the participant.
Example: Example:
The following is an example of this component. It contains a SOURCE The following is an example of this component. It contains a
property which points to a VCARD providing information about the STRUCTURED-DATA property which points to a VCARD providing
event participant. information about the event participant.
BEGIN:PARTICIPANT BEGIN:PARTICIPANT
PARTICIPANT-TYPE:PERFORMER PARTICIPANT-TYPE:PERFORMER
SOURCE:http://dir.example.com/vcard/aviolinist.vcf STRUCTURED-DATA;VALUE=URI:http://dir.example.com/vcard/aviolinist.vcf
END:PARTICIPANT END:PARTICIPANT
Example: Example:
The following is an example for the primary contact. The following is an example for the primary contact.
BEGIN: PARTICIPANT BEGIN: PARTICIPANT
SOURCE;FMTTYPE=text/vcard; STRUCTURED-DATA;VALUE=URI;
http://dir.example.com/vcard/contacts/contact1.vcf http://dir.example.com/vcard/contacts/contact1.vcf
PARTICIPANT-TYPE:CONTACT PARTICIPANT-TYPE:CONTACT
DESCRIPTION:A contact: DESCRIPTION:A contact:
END:PARTICIPANT END:PARTICIPANT
8.2. Schedulable Participant 7.2. Schedulable Participant
A PARTICIPANT component may represent someone or something that needs A PARTICIPANT component may represent someone or something that needs
to be scheduled as defined for ATTENDEE in [RFC5545] and [RFC5546]. to be scheduled as defined for ATTENDEE in [RFC5545] and [RFC5546].
The PARTICIPANT component may also represent someone or something The PARTICIPANT component may also represent someone or something
that is NOT to receive scheduling messages. that is NOT to receive scheduling messages.
A PARTICIPANT component is defined to be schedulable if A PARTICIPANT component is defined to be schedulable if
o It contains a CALENDAR-ADDRESS property o It contains a CALENDAR-ADDRESS property
skipping to change at page 26, line 5 skipping to change at page 25, line 5
If both of these conditions apply then the participant defined by the If both of these conditions apply then the participant defined by the
value of the URL property will take part in scheduling operations as value of the URL property will take part in scheduling operations as
defined in [RFC5546]. defined in [RFC5546].
An appropriate use for the PARTICIPANT component in scheduling would An appropriate use for the PARTICIPANT component in scheduling would
be to store SEQUENCE and DTSTAMP properties associated with replies be to store SEQUENCE and DTSTAMP properties associated with replies
from each ATTENDEE. A LOCATION property within the PARTICIPANT from each ATTENDEE. A LOCATION property within the PARTICIPANT
component might allow better selection of meeting times when component might allow better selection of meeting times when
participants are in different timezones. participants are in different timezones.
9. Extended examples 8. Extended examples
The following are some examples of the use of the properties defined The following are some examples of the use of the properties defined
in this specification. They include additional properties defined in in this specification. They include additional properties defined in
[RFC7986] which includes IMAGE. [RFC7986] which includes IMAGE.
9.1. Example 1 8.1. Example 1
The following is an example of a VEVENT describing a concert. It The following is an example of a VEVENT describing a concert. It
includes location information for the venue itself as well as includes location information for the venue itself as well as
references to parking and restaurants. references to parking and restaurants.
BEGIN:VEVENT BEGIN:VEVENT
CREATED:20170216T145739Z CREATED:20170216T145739Z
DESCRIPTION: Piano Sonata No 3\n DESCRIPTION: Piano Sonata No 3\n
Piano Sonata No 30 Piano Sonata No 30
DTSTAMP:20171116T145739Z DTSTAMP:20171116T145739Z
skipping to change at page 26, line 35 skipping to change at page 25, line 35
SUMMARY:Beethoven Piano Sonatas SUMMARY:Beethoven Piano Sonatas
UID:123456 UID:123456
STRUCTURED-LOCATION;LABEL="The venue";VALUE=URI: STRUCTURED-LOCATION;LABEL="The venue";VALUE=URI:
http://dir.example.com/venues/big-hall.vcf http://dir.example.com/venues/big-hall.vcf
STRUCTURED-LOCATION;LABEL="Parking for the venue";VALUE=URI: STRUCTURED-LOCATION;LABEL="Parking for the venue";VALUE=URI:
http://dir.example.com/venues/parking.vcf http://dir.example.com/venues/parking.vcf
IMAGE;VALUE=URI;DISPLAY=BADGE;FMTTYPE=image/png:h IMAGE;VALUE=URI;DISPLAY=BADGE;FMTTYPE=image/png:h
ttp://example.com/images/concert.png ttp://example.com/images/concert.png
BEGIN:PARTICIPANT BEGIN:PARTICIPANT
PARTICIPANT-TYPE:SPONSOR PARTICIPANT-TYPE:SPONSOR
SOURCE:http://example.com/sponsor.vcf STRUCTURED-DATA;VALUE=URI:http://example.com/sponsor.vcf
END:PARTICIPANT END:PARTICIPANT
BEGIN:PARTICIPANT BEGIN:PARTICIPANT
PARTICIPANT-TYPE:PERFORMER: PARTICIPANT-TYPE:PERFORMER:
SOURCE:http://www.example.com/people/johndoe.vcf STRUCTURED-DATA;VALUE=URI:http://www.example.com/people/johndoe.vcf
END:PARTICIPANT END:PARTICIPANT
END:VEVENT END:VEVENT
9.2. Example 2 8.2. Example 2
The following is an example of a VEVENT describing a meeting. One of The following is an example of a VEVENT describing a meeting. One of
the attendees is a remote participant. the attendees is a remote participant.
BEGIN:VEVENT BEGIN:VEVENT
CREATED:20170216T145739Z CREATED:20170216T145739Z
DTSTAMP:20101116T145739Z DTSTAMP:20101116T145739Z
DTSTART;TZID=America/New_York:20170315T150000Z DTSTART;TZID=America/New_York:20170315T150000Z
DTEND;TZID=America/New_York:20170315T163000Z DTEND;TZID=America/New_York:20170315T163000Z
LAST-MODIFIED:20170216T145739Z LAST-MODIFIED:20170216T145739Z
SUMMARY:Conference plaaning SUMMARY:Conference plaaning
UID:123456 UID:123456
ORGANIZER:mailto:a@example.com ORGANIZER:mailto:a@example.com
ATTENDEE;PARTSTAT=ACCEPTED;CN=A:mailto:a@example.com ATTENDEE;PARTSTAT=ACCEPTED;CN=A:mailto:a@example.com
ATTENDEE;RSVP=TRUE;CN=B:mailto:b@example.com ATTENDEE;RSVP=TRUE;CN=B:mailto:b@example.com
BEGIN:PARTICIPANT BEGIN:PARTICIPANT
PARTICIPANT-TYPE:ACTIVE: PARTICIPANT-TYPE:ACTIVE:
SOURCE:http://www.example.com/people/b.vcf STRUCTURED-DATA;VALUE=URI:http://www.example.com/people/b.vcf
LOCATION:At home LOCATION:At home
END:PARTICIPANT END:PARTICIPANT
END:VEVENT END:VEVENT
10. Security Considerations 9. Security Considerations
Applications using these properties need to be aware of the risks Applications using these properties need to be aware of the risks
entailed in using the URIs provided as values. See [RFC3986] for a entailed in using the URIs provided as values. See [RFC3986] for a
discussion of the security considerations relating to URIs. discussion of the security considerations relating to URIs.
Security considerations relating to the "ATTACH" property, as Security considerations relating to the "ATTACH" property, as
described in [RFC5545], are applicable to the "STRUCTURED-DATA" described in [RFC5545], are applicable to the "STRUCTURED-DATA"
property. property.
When processing HTML content applications need to be aware of the When processing HTML content applications need to be aware of the
many security and privacy issues as described in the IANA many security and privacy issues as described in the IANA
considerations section of [W3C.REC-html51-20171003] considerations section of [W3C.REC-html51-20171003]
11. Privacy Considerations 10. Privacy Considerations
Properties with a "URI" value type can expose their users to privacy Properties with a "URI" value type can expose their users to privacy
leaks as any network access of the URI data can be tracked. Clients leaks as any network access of the URI data can be tracked. Clients
SHOULD NOT automatically download data referenced by the URI without SHOULD NOT automatically download data referenced by the URI without
explicit instruction from users. This specification does not explicit instruction from users. This specification does not
introduce any additional privacy concerns beyond those described in introduce any additional privacy concerns beyond those described in
[RFC5545]. [RFC5545].
The addition of location information to the new participant component The addition of location information to the new participant component
provides information about the location of participants at a given provides information about the location of participants at a given
time. time.
12. IANA Considerations 11. IANA Considerations
12.1. Additional iCalendar Registrations 11.1. Additional iCalendar Registrations
12.1.1. Properties 11.1.1. Properties
This document defines the following new iCalendar properties to be This document defines the following new iCalendar properties to be
added to the registry defined in Section 8.2.3 of [RFC5545]: added to the registry defined in Section 8.2.3 of [RFC5545]:
+---------------------+---------+----------------------+ +---------------------+---------+----------------------+
| Property | Status | Reference | | Property | Status | Reference |
+---------------------+---------+----------------------+ +---------------------+---------+----------------------+
| CALENDAR-ADDRESS | Current | RFCXXXX, Section 7.2 | | CALENDAR-ADDRESS | Current | RFCXXXX, Section 6.2 |
| PARTICIPANT-TYPE | Current | RFCXXXX, Section 7.1 | | PARTICIPANT-TYPE | Current | RFCXXXX, Section 6.1 |
| SOURCE | Current | RFCXXXX, Section 6 | | STRUCTURED-DATA | Current | RFCXXXX, Section 6.6 |
| STRUCTURED-DATA | Current | RFCXXXX, Section 7.6 | | STYLED-DESCRIPTION | Current | RFCXXXX, Section 6.3 |
| STYLED-DESCRIPTION | Current | RFCXXXX, Section 7.3 | | STRUCTURED-LOCATION | Current | RFCXXXX, Section 6.4 |
| STRUCTURED-LOCATION | Current | RFCXXXX, Section 7.4 | | STRUCTURED-RESOURCE | Current | RFCXXXX, Section 6.5 |
| STRUCTURED-RESOURCE | Current | RFCXXXX, Section 7.5 |
+---------------------+---------+----------------------+ +---------------------+---------+----------------------+
12.1.2. Parameters 11.1.2. Parameters
This document defines the following new iCalendar property parameters This document defines the following new iCalendar property parameters
to be added to the registry defined in Section 8.2.4 of [RFC5545]: to be added to the registry defined in Section 8.2.4 of [RFC5545]:
+--------------------+---------+----------------------+ +--------------------+---------+----------------------+
| Property Parameter | Status | Reference | | Property Parameter | Status | Reference |
+--------------------+---------+----------------------+ +--------------------+---------+----------------------+
| LOCTYPE | Current | RFCXXXX, Section 5.1 | | LOCTYPE | Current | RFCXXXX, Section 5.1 |
| ORDER | Current | RFCXXXX, Section 5.3 | | ORDER | Current | RFCXXXX, Section 5.3 |
| RESTYPE | Current | RFCXXXX, Section 5.2 | | RESTYPE | Current | RFCXXXX, Section 5.2 |
| SCHEMA | Current | RFCXXXX, Section 5.4 | | SCHEMA | Current | RFCXXXX, Section 5.4 |
+--------------------+---------+----------------------+ +--------------------+---------+----------------------+
12.1.3. Components 11.1.3. Components
This document defines the following new iCalendar components to be This document defines the following new iCalendar components to be
added to the registry defined in Section 8.3.1 of [RFC5545]: added to the registry defined in Section 8.3.1 of [RFC5545]:
+-------------+---------+----------------------+ +-------------+---------+----------------------+
| Component | Status | Reference | | Component | Status | Reference |
+-------------+---------+----------------------+ +-------------+---------+----------------------+
| PARTICIPANT | Current | RFCXXXX, Section 8.1 | | PARTICIPANT | Current | RFCXXXX, Section 7.1 |
+-------------+---------+----------------------+ +-------------+---------+----------------------+
12.2. New Registration Tables 11.2. New Registration Tables
This section defines new registration tables for PARTICIPANT-TYPE and This section defines new registration tables for PARTICIPANT-TYPE and
RESTYPE values. These tables are updated using the same approaches RESTYPE values. These tables are updated using the same approaches
laid down in Section 8.2.1 of [RFC5545] laid down in Section 8.2.1 of [RFC5545]
12.2.1. Participant Types 11.2.1. Participant Types
The following table has been used to initialize the participant types The following table has been used to initialize the participant types
registry. registry.
+-------------------+---------+----------------------+ +-------------------+---------+----------------------+
| Participant Type | Status | Reference | | Participant Type | Status | Reference |
+-------------------+---------+----------------------+ +-------------------+---------+----------------------+
| ACTIVE | Current | RFCXXXX, Section 7.1 | | ACTIVE | Current | RFCXXXX, Section 6.1 |
| INACTIVE | Current | RFCXXXX, Section 7.1 | | INACTIVE | Current | RFCXXXX, Section 6.1 |
| SPONSOR | Current | RFCXXXX, Section 7.1 | | SPONSOR | Current | RFCXXXX, Section 6.1 |
| CONTACT | Current | RFCXXXX, Section 7.1 | | CONTACT | Current | RFCXXXX, Section 6.1 |
| BOOKING-CONTACT | Current | RFCXXXX, Section 7.1 | | BOOKING-CONTACT | Current | RFCXXXX, Section 6.1 |
| EMERGENCY-CONTACT | Current | RFCXXXX, Section 7.1 | | EMERGENCY-CONTACT | Current | RFCXXXX, Section 6.1 |
| PUBLICITY-CONTACT | Current | RFCXXXX, Section 7.1 | | PUBLICITY-CONTACT | Current | RFCXXXX, Section 6.1 |
| PLANNER-CONTACT | Current | RFCXXXX, Section 7.1 | | PLANNER-CONTACT | Current | RFCXXXX, Section 6.1 |
| PERFORMER | Current | RFCXXXX, Section 7.1 | | PERFORMER | Current | RFCXXXX, Section 6.1 |
| SPEAKER | Current | RFCXXXX, Section 7.1 | | SPEAKER | Current | RFCXXXX, Section 6.1 |
+-------------------+---------+----------------------+ +-------------------+---------+----------------------+
12.2.2. Resource Types 11.2.2. Resource Types
The following table has been used to initialize the resource types The following table has been used to initialize the resource types
registry. registry.
+-------------------------+---------+----------------------+ +-------------------------+---------+----------------------+
| Resource Type | Status | Reference | | Resource Type | Status | Reference |
+-------------------------+---------+----------------------+ +-------------------------+---------+----------------------+
| PROJECTOR | Current | RFCXXXX, Section 5.2 | | PROJECTOR | Current | RFCXXXX, Section 5.2 |
| ROOM | Current | RFCXXXX, Section 5.2 | | ROOM | Current | RFCXXXX, Section 5.2 |
| REMOTE-CONFERENCE-AUDIO | Current | RFCXXXX, Section 5.2 | | REMOTE-CONFERENCE-AUDIO | Current | RFCXXXX, Section 5.2 |
| REMOTE-CONFERENCE-VIDEO | Current | RFCXXXX, Section 5.2 | | REMOTE-CONFERENCE-VIDEO | Current | RFCXXXX, Section 5.2 |
+-------------------------+---------+----------------------+ +-------------------------+---------+----------------------+
13. Acknowledgements 12. Acknowledgements
The author would like to thank Chuck Norris of eventful.com for his The author would like to thank Chuck Norris of eventful.com for his
work which led to the development of this RFC. work which led to the development of this RFC.
The author would also like to thank the members of CalConnect, The The author would also like to thank the members of CalConnect, The
Calendaring and Scheduling Consortium, the Event Publication Calendaring and Scheduling Consortium, the Event Publication
technical committee and the following individuals for contributing technical committee and the following individuals for contributing
their ideas and support: their ideas and support:
Cyrus Daboo, John Haug, Dan Mendell, Ken Murchison, Scott Otis. Cyrus Daboo, John Haug, Dan Mendell, Ken Murchison, Scott Otis.
14. References 13. References
14.1. Normative References 13.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2426] Dawson, F. and T. Howes, "vCard MIME Directory Profile", [RFC2426] Dawson, F. and T. Howes, "vCard MIME Directory Profile",
RFC 2426, DOI 10.17487/RFC2426, September 1998, RFC 2426, DOI 10.17487/RFC2426, September 1998,
<https://www.rfc-editor.org/info/rfc2426>. <https://www.rfc-editor.org/info/rfc2426>.
skipping to change at page 31, line 23 skipping to change at page 30, line 23
Recommendation REC-html51-20171003, October 2017, Recommendation REC-html51-20171003, October 2017,
<https://www.w3.org/TR/2017/REC-html51-20171003>. <https://www.w3.org/TR/2017/REC-html51-20171003>.
[W3C.REC-xml-20081126] [W3C.REC-xml-20081126]
Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., and Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., and
F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth
Edition)", World Wide Web Consortium Recommendation REC- Edition)", World Wide Web Consortium Recommendation REC-
xml-20081126, November 2008, xml-20081126, November 2008,
<http://www.w3.org/TR/2008/REC-xml-20081126>. <http://www.w3.org/TR/2008/REC-xml-20081126>.
14.2. Informative References 13.2. Informative References
[iana-property-registry] [iana-property-registry]
"IANA iCalendar Element Registries", "IANA iCalendar Element Registries",
<https://www.iana.org/assignments/icalendar/ <https://www.iana.org/assignments/icalendar/
icalendar.xhtml>. icalendar.xhtml>.
Appendix A. Open issues Appendix A. Open issues
None at the moment None at the moment
Appendix B. Change log Appendix B. Change log
To be deleted on publication
calext-v14 2019-06-11 MD
o Definition of event and social calendaring.
o Remove redefinition of SOURCE - use STRUCTURED-DATA.
calext-v13 2019-05-26 MD calext-v13 2019-05-26 MD
o Respond to various issues. o Respond to various issues.
calext-v12 2019-02-28 MD calext-v12 2019-02-28 MD
o Fix styled-description example. Respond to various AD issues. o Fix styled-description example. Respond to various AD issues.
Some typos. Some typos.
calext-v11 2019-02-27 MD calext-v11 2019-02-27 MD
skipping to change at page 32, line 22 skipping to change at page 31, line 32
calext-v04 2017-10-11 MD calext-v04 2017-10-11 MD
o Change SCHEDULE-ADDRESS to CALENDAR-ADDRESS o Change SCHEDULE-ADDRESS to CALENDAR-ADDRESS
o Explicitly broaden scope of SOURCE o Explicitly broaden scope of SOURCE
o Add initial registry for RESTYPE and move new tables into separate o Add initial registry for RESTYPE and move new tables into separate
section. section.
o Fix PARTTYPE/PARTICPANT-TYPE inconsistency o Fix PARTTYPE/PARTICIPANT-TYPE inconsistency
calext-v03 2017-10-09 MD calext-v03 2017-10-09 MD
o Mostly typographical and other minor changes o Mostly typographical and other minor changes
calext-v02 2017-04-20 MD calext-v02 2017-04-20 MD
o Add SCHEDULE-ADDRESS property o Add SCHEDULE-ADDRESS property
o PARTICIPANT becomes a component rather than a property. Turn many o PARTICIPANT becomes a component rather than a property. Turn many
 End of changes. 56 change blocks. 
192 lines changed or deleted 162 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/