draft-ietf-calext-eventpub-extensions-02.txt   draft-ietf-calext-eventpub-extensions-03.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) April 21, 2017 Updates: 5545,5546 (if approved) May 4, 2017
Intended status: Standards Track Intended status: Standards Track
Expires: October 23, 2017 Expires: November 5, 2017
Event Publishing Extensions to iCalendar Event Publishing Extensions to iCalendar
draft-ietf-calext-eventpub-extensions-02 draft-ietf-calext-eventpub-extensions-03
Abstract Abstract
This specification introduces a number of new iCalendar properties This specification introduces a number of new iCalendar properties
and components which are of particular use for event publishers and and components which are of particular use for event publishers and
in social networking. 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.
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 October 23, 2017. This Internet-Draft will expire on November 5, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 3, line 16 skipping to change at page 3, line 16
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
description or to add x-properties. description or to add x-properties.
This document defines a number of properties and components This document defines a number of properties and a component
referencing such external information that can provide additional referencing such external information that can provide additional
information about an iCalendar component. The intent is to allow information about an iCalendar component. The intent is to allow
interchange of such information between applications or systems interchange of such information between applications or systems
(e.g., between clients, between client and server, and between (e.g., between clients, between client and server, and between
servers). Formats such as VCARD are likely to be most useful. servers). Formats such as VCARD are likely to be most useful to the
receivers of such events as they may be used in other applications -
such as address books.
The following properties and components are defined in this The following properties are defined in this specification
specification
Styled-Description: Supports HTML descriptions. Event publishers Styled-Description: Supports HTML descriptions. Event publishers
typically wish to provide more and better formatted information typically wish to provide more and better formatted information
about the event. 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,
skipping to change at page 3, line 48 skipping to change at page 3, line 49
elements of events and tasks such as start time, end time, elements of events and tasks such as start time, end time,
location, summary, etc. However, different types of events often location, summary, etc. However, different types of events often
have other specific "fields" that it is useful to include in the have other specific "fields" that it is useful to include in the
calendar data. For example, an event representing an airline calendar data. For example, an event representing an airline
flight could include the airline, flight number, departure and flight could include the airline, flight number, departure and
arrival airport codes, check-in and gate-closing times etc. As arrival airport codes, check-in and gate-closing times etc. As
another example, a sporting event might contain information about another example, a sporting event might contain information about
the type of sport, the home and away teams, the league the teams the type of sport, the home and away teams, the league the teams
are in, information about nearby parking, etc. are in, information about nearby parking, etc.
Participant: Many people or groups may participate in an event. In addition this specification defines a new PARTICIPANT component.
This component provides detailed information. Such participants Many people or groups may participate in an event. This component
may act as attendees to the event (or derived events) or may just provides detailed information. Such participants may act as
provide a reference - perhaps for mailing lists. attendees to the event (or derived events) or may just provide a
reference - perhaps for mailing lists.
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 "OPTIONAL" in this document are to be interpreted as described in
[RFC2119]. [RFC2119].
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 introduces some In a break with this 'tradition' this specification introduces one of
of these extensions as components rather than properties. This is a these extensions as a component rather than a property. This is a
better match for the way XML and JSON handles such structures and better match for the way XML and JSON handles such structures and
allows richer definitions. allows richer definitions.
It also allows for the addition of extra properties inside the It also allows for the addition of extra properties inside the
component and resolves some of the problems of trying to add detailed component and resolves some of the problems of trying to add detailed
information as a parameter. information as a parameter.
3. Typed References 3. Typed References
The properties defined here can all reference external meta-data The properties defined here can all reference external meta-data
which may be used by applications to provide enhanced value to users. which may be used by applications to provide enhanced value to users.
By providing type information as parameters, clients and servers are By providing type information as parameters, clients and servers are
able to discover interesting references and make use of them, perhaps able to discover interesting references and make use of them, perhaps
for indexing or the presentation of additional related information for indexing or the presentation of additional related information
for the user. for the user.
These properties are designed to handle common use cases in event
publication. It is generally important to provide information about
the organizers of such events. Sponsors wish to be referenced in a
prominent manner. In social calendaring it is often important to
identify the active participants in the event, for example a school
sports team, and the inactive participants, for example the parents.
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, information about a number of interesting
locations can be communicated, for example, parking, restaurants and locations can be communicated, for example, parking, restaurants and
the venue. Servers and clients can retrieve the objects when storing the venue. Servers and clients can retrieve the objects when storing
the event and use them to index by geographic location. the event and use them to index by geographic location.
These PARTICIPANT component is designed to handle common use cases in
event publication. It is generally important to provide information
about the organizers of such events. Sponsors wish to be referenced
in a prominent manner. In social calendaring it is often important
to identify the active participants in the event, for example a
school sports team, and the inactive participants, for example the
parents.
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.
3.1. Use Cases 3.1. Use Cases
The main motivation for these properties has been event publication The main motivation for these properties has been event publication
but there are opportunities for use elsewhere. The following use but there are opportunities for use elsewhere. The following use
cases will describe some possible scenarios. cases will describe some possible scenarios.
3.1.1. Piano Concert Performance 3.1.1. Piano Concert Performance
In putting together a concert there are many participants: piano In putting together a concert there are many participants: piano
tuner, performer, stage hands etc. In addition there are sponsors tuner, performer, stage hands etc. In addition there are sponsors
and various contacts to be provided. There will also be a number of and various contacts to be provided. There will also be a number of
related locations. A number of events can be created, all of which related locations. A number of events can be created, all of which
relate to the performance in different ways. relate to the performance in different ways.
There may be an iTip [RFC5545] 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
information about the performer. This event would also hold information about the performer. This event would also hold
information about parking, local subway stations and the venue information about parking, local subway stations and the venue
itself. In addition, there will be sponsorship information for itself. In addition, there will 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.
skipping to change at page 7, line 8 skipping to change at page 7, line 8
; The following are OPTIONAL, ; The following are OPTIONAL,
; and MAY occur more than once. ; and MAY occur more than once.
; ;
styleddescription / sdataprop styleddescription / sdataprop
; ;
) )
5. New Property Parameters 5. New Property Parameters
This specification makes use of the LABEL property parameter which is This specification makes use of the LABEL property parameter which is
defined in [I-D.ietf-calext-extensions] defined in [RFC7986]
5.1. Loctype 5.1. Loctype
Parameter name: LOCTYPE Parameter name: LOCTYPE
Purpose: To specify the type of location. Purpose: To specify the type of location.
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 20 skipping to change at page 8, line 20
Format Definition: Format Definition:
This parameter is defined by the following notation: This parameter is defined by the following notation:
orderparam = "ORDER" "=" integer ;Must be greater than or equal to 1 orderparam = "ORDER" "=" integer ;Must be greater than or equal to 1
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. Lower values correspond to a higher level quantifies the order with 1 being the first in the ordering.
of ordering, with 1 being the highest.
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. property instance as being at the lowest level of ordering, that
is, the property will appear after any other instances of the same
property with any value of 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 9, line 15 skipping to change at page 9, line 17
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
6. New Properties 6. New Properties
6.1. Participant Type 6.1. Participant Type
Property name: PARTTYPE 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 in Section 8. values are defined in Section 8.
Property Parameters: Non-standard parameters can be specified on Property Parameters: Non-standard parameters can be specified on
this property. this property.
Conformance: This property MUST be specified within a PARTICIPANT Conformance: This property MUST be specified within a PARTICIPANT
skipping to change at page 10, line 13 skipping to change at page 10, line 16
component. component.
Description: This property provides a calendar user address for the Description: This property provides a calendar user address for the
participant. If there is an ATTENDEE property with the same value participant. If there is an ATTENDEE property with the same value
then the participant is schedulable. then the participant is schedulable.
Format Definition: Format Definition:
This parameter is defined by the following notation: This parameter is defined by the following notation:
scheduleaddress = "SCHEDULE-ADDRESS" "=" iana-token scheduleaddress = "SCHEDULE-ADDRESS" "=" cal-address
6.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 or augment that provided by the descriptions to replace or augment 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, and language property parameters can be specified representation, format type, and language property parameters can
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", 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
skipping to change at page 15, line 15 skipping to change at page 15, line 15
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;restype="projector": STRUCTURED-RESOURCE;restype="projector":
http://dir.example.com/projectors/3d.vcf http://dir.example.com/projectors/3d.vcf
6.6. Source 6.6. Source
Property name: SOURCE Property name: SOURCE
Purpose: This property provides a reference to vcard information Purpose: This property provides a reference to information about a
about a participant in an event or optionally a plain text typed component such as a participant possibly as a vcard or optionally
value. a plain text typed value.
Value type: The default value type for this property is URI. The Value type: The default value type for this property is URI. The
value type can also be set to TEXT to indicate plain text content. value type can also be set to TEXT to indicate plain text content.
Property Parameters: Non-standard or format type parameters can be Property Parameters: Non-standard or format type parameters can be
specified on this property. specified on this property.
Conformance: This property MAY be appear in any iCalendar component. Conformance: This property MAY be appear in any iCalendar component.
Description: This property provides information about the component Description: This property provides information about the component
in which it appears. It may provide a refernce to a vcard giving in which it appears. It may provide a reference to a vcard giving
directory information about a resource or participant. directory information about a resource or participant.
Format Definition: Format Definition:
This property is defined by the following notation: This property is defined by the following notation:
source = "SOURCE" sourceparam source = "SOURCE" sourceparam
( (
( (
";" "VALUE" "=" "URI" ";" "VALUE" "=" "URI"
skipping to change at page 16, line 48 skipping to change at page 16, line 48
SOURCE;FMTTYPE=text/vcard; SOURCE;FMTTYPE=text/vcard;
http://dir.example.com/vcard/contacts/contact1.vcf http://dir.example.com/vcard/contacts/contact1.vcf
6.7. Structured-Data 6.7. 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 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.
The format type and schema parameters can be specified on this The format type and schema parameters can be specified on this
property and are RECOMMENDED for text or inline binary encoded property and are RECOMMENDED for text or inline binary encoded
content information. content information.
Conformance: This property can be specified multiple times in an Conformance: This property can be specified multiple times in an
iCalendar object. Typically it would be used in "VEVENT", iCalendar object. Typically it would be used in "VEVENT",
"VTODO", or "VJOURNAL" calendar components. "VTODO", or "VJOURNAL" calendar components.
Description: This property is used to specify ancillary data in some Description: This property is used to specify ancillary data in some
structured format either directly (inline) as a "TEXT" or "BINARY" structured format either directly (inline) as a "TEXT" or "BINARY"
value, or as a link via a "URI" value. value, or as a link via a "URI" value.
Rather than define new iCalendar properties for the variety of Rather than define new iCalendar properties for the variety of
event types that might occur, it would be better to leverage event types that might occur, it would be better to leverage
existing "schemas" for such data. For example, schemas available existing schemas for such data. For example, schemas available at
at https://schema.org include different event types. By using https://schema.org include different event types. By using
standard schemas, interoperability can be improved between standard schemas, interoperability can be improved between
calendar clients and non-calendaring systems that wish to generate calendar clients and non-calendaring systems that wish to generate
or process the data. or process the data.
This property allows the direct inclusion of ancillary data whose This property allows the direct inclusion of ancillary data whose
schema is defined elsewhere. This property also includes schema is defined elsewhere. This property also includes
parameters to clearly identify the type of the schema being used parameters to clearly identify the type of the schema being used
so that clients can quickly and easily spot what is relevant so that clients can quickly and easily spot what is relevant
within the calendar data and present that to users or process it within the calendar data and present that to users or process it
within the calendaring system. within the calendaring system.
skipping to change at page 20, line 7 skipping to change at page 20, line 7
The STRUCTURED-ADDRESS property if present will provide a cal- The STRUCTURED-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 / seq / created / description / last-mod / priority / seq /
source / status / structuredaddress / summary / url / source / status / scheduleaddress / 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 / rstatus / related /
resources / x-prop / iana-prop resources / 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 21, line 36 skipping to change at page 21, line 36
property. property.
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
particpants are in different timezones. participants are in different timezones.
8. Participant Types 8. Participant Types
This section describes types of participation and provide registered This section describes types of participation and provide registered
values for the PARTTYPE property. values for the PARTTYPE property.
ACTIVE: A participant taking an active role - for example a team ACTIVE: A participant taking an active role - for example a team
member. member.
INACTIVE: A participant taking an inactive part - for example an INACTIVE: A participant taking an inactive part - for example an
skipping to change at page 22, line 28 skipping to change at page 22, line 28
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
9. Extended examples 9. 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
[I-D.ietf-calext-extensions] which includes IMAGE and LIVEFEED. [RFC7986] which includes IMAGE and LIVEFEED.
9.1. Example 1 9.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:20101116T145739Z CREATED:20101116T145739Z
DESCRIPTION: Piano Sonata No 3\n DESCRIPTION: Piano Sonata No 3\n
Piano Sonata No 30 Piano Sonata No 30
skipping to change at page 25, line 41 skipping to change at page 25, line 41
and Scheduling Consortium Event Publication technical committee and and Scheduling Consortium Event Publication technical committee and
the following individuals for contributing their ideas and support: the following individuals for contributing their ideas and support:
Cyrus Daboo, John Haug, Dan Mendell, Ken Murchison, Scott Otis, Cyrus Daboo, John Haug, Dan Mendell, Ken Murchison, Scott Otis,
The authors would also like to thank the Calendaring and Scheduling The authors would also like to thank the Calendaring and Scheduling
Consortium for advice with this specification. Consortium for advice with this specification.
14. Normative References 14. Normative References
[I-D.ietf-calext-extensions]
Daboo, C., "New Properties for iCalendar", draft-ietf-
calext-extensions-05 (work in progress), August 2016.
[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,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", RFC 2434,
DOI 10.17487/RFC2434, October 1998,
<http://www.rfc-editor.org/info/rfc2434>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>.
[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,
<http://www.rfc-editor.org/info/rfc3986>. <http://www.rfc-editor.org/info/rfc3986>.
[RFC4589] Schulzrinne, H. and H. Tschofenig, "Location Types [RFC4589] Schulzrinne, H. and H. Tschofenig, "Location Types
Registry", RFC 4589, DOI 10.17487/RFC4589, July 2006, Registry", RFC 4589, DOI 10.17487/RFC4589, July 2006,
<http://www.rfc-editor.org/info/rfc4589>. <http://www.rfc-editor.org/info/rfc4589>.
[RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and [RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and
Scheduling Core Object Specification (iCalendar)", Scheduling Core Object Specification (iCalendar)",
RFC 5545, DOI 10.17487/RFC5545, September 2009, RFC 5545, DOI 10.17487/RFC5545, September 2009,
<http://www.rfc-editor.org/info/rfc5545>. <http://www.rfc-editor.org/info/rfc5545>.
[RFC5546] Daboo, C., Ed., "iCalendar Transport-Independent [RFC5546] Daboo, C., Ed., "iCalendar Transport-Independent
Interoperability Protocol (iTIP)", RFC 5546, Interoperability Protocol (iTIP)", RFC 5546,
DOI 10.17487/RFC5546, December 2009, DOI 10.17487/RFC5546, December 2009,
<http://www.rfc-editor.org/info/rfc5546>. <http://www.rfc-editor.org/info/rfc5546>.
[RFC7986] Daboo, C., "New Properties for iCalendar", RFC 7986,
DOI 10.17487/RFC7986, October 2016,
<http://www.rfc-editor.org/info/rfc7986>.
[W3C.REC-xml-20060816] [W3C.REC-xml-20060816]
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 (Fourth F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fourth
Edition)", World Wide Web Consortium Recommendation REC- Edition)", World Wide Web Consortium Recommendation REC-
xml-20060816, August 2006, xml-20060816, August 2006,
<http://www.w3.org/TR/2006/REC-xml-20060816>. <http://www.w3.org/TR/2006/REC-xml-20060816>.
Appendix A. Open issues Appendix A. Open issues
restype values: Need to determine what if any registry of resource restype values: Need to determine what if any registry of resource
 End of changes. 29 change blocks. 
76 lines changed or deleted 71 lines changed or added

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