Try out our new RRULE tool for creating RRULE compatible strings.
New Properties for iCalendar (RFC 7986)
Abstract
This document defines a set of new properties for iCalendar data and extends the use of some existing properties to the entire iCalendar object.
Author
C. Daboo, Apple, Inc., October 2016
Acknowledgments
Thanks to the following individuals for feedback: Bernard Desruisseaux, Mike Douglass, Lucia Fedorova, Ken Murchison, Arnaud Quillaud, and Dave Thewlis.
This specification came about via discussions at the Calendaring and Scheduling Consortium.
10.2. Informative References
[RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397, DOI 10.17487/RFC2397, August 1998, <http://www.rfc-editor.org/info/rfc2397>
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, DOI 10.17487/RFC3261, June 2002, <http://www.rfc-editor.org/info/rfc3261>
[RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3966, DOI 10.17487/RFC3966, December 2004, <http://www.rfc-editor.org/info/rfc3966>
[RFC5122] Saint-Andre, P., "Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)", RFC 5122, DOI 10.17487/RFC5122, February 2008, <http://www.rfc-editor.org/info/rfc5122>
[RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing", RFC 7230, DOI 10.17487/RFC7230, June 2014, <http://www.rfc-editor.org/info/rfc7230>
Table of Contents
1. Introduction ....................................................3 2. Conventions Used in This Document ...............................3 3. Backwards-Compatible Extension Properties .......................3 4. Modifications to Calendar Components ............................4 5. Properties ......................................................5 5.1. NAME Property ..............................................5 5.2. DESCRIPTION Property .......................................6 5.3. UID Property ...............................................7 5.4. LAST-MODIFIED Property .....................................8 5.5. URL Property ...............................................8 5.6. CATEGORIES Property ........................................8 5.7. REFRESH-INTERVAL Property ..................................9 5.8. SOURCE Property ...........................................10 5.9. COLOR Property ............................................10 5.10. IMAGE Property ...........................................11 5.11. CONFERENCE Property ......................................13 6. Property Parameters ............................................14 6.1. DISPLAY Property Parameter ................................14 6.2. EMAIL Property Parameter ..................................15 6.3. FEATURE Property Parameter ................................16 6.4. LABEL Property Parameter ..................................17 7. Security Considerations ........................................18 8. Privacy Considerations .........................................18 9. IANA Considerations ............................................19 9.1. Property Registrations ....................................19 9.2. Parameter Registrations ...................................20 9.3. Property Parameter Value Registries .......................20 10. References ....................................................21 10.1. Normative References .....................................21 10.2. Informative References ...................................22 Acknowledgments ...................................................23 Author's Address ..................................................23
1. Introduction
The iCalendar [RFC5545] data format is used to represent calendar data and is used with the iCalendar Transport-Independent Interoperability Protocol (iTIP) [RFC5546] to handle scheduling operations between calendar users. iCalendar is in widespread use, and in accordance with provisions in that specification, extension elements have been added by various vendors to the data format in order to support and enhance capabilities. This specification collects a number of these ad hoc extensions and uses the new IANA registry capability defined in [RFC5545] to register standard variants with clearly defined definitions and semantics. In addition, some new elements are introduced for features that vendors have recently been requesting.
This document was automatically converted to XHTML using an RFC to HTML converter with the original text document at the Internet Engineering Task Force web site at ietf.org . The original text document should be referred to if there are any errors or discrepancies found in this document.
Need to test your iCalendar feeds?
The iCalendar Validator provides developers and testers a method to validate their iCalendar feeds, which can take data from either a URL, file or text snippet and compare it against the RFC 5545 specification. We believe we have one of the best iCalendar validation tools available on the internet. More information about the validator can be found here.