draft-ietf-calext-eventpub-extensions-10.txt   draft-ietf-calext-eventpub-extensions-11.txt 
Network Working Group M. Douglass Network Working Group M. Douglass
Internet-Draft Spherical Cow Group Internet-Draft Spherical Cow Group
Updates: 5545 (if approved) October 19, 2018 Updates: 5545 (if approved) February 25, 2019
Intended status: Standards Track Intended status: Standards Track
Expires: April 22, 2019 Expires: August 29, 2019
Event Publishing Extensions to iCalendar Event Publishing Extensions to iCalendar
draft-ietf-calext-eventpub-extensions-10 draft-ietf-calext-eventpub-extensions-11
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 April 22, 2019. This Internet-Draft will expire on August 29, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 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 . . . . . . . . . . . . 4 1.1. Conventions Used in This Document . . . . . . . . . . . . 4
2. Components and properties . . . . . . . . . . . . . . . . . . 4 2. Components and properties . . . . . . . . . . . . . . . . . . 4
3. Typed References . . . . . . . . . . . . . . . . . . . . . . 4 3. Typed References . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 5 3.1. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1.1. Piano Concert Performance . . . . . . . . . . . . . . 5 3.1.1. Piano Concert Performance . . . . . . . . . . . . . . 6
3.1.2. Itineraries . . . . . . . . . . . . . . . . . . . . . 6 3.1.2. Itineraries . . . . . . . . . . . . . . . . . . . . . 6
3.1.2.1. Reserving facilities . . . . . . . . . . . . . . 6 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 . . . . . . . . . . . . . . . . . . . . . . . . . 8 5.1. Loctype . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.2. Restype . . . . . . . . . . . . . . . . . . . . . . . . . 8 5.2. Restype . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.3. Order . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.3. Order . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.4. Schema . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.4. Schema . . . . . . . . . . . . . . . . . . . . . . . . . 9
6. Redefined Property SOURCE . . . . . . . . . . . . . . . . . . 10 5.5. Derived . . . . . . . . . . . . . . . . . . . . . . . . . 10
6. Redefined Property SOURCE . . . . . . . . . . . . . . . . . . 11
7. New Properties . . . . . . . . . . . . . . . . . . . . . . . 12 7. New Properties . . . . . . . . . . . . . . . . . . . . . . . 12
7.1. Participant Type . . . . . . . . . . . . . . . . . . . . 12 7.1. Participant Type . . . . . . . . . . . . . . . . . . . . 12
7.2. Calendar Address . . . . . . . . . . . . . . . . . . . . 13 7.2. Calendar Address . . . . . . . . . . . . . . . . . . . . 14
7.3. Styled-Description . . . . . . . . . . . . . . . . . . . 14 7.3. Styled-Description . . . . . . . . . . . . . . . . . . . 15
7.4. Structured-Location . . . . . . . . . . . . . . . . . . . 16 7.4. Structured-Location . . . . . . . . . . . . . . . . . . . 17
7.5. Structured-Resource . . . . . . . . . . . . . . . . . . . 17 7.5. Structured-Resource . . . . . . . . . . . . . . . . . . . 18
7.6. Structured-Data . . . . . . . . . . . . . . . . . . . . . 19 7.6. Structured-Data . . . . . . . . . . . . . . . . . . . . . 20
8. New Components . . . . . . . . . . . . . . . . . . . . . . . 21 8. New Components . . . . . . . . . . . . . . . . . . . . . . . 22
8.1. Participant . . . . . . . . . . . . . . . . . . . . . . . 22 8.1. Participant . . . . . . . . . . . . . . . . . . . . . . . 23
8.2. Schedulable Participant . . . . . . . . . . . . . . . . . 24 8.2. Schedulable Participant . . . . . . . . . . . . . . . . . 25
9. Extended examples . . . . . . . . . . . . . . . . . . . . . . 24 9. Extended examples . . . . . . . . . . . . . . . . . . . . . . 25
9.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . 24 9.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . 25
9.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . 25 9.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . 26
10. Security Considerations . . . . . . . . . . . . . . . . . . . 26 10. Security Considerations . . . . . . . . . . . . . . . . . . . 27
11. Privacy Considerations . . . . . . . . . . . . . . . . . . . 26 11. Privacy Considerations . . . . . . . . . . . . . . . . . . . 27
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
12.1. Additional iCalendar Registrations . . . . . . . . . . . 27 12.1. Additional iCalendar Registrations . . . . . . . . . . . 28
12.1.1. Properties . . . . . . . . . . . . . . . . . . . . . 27 12.1.1. Properties . . . . . . . . . . . . . . . . . . . . . 28
12.1.2. Parameters . . . . . . . . . . . . . . . . . . . . . 27 12.1.2. Parameters . . . . . . . . . . . . . . . . . . . . . 28
12.1.3. Components . . . . . . . . . . . . . . . . . . . . . 27 12.1.3. Components . . . . . . . . . . . . . . . . . . . . . 28
12.2. New Registration Tables . . . . . . . . . . . . . . . . 28 12.2. New Registration Tables . . . . . . . . . . . . . . . . 29
12.2.1. Participant Types . . . . . . . . . . . . . . . . . 28 12.2.1. Participant Types . . . . . . . . . . . . . . . . . 29
12.2.2. Resource Types . . . . . . . . . . . . . . . . . . . 28 12.2.2. Resource Types . . . . . . . . . . . . . . . . . . . 29
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 29
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 29 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 30
14.1. Normative References . . . . . . . . . . . . . . . . . . 29 14.1. Normative References . . . . . . . . . . . . . . . . . . 30
14.2. Informative References . . . . . . . . . . . . . . . . . 29 14.2. Informative References . . . . . . . . . . . . . . . . . 30
Appendix A. Open issues . . . . . . . . . . . . . . . . . . . . 31
Appendix A. Open issues . . . . . . . . . . . . . . . . . . . . 30 Appendix B. Change log . . . . . . . . . . . . . . . . . . . . . 31
Appendix B. Change log . . . . . . . . . . . . . . . . . . . . . 30 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 33
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
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 36 skipping to change at page 3, line 36
between servers). Formats such as VCARD are likely to be most useful between servers). Formats such as VCARD are likely to be most useful
to the receivers of such events as they may be used in other to the receivers of such events as they may be used in other
applications - such as address books. applications - such as address books.
This specification defines a new PARTICIPANT component. Many people This specification defines a new PARTICIPANT component. Many people
or groups may participate in an event. This component provides or groups may participate in an event. This component provides
detailed information. Such participants may act as attendees to the detailed information. Such participants may act as attendees to the
event (or derived events) or may just provide a reference - perhaps event (or derived events) or may just provide a reference - perhaps
for mailing lists. for mailing lists.
Additionally this specification defines a new use for the RELATED
parameter to allow locations to be defined as the start and/or end
location of a component.
The following properties are defined in this specification The following properties are defined in this specification
STYLED-DESCRIPTION: Supports HTML descriptions. Event publishers STYLED-DESCRIPTION: Supports rich-text descriptions, for example
typically wish to provide more and better formatted information HTML. Event publishers typically wish to provide more and better
about the event. formatted information about the event.
STRUCTURED-LOCATION: There may be a number of locations associated STRUCTURED-LOCATION: There may be a number of locations associated
with an event. This provides detailed information about the with an event. This provides detailed information about the
location. location.
STRUCTURED-RESOURCE: Events need resources such as rooms, STRUCTURED-RESOURCE: Events need resources such as rooms,
projectors, conferencing capabilities. projectors, conferencing capabilities.
STRUCTURED-DATA: The existing properties in iCalendar cover key STRUCTURED-DATA: The existing properties in iCalendar cover key
elements of events and tasks such as start time, end time, elements of events and tasks such as start time, end time,
skipping to change at page 8, line 24 skipping to change at page 8, line 24
loctypeparam = "LOCTYPE" "=" param-value loctypeparam = "LOCTYPE" "=" param-value
Description: This parameter MAY be specified on STRUCTURED-LOCATION Description: This parameter MAY be specified on STRUCTURED-LOCATION
and provides a way to differentiate multiple properties. For and provides a way to differentiate multiple properties. For
example, it allows event producers to provide location information example, it allows event producers to provide location information
for the venue and the parking. for the venue and the parking.
Values for this parameter are taken from the values defined in Values for this parameter are taken from the values defined in
[RFC4589]. New location types SHOULD be registered in the manner [RFC4589]. New location types SHOULD be registered in the manner
laid down in that specification laid down in that specification.
5.2. Restype 5.2. Restype
Parameter name: RESTYPE Parameter name: RESTYPE
Purpose: To specify the type of resource. Purpose: To specify the type of resource.
Format Definition: Format Definition:
This parameter is defined by the following notation: This parameter is defined by the following notation:
skipping to change at page 8, line 50 skipping to change at page 8, line 50
/ "REMOTE-CONFERENCE-AUDIO" / "REMOTE-CONFERENCE-AUDIO"
/ "REMOTE-CONFERENCE-VIDEO" / "REMOTE-CONFERENCE-VIDEO"
/ x-name ; Experimental status / x-name ; Experimental status
/ iana-token) ; Other IANA-registered / iana-token) ; Other IANA-registered
; values ; values
Description: This parameter MAY be specified on STRUCTURED-RESOURCE Description: This parameter MAY be specified on STRUCTURED-RESOURCE
and provides a way to differentiate multiple properties. and provides a way to differentiate multiple properties.
The registered values are described below. New resource types The registered values are described below. New resource types
SHOULD be registered in the manner laid down in this specification SHOULD be registered in the manner laid down in this
specification.
ROOM: A room for the event/meeting. ROOM: A room for the event/meeting.
PROJECTOR: Projection equipment. PROJECTOR: Projection equipment.
REMOTE-CONFERENCE-AUDIO: Audio remote conferencing facilities. REMOTE-CONFERENCE-AUDIO: Audio remote conferencing facilities.
REMOTE-CONFERENCE-VIDEO: Video remote conferencing facilities. REMOTE-CONFERENCE-VIDEO: Video remote conferencing facilities.
5.3. Order 5.3. Order
skipping to change at page 10, line 24 skipping to change at page 10, line 24
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:Zm9vYmFy
5.5. Derived
Parameter Name: DERIVED
Purpose: To specify that the value of the associated property is
derived from some other property value or values.
Format Definition:
This parameter is defined by the following notation:
derivedparam = "DERIVED" "=" ("TRUE" / "FALSE")
; Default is FALSE
Description: This property parameter can be specified on any
property when the value is derived from some other property or
properties. When present with a value of TRUE clients MUST NOT
update the property.
As an example, if a STYLED-DESCRIPTION property is present with
FMTTYPE="application/rtf" then there may be an additional STYLED-
DESCRIPTION property with FMTTYPE="text/html" and DERIVED=TRUE and
a value created from the rtf value.
Example:
STRUCTURED-DESCRIPTION;FMTTYPE=text/html;
DERIVED=TRUE:<html>...
6. Redefined Property SOURCE 6. Redefined Property SOURCE
The SOURCE property defined in [RFC7986] is redefined to allow The SOURCE property defined in [RFC7986] is redefined to allow
VALUE=TEXT and broaden its usage to any component. VALUE=TEXT and broaden its usage to any component.
Property name: SOURCE Property name: SOURCE
Purpose: This property provides a reference to information about a Purpose: This property provides a reference to information about a
component such as a participant possibly as a vcard or optionally component such as a participant possibly as a vcard or optionally
a plain text typed value. a plain text typed value.
skipping to change at page 14, line 20 skipping to change at page 15, line 10
This parameter is defined by the following notation: This parameter is defined by the following notation:
calendaraddress = "CALENDAR-ADDRESS" "=" cal-address calendaraddress = "CALENDAR-ADDRESS" "=" cal-address
7.3. Styled-Description 7.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 or augment that provided by the descriptions to replace that provided by the DESCRIPTION property.
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.
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, derived and language property
be specified on this property. parameters can 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", "PARTICIPANT", or "VALARM" calendar "VEVENT", "VTODO", "VJOURNAL", "PARTICIPANT", or "VALARM" calendar
components. components.
If it does appear more than once there MUST be exactly one
instance of the property with no DERIVED parameter or
DERIVED=FALSE. All others MUST have DERIVED=TRUE.
Additionally, if there is one or more STYLED-DESCRIPTION property
then the DESCRIPTION property should be either absent or have the
parameter DERIVED=TRUE.
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. In the PARTICIPANT component it for an EMAIL category of alarm. In the PARTICIPANT component it
provides a detailed description of the participant. 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 inline as the property
DESCRIPTION property. value.
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/ In either case the DESCRIPTION property should be absent or
or language specific version of the DESCRIPTION property. The URL contain a plain text rendering of the styled text.
property should be used to link to websites or other related
information.
Applications MAY attempt to guess the media type of the resource Applications MAY attempt to guess the media type of the resource
via inspection of its content if and only if the media type of the via inspection of its content if and only if the media type of the
resource is not given by the "FMTTYPE" parameter. If the media resource is not given by the "FMTTYPE" parameter. If the media
type remains unknown, calendar applications SHOULD treat it as type remains unknown, calendar applications SHOULD treat it as
type "text/html". type "text/html".
Multiple STYLED-DESCRIPTION properties may be used to provide Multiple STYLED-DESCRIPTION properties may be used to provide
different formats or different language variants. different formats or different language variants. However all but
one MUST have DERIVED=TRUE.
Format Definition: Format Definition:
This property is defined by the following notation: This property is defined by the following notation:
styleddescription = "STYLED-DESCRIPTION" styleddescparam ":" styleddescription = "STYLED-DESCRIPTION" styleddescparam ":"
( (
( (
";" "VALUE" "=" "URI" ";" "VALUE" "=" "URI"
":" uri ":" uri
skipping to change at page 15, line 39 skipping to change at page 16, line 35
) )
) )
CRLF CRLF
styleddescparam = *( styleddescparam = *(
; ;
; The following are OPTIONAL, ; The following are OPTIONAL,
; but MUST NOT occur more than once. ; but MUST NOT occur more than once.
; ;
(";" altrepparam) / (";" languageparam) / (";" altrepparam) / (";" languageparam) /
(";" fmttypeparam) / (";" fmttypeparam) / (";" derivedparam) /
; ;
; the following is OPTIONAL ; the following is OPTIONAL
; and MAY occur more than once ; and MAY occur more than once
; ;
(";" other-param) (";" other-param)
) )
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
skipping to change at page 16, line 21 skipping to change at page 17, line 16
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.
Property Parameters: IANA, non-standard, label, loctype or format Property Parameters: IANA, non-standard, label, loctype, related or
type parameters can be specified on this property. format type parameters can be specified on this property.
Conformance: This property MAY be specified zero or more times in Conformance: This property MAY be specified zero or more times in
any iCalendar component. any iCalendar component.
Description: When used in a component the value of this property Description: When used in a component the value of this property
provides information about the event venue or of related services provides information about the event venue or of related services
such as parking, dining, stations etc.. such as parking, dining, stations etc..
When a LABEL parameter is supplied the language of the label must When a LABEL parameter is supplied the language of the label must
match that of the content and of the LANGUAGE parameter if match that of the content and of the LANGUAGE parameter if
present. present.
Use of the related parameter: This allows a location to define the
start and/or end timezone of the associated component. If a
location is specified with a RELATED parameter then the affected
DTSTART or DTEND properties MUST be specified as floating DATE-
TIME value.
If the RELATED parameter is present with a value of START, then
the "DTSTART" property MUST be present in the associated "VEVENT"
or "VTODO" calendar component.
For an event, if the RELATED parameter is present with a value of
END, then the "DTEND" property or the "DTSTART" and "DURATION "
properties MUST be present in the associated "VEVENT" calendar
component.
For a to-do with a RELATED value of END, then either the "DUE"
property or the "DTSTART" and "DURATION " properties MUST be
present in the associated "VTODO" calendar component.
If there is a location specified with RELATED=START and no
location is specified with RELATED=END then the event is assumed
to start and end in the same timezone.
Format Definition: Format Definition:
This property is defined by the following notation: This property is defined by the following notation:
strucloc = "STRUCTURED-LOCATION" struclocparam strucloc = "STRUCTURED-LOCATION" struclocparam
( (
( (
";" "VALUE" "=" "URI" ";" "VALUE" "=" "URI"
":" uri ":" uri
) / ) /
skipping to change at page 17, line 28 skipping to change at page 18, line 30
CRLF CRLF
struclocparam = *( struclocparam = *(
; ;
; the following are OPTIONAL ; the following are OPTIONAL
; but MUST NOT occur more than once ; but MUST NOT occur more than once
; ;
(";" fmttypeparam) / (";" fmttypeparam) /
(";" labelparam) / (";" labelparam) /
(";" languageparam) / (";" languageparam) /
(";" trigrelparam) /
(";" loctypeparam) / (";" loctypeparam) /
; ;
; the following is OPTIONAL ; the following is OPTIONAL
; and MAY occur more than once ; and MAY occur more than once
; ;
(";" other-param) (";" other-param)
) )
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:
http://dir.example.com/venues/big-hall.vcf http://dir.example.com/venues/big-hall.vcf
7.5. Structured-Resource 7.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.
Property Parameters: IANA, non-standard, label, restype or format Property Parameters: IANA, non-standard, label, restype or format
type parameters can be specified on this property. type parameters can be specified on this property.
skipping to change at page 25, line 18 skipping to change at page 26, line 18
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
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:Beethoven Piano Sonatas SUMMARY:Beethoven Piano Sonatas
UID:123456 UID:123456
STRUCTURED-LOCATION;LABEL="The venue": 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="The venue": 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 SOURCE: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 SOURCE:http://www.example.com/people/johndoe.vcf
 End of changes. 28 change blocks. 
60 lines changed or deleted 124 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/