draft-ietf-calext-eventpub-extensions-07.txt   draft-ietf-calext-eventpub-extensions-08.txt 
Network Working Group M. Douglass Network Working Group M. Douglass
Internet-Draft Spherical Cow Group Internet-Draft Spherical Cow Group
Updates: 5545,5546 (if approved) May 15, 2018 Updates: 5545 (if approved) August 6, 2018
Intended status: Standards Track Intended status: Standards Track
Expires: November 16, 2018 Expires: February 7, 2019
Event Publishing Extensions to iCalendar Event Publishing Extensions to iCalendar
draft-ietf-calext-eventpub-extensions-07 draft-ietf-calext-eventpub-extensions-08
Abstract Abstract
This specification updates [RFC5545] and [RFC5546] by introducing a This specification updates [RFC5545] and [RFC5546] by introducing a
number of new iCalendar properties and components which are of number of new iCalendar properties and components which are of
particular use for event publishers and in social networking. particular use for 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 iCalendar [RFC5545] to allow for data that is directly pertinent to
an event or task to be included with the calendar data. an event or task to be included with the calendar data.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
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 16, 2018. This Internet-Draft will expire on February 7, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
skipping to change at page 2, line 42 skipping to change at page 2, line 42
8. New Components . . . . . . . . . . . . . . . . . . . . . . . 21 8. New Components . . . . . . . . . . . . . . . . . . . . . . . 21
8.1. Participant . . . . . . . . . . . . . . . . . . . . . . . 22 8.1. Participant . . . . . . . . . . . . . . . . . . . . . . . 22
8.2. Schedulable Participant . . . . . . . . . . . . . . . . . 24 8.2. Schedulable Participant . . . . . . . . . . . . . . . . . 24
9. Extended examples . . . . . . . . . . . . . . . . . . . . . . 24 9. Extended examples . . . . . . . . . . . . . . . . . . . . . . 24
9.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . 24 9.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . 24
9.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . 25 9.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . 25
10. Security Considerations . . . . . . . . . . . . . . . . . . . 26 10. Security Considerations . . . . . . . . . . . . . . . . . . . 26
11. Privacy Considerations . . . . . . . . . . . . . . . . . . . 26 11. Privacy Considerations . . . . . . . . . . . . . . . . . . . 26
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
12.1. Additional iCalendar Registrations . . . . . . . . . . . 27 12.1. Additional iCalendar Registrations . . . . . . . . . . . 27
12.1.1. Property Registrations . . . . . . . . . . . . . . . 27 12.1.1. Properties . . . . . . . . . . . . . . . . . . . . . 27
12.1.2. Parameter Registrations . . . . . . . . . . . . . . 27 12.1.2. Parameters . . . . . . . . . . . . . . . . . . . . . 27
12.1.3. Component Registrations . . . . . . . . . . . . . . 27 12.1.3. Components . . . . . . . . . . . . . . . . . . . . . 27
12.2. New Registration Tables . . . . . . . . . . . . . . . . 28 12.2. New Registration Tables . . . . . . . . . . . . . . . . 28
12.2.1. Participant Types Registry . . . . . . . . . . . . . 28 12.2.1. Participant Types . . . . . . . . . . . . . . . . . 28
12.2.2. Resource Types Registry . . . . . . . . . . . . . . 28 12.2.2. Resource Types . . . . . . . . . . . . . . . . . . . 28
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28
14. Normative References . . . . . . . . . . . . . . . . . . . . 29 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 29
14.1. Normative References . . . . . . . . . . . . . . . . . . 29
14.2. Informative References . . . . . . . . . . . . . . . . . 29
Appendix A. Open issues . . . . . . . . . . . . . . . . . . . . 30 Appendix A. Open issues . . . . . . . . . . . . . . . . . . . . 30
Appendix B. Change log . . . . . . . . . . . . . . . . . . . . . 30 Appendix B. Change log . . . . . . . . . . . . . . . . . . . . . 30
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 32 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 32
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
skipping to change at page 9, line 35 skipping to change at page 9, line 35
Description: The ORDER parameter is OPTIONAL and is used to indicate Description: The ORDER parameter is OPTIONAL and is used to indicate
the relative ordering of the corresponding instance of a property. the relative ordering of the corresponding instance of a property.
Its value MUST be an integer greater than or equal to 1 that Its value MUST be an integer greater than or equal to 1 that
quantifies the order with 1 being the first in the ordering. quantifies the order with 1 being the first in the ordering.
When the parameter is absent, the default MUST be to interpret the When the parameter is absent, the default MUST be to interpret the
property instance as being at the lowest level of ordering, that property instance as being at the lowest level of ordering, that
is, the property will appear after any other instances of the same is, the property will appear after any other instances of the same
property with any value of ORDER. property with any value of ORDER.
When any ORDER parameters have the same value all the associated
properties appear as a group within which there is no defined
order.
Note that the value of this parameter is to be interpreted only in Note that the value of this parameter is to be interpreted only in
relation to values assigned to other corresponding instances of relation to values assigned to other corresponding instances of
the same property in the same entity. A given value, or the the same property in the same entity. A given value, or the
absence of a value, MUST NOT be interpreted on its own. absence of a value, MUST NOT be interpreted on its own.
This parameter MAY be applied to any property that allows multiple This parameter MAY be applied to any property that allows multiple
instances. instances.
5.4. Schema 5.4. Schema
skipping to change at page 14, line 33 skipping to change at page 14, line 33
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.
Property Parameters: IANA, non-standard, id, alternate text Property Parameters: IANA, non-standard, id, alternate text
representation, format type, and language property parameters can representation, format type, and language property parameters can
be specified on this property. be specified on this property.
Conformance: The property can be specified multiple times in the Conformance: The property can be specified multiple times in the
"VEVENT", "VTODO", "VJOURNAL", or "VALARM" calendar components. "VEVENT", "VTODO", "VJOURNAL", "PARTICIPANT", or "VALARM" calendar
components.
Description: This property is used in the "VEVENT" and "VTODO" to Description: This property is used in the "VEVENT" and "VTODO" to
capture lengthy textual descriptions associated with the activity. capture lengthy textual descriptions associated with the activity.
This property is used in the "VJOURNAL" calendar component to This property is used in the "VJOURNAL" calendar component to
capture one or more textual journal entries. This property is capture one or more textual journal entries. This property is
used in the "VALARM" calendar component to capture the display used in the "VALARM" calendar component to capture the display
text for a DISPLAY category of alarm, and to capture the body text text for a DISPLAY category of alarm, and to capture the body text
for an EMAIL category of alarm. for an EMAIL category of alarm. In the PARTICIPANT component it
provides a detailed description of the participant.
VALUE=TEXT is used to provide rich-text variants of the plain-text VALUE=TEXT is used to provide rich-text variants of the plain-text
DESCRIPTION property. DESCRIPTION property.
VALUE=URI is used to provide a link to rich-text content which is VALUE=URI is used to provide a link to rich-text content which is
expected to be displayed inline as part of the event. expected to be displayed inline as part of the event.
The intent of this property is limited to providing a styled and/ The intent of this property is limited to providing a styled and/
or language specific version of the DESCRIPTION property. The URL or language specific version of the DESCRIPTION property. The URL
property should be used to link to websites or other related property should be used to link to websites or other related
skipping to change at page 22, line 24 skipping to change at page 22, line 24
Description: This component provides information about an Description: This component provides information about an
participant in an event, task or poll. A participant may be an participant in an event, task or poll. A participant may be an
attendee in a scheduling sense and the ATTENDEE property may be attendee in a scheduling sense and the ATTENDEE property may be
specified in addition. Participants in events can be individuals specified in addition. Participants in events can be individuals
or organizations, for example a soccer team, the spectators, or or organizations, for example a soccer team, the spectators, or
the musicians. the musicians.
The SOURCE property if present may refer to an external definition The SOURCE property if present may refer to an external definition
of the participant - such as a vcard. of the participant - such as a vcard.
The STRUCTURED-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 property is defined by the following notation: This property is defined by the following notation:
participantc = "BEGIN" ":" "PARTICIPANT" CRLF participantc = "BEGIN" ":" "PARTICIPANT" CRLF
partprop *alarmc partprop *alarmc
"END" ":" "PARTICIPANT" CRLF "END" ":" "PARTICIPANT" CRLF
partprop = *( partprop = *(
; ;
; The following are REQUIRED, ; The following are REQUIRED,
; but MUST NOT occur more than once. ; but MUST NOT occur more than once.
; ;
dtstamp / participanttype / dtstamp / participanttype /
; ;
; The following are OPTIONAL, ; The following are OPTIONAL,
; but MUST NOT occur more than once. ; but MUST NOT occur more than once.
; ;
created / description / last-mod / priority / seq / created / description / last-mod / priority / seq /
source / status / scheduleaddress / summary / url / source / 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 / rstatus / related / contact / location / rstatus / related /
resources / x-prop / iana-prop resources / strucloc / strucres / styleddescription /
; x-prop / 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.
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 SOURCE
property which points to a VCARD providing information about the property which points to a VCARD providing information about the
event participant. event participant.
skipping to change at page 24, line 9 skipping to change at page 24, line 9
PARTICIPANT-TYPE:PRINCIPAL_PERFORMER PARTICIPANT-TYPE:PRINCIPAL_PERFORMER
SOURCE:http://dir.example.com/vcard/aviolinist.vcf SOURCE: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; SOURCE;FMTTYPE=text/vcard;
http://dir.example.com/vcard/contacts/contact1.vcf http://dir.example.com/vcard/contacts/contact1.vcf
PARTICIPANT-TYPE:PRIMARY-CONTACT PARTICIPANT-TYPE:PRIMARY-CONTACT
DESCRIPTION:A contact: DESCRIPTION:A contact:
END:PARTICIPANT END:PARTICIPANT
8.2. Schedulable Participant 8.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.
skipping to change at page 27, line 7 skipping to change at page 27, line 7
introduce any additional privacy concerns beyond those described in introduce any additional privacy concerns beyond those described in
[RFC5545]. [RFC5545].
12. IANA Considerations 12. IANA Considerations
This section defines updates to the tables defined in [RFC5545] and This section defines updates to the tables defined in [RFC5545] and
new tables. new tables.
12.1. Additional iCalendar Registrations 12.1. Additional iCalendar Registrations
12.1.1. Property Registrations 12.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 7.2 |
| PARTICIPANT-TYPE | Current | RFCXXXX, Section 7.1 | | PARTICIPANT-TYPE | Current | RFCXXXX, Section 7.1 |
| SOURCE | Current | RFCXXXX, Section 6 | | SOURCE | Current | RFCXXXX, Section 6 |
| STRUCTURED-DATA | Current | RFCXXXX, Section 7.6 | | STRUCTURED-DATA | Current | RFCXXXX, Section 7.6 |
| STYLED-DESCRIPTION | Current | RFCXXXX, Section 7.3 | | STYLED-DESCRIPTION | Current | RFCXXXX, Section 7.3 |
| STRUCTURED-LOCATION | Current | RFCXXXX, Section 7.4 | | STRUCTURED-LOCATION | Current | RFCXXXX, Section 7.4 |
| STRUCTURED-RESOURCE | Current | RFCXXXX, Section 7.5 | | STRUCTURED-RESOURCE | Current | RFCXXXX, Section 7.5 |
+---------------------+---------+----------------------+ +---------------------+---------+----------------------+
12.1.2. Parameter Registrations 12.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. Component Registrations 12.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 8.1 |
+-------------+---------+----------------------+ +-------------+---------+----------------------+
12.2. New Registration Tables 12.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 maybe updated using the same approaches RESTYPE values. These tables may be updated using the same
laid down in Section 8.2.1 of [RFC5545] approaches laid down in Section 8.2.1 of [RFC5545]
12.2.1. Participant Types Registry 12.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 7.1 |
| INACTIVE | Current | RFCXXXX, Section 7.1 | | INACTIVE | Current | RFCXXXX, Section 7.1 |
| SPONSOR | Current | RFCXXXX, Section 7.1 | | SPONSOR | Current | RFCXXXX, Section 7.1 |
| CONTACT | Current | RFCXXXX, Section 7.1 | | CONTACT | Current | RFCXXXX, Section 7.1 |
| BOOKING-CONTACT | Current | RFCXXXX, Section 7.1 | | BOOKING-CONTACT | Current | RFCXXXX, Section 7.1 |
| EMERGENCY-CONTACT | Current | RFCXXXX, Section 7.1 | | EMERGENCY-CONTACT | Current | RFCXXXX, Section 7.1 |
| PUBLICITY-CONTACT | Current | RFCXXXX, Section 7.1 | | PUBLICITY-CONTACT | Current | RFCXXXX, Section 7.1 |
| PLANNER-CONTACT | Current | RFCXXXX, Section 7.1 | | PLANNER-CONTACT | Current | RFCXXXX, Section 7.1 |
| PERFORMER | Current | RFCXXXX, Section 7.1 | | PERFORMER | Current | RFCXXXX, Section 7.1 |
| SPEAKER | Current | RFCXXXX, Section 7.1 | | SPEAKER | Current | RFCXXXX, Section 7.1 |
+-------------------+---------+----------------------+ +-------------------+---------+----------------------+
12.2.2. Resource Types Registry 12.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 |
skipping to change at page 29, line 9 skipping to change at page 29, line 9
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. Normative References 14. References
14.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>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005, RFC 3986, DOI 10.17487/RFC3986, January 2005,
<https://www.rfc-editor.org/info/rfc3986>. <https://www.rfc-editor.org/info/rfc3986>.
skipping to change at page 29, line 43 skipping to change at page 29, line 45
<https://www.rfc-editor.org/info/rfc5546>. <https://www.rfc-editor.org/info/rfc5546>.
[RFC7986] Daboo, C., "New Properties for iCalendar", RFC 7986, [RFC7986] Daboo, C., "New Properties for iCalendar", RFC 7986,
DOI 10.17487/RFC7986, October 2016, DOI 10.17487/RFC7986, October 2016,
<https://www.rfc-editor.org/info/rfc7986>. <https://www.rfc-editor.org/info/rfc7986>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[W3C.REC-xml-20060816] 14.2. Informative References
Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., and
F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fourth [iana-property-registry]
Edition)", World Wide Web Consortium Recommendation REC- "IANA iCalendar Element Registries",
xml-20060816, August 2006, <https://www.iana.org/assignments/icalendar/
<http://www.w3.org/TR/2006/REC-xml-20060816>. 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
calext-v08 2018-07-06 MD
o Add some text for equal ORDER values
o Switched scheduleaddress to calendaraddress in participant abnf.
Also added more properties
o Fixed PARTICIPANT abnf
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/PARTICPANT-TYPE inconsistency
 End of changes. 24 change blocks. 
53 lines changed or deleted 74 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/