draft-ietf-calext-eventpub-extensions-05.txt   draft-ietf-calext-eventpub-extensions-06.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) October 11, 2017 Updates: 5545,5546 (if approved) May 5, 2018
Intended status: Standards Track Intended status: Standards Track
Expires: April 14, 2018 Expires: November 6, 2018
Event Publishing Extensions to iCalendar Event Publishing Extensions to iCalendar
draft-ietf-calext-eventpub-extensions-05 draft-ietf-calext-eventpub-extensions-06
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 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 14, 2018. This Internet-Draft will expire on November 6, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 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
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
skipping to change at page 2, line 17 skipping to change at page 2, line 17
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 . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 5 3.1. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1.1. Piano Concert Performance . . . . . . . . . . . . . . 5 3.1.1. Piano Concert Performance . . . . . . . . . . . . . . 5
3.1.2. Itineraries . . . . . . . . . . . . . . . . . . . . . 6 3.1.2. Itineraries . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . . 8 5.3. Order . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.4. Schema . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.4. Schema . . . . . . . . . . . . . . . . . . . . . . . . . 9
6. Redefined Property SOURCE . . . . . . . . . . . . . . . . . . 10 6. Redefined Property SOURCE . . . . . . . . . . . . . . . . . . 10
7. New Properties . . . . . . . . . . . . . . . . . . . . . . . 11 7. New Properties . . . . . . . . . . . . . . . . . . . . . . . 11
7.1. Participant Type . . . . . . . . . . . . . . . . . . . . 11 7.1. Participant Type . . . . . . . . . . . . . . . . . . . . 11
7.2. Calendar Address . . . . . . . . . . . . . . . . . . . . 12 7.2. Calendar Address . . . . . . . . . . . . . . . . . . . . 12
skipping to change at page 5, line 27 skipping to change at page 5, line 30
to help the selection. to help the selection.
The PARTICIPANT component is designed to handle common use cases in The PARTICIPANT component is designed to handle common use cases in
event publication. It is generally important to provide information event publication. It is generally important to provide information
about the organizers of such events. Sponsors wish to be referenced about the organizers of such events. Sponsors wish to be referenced
in a prominent manner. In social calendaring it is often important in a prominent manner. In social calendaring it is often important
to identify the active participants in the event, for example a to identify the active participants in the event, for example a
school sports team, and the inactive participants, for example the school sports team, and the inactive participants, for example the
parents. parents.
The PARTICIPANT component canalso be used to provide useful extra The PARTICIPANT component can also be used to provide useful extra
daat about an attendee. For example a LOCATION property inside the data about an attendee. For example a LOCATION property inside the
PARTICIPANT gives the actual location of a remote attendee. PARTICIPANT gives the actual location of a remote attendee.
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
skipping to change at page 6, line 21 skipping to change at page 6, line 25
These additions also provide opportunities for the travel industry. These additions also provide opportunities for the travel industry.
When booking a flight the PARTICIPANT component can be used to When booking a flight the PARTICIPANT component can be used to
provide references to businesses at the airports and to car hire provide references to businesses at the airports and to car hire
businesses at the destination. businesses at the destination.
The embedded location information can guide the traveller at the The embedded location information can guide the traveller at the
airport or to their final destination. The contact information can airport or to their final destination. The contact information can
provide detailed information about the booking agent, the airlines provide detailed information about the booking agent, the airlines
and car hire companies and the hotel. and car hire companies and the hotel.
3.1.2.1. Reserving facilities
For a meeting, the size of a room and the equipment needed depends to
some extent on the number of attendees actually in the room.
A meeting may have 10 attendees non of which are co-located. The
current ATTENDEE property dos not allow for the additon of such meta-
data. The PARTICIPANT property allows attendees to specify their
location.
4. Modifications to Calendar Components 4. Modifications to Calendar Components
The following changes to the syntax defined in iCalendar [RFC5545] The following changes to the syntax defined in iCalendar [RFC5545]
are made here. New elements are defined in subsequent sections. are made here. New elements are defined in subsequent sections.
eventc = "BEGIN" ":" "VEVENT" CRLF eventc = "BEGIN" ":" "VEVENT" CRLF
eventprop *alarmc *participantc eventprop *alarmc *participantc
"END" ":" "VEVENT" CRLF "END" ":" "VEVENT" CRLF
eventprop =/ *( eventprop =/ *(
 End of changes. 8 change blocks. 
7 lines changed or deleted 18 lines changed or added

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