Microformats Wiki - User contributions [en]

rfc-2445

2025-01-30T14:35:29Z

D: Added a bunch more information about iCalendar and its recent evolution

{{DISPLAYTITLE:iCalendar RFC 2445}}

{{warning|This page needs to be updated to be based on RFC 5445, moving old content to a History section for the legacy impact of 2445 on original hCalendar design etc.}}

iCalendar is a specification maintained by the IETF Calendaring Extensions (calext) Working Group, and is a widely used standard for the storage and exchange of calendar information. It was originally specified, as "vCalendar", by the Versit Consortium, before being passed to the Internet Mail Consortium, and finally adopted by the IETF. The second revision of the standard, renamed to iCalendar, has formed the basis of many calendaring applications for decades. Recent work within the IETF has proposed both new JSON-based syntax, as well as revised and extended semantics.

The core iCalendar objects include: events, todos, journal entries, and supporting timezone data. These definitions formed the semantic basis for the [[hcalendar|hCalendar]] microformat.

== History ==

* [https://cs.brown.edu/courses/cs190/old.spr1998/projects/acms/vCalendar_specs.pdf vCalendar] The original vCalendar specification, no longer in significant use.
* [http://www.ietf.org/rfc/rfc2445.txt RFC 2445], "Internet Calendaring and Scheduling Core Object Specification (iCalendar)", from 1998, defines the iCalendar 2.0 format, the basis for [[hcalendar|hCalendar]].
* [http://www.ietf.org/rfc/rfc5445.txt RFC 5445], "Internet Calendaring and Scheduling Core Object Specification (iCalendar)", from 2009, updates and replaces RFC 2445.
* [http://www.ietf.org/rfc/rfc6321.txt RFC 6321], "xCal: The XML Format for iCalendar", from 2011, maps the iCalendar syntax to XML.
* [http://www.ietf.org/rfc/rfc7265.txt RFC 7265], "jCal: The JSON Format for iCalendar", from 2014, maps the iCalendar syntax to JSON.
* [http://www.ietf.org/rfc/rfc7529.txt RFC 7529], "Non-Gregorian Recurrence Rules in the Internet Calendaring and Scheduling Core Object Specification (iCalendar)", from 2015, extends iCalendar.
* [http://www.ietf.org/rfc/rfc7953.txt RFC 7953], "Calendar Availability", from 2016, extends iCalendar with free/busy components for public scheduling.
* [http://www.ietf.org/rfc/rfc7986.txt RFC 7986], "New Properties for iCalendar", from 2016, extends iCalendar.
* [http://www.ietf.org/rfc/rfc9074.txt RFC 9074], "'VALARM' Extensions for iCalendar", from 2021, extends iCalendar to support alarms.
* [http://www.ietf.org/rfc/rfc9253.txt RFC 9253], "Support for iCalendar Relationships", from 2022, extends iCalendar to support relationships between calendar objects.

As of 2025, work in the IETF continues on a revised JSON format (JSCalendar), guidelines for conversion from iCalendar to JSCalendar (potentially valuable for microformats), revisions to tasks, extensions for polling and subscription, and more.

== References ==
When normatively referencing <nowiki>RFC 2445</nowiki> on this wiki, either do so by linking to this page with:
<nowiki>{{RFC2445}}</nowiki>
or directly to http://www.ietf.org/rfc/rfc2445.txt.

Avoid linking to the informative HTML translation of rfc2445.txt, which you must explicitly do by avoiding simply using the string <nowiki>RFC 2445</nowiki> in your text, as MediaWiki appears to auto-hyperlink it to the HTML translation thus: RFC 2445.

== Validator ==
* https://icalendar.org/validator.html
** [https://icalendar.org/More-Info/about-the-icalendar-validator.html About the validator.] (initial version launched in June 2015)

== See Also ==
* [[icalendar-errata|iCalendar errata]]
* [[icalendar-implementations|iCalendar implementations]]
* [[icalendar-issues|iCalendar issues]]
* [[hcalendar|hCalendar]]

hcalendar-implementations-fr

2025-01-30T13:40:42Z

D: /* Librairies */ Update URL for vobject

<h1>hCalendar Implémentations</h1>
{{TOC-right}}
Cette page est une section '''pour information''' de la spécification [[hcalendar-fr|hCalendar]].

Les implémentations suivantes ont été développées et génèrent ou parsent les hCalendars.
Si vous avez une implémentation [[hcalendar-fr|hCalendar]], sentez-vous libre de l'ajouter dans la section Nouvelles Implémentations. Si vous avez une page ou un site qui ''publie'' simplement des événements hCalendar, utilisez svp à la place [[hcalendar-examples-in-wild-fr|hcalendar-exemples-dans-la-jungle]].

==Nouvelles Implémentations==
Ajoutez-ici les nouvelles implémentations :
* Le calendrier du [http://TikiWiki.org CMS/Groupware TikiWiki] utilise le balisage hCalendar pour les événements. C'est une fonctionnalité intégrée (pas besoin de téléchargement de module/plugin/etc. séparé). Vous pouvez le voir à l'action sur [http://wiki-translation.com wiki-translation.com]
* [http://code.google.com/p/schoorbs Schoorbs] a des réservations enrichies de hCalendar dans view_entry.php depuis la révision 175 (devenant 1.0-Alpha2).
* [http://buzzword.org/cognition/ Cognition] supporte [[User:TobyInk/hcalendar-1.1|hcalendar 1.1]]
* ...

== Publier ==
Les implémentations que vous pouvez utiliser pour rédiger, créer et publier des événements hCalendar.

===Créateurs basés sur le Web===
;hCalendar Creator : [http://microformats.org/code/hcalendar/creator hCalendar creator] ([[hcalendar-creator-feedback-fr|hCalendar creator feedback]]) - créez vos propres événements hCalendar.
;Conference Schedule Creator : [http://dmitry.baranovskiy.com/work/csc/ Conference Schedule Creator] ([[hcalendar-schedule-creator-feedback-fr|Conference Schedule Creator feedback]]) - créez vos propres programmes de conférences avec des événements hCalendar.

=== Outils de Blog et CMS ===
;Midgard CMS : [http://www.midgard-project.org/documentation/net-nemein-calendar/ Midgard CMS - net.nemein.calendar] - comme c'est [http://bergie.iki.fi/blog/new-event-calendar-for-midcom.html blogué par Henri Bergius]
;Drupal module : [http://hybernaut.com/upcoming-hcal Drupal Upcoming.org syndication module emits hCalendar]
;MovableType et WordPress plug-ins : [http://structuredblogging.org/formats.php StructuredBlogging] est un ensemble de plugins [http://structuredblogging.org/structuredblogging-wp-latest.zip pour WordPress] et [http://structuredblogging.org/structuredblogging-wp-latest.zip pour MovableType] qui supporte l'embarquement de hCalendar et d'autre microformats dans les gabarits et les billets de blog.
;Textpattern plug-ins :
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] est un plugin pour [http://textpattern.com/ Textpattern] qui supporte l'embarquement de hCalendar et d'autres microformats dans les gabarits et billets de blog. Ecrit par [http://placenamehere.com/ Chris Casciano].
* [http://euphemize.net/blog/plugins/textpattern/jmc_event_manager/ jmc_event_manager] est un plugin pour [http://textpattern.com/ Textpattern] qui produit des événements et lieux en formats hCalendar (et hCard). Ecrit par [http://euphemize.net/ Joel Courtney].

=== Scripts et plugins pour Navigateurs ===
Plugins navigateurs qui fonctionnent avec les outils de publication existants :
; Tout navigateur avec javascript et un petit morceau de CSS : [http://microformats.org/code/hcalendar/creator microformats.org hCalendar creator] (vor aussi l'original : [http://theryanking.com/ Ryan King] a un [http://theryanking.com/microformats/hcalendar-creator.html hCalendar creator]).
; Firefox Greasemonkey user script hCalendar creator : [http://www.decafbad.com/blog/2005/06/08/greasemonkey_magic magic_hcalendar Greasemonkey user script par Les Orchard] - permet une saisie facile par formulaire d'un événement dans n'importe quelle aire de texte, par ex. à l'intérieur d'une aire de texte pour billet de blog.
; Firefox Greasemonkey user script hCalendar vers Google Calendar: [http://torrez.us Elias Torres] a créé un [http://torrez.us/archives/2006/04/13/431/ script simple] qui parsera les entrées hCalendar et créera un lien pour ajouter un événement vers [http://www.google.com/calendar/ le service de Google Calendar]. Basé sur le travail de [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats George] et de [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats Arve].

=== Outil de Publication de Bureau ===
;Dreamweaver Extension : [http://www.webstandards.org/action/dwtf/microformats/ Extension suite] pour Dreamweaver 8 tirée du [http://webstandards.org/ Web Standards Project].
;xfy :
dans la [https://www.xfytec.com/community/ Communauté xfy], il existe quelques implémentations hCalendar.
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=15&lid=25 hCalendar via RSS] parse un fil RSS, retrouve les documents XHTML liés à partir de ce fil et syndique les hCalendars à l'intérieur d'une vue calendrier.
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=19&lid=23 hCalendar Marker XVCD] aide à marquer une information évènement en document XHTML avec hCalendar.
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=15&lid=17 Simple RDF Calendar XVCD] est un outil de programmation qui utilise le format RDF Calendar. Il convertir aussi le format RDF Calendar vers les formats iCalendar et hCalendar.

== Recherche et Découverte ==
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexe les [[hcard-fr|hCard]], [[hcalendar-fr|hCalendar]] et [[hreview-fr|hReview]] comme [http://tantek.com/log/2006/05.html#d31t1802 annoncé par Tantek].
* [http://leftlogic.com/info/articles/microformats_bookmarklet Microformats Bookmarklet] est un bookmarklet conçu pour Safari (fonctionne dans Firefox et Camino) qui se superpose sur la page en cours pour permettre aux utilisateurs d'importer des [[hcard-fr|hCards]] ou des [[hcalendar-fr|hCalendars]]. Ecrit par [http://leftlogic.com Remy Sharp].
;Windows Live Writer :
* WLW's [http://gallery.live.com/liveItemDetail.aspx?li=9751e563-1408-4fc3-8028-bd4351edb1fb&l=8 Plugin Events] formate les événements dans les billets de blog avec hCalendar.

== Conversion et Importation ==
Les implémentations que vous pouvez utiliser pour l'importation dans une application calendrier, généralement en convertissant hCalendar vers iCalendar/vCalendar.

=== Web Services ===
Ceux-ci renvoient des formats iCalendar (.ics) et d'autres formats de calendrier à l'intérieur de programmes typiques de calendriers ou autre traitement.
* [http://feeds.technorati.com/events Technorati Events Feed service] utilise la librairie X2V pour parser hCalendar et renvoyer iCalendar (.ics).
** Notez l'URL facile à retenir, par ex. http://feeds.technorati.com/events/http%3A//microformats.org
* [http://suda.co.uk/projects/X2V/ X2V] parse hCalendar et produit un flux .ics (iCalendar). ** Note : a besoin d'être mis à jour pour garder une trace des modifications dans la spécification au fur et à mesure qu'elle arrive.

* [http://spanningsalesforce.com/ Spanning Salesforce] produit des fils RSS hCalendar et des calendriers .ics extraits de Salesforce.com.
* [http://makedatamakesense.com/myspace/event/ MySpace Events RSS Creator] crée des fils RSS des événements MySpace avec une syntaxe hCalendar.

=== Plugins Firefox Greasemonkey ===
* [http://george.hotelling.net/90percent/ George] a construit un [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey script utilisateur qui détecte les événements hCalendar et permet aux utilisateurs de les ajouter facilement à leurs application(s) de calendrier].
* [http://inside.glnetworks.de/ Martin Rehfeld] a mis à jour les travaux de [http://blogmatrix.blogmatrix.com/ David Janes] et produit un [[Greasemonkey-fr|Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] qui trouve beaucoup d'éléments microformats, y compris les événements hCalendar et [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 affiche un menu popup d'actions].
La conversion hCalendar en vCalendar est faite en interne dans le script. ''Ceci fonctionnera désormais bien dans FireFox 1.5+/GreaseMonkey 0.6.4+.''

===Agrégateurs ===
* [http://placenamehere.com/mf/nnwextract/ Extract Microformats] est un script pour NetNewsWire qui supporte l'extraction de données hCard et hCalendar dans les billets de blogs (via technorati service). Ecrit par [[User:ChrisCasciano|Chris Casciano]]
* [http://kula.jp/software/endo/screenshots/ Endo], un agrégateur OS X supporte de découvrir les hCal et ajoute ces événements dans iCal.
Regardez la photo d'écran en bas de la page.

== Browsing ==
Les implémentations qui détectent, affichent et autrement soulignent les événements hCalendar dans les pages.
* Dans la [http://www.xfytec.com/community/ xfy Community], il existe quelques implémentations hCalendar. "hCalendar via RSS" parse un fil RSS, retrouve les documents XHTML liés à partir de ce fil, et syndique les hCalendars à l'intérieur d'une vue calendrier.
* [http://code.google.com/p/js-hcalendar js-hcalendar] parse hCalendar et produit un HTML affichable en calendrier HTML fondé sur tableau/CSS (précédemment appelé JSCalendar).
* [http://thebitterpill.com/07-2007/a-jquery-hcal-parser/ jqueryhcal] est un parseur hCalendar basé sur jQuery qui supporte les événements sur plusieurs jours, dtend et d'autres fonctionnalités.

=== Extensions Firefox ===
*[http://www.orch8.net/ AlchemyPoint] est une extension Firefox et un service proxy qui peut détecter les microformats dans les documents HTML et afficher les suggestions navigation/mashup en se fondant sur leurs contenus.
* [http://blog.codeeg.com/tails-firefox-extension/ Tails est une extension Firefox] qui affichera la présence de microformats ([[hcard-fr|hCard]], [[hcalendar-fr|hCalendar]], [[hreview-fr|hReview]], [[xfolk-fr|xFolk]]) sur une page web.

===Imminent===
*[http://reminderfox.mozdev.org/ ReminderFox] a un import de hCalendar sur sa "to do liste".

=== Extension Flock ===
*[http://www.orch8.net/ AlchemyPoint] est une extension Firefox et un service proxy qui peut détecter les microformats dans les documents HTML et afficher les suggestions navigation/mashup en se fondant sur leurs contenus.
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - porte l'extension Tails pour Flock 0.5.12 qui cherche les hCards, hCalendar, xFolk et hReview et les secoue dans une barre supérieure bien commode.

== Librairies ==
Les librairies open source des parsers hCalendar et autres codes aparentés pour construire des implémentations hCalendar. . Note : il est très probable que quelques-unes des implémentations au-dessus puissent être dupliquées dans cette section. C'est ok.
; Javascript :
* [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats parseur simple hCalendar] par [http://virtuelvis.com/ Arve Bersvendsen]
* [http://microformats.org/code/hcalendar/creator hCalendar creator] ([[hcalendar-creator-feedback-fr|hCalendar creator feedback]])
; PHP :
*[http://randomchaos.com/microformats/base/ Microformat Base] est un crawler d'agrégation de microformat open-source PHP, reconnaissant actuellement hreview, hcalendar et hcard.
*[http://fresh.t-systems-sfr.com/unix/src/www/WebCalendar-devel-1.1.1.tar.gz:a/WebCalendar-1.1.1/includes/classes/hKit/hcal.profile.php profil hCalendar] pour le parseur [http://allinthehead.com/hkit/ hKit].
; Python :
* [https://github.com/py-vobject/vobject vObject], une partie du projet Chandler déclare un support du hCalendar.
; Ruby : [http://opensource.reevoo.com/2006/03/08/release-uformats-12/ uformats] est une librairie ruby qui peut parser [[hcalendar-fr|hCalendar]], [[hcard-fr|hCard]], [[hreview-fr|hReview]] et [[rel-tag-fr|rel-tag]]
; XSLT :
* X2V est disponible en tant que librairie XSLT
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] de [[User:DanC]] comprend toICal.xsl et des contenus de tests ;
elle fonctionne beaucoup comme xhtml2vcal.xsl dans X2V. Voir aussi : [http://www.w3.org/2002/12/cal/ RDF Calendar workspace] avec les contenus de test icalendar.

== Pages en rapport ==
{{hcalendar-related-pages-fr}}

hcalendar-implementations

2025-01-30T13:38:34Z

D: /* Libraries */ Update vobject details.

{{DISPLAYTITLE:hCalendar Implementations}}

This page is an '''informative''' section of the [[hcalendar|hCalendar specification]].

The following implementations have been developed which either generate or parse hCalendars. If you have an [[hcalendar|hCalendar]] implementation, feel free to add it to the New Implementations section. If you have a page or site which just ''publishes'' hCalendar events, please use [[hcalendar-examples-in-wild]] instead.

==New Implementations==
Add new implementations here:

* [http://www.agitraining.com/ AGI Adobe Training] uses hCalendar to list training course dates and share upcoming classes such as the list of scheduled [http://www.agitraining.com/adobe/photoshop/classes Photoshop classes].
* [http://iwenty.pl Iwenty.pl] is a polish search engine indexes web sites with events which implementing [[hcalendar|hCalendar]] microformat.
* [http://www.ledet.com/ Ledet Adobe Training Centers] uses hCalendar to distribute and list training class information at the company's [http://www.ledet.com/events training class listing].
* [http://www.cgtworld.com/ Cybernation Gamers Tournament] uses hCalendar in the match event like [http://www.cgtworld.com/match/id-193/ READY vs SouL].
* [http://www.w3.org/People/Bos/HcalProxy/ Hcalproxy] runs as an HTTP server, either standalone or under inetd(8), and converts hCalendar to iCalendar.
* The calendar of [http://TikiWiki.org TikiWiki CMS/Groupware] uses hCalendar markup for events. It's a built-in feature (no need to download separate module/plugin/etc). You can see in action over at [http://wiki-translation.com wiki-translation.com]
* [http://code.google.com/p/schoorbs Schoorbs] has bookings flavored with hCalendar in view_entry.php since revision 175 (becoming 1.0-Alpha2).
* [http://buzzword.org/cognition/ Cognition] supports [[User:TobyInk/hcalendar-1.1|hcalendar 1.1]]
* ...

==Authoring==
Implementations you can use to author, create, and publish hCalendar events.

===Web-based Creators===
;hCalendar Creator : [http://microformats.org/code/hcalendar/creator hCalendar creator] ([[hcalendar-creator-feedback|hCalendar creator feedback]]) - create your own hCalendar events.
;Conference Schedule Creator : [http://dmitry.baranovskiy.com/work/csc/ Conference Schedule Creator] ([[hcalendar-schedule-creator-feedback|Conference Schedule Creator feedback]]) - create your conference schedule with hCalendar events.
;Permatime hCalendar vevent generator : [http://permatime.com/ Permatime] enables sharing of points in time as well as acting as a quick way to generate hcalendar vevents.
;Dingbee : [http://dingbee.com Dingbee] allows you to share your events with hCalendar support.

===Blogging and CMS tools===
;Drupal module : [http://hybernaut.com/upcoming-hcal Drupal Upcoming.org syndication module emits hCalendar]

;[http://www.helioscalendar.com/ Helios Calendar] : for-sale PHP calendaring software that supports hCalendar. Example site with event: [http://www.caamuseum.org/hcalendar/events/index.php?com=detail&eID=2571 California African American Museum: DOCUMENTARY SCREENING]

;Midgard CMS : [http://www.midgard-project.org/documentation/net-nemein-calendar/ Midgard CMS - net.nemein.calendar] - as [http://bergie.iki.fi/blog/new-event-calendar-for-midcom.html blogged by Henri Bergius]

;Textpattern plug-ins :
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCalendar and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* [http://euphemize.net/blog/plugins/textpattern/jmc_event_manager/ jmc_event_manager] is a plugin for [http://textpattern.com/ Textpattern] that outputs events and locations in hCalendar (and hCard) formats. Written by [http://euphemize.net/ Joel Courtney].

===Browser scripts and plug-ins===
Browser plugins that work with existing authoring tools:
; Any browser with javascript and a little bit of CSS : [http://microformats.org/code/hcalendar/creator microformats.org hCalendar creator] (see also original: [http://theryanking.com/ Ryan King] has an [http://theryanking.com/microformats/hcalendar-creator.html hCalendar creator]).
; Firefox Greasemonkey user script hCalendar creator : [http://www.decafbad.com/blog/2005/06/08/greasemonkey_magic magic_hcalendar Greasemonkey user script by Les Orchard] - allows easy form entry of an event into any textarea, e.g. into a blog post text area.
; Firefox Greasemonkey user script hCalendar to Google Calendar: [http://torrez.us Elias Torres] has created a [http://torrez.us/archives/2006/04/13/431/ simple script] that will parse hCalendar entries and create a link to add event to [http://www.google.com/calendar/ Google Calendar's] service. Based on [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats George's] and [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats Arve's] work.

===Desktop Authoring Tools===
;Dreamweaver Extension : [http://www.webstandards.org/action/dwtf/microformats/ Extension suite] for Dreamweaver 8 from the [http://webstandards.org/ Web Standards Project].
;xfy :
In [https://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations.
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=15&lid=25 hCalendar via RSS] parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=19&lid=23 hCalendar Marker XVCD] helps to mark up an event information in XHTML document with hCalendar.
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=15&lid=17 Simple RDF Calendar XVCD] is a schedule tool which uses RDF Calendar format. It also converts RDF Calendar format to iCalendar and hCalendar format.
;Windows Live Writer :
* WLW's [http://gallery.live.com/liveItemDetail.aspx?li=9751e563-1408-4fc3-8028-bd4351edb1fb&l=8 Event Plugin] formats events in blog posts with hCalendar.

==Search and Discovery==
* [http://leftlogic.com/projects/microformats_bookmarklet Microformats Bookmarklet] is a bookmarklet designed for Safari (works in Firefox and Camino) that overlays on the current page to allow users to import individual [[hcard|hCards]] or [[hcalendar|hCalendars]]. Written by [http://leftlogic.com Remy Sharp].
* [http://iwenty.pl Iwenty.pl] is a polish search engine indexes web sites with events which implementing [[hcalendar|hCalendar]] microformat.

==Conversion and Import==
Implementations you can use to importing into a calendar application, typically by converting hCalendar to iCalendar/vCalendar.

===Web Services===
These return iCalendar (.ics) and other calendar formats for easy importing into typical calendar programs or other processing.
* [http://h2vx.com/ics H2VX Events Conversion service] uses X2V library to parse hCalendar and return iCalendar (.ics).
**The [http://georgebrock.com/projects/enhanced-hcalendar-downloads/ enhanced-hcalendar-downloads] script detects links to this service and displays a menu when they are clicked containing the original Technorati link and links to add the event to Google, Yahoo! and 30boxes. (see also [http://github.com/georgebrock/enhanced-hcalendar-downloads/ Github: enhanced-hcalendar-downloads]).
* [http://suda.co.uk/projects/X2V/ X2V] parses hCalendar and produces a .ics (iCalendar) stream.
**Note: needs to be updated to track changes in the specification as they occur.

* [http://spanningsalesforce.com/ Spanning Salesforce] produces hCalendar-enabled RSS feeds and .ics calendars from Salesforce.com.
* [http://makedatamakesense.com/myspace/event/ MySpace Events RSS Creator] creates RSS feeds of MySpace events with hCalendar markup.

===Firefox Greasemonkey Plugins===
* [http://george.hotelling.net/90percent/ George] has built a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script that detects hCalendar events and allows users to easily add them to their calendar application(s)].
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including hCalendar events, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCalendar to vCalendar conversion is done internally within the script. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''

===Aggregators===
* [http://placenamehere.com/mf/nnwextract/ Extract Microformats] is a script for NetNewsWire that supports extracting hCard and hCalendar data in blog posts (via Technorati service). Written by [[User:ChrisCasciano|Chris Casciano]]
* [http://kula.jp/software/endo/screenshots/ Endo], an OS X aggregator, supports discovering hCalendar and adding those events to iCal. Look at the last screenshot at the bottom of the page.

===Converters===
* [http://www.w3.org/People/Bos/HcalProxy/ Hcalproxy] runs as an HTTP server, either standalone or under inetd(8), and converts hCalendar to iCalendar. E.g., if Hcalproxy is running on localhost port 8000 and <nowiki>http://example.org/page.html</nowiki> points is an HTML page, then <nowiki>http://localhost:8000/http://example.org/page.html</nowiki> is an iCalendar document with the events from that page.

==Browsing==
Implementations that detect, display and otherwise highlight hCalendar events in pages.

* In [http://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations. "hCalendar via RSS" parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.
* [http://code.google.com/p/js-hcalendar js-hcalendar] parses hCalendar and produces a displayable HTML table/CSS-based calendar (formerly called JSCalendar).
* [http://thebitterpill.com/07-2007/a-jquery-hcal-parser/ jqueryhcal] is a jQuery-based hCalendar parser that supports multi-day events, dtend, and other features.

===Firefox extension===
*[http://www.orch8.net/ AlchemyPoint] is a Firefox extension and proxy service that can detect microformats in HTML documents and display browsing/mashup suggestions based on their contents.
*[http://blog.codeeg.com/tails-firefox-extension/ Tails is a Firefox Extension] that will display the presence of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage.
*[https://addons.mozilla.org/en-US/firefox/addon/4106 Operator] also displays the presence of microformats, is extensible, and allows you to add actions such as "Add hCalender to Yahoo! Calendar".

====Pending====
*[http://reminderfox.mozdev.org/ ReminderFox] have hCalendar import on their "to do " list.

===Flock extension===
*[http://www.orch8.net/ AlchemyPoint] is a Flock extension and proxy service that can detect microformats in HTML documents and display browsing/mashup suggestions based on their contents.
*[http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar

==Libraries==
Open source libraries of hCalendar parsers and other related code for building hCalendar implementations. Note: it is very likely that some of the above implementations may be duplicated in this section. That's ok.
; Javascript :
* [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats simple hCalendar parser] by [http://virtuelvis.com/ Arve Bersvendsen]
* [http://microformats.org/code/hcalendar/creator hCalendar creator] ([[hcalendar-creator-feedback|hCalendar creator feedback]])
; PHP :
*[http://randomchaos.com/microformats/base/ Microformat Base] is an open-source PHP microformat aggregation crawler, currently recognizing hreview, hcalendar, and hcard (Source code no longer available as of 6 Dec 06).
*[http://enarion.net/phpmicroformats/ phpMicroformats] is a PHP class library that generates microformats for calendar events (hCalendar) and vcards (hCard).
* [http://fresh.t-systems-sfr.com/unix/src/www/WebCalendar-devel-1.1.1.tar.gz:a/WebCalendar-1.1.1/includes/classes/hKit/hcal.profile.php hCalendar profile] for the [http://allinthehead.com/hkit/ hKit] parser.
; Ruby [http://rubyforge.org/projects/uformats/ uformats]: is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]
; XSLT :
* X2V is available as an XSLT library
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] by [[User:DanC]] includes toICal.xsl and test materials; it works much like xhtml2vcal.xsl in X2V. See also: [http://www.w3.org/2002/12/cal/ RDF Calendar workspace] with icalendar test materials.
; Python :
* [https://github.com/py-vobject/vobject vObject], an Apache2-licensed Python [[icalendar|iCalendar]]/[[vcard|vCard]] package, has support for export of calendar objects in [[hcalendar|hCalendar]] format.

== Old ==
Past sites/services/implementations of hCalendar. Some sites may have gone offline, others may have changed completely.

Previously:
* 2005-2009? StructuredBlogging (<nowiki>http://structuredblogging.org/formats.php</nowiki>) was a set of plugins (<nowiki>http://structuredblogging.org/structuredblogging-wp-latest.zip</nowiki>) for WordPress and MovableType that supported embedding hCalendar and other microformats in templates and blog posts.

* 2005-2011 <nowiki>http://feeds.technorati.com/events</nowiki> Technorati Events Feed service] uses X2V library to parse hCalendar and return iCalendar (.ics).
**Note friendly URL, e.g. <nowiki>http://feeds.technorati.com/events/http%3A//microformats.org</nowiki>

* 2006-2008 <nowiki>http://kitchen.technorati.com/search Technorati Microformats Search</nowiki> indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek].

== Related Pages ==
{{hcalendar-related-pages}}

icalendar-implementations

2025-01-30T13:32:57Z

D: Better internal linkage.

<h1> iCalendar implementations </h1>
{{TOC-right}}
This is a list of calendar programs, applications and services that support the iCalendar {{RFC2445}} standard.

In addition, please note any quirks or bugs with implementations' handling of iCalendar - we've already discovered some in the development of [[hcalendar|hCalendar]] and proxies like X2V.

== libraries ==

=== C libical ===
Open source C-based implementation of iCalendar.

* [https://github.com/libical/libical Github]

=== Python icalendar ===
Python implementation of iCalendar.

* [https://pypi.python.org/pypi/icalendar/ PyPI]

=== Python vobject ===
Apache 2.0-licensed Python iCalendar parser/generator library package, which also supports [[vcard|vCard]] and [[hcalendar|hCalendar]].

* [https://github.com/py-vobject/vobject GitHub]
* [https://pypi.org/project/vobject/ PyPI]

== services ==
=== Google Calendar ===
http://calendar.google.com/
* supports subscribing to "webcal:" and "http:" URLs to iCalendar

== products ==
=== Apple Calendar.app ===
Apple Calendar.app, formerly known as iCal.
* platform: OSX
* handles "webcal:" URLs and supports subscribing to events.

==== Apple iCal 2.0.5 ====
Apple iCal.app 2.0.5 build 1069 (AppleiCal205)

===== iCal 2.0.5 notes =====
* '''Requires dates and date-times without separators.''' Apple iCal 2.0.5 (and probably other versions) appears to require dates without "-" and times without ":" which appears to be consistent with the iCalendar spec due to:
** iCalendar section 4.3.4 Date - "date-value = date-fullyear date-month date-mday" (no separators)
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators)

As a result Apple iCal 2.0.5 ignores date and date-time properties (e.g. DTSTART, DTEND, etc.) when date components (year, month, day) are separated by "-" or when time components (hours, minutes, seconds) are separated by ":" (both as allowed by [[ISO8601]] and required by [[RFC3339]]).

However per [[accessibility]] research, dates and times with separators are more readable and accessible, and consequently explicitly allowed by hCalendar.

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date and date-time properties (e.g. DTSTART, DTEND, etc.) with separators, and remove separators when converting to iCalendar.

* '''Requires date-times with seconds explicitly specified.''' Apple iCal 2.0.5 (and probably other versions) appears to require date-times with the seconds explicitly specified, which appears to be consistent with the iCalendar spec:
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators)

However in practice (see [[hcalendar-examples-in-wild]]) hCalendar date-time properties often omit the seconds because when they are "00" for simplicity and easier/quicker readability.

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date-time properties (e.g. DTSTART, DTEND, etc.) without the seconds explicitly specified, and imply "00" seconds when converting to iCalendar.

* '''Requires floating or UTC date-times.''' Apple iCal 2.0.5 (and probably other versions) appears to require date-times which are either floating (no time zone) or explicitly specified to be UTC and ignores date-times which use timezone offsets, which appears to be consistent with the iCalendar spec:
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators) and: <blockquote><p>The form of time with UTC offset MUST NOT be used. For example, the following is NOT VALID for a time value:</p><pre>230000-0800 ;Invalid time format</pre></blockquote>

However, in practice (see [[hcalendar-examples-in-wild]]) hCalendar date-time properties often state the timezone offset in order to make the human visible time consistent with the machine readable time for easier verification (minimize DRY divergence probability).

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date-time properties (e.g. DTSTART, DTEND, etc.) with an explicit timezone offset, and convert the specified date-time value to a UTC value when converting to iCalendar.

All hCalendar processor requirements above should be documented thoroughly in [[hcalendar-parsing]].

==== Apple Calendar.app 8.0 (2092.3) ====

Timezone handling: Calendar.app is incompatible with timezone-aware dates produced by the Python iCalendar implementation which puts quotation marks around TZIDs. See [https://gist.github.com/tommorris/0aca78d680804c04bf1e35318893a34a this gist] for details.

=== KOrganizer ===
* platforms: All Linux, *BSD, etc. (Wherever KDE runs)
* supports the "webcal:" protocol, as well as "http:", "ftp:", "fish:", etc.

=== Evolution ===
* platform: Fedora Core 3
* supports "webcal:" protocol

=== Sunbird ===
[http://www.mozilla.org/projects/calendar/sunbird.html Mozilla Sunbird]
* platforms: Windows XP, others?
* supports "webcal:" protocol

=== Microsoft Outlook ===
==== Microsoft Outlook 2007 ====
Microsoft Outlook 2007 (MSOutlook2k7)
* platforms: Windows
* supports importing and subscribing to .ics files, "webcal:" URLs, etc.

==== Microsoft Outlook 2003 ====
Microsoft Outlook 2003 (MSOutlook2k3)
* platforms: Windows
* supports importing .ics files

===== MSOutlook2k3 general comments =====
For importing, MSOutlook2k3 apparently requires VEVENTS to have <code>UID</code>, <code>DTSTAMP</code>, and <code>METHOD</code> properties. ('''citation/platform/date tested info needed'''). If any of the three is not present, returns this message:

<pre>
This error can appear if you have attempted to save a recurring Lunar appointment in iCalendar format.
To avoid this error, set the appointment option to Gregorian instead of Lunar.
</pre>

After some testing, this seems to be the generic message to indicate a problem with event import.

No such restriction is placed on [[rfc-2445#vCalendar|vCalendar 1.0]] events. So, if <code>VERSION:1.0</code> is output instead of <code>VERSION:2.0</code>, the only required field is <code>DTSTART</code>.
Note that <code>VERSION</code> property may be omitted. In this case, value inferred as <code>1.0</code>.

* UID and DTSTAMP is required for Outlook to import. [[User:GeoffWebb|GeoffWebb]] 14:03, 9 Dec 2005 (PST)

===== Potential Security Related Issue w/ Outlook 2003 and Standard Account =====

I've been all over the web tracing the "Lunar" exception.
I believe I'm come across another lunar permutation.
I have an XP box running Outlook 2003 SP3 with Admin privileges, and I have an XP box running Outlook 2003 SP3 (same build number) running under a standard account.
The .ics will try to import correctly under the Admin account (aka, it will prompt you for acceptance, everything working as expected). HOWEVER, the same .ics file will throw the "lunar" exception on the ~standard~ account.

Here is my environment information just in case you're bumping your head on this issue.

Outlook 2003 with SP3 Build Number : 11.8325.8329

.ics file contents (aka, "known to work" file contents under the Admin account)

<pre>BEGIN:VCALENDAR
VERSION:2.0
PRODID:www.testMeiCalendar.net
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20101231T230000
DTEND:20110101T010000
SUMMARY:New Years Eve Reminder
LOCATION:Downtown
DESCRIPTION:Let's get together for New Years Eve
UID:ABCD1234
SEQUENCE:0
DTSTAMP:20101125T112600
END:VEVENT
END:VCALENDAR
</pre>

To be honest, I probably will just abandon trying to use it for this project because of this issue.
But I wanted to report it, so someone doesn't waste a day thinking the issue is the contents of the .ics file.

===== MSOutlook2k3 sample importable iCalendar =====
<pre>
BEGIN:VCALENDAR
VERSION:2.0
METHOD:PUBLISH
BEGIN:VEVENT
UID:0
DTSTAMP:20060601T080000
DTSTART:20060601T080000
END:VEVENT
END:VCALENDAR
</pre>

===== MSOutlook2k3 sample importable vCalendar =====
<pre>
BEGIN:VCALENDAR
BEGIN:VEVENT
DTSTART:20060601T080000
END:VEVENT
END:VCALENDAR
</pre>

=== Fantastical ===

* Platform: Mac and iOS
* supports importing ICS files and subscribing using webcal (tested using Facebok URL)
* Implemented using libical

== notes ==
* the "webcal:" URL protocol scheme is non-standard.

== contributors==
* Tantek Çelik
* [[DimitriGlazkov|Dimitri Glazkov]]
* [[User:TomMorris|Tom Morris]]

== related pages ==
{{hcalendar-related-pages}}

icalendar-implementations

2025-01-30T13:30:08Z

D: /* Python iCalendar */ Remove this section: its content is merged into the previous section.

<h1> iCalendar implementations </h1>
{{TOC-right}}
This is a list of calendar programs, applications and services that support the iCalendar {{RFC2445}} standard.

In addition, please note any quirks or bugs with implementations' handling of iCalendar - we've already discovered some in the development of [[hcalendar|hCalendar]] and proxies like X2V.

== libraries ==

=== C libical ===
Open source C-based implementation of iCalendar.

* [https://github.com/libical/libical Github]

=== Python icalendar ===
Python implementation of iCalendar.

* [https://pypi.python.org/pypi/icalendar/ PyPI]

=== Python vobject ===
Apache 2.0-licensed Python iCalendar parser/generator library package, which also supports vCard and hCalendar.

* [https://github.com/py-vobject/vobject GitHub]
* [https://pypi.org/project/vobject/ PyPI]

== services ==
=== Google Calendar ===
http://calendar.google.com/
* supports subscribing to "webcal:" and "http:" URLs to iCalendar

== products ==
=== Apple Calendar.app ===
Apple Calendar.app, formerly known as iCal.
* platform: OSX
* handles "webcal:" URLs and supports subscribing to events.

==== Apple iCal 2.0.5 ====
Apple iCal.app 2.0.5 build 1069 (AppleiCal205)

===== iCal 2.0.5 notes =====
* '''Requires dates and date-times without separators.''' Apple iCal 2.0.5 (and probably other versions) appears to require dates without "-" and times without ":" which appears to be consistent with the iCalendar spec due to:
** iCalendar section 4.3.4 Date - "date-value = date-fullyear date-month date-mday" (no separators)
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators)

As a result Apple iCal 2.0.5 ignores date and date-time properties (e.g. DTSTART, DTEND, etc.) when date components (year, month, day) are separated by "-" or when time components (hours, minutes, seconds) are separated by ":" (both as allowed by [[ISO8601]] and required by [[RFC3339]]).

However per [[accessibility]] research, dates and times with separators are more readable and accessible, and consequently explicitly allowed by hCalendar.

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date and date-time properties (e.g. DTSTART, DTEND, etc.) with separators, and remove separators when converting to iCalendar.

* '''Requires date-times with seconds explicitly specified.''' Apple iCal 2.0.5 (and probably other versions) appears to require date-times with the seconds explicitly specified, which appears to be consistent with the iCalendar spec:
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators)

However in practice (see [[hcalendar-examples-in-wild]]) hCalendar date-time properties often omit the seconds because when they are "00" for simplicity and easier/quicker readability.

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date-time properties (e.g. DTSTART, DTEND, etc.) without the seconds explicitly specified, and imply "00" seconds when converting to iCalendar.

* '''Requires floating or UTC date-times.''' Apple iCal 2.0.5 (and probably other versions) appears to require date-times which are either floating (no time zone) or explicitly specified to be UTC and ignores date-times which use timezone offsets, which appears to be consistent with the iCalendar spec:
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators) and: <blockquote><p>The form of time with UTC offset MUST NOT be used. For example, the following is NOT VALID for a time value:</p><pre>230000-0800 ;Invalid time format</pre></blockquote>

However, in practice (see [[hcalendar-examples-in-wild]]) hCalendar date-time properties often state the timezone offset in order to make the human visible time consistent with the machine readable time for easier verification (minimize DRY divergence probability).

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date-time properties (e.g. DTSTART, DTEND, etc.) with an explicit timezone offset, and convert the specified date-time value to a UTC value when converting to iCalendar.

All hCalendar processor requirements above should be documented thoroughly in [[hcalendar-parsing]].

==== Apple Calendar.app 8.0 (2092.3) ====

Timezone handling: Calendar.app is incompatible with timezone-aware dates produced by the Python iCalendar implementation which puts quotation marks around TZIDs. See [https://gist.github.com/tommorris/0aca78d680804c04bf1e35318893a34a this gist] for details.

=== KOrganizer ===
* platforms: All Linux, *BSD, etc. (Wherever KDE runs)
* supports the "webcal:" protocol, as well as "http:", "ftp:", "fish:", etc.

=== Evolution ===
* platform: Fedora Core 3
* supports "webcal:" protocol

=== Sunbird ===
[http://www.mozilla.org/projects/calendar/sunbird.html Mozilla Sunbird]
* platforms: Windows XP, others?
* supports "webcal:" protocol

=== Microsoft Outlook ===
==== Microsoft Outlook 2007 ====
Microsoft Outlook 2007 (MSOutlook2k7)
* platforms: Windows
* supports importing and subscribing to .ics files, "webcal:" URLs, etc.

==== Microsoft Outlook 2003 ====
Microsoft Outlook 2003 (MSOutlook2k3)
* platforms: Windows
* supports importing .ics files

===== MSOutlook2k3 general comments =====
For importing, MSOutlook2k3 apparently requires VEVENTS to have <code>UID</code>, <code>DTSTAMP</code>, and <code>METHOD</code> properties. ('''citation/platform/date tested info needed'''). If any of the three is not present, returns this message:

<pre>
This error can appear if you have attempted to save a recurring Lunar appointment in iCalendar format.
To avoid this error, set the appointment option to Gregorian instead of Lunar.
</pre>

After some testing, this seems to be the generic message to indicate a problem with event import.

No such restriction is placed on [[rfc-2445#vCalendar|vCalendar 1.0]] events. So, if <code>VERSION:1.0</code> is output instead of <code>VERSION:2.0</code>, the only required field is <code>DTSTART</code>.
Note that <code>VERSION</code> property may be omitted. In this case, value inferred as <code>1.0</code>.

* UID and DTSTAMP is required for Outlook to import. [[User:GeoffWebb|GeoffWebb]] 14:03, 9 Dec 2005 (PST)

===== Potential Security Related Issue w/ Outlook 2003 and Standard Account =====

I've been all over the web tracing the "Lunar" exception.
I believe I'm come across another lunar permutation.
I have an XP box running Outlook 2003 SP3 with Admin privileges, and I have an XP box running Outlook 2003 SP3 (same build number) running under a standard account.
The .ics will try to import correctly under the Admin account (aka, it will prompt you for acceptance, everything working as expected). HOWEVER, the same .ics file will throw the "lunar" exception on the ~standard~ account.

Here is my environment information just in case you're bumping your head on this issue.

Outlook 2003 with SP3 Build Number : 11.8325.8329

.ics file contents (aka, "known to work" file contents under the Admin account)

<pre>BEGIN:VCALENDAR
VERSION:2.0
PRODID:www.testMeiCalendar.net
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20101231T230000
DTEND:20110101T010000
SUMMARY:New Years Eve Reminder
LOCATION:Downtown
DESCRIPTION:Let's get together for New Years Eve
UID:ABCD1234
SEQUENCE:0
DTSTAMP:20101125T112600
END:VEVENT
END:VCALENDAR
</pre>

To be honest, I probably will just abandon trying to use it for this project because of this issue.
But I wanted to report it, so someone doesn't waste a day thinking the issue is the contents of the .ics file.

===== MSOutlook2k3 sample importable iCalendar =====
<pre>
BEGIN:VCALENDAR
VERSION:2.0
METHOD:PUBLISH
BEGIN:VEVENT
UID:0
DTSTAMP:20060601T080000
DTSTART:20060601T080000
END:VEVENT
END:VCALENDAR
</pre>

===== MSOutlook2k3 sample importable vCalendar =====
<pre>
BEGIN:VCALENDAR
BEGIN:VEVENT
DTSTART:20060601T080000
END:VEVENT
END:VCALENDAR
</pre>

=== Fantastical ===

* Platform: Mac and iOS
* supports importing ICS files and subscribing using webcal (tested using Facebok URL)
* Implemented using libical

== notes ==
* the "webcal:" URL protocol scheme is non-standard.

== contributors==
* Tantek Çelik
* [[DimitriGlazkov|Dimitri Glazkov]]
* [[User:TomMorris|Tom Morris]]

== related pages ==
{{hcalendar-related-pages}}

icalendar-implementations

2025-01-30T13:29:24Z

D: /* libraries */ Merge Python iCalendar into this section.

<h1> iCalendar implementations </h1>
{{TOC-right}}
This is a list of calendar programs, applications and services that support the iCalendar {{RFC2445}} standard.

In addition, please note any quirks or bugs with implementations' handling of iCalendar - we've already discovered some in the development of [[hcalendar|hCalendar]] and proxies like X2V.

== libraries ==

=== C libical ===
Open source C-based implementation of iCalendar.

* [https://github.com/libical/libical Github]

=== Python icalendar ===
Python implementation of iCalendar.

* [https://pypi.python.org/pypi/icalendar/ PyPI]

=== Python vobject ===
Apache 2.0-licensed Python iCalendar parser/generator library package, which also supports vCard and hCalendar.

* [https://github.com/py-vobject/vobject GitHub]
* [https://pypi.org/project/vobject/ PyPI]

== Python iCalendar ==
Python implementation of iCalendar.

* [https://pypi.python.org/pypi/icalendar/ PyPI]

== services ==
=== Google Calendar ===
http://calendar.google.com/
* supports subscribing to "webcal:" and "http:" URLs to iCalendar

== products ==
=== Apple Calendar.app ===
Apple Calendar.app, formerly known as iCal.
* platform: OSX
* handles "webcal:" URLs and supports subscribing to events.

==== Apple iCal 2.0.5 ====
Apple iCal.app 2.0.5 build 1069 (AppleiCal205)

===== iCal 2.0.5 notes =====
* '''Requires dates and date-times without separators.''' Apple iCal 2.0.5 (and probably other versions) appears to require dates without "-" and times without ":" which appears to be consistent with the iCalendar spec due to:
** iCalendar section 4.3.4 Date - "date-value = date-fullyear date-month date-mday" (no separators)
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators)

As a result Apple iCal 2.0.5 ignores date and date-time properties (e.g. DTSTART, DTEND, etc.) when date components (year, month, day) are separated by "-" or when time components (hours, minutes, seconds) are separated by ":" (both as allowed by [[ISO8601]] and required by [[RFC3339]]).

However per [[accessibility]] research, dates and times with separators are more readable and accessible, and consequently explicitly allowed by hCalendar.

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date and date-time properties (e.g. DTSTART, DTEND, etc.) with separators, and remove separators when converting to iCalendar.

* '''Requires date-times with seconds explicitly specified.''' Apple iCal 2.0.5 (and probably other versions) appears to require date-times with the seconds explicitly specified, which appears to be consistent with the iCalendar spec:
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators)

However in practice (see [[hcalendar-examples-in-wild]]) hCalendar date-time properties often omit the seconds because when they are "00" for simplicity and easier/quicker readability.

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date-time properties (e.g. DTSTART, DTEND, etc.) without the seconds explicitly specified, and imply "00" seconds when converting to iCalendar.

* '''Requires floating or UTC date-times.''' Apple iCal 2.0.5 (and probably other versions) appears to require date-times which are either floating (no time zone) or explicitly specified to be UTC and ignores date-times which use timezone offsets, which appears to be consistent with the iCalendar spec:
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators) and: <blockquote><p>The form of time with UTC offset MUST NOT be used. For example, the following is NOT VALID for a time value:</p><pre>230000-0800 ;Invalid time format</pre></blockquote>

However, in practice (see [[hcalendar-examples-in-wild]]) hCalendar date-time properties often state the timezone offset in order to make the human visible time consistent with the machine readable time for easier verification (minimize DRY divergence probability).

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date-time properties (e.g. DTSTART, DTEND, etc.) with an explicit timezone offset, and convert the specified date-time value to a UTC value when converting to iCalendar.

All hCalendar processor requirements above should be documented thoroughly in [[hcalendar-parsing]].

==== Apple Calendar.app 8.0 (2092.3) ====

Timezone handling: Calendar.app is incompatible with timezone-aware dates produced by the Python iCalendar implementation which puts quotation marks around TZIDs. See [https://gist.github.com/tommorris/0aca78d680804c04bf1e35318893a34a this gist] for details.

=== KOrganizer ===
* platforms: All Linux, *BSD, etc. (Wherever KDE runs)
* supports the "webcal:" protocol, as well as "http:", "ftp:", "fish:", etc.

=== Evolution ===
* platform: Fedora Core 3
* supports "webcal:" protocol

=== Sunbird ===
[http://www.mozilla.org/projects/calendar/sunbird.html Mozilla Sunbird]
* platforms: Windows XP, others?
* supports "webcal:" protocol

=== Microsoft Outlook ===
==== Microsoft Outlook 2007 ====
Microsoft Outlook 2007 (MSOutlook2k7)
* platforms: Windows
* supports importing and subscribing to .ics files, "webcal:" URLs, etc.

==== Microsoft Outlook 2003 ====
Microsoft Outlook 2003 (MSOutlook2k3)
* platforms: Windows
* supports importing .ics files

===== MSOutlook2k3 general comments =====
For importing, MSOutlook2k3 apparently requires VEVENTS to have <code>UID</code>, <code>DTSTAMP</code>, and <code>METHOD</code> properties. ('''citation/platform/date tested info needed'''). If any of the three is not present, returns this message:

<pre>
This error can appear if you have attempted to save a recurring Lunar appointment in iCalendar format.
To avoid this error, set the appointment option to Gregorian instead of Lunar.
</pre>

After some testing, this seems to be the generic message to indicate a problem with event import.

No such restriction is placed on [[rfc-2445#vCalendar|vCalendar 1.0]] events. So, if <code>VERSION:1.0</code> is output instead of <code>VERSION:2.0</code>, the only required field is <code>DTSTART</code>.
Note that <code>VERSION</code> property may be omitted. In this case, value inferred as <code>1.0</code>.

* UID and DTSTAMP is required for Outlook to import. [[User:GeoffWebb|GeoffWebb]] 14:03, 9 Dec 2005 (PST)

===== Potential Security Related Issue w/ Outlook 2003 and Standard Account =====

I've been all over the web tracing the "Lunar" exception.
I believe I'm come across another lunar permutation.
I have an XP box running Outlook 2003 SP3 with Admin privileges, and I have an XP box running Outlook 2003 SP3 (same build number) running under a standard account.
The .ics will try to import correctly under the Admin account (aka, it will prompt you for acceptance, everything working as expected). HOWEVER, the same .ics file will throw the "lunar" exception on the ~standard~ account.

Here is my environment information just in case you're bumping your head on this issue.

Outlook 2003 with SP3 Build Number : 11.8325.8329

.ics file contents (aka, "known to work" file contents under the Admin account)

<pre>BEGIN:VCALENDAR
VERSION:2.0
PRODID:www.testMeiCalendar.net
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20101231T230000
DTEND:20110101T010000
SUMMARY:New Years Eve Reminder
LOCATION:Downtown
DESCRIPTION:Let's get together for New Years Eve
UID:ABCD1234
SEQUENCE:0
DTSTAMP:20101125T112600
END:VEVENT
END:VCALENDAR
</pre>

To be honest, I probably will just abandon trying to use it for this project because of this issue.
But I wanted to report it, so someone doesn't waste a day thinking the issue is the contents of the .ics file.

===== MSOutlook2k3 sample importable iCalendar =====
<pre>
BEGIN:VCALENDAR
VERSION:2.0
METHOD:PUBLISH
BEGIN:VEVENT
UID:0
DTSTAMP:20060601T080000
DTSTART:20060601T080000
END:VEVENT
END:VCALENDAR
</pre>

===== MSOutlook2k3 sample importable vCalendar =====
<pre>
BEGIN:VCALENDAR
BEGIN:VEVENT
DTSTART:20060601T080000
END:VEVENT
END:VCALENDAR
</pre>

=== Fantastical ===

* Platform: Mac and iOS
* supports importing ICS files and subscribing using webcal (tested using Facebok URL)
* Implemented using libical

== notes ==
* the "webcal:" URL protocol scheme is non-standard.

== contributors==
* Tantek Çelik
* [[DimitriGlazkov|Dimitri Glazkov]]
* [[User:TomMorris|Tom Morris]]

== related pages ==
{{hcalendar-related-pages}}

icalendar-implementations

2025-01-30T13:27:28Z

D: /* libraries */ Highlight language

<h1> iCalendar implementations </h1>
{{TOC-right}}
This is a list of calendar programs, applications and services that support the iCalendar {{RFC2445}} standard.

In addition, please note any quirks or bugs with implementations' handling of iCalendar - we've already discovered some in the development of [[hcalendar|hCalendar]] and proxies like X2V.

== libraries ==

=== C libical ===
Open source C-based implementation of iCalendar.

* [https://github.com/libical/libical Github]

=== Python vobject ===
Apache 2.0-licensed Python iCalendar parser/generator library package

* [https://github.com/py-vobject/vobject GitHub]
* [https://pypi.org/project/vobject/ PyPI]

== Python iCalendar ==
Python implementation of iCalendar.

* [https://pypi.python.org/pypi/icalendar/ PyPI]

== services ==
=== Google Calendar ===
http://calendar.google.com/
* supports subscribing to "webcal:" and "http:" URLs to iCalendar

== products ==
=== Apple Calendar.app ===
Apple Calendar.app, formerly known as iCal.
* platform: OSX
* handles "webcal:" URLs and supports subscribing to events.

==== Apple iCal 2.0.5 ====
Apple iCal.app 2.0.5 build 1069 (AppleiCal205)

===== iCal 2.0.5 notes =====
* '''Requires dates and date-times without separators.''' Apple iCal 2.0.5 (and probably other versions) appears to require dates without "-" and times without ":" which appears to be consistent with the iCalendar spec due to:
** iCalendar section 4.3.4 Date - "date-value = date-fullyear date-month date-mday" (no separators)
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators)

As a result Apple iCal 2.0.5 ignores date and date-time properties (e.g. DTSTART, DTEND, etc.) when date components (year, month, day) are separated by "-" or when time components (hours, minutes, seconds) are separated by ":" (both as allowed by [[ISO8601]] and required by [[RFC3339]]).

However per [[accessibility]] research, dates and times with separators are more readable and accessible, and consequently explicitly allowed by hCalendar.

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date and date-time properties (e.g. DTSTART, DTEND, etc.) with separators, and remove separators when converting to iCalendar.

* '''Requires date-times with seconds explicitly specified.''' Apple iCal 2.0.5 (and probably other versions) appears to require date-times with the seconds explicitly specified, which appears to be consistent with the iCalendar spec:
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators)

However in practice (see [[hcalendar-examples-in-wild]]) hCalendar date-time properties often omit the seconds because when they are "00" for simplicity and easier/quicker readability.

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date-time properties (e.g. DTSTART, DTEND, etc.) without the seconds explicitly specified, and imply "00" seconds when converting to iCalendar.

* '''Requires floating or UTC date-times.''' Apple iCal 2.0.5 (and probably other versions) appears to require date-times which are either floating (no time zone) or explicitly specified to be UTC and ignores date-times which use timezone offsets, which appears to be consistent with the iCalendar spec:
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators) and: <blockquote><p>The form of time with UTC offset MUST NOT be used. For example, the following is NOT VALID for a time value:</p><pre>230000-0800 ;Invalid time format</pre></blockquote>

However, in practice (see [[hcalendar-examples-in-wild]]) hCalendar date-time properties often state the timezone offset in order to make the human visible time consistent with the machine readable time for easier verification (minimize DRY divergence probability).

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date-time properties (e.g. DTSTART, DTEND, etc.) with an explicit timezone offset, and convert the specified date-time value to a UTC value when converting to iCalendar.

All hCalendar processor requirements above should be documented thoroughly in [[hcalendar-parsing]].

==== Apple Calendar.app 8.0 (2092.3) ====

Timezone handling: Calendar.app is incompatible with timezone-aware dates produced by the Python iCalendar implementation which puts quotation marks around TZIDs. See [https://gist.github.com/tommorris/0aca78d680804c04bf1e35318893a34a this gist] for details.

=== KOrganizer ===
* platforms: All Linux, *BSD, etc. (Wherever KDE runs)
* supports the "webcal:" protocol, as well as "http:", "ftp:", "fish:", etc.

=== Evolution ===
* platform: Fedora Core 3
* supports "webcal:" protocol

=== Sunbird ===
[http://www.mozilla.org/projects/calendar/sunbird.html Mozilla Sunbird]
* platforms: Windows XP, others?
* supports "webcal:" protocol

=== Microsoft Outlook ===
==== Microsoft Outlook 2007 ====
Microsoft Outlook 2007 (MSOutlook2k7)
* platforms: Windows
* supports importing and subscribing to .ics files, "webcal:" URLs, etc.

==== Microsoft Outlook 2003 ====
Microsoft Outlook 2003 (MSOutlook2k3)
* platforms: Windows
* supports importing .ics files

===== MSOutlook2k3 general comments =====
For importing, MSOutlook2k3 apparently requires VEVENTS to have <code>UID</code>, <code>DTSTAMP</code>, and <code>METHOD</code> properties. ('''citation/platform/date tested info needed'''). If any of the three is not present, returns this message:

<pre>
This error can appear if you have attempted to save a recurring Lunar appointment in iCalendar format.
To avoid this error, set the appointment option to Gregorian instead of Lunar.
</pre>

After some testing, this seems to be the generic message to indicate a problem with event import.

No such restriction is placed on [[rfc-2445#vCalendar|vCalendar 1.0]] events. So, if <code>VERSION:1.0</code> is output instead of <code>VERSION:2.0</code>, the only required field is <code>DTSTART</code>.
Note that <code>VERSION</code> property may be omitted. In this case, value inferred as <code>1.0</code>.

* UID and DTSTAMP is required for Outlook to import. [[User:GeoffWebb|GeoffWebb]] 14:03, 9 Dec 2005 (PST)

===== Potential Security Related Issue w/ Outlook 2003 and Standard Account =====

I've been all over the web tracing the "Lunar" exception.
I believe I'm come across another lunar permutation.
I have an XP box running Outlook 2003 SP3 with Admin privileges, and I have an XP box running Outlook 2003 SP3 (same build number) running under a standard account.
The .ics will try to import correctly under the Admin account (aka, it will prompt you for acceptance, everything working as expected). HOWEVER, the same .ics file will throw the "lunar" exception on the ~standard~ account.

Here is my environment information just in case you're bumping your head on this issue.

Outlook 2003 with SP3 Build Number : 11.8325.8329

.ics file contents (aka, "known to work" file contents under the Admin account)

<pre>BEGIN:VCALENDAR
VERSION:2.0
PRODID:www.testMeiCalendar.net
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20101231T230000
DTEND:20110101T010000
SUMMARY:New Years Eve Reminder
LOCATION:Downtown
DESCRIPTION:Let's get together for New Years Eve
UID:ABCD1234
SEQUENCE:0
DTSTAMP:20101125T112600
END:VEVENT
END:VCALENDAR
</pre>

To be honest, I probably will just abandon trying to use it for this project because of this issue.
But I wanted to report it, so someone doesn't waste a day thinking the issue is the contents of the .ics file.

===== MSOutlook2k3 sample importable iCalendar =====
<pre>
BEGIN:VCALENDAR
VERSION:2.0
METHOD:PUBLISH
BEGIN:VEVENT
UID:0
DTSTAMP:20060601T080000
DTSTART:20060601T080000
END:VEVENT
END:VCALENDAR
</pre>

===== MSOutlook2k3 sample importable vCalendar =====
<pre>
BEGIN:VCALENDAR
BEGIN:VEVENT
DTSTART:20060601T080000
END:VEVENT
END:VCALENDAR
</pre>

=== Fantastical ===

* Platform: Mac and iOS
* supports importing ICS files and subscribing using webcal (tested using Facebok URL)
* Implemented using libical

== notes ==
* the "webcal:" URL protocol scheme is non-standard.

== contributors==
* Tantek Çelik
* [[DimitriGlazkov|Dimitri Glazkov]]
* [[User:TomMorris|Tom Morris]]

== related pages ==
{{hcalendar-related-pages}}

icalendar-implementations

2025-01-30T11:55:14Z

D: /* libraries */ Add py-vobject

<h1> iCalendar implementations </h1>
{{TOC-right}}
This is a list of calendar programs, applications and services that support the iCalendar {{RFC2445}} standard.

In addition, please note any quirks or bugs with implementations' handling of iCalendar - we've already discovered some in the development of [[hcalendar|hCalendar]] and proxies like X2V.

== libraries ==

=== libical ===
Open source C-based implementation of iCalendar.

* [https://github.com/libical/libical Github]

=== vobject ===
Apache 2.0-licensed Python iCalendar parser/generator library package

* [https://github.com/py-vobject/vobject GitHub]
* [https://pypi.org/project/vobject/ PyPI]

== Python iCalendar ==
Python implementation of iCalendar.

* [https://pypi.python.org/pypi/icalendar/ PyPI]

== services ==
=== Google Calendar ===
http://calendar.google.com/
* supports subscribing to "webcal:" and "http:" URLs to iCalendar

== products ==
=== Apple Calendar.app ===
Apple Calendar.app, formerly known as iCal.
* platform: OSX
* handles "webcal:" URLs and supports subscribing to events.

==== Apple iCal 2.0.5 ====
Apple iCal.app 2.0.5 build 1069 (AppleiCal205)

===== iCal 2.0.5 notes =====
* '''Requires dates and date-times without separators.''' Apple iCal 2.0.5 (and probably other versions) appears to require dates without "-" and times without ":" which appears to be consistent with the iCalendar spec due to:
** iCalendar section 4.3.4 Date - "date-value = date-fullyear date-month date-mday" (no separators)
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators)

As a result Apple iCal 2.0.5 ignores date and date-time properties (e.g. DTSTART, DTEND, etc.) when date components (year, month, day) are separated by "-" or when time components (hours, minutes, seconds) are separated by ":" (both as allowed by [[ISO8601]] and required by [[RFC3339]]).

However per [[accessibility]] research, dates and times with separators are more readable and accessible, and consequently explicitly allowed by hCalendar.

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date and date-time properties (e.g. DTSTART, DTEND, etc.) with separators, and remove separators when converting to iCalendar.

* '''Requires date-times with seconds explicitly specified.''' Apple iCal 2.0.5 (and probably other versions) appears to require date-times with the seconds explicitly specified, which appears to be consistent with the iCalendar spec:
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators)

However in practice (see [[hcalendar-examples-in-wild]]) hCalendar date-time properties often omit the seconds because when they are "00" for simplicity and easier/quicker readability.

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date-time properties (e.g. DTSTART, DTEND, etc.) without the seconds explicitly specified, and imply "00" seconds when converting to iCalendar.

* '''Requires floating or UTC date-times.''' Apple iCal 2.0.5 (and probably other versions) appears to require date-times which are either floating (no time zone) or explicitly specified to be UTC and ignores date-times which use timezone offsets, which appears to be consistent with the iCalendar spec:
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators) and: <blockquote><p>The form of time with UTC offset MUST NOT be used. For example, the following is NOT VALID for a time value:</p><pre>230000-0800 ;Invalid time format</pre></blockquote>

However, in practice (see [[hcalendar-examples-in-wild]]) hCalendar date-time properties often state the timezone offset in order to make the human visible time consistent with the machine readable time for easier verification (minimize DRY divergence probability).

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date-time properties (e.g. DTSTART, DTEND, etc.) with an explicit timezone offset, and convert the specified date-time value to a UTC value when converting to iCalendar.

All hCalendar processor requirements above should be documented thoroughly in [[hcalendar-parsing]].

==== Apple Calendar.app 8.0 (2092.3) ====

Timezone handling: Calendar.app is incompatible with timezone-aware dates produced by the Python iCalendar implementation which puts quotation marks around TZIDs. See [https://gist.github.com/tommorris/0aca78d680804c04bf1e35318893a34a this gist] for details.

=== KOrganizer ===
* platforms: All Linux, *BSD, etc. (Wherever KDE runs)
* supports the "webcal:" protocol, as well as "http:", "ftp:", "fish:", etc.

=== Evolution ===
* platform: Fedora Core 3
* supports "webcal:" protocol

=== Sunbird ===
[http://www.mozilla.org/projects/calendar/sunbird.html Mozilla Sunbird]
* platforms: Windows XP, others?
* supports "webcal:" protocol

=== Microsoft Outlook ===
==== Microsoft Outlook 2007 ====
Microsoft Outlook 2007 (MSOutlook2k7)
* platforms: Windows
* supports importing and subscribing to .ics files, "webcal:" URLs, etc.

==== Microsoft Outlook 2003 ====
Microsoft Outlook 2003 (MSOutlook2k3)
* platforms: Windows
* supports importing .ics files

===== MSOutlook2k3 general comments =====
For importing, MSOutlook2k3 apparently requires VEVENTS to have <code>UID</code>, <code>DTSTAMP</code>, and <code>METHOD</code> properties. ('''citation/platform/date tested info needed'''). If any of the three is not present, returns this message:

<pre>
This error can appear if you have attempted to save a recurring Lunar appointment in iCalendar format.
To avoid this error, set the appointment option to Gregorian instead of Lunar.
</pre>

After some testing, this seems to be the generic message to indicate a problem with event import.

No such restriction is placed on [[rfc-2445#vCalendar|vCalendar 1.0]] events. So, if <code>VERSION:1.0</code> is output instead of <code>VERSION:2.0</code>, the only required field is <code>DTSTART</code>.
Note that <code>VERSION</code> property may be omitted. In this case, value inferred as <code>1.0</code>.

* UID and DTSTAMP is required for Outlook to import. [[User:GeoffWebb|GeoffWebb]] 14:03, 9 Dec 2005 (PST)

===== Potential Security Related Issue w/ Outlook 2003 and Standard Account =====

I've been all over the web tracing the "Lunar" exception.
I believe I'm come across another lunar permutation.
I have an XP box running Outlook 2003 SP3 with Admin privileges, and I have an XP box running Outlook 2003 SP3 (same build number) running under a standard account.
The .ics will try to import correctly under the Admin account (aka, it will prompt you for acceptance, everything working as expected). HOWEVER, the same .ics file will throw the "lunar" exception on the ~standard~ account.

Here is my environment information just in case you're bumping your head on this issue.

Outlook 2003 with SP3 Build Number : 11.8325.8329

.ics file contents (aka, "known to work" file contents under the Admin account)

<pre>BEGIN:VCALENDAR
VERSION:2.0
PRODID:www.testMeiCalendar.net
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20101231T230000
DTEND:20110101T010000
SUMMARY:New Years Eve Reminder
LOCATION:Downtown
DESCRIPTION:Let's get together for New Years Eve
UID:ABCD1234
SEQUENCE:0
DTSTAMP:20101125T112600
END:VEVENT
END:VCALENDAR
</pre>

To be honest, I probably will just abandon trying to use it for this project because of this issue.
But I wanted to report it, so someone doesn't waste a day thinking the issue is the contents of the .ics file.

===== MSOutlook2k3 sample importable iCalendar =====
<pre>
BEGIN:VCALENDAR
VERSION:2.0
METHOD:PUBLISH
BEGIN:VEVENT
UID:0
DTSTAMP:20060601T080000
DTSTART:20060601T080000
END:VEVENT
END:VCALENDAR
</pre>

===== MSOutlook2k3 sample importable vCalendar =====
<pre>
BEGIN:VCALENDAR
BEGIN:VEVENT
DTSTART:20060601T080000
END:VEVENT
END:VCALENDAR
</pre>

=== Fantastical ===

* Platform: Mac and iOS
* supports importing ICS files and subscribing using webcal (tested using Facebok URL)
* Implemented using libical

== notes ==
* the "webcal:" URL protocol scheme is non-standard.

== contributors==
* Tantek Çelik
* [[DimitriGlazkov|Dimitri Glazkov]]
* [[User:TomMorris|Tom Morris]]

== related pages ==
{{hcalendar-related-pages}}