iCalendar
iCalendar | |
---|---|
File extension : |
.ics, .ifb, .iCal, .iFBf
|
MIME type : | text / calendar |
Type: | Calendar exchange format |
Standard (s) : | RFC 5545 |
iCalendar is a data format for the exchange of calendar content , which is standardized in RFC 5545 . The format is based on vCalendar and was originally defined in RFC 2445 from November 1998.
The abbreviation iCal is the file name extension for iCalendar files under macOS and was previously used for the calendar application of this operating system. ics is the corresponding filename extension for other operating systems. The filename extensions iFBf (for Mac OS X) and ifb (all other operating systems) are provided for information on when you are free or busy.
iCalendar is not limited to file sharing or any particular network protocol . Rather, the standard fundamentally defines the Internet Media Type text / calendar for almost any embedding.
For example, websites can be used to distribute the dates of an event using iCalendar, to publish occupancy times or waste collection dates. WebDAV servers enable the format to synchronize appointments. It is also possible to exchange appointments in the Personal Area Network - for example via IrDA or Bluetooth - between PDAs or mobile phones . With the help of iCalendar it is also possible to use calendar information together in several applications.
RFC 5546 defines the iTIP protocol based on iCalendar for interoperability in groups on the application layer . RFC 6047 in turn defines iMIP based on iTIP for exchange using the Simple Mail Transfer Protocol .
The iCalendar format is accepted by the majority of calendar programs that can incorporate (subscribe to) web-based calendar data, among other things. a. Google Calendar / Android Calendar, Microsoft Outlook , Blackberry Calendar Apps and all macOS / iOS calendar applications. This is why iCalendar-based calendars are widely used to publish fixtures for sports and music events. One directory of such calendars is iCalShare.
The Calsify working group of the Internet Engineering Task Force was responsible .
example
BEGIN:VCALENDAR VERSION:2.0 PRODID:http://www.example.com/calendarapplication/ METHOD:PUBLISH BEGIN:VTIMEZONE TZID:Europe/Berlin BEGIN:STANDARD DTSTART:16011028T030000 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010325T020000 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3 TZOFFSETFROM:+0100 TZOFFSETTO:+0200 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:[email protected] ORGANIZER;CN="Alice Balder, Example Inc.":MAILTO:[email protected] LOCATION:Irgendwo GEO:48.85299;2.36885 SUMMARY:Eine Kurzinfo DESCRIPTION:Beschreibung des Termines CLASS:PUBLIC DTSTART;TZID=Europe/Berlin:20200910T220000Z DTEND;TZID=Europe/Berlin:20200919T215900Z DTSTAMP;TZID=Europe/Berlin:20200812T125900Z END:VEVENT END:VCALENDAR
See also
Individual evidence
- ↑ RFC 2446 - iCalendar Transport-Independent Interoperability Protocol (iTIP) . Internet Engineering Task Force. November 1998. Retrieved August 20, 2011.
- ↑ RFC 2447 - iCalendar Message-Based Interoperability Protocol (iMIP) . Internet Engineering Task Force. November 1998. Retrieved August 20, 2011.
- ↑ Patrick Crowley: iCalShare ( English ) Retrieved on December 1, 2018: "The largest calendar sharing resource on the web."
- ↑ Calsify Status Pages . Internet Engineering Task Force. Retrieved August 8, 2011.