Event Publishing Extensions to iCalendar
draft-douglass-calendar-extension-05
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
|
|
|---|---|---|---|
| Author | Michael Douglass | ||
| Last updated | 2016-06-14 | ||
| Replaced by | draft-ietf-calext-eventpub-extensions, RFC 9073 | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-douglass-calendar-extension-05
"awayTeam": "San Francisco Giants"\n
}\n
6. Associate Types
This section describes types of association and provide registered
values for the ASSOCIATE property ASSOCTYPE parameter.
Douglass Expires December 16, 2016 [Page 17]
Internet-Draft Event Publishing Extensions to iCalendar June 2016
ACTIVE: An associate taking an active role - for example a team
member.
INACTIVE: An associate taking an inactive part - for example an
audience member.
SPONSOR: A sponsor of the event. The ORDER parameter may be used
with this associate type to define the relative order of multiple
sponsors.
CONTACT: Contact information for the event. The ORDER parameter may
be used with this associate type to define the relative order of
multiple contacts.
BOOKING-CONTACT: Contact information for reservations or payment
EMERGENCY-CONTACT: Contact in case of emergency
PUBLICITY-CONTACT: Contact for publicity
PLANNER-CONTACT: Contact for the event planner or organizer
PERFORMER: A performer - for example the soloist or the accompanist.
The ORDER parameter may be used with this associate type to define
the relative order of multiple sponsors. For example, ORDER=1
could define the principal performer or soloist.
SPEAKER: Speaker at an event
7. Extended examples
The following are some examples of the use of the properties defined
in this specification. They include additional properties defined in
[I-D.daboo-icalendar-extensions] which includes IMAGE and LIVEFEED.
7.1. Example 1
Douglass Expires December 16, 2016 [Page 18]
Internet-Draft Event Publishing Extensions to iCalendar June 2016
The following is an example of a VEVENT describing a concert. It
includes location information for the venue itself as well as
references to parking and restaurants.
BEGIN:VEVENT
CREATED:20101116T145739Z
DESCRIPTION: Piano Sonata No 3\n
Piano Sonata No 30
DTSTAMP:20101116T145739Z
DTSTART;TZID=America/New_York:20110315T150000Z
DTEND;TZID=America/New_York:20110315T163000Z
LAST-MODIFIED:20101116T145739Z
SUMMARY:Beethoven Piano Sonatas
UID:123456
STRUCTURED-LOCATION;LABEL="The venue":
http://dir.example.com/venues/big-hall.vcf
STRUCTURED-LOCATION;LABEL="The venue":
http://dir.example.com/venues/parking.vcf
ASSOCIATE;ASSOCTYPE=SPONSOR:http://example.com/sponsor.vcf
ASSOCIATE;ASSOCTYPE=PERFORMER:
http://www.example.com/people/johndoe.vcf
END:VEVENT
8. Security Considerations
Applications using these properties need to be aware of the risks
entailed in using the URIs provided as values. See [RFC3986] for a
discussion of the security considerations relating to URIs.
Security considerations relating to the "ATTACH" property, as
described in [RFC5545], are applicable to the "STRUCTURED-DATA"
property.
9. Privacy Considerations
Properties with a "URI" value type can expose their users to privacy
leaks as any network access of the URI data can be tracked. Clients
SHOULD NOT automatically download data referenced by the URI without
explicit instruction from users. This specification does not
introduce any additional privacy concerns beyond those described in
[RFC5545].
10. IANA Considerations
Douglass Expires December 16, 2016 [Page 19]
Internet-Draft Event Publishing Extensions to iCalendar June 2016
10.1. Property Registrations
This document defines the following new iCalendar properties to be
added to the registry defined in Section 8.2.3 of [RFC5545]:
+---------------------+---------+----------------------+
| Property | Status | Reference |
+---------------------+---------+----------------------+
| ASSOCIATE | Current | RFCXXXX, Section 5.1 |
| STRUCTURED-DATA | Current | RFCXXXX, Section 5.5 |
| STYLED-DESCRIPTION | Current | RFCXXXX, Section 5.2 |
| STRUCTURED-LOCATION | Current | RFCXXXX, Section 5.3 |
| STRUCTURED-RESOURCE | Current | RFCXXXX, Section 5.4 |
+---------------------+---------+----------------------+
10.2. Parameter Registrations
This document defines the following new iCalendar property parameters
to be added to the registry defined in Section 8.2.4 of [RFC5545]:
+--------------------+---------+----------------------+
| Property Parameter | Status | Reference |
+--------------------+---------+----------------------+
| ASSOCTYPE | Current | RFCXXXX, Section 4.2 |
| LABEL | Current | RFCXXXX, Section 4.5 |
| LOCTYPE | Current | RFCXXXX, Section 4.1 |
| ORDER | Current | RFCXXXX, Section 4.4 |
| RESTYPE | Current | RFCXXXX, Section 4.3 |
| SCHEMA | Current | RFCXXXX, Section 4.6 |
+--------------------+---------+----------------------+
10.3. Associate Type Registrations
The following table has been used to initialize the associate types
registry.
Douglass Expires December 16, 2016 [Page 20]
Internet-Draft Event Publishing Extensions to iCalendar June 2016
+-------------------+---------+--------------------+
| Associate Type | Status | Reference |
+-------------------+---------+--------------------+
| ACTIVE | Current | RFCXXXX, Section 6 |
| INACTIVE | Current | RFCXXXX, Section 6 |
| SPONSOR | Current | RFCXXXX, Section 6 |
| CONTACT | Current | RFCXXXX, Section 6 |
| BOOKING-CONTACT | Current | RFCXXXX, Section 6 |
| EMERGENCY-CONTACT | Current | RFCXXXX, Section 6 |
| PUBLICITY-CONTACT | Current | RFCXXXX, Section 6 |
| PLANNER-CONTACT | Current | RFCXXXX, Section 6 |
| PERFORMER | Current | RFCXXXX, Section 6 |
| SPEAKER | Current | RFCXXXX, Section 6 |
+-------------------+---------+--------------------+
11. Acknowledgements
The author would like to thank Chuck Norris of eventful.com for his
work which led to the development of this RFC.
The author would also like to thank the members of the Calendaring
and Scheduling Consortium Event Publication technical committee and
the following individuals for contributing their ideas and support:
Cyrus Daboo, John Haug, Dan Mendell, Scott Otis,
The authors would also like to thank the Calendaring and Scheduling
Consortium for advice with this specification.
12. Normative References
[I-D.daboo-icalendar-extensions]
Daboo, C., "New Properties for iCalendar", draft-daboo-
icalendar-extensions-09 (work in progress), July 2014.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<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>.
Douglass Expires December 16, 2016 [Page 21]
Internet-Draft Event Publishing Extensions to iCalendar June 2016
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005,
<http://www.rfc-editor.org/info/rfc3986>.
[RFC4589] Schulzrinne, H. and H. Tschofenig, "Location Types
Registry", RFC 4589, DOI 10.17487/RFC4589, July 2006,
<http://www.rfc-editor.org/info/rfc4589>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234,
DOI 10.17487/RFC5234, January 2008,
<http://www.rfc-editor.org/info/rfc5234>.
[RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and
Scheduling Core Object Specification (iCalendar)",
RFC 5545, DOI 10.17487/RFC5545, September 2009,
<http://www.rfc-editor.org/info/rfc5545>.
[W3C.REC-xml-20060816]
Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., and
F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fourth
Edition)", World Wide Web Consortium Recommendation REC-
xml-20060816, August 2006,
<http://www.w3.org/TR/2006/REC-xml-20060816>.
Appendix A. Open issues
restype values: Need to determine what if any registry of resource
types already exists and use that.
Appendix B. Change log
v05 2016-06-14 MD
o Remove GROUP and HASH. they can be dealt with elsewhere if desired
o Change ORDER to integer >= 1.
o Incorporate Structured-Data into this specification.
v04 2014-02-01 MD
o Added updates attribute.
o Minor typos.
o Resubmitted mostly to refresh the draft.
Douglass Expires December 16, 2016 [Page 22]
Internet-Draft Event Publishing Extensions to iCalendar June 2016
v03 2013-03-06 MD
o Replace PARTICIPANT with ASSOCIATE plus related changes.
o Added section showing modifications to components.
o Replace ID with GROUP and modify HASH.
o Replace TITLE param with LABEL.
o Fixed STYLED-DESCRIPTION in various ways, correct example.
v02 2012-11-02 MD
o Collapse sections with description of properties and the use cases
into a section with sub-sections.
o New section to describe relating properties.
o Remove idref and upgrade hash to have the reference
o No default value types on properties..
v01 2012-10-18 MD Many changes.
o SPONSOR and STRUCTURED-CONTACT are now in PARTICIPANT
o Add a STRUCTURED-RESOURCE property
o STYLED-DESCRIPTION to handle rich text
o Much more...
2011-01-07
o Remove MEDIA - it's going in the Cyrus RFC
o Rename EXTENDED-... to STRUCTURED-...
o Add TYPE parameter to SPONSOR
v00 2007-10-19 MD Initial version
Author's Address
Douglass Expires December 16, 2016 [Page 23]
Internet-Draft Event Publishing Extensions to iCalendar June 2016
Michael Douglass
Spherical Cow Group
226 3rd Street
Troy, NY 12180
USA
Email: mdouglass@sphericalcowgroup.com
URI: http://sphericalcowgroup.com
Douglass Expires December 16, 2016 [Page 24]