<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://microformats.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Beat-boxing</id>
	<title>Microformats Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://microformats.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Beat-boxing"/>
	<link rel="alternate" type="text/html" href="https://microformats.org/wiki/Special:Contributions/Beat-boxing"/>
	<updated>2026-05-11T01:48:45Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.38.4</generator>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcalendar-faq&amp;diff=21386</id>
		<title>hcalendar-faq</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcalendar-faq&amp;diff=21386"/>
		<updated>2007-07-14T04:33:42Z</updated>

		<summary type="html">&lt;p&gt;Beat-boxing: /* Q&amp;amp;A */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt; hCalendar FAQ &amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page is for documenting Q&amp;amp;A about [[hcalendar|hCalendar]].  If you have a new question to ask, Please consider first asking your question on the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss] list. New questions and answers should be added to the end of the list.  If you have a new question but not an answer, please add it to [[hcalendar-issues|hCalendar issues]].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;Editing this Page&amp;lt;/h2&amp;gt;&lt;br /&gt;
Please do not use &amp;quot;?&amp;quot; or other punctuation in the headers - it helps to keep the URLs to their fragment identifiers shorter and easier to read, copy/paste etc.  See [[how-to-play]] for more wiki editing guidelines.&lt;br /&gt;
&lt;br /&gt;
== Q&amp;amp;A ==&lt;br /&gt;
&lt;br /&gt;
# ''How do I use a class inside &amp;lt;span class=&amp;quot;vcalendar&amp;quot;&amp;gt; when I don't want the element I use it on to be a property of the calendar?''&lt;br /&gt;
#*Use a class name that isn't a defined iCalendar property name.&lt;br /&gt;
# ''What happens if the class is used both inside and outside &amp;lt;span class=&amp;quot;vcalendar&amp;quot;&amp;gt;?''&lt;br /&gt;
#* That works fine.&lt;br /&gt;
# ''What do I do if I want to add styling to a group of calendar events, especially if the calendar contains dynamic content? ''&lt;br /&gt;
#* You can write style rules that incorporate both the context of said group (say it is in an ordered list with class name &amp;quot;group&amp;quot; for example) and the events, e.g.:&amp;lt;code&amp;gt;ol.group .vevent { /* insert common styling here */ } &amp;lt;/code&amp;gt;&lt;br /&gt;
# ''What do you do if you don't want the calendar or card to be displayed?''&lt;br /&gt;
#* If you don't want the calendar or card to be displayed, why are you publishing it on the Web?&lt;br /&gt;
# ''What if you don't want specific properties to show up?''&lt;br /&gt;
#* You can trivially use CSS to hide (or otherwise alter the display) of certain properties.  E.g. if you want to hide the &amp;quot;location&amp;quot; from all your VEVENTs you would write a rule like this: &amp;lt;code&amp;gt; .vevent .location { display:none } &amp;lt;/code&amp;gt;. This won't, however, keep the properties from being read in the HTML source; or seen by people who don't have CSS enabled; or discovered by search engines or other robots.&lt;br /&gt;
# ''If we use &amp;amp;lt;abbr&amp;amp;gt; title for the ISODate, how do we specify a different tooltip?''&lt;br /&gt;
#* For reasons of metadata transparency and visibility, it is recommended that you DO NOT specify a different tooltip.  However, if in your particular content or application you must, you can do so with a nested span e.g. &amp;lt;code&amp;gt; &amp;lt;abbr title=&amp;quot;20050221&amp;quot;&amp;gt;&amp;lt;span title=&amp;quot;tooltip text&amp;quot;&amp;gt;Feb. 21st&amp;lt;/span&amp;gt;&amp;lt;/abbr&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
# ''Would the use of &amp;amp;lt;acronym&amp;amp;gt; for DTSTART be just as good as &amp;amp;lt;abbr&amp;amp;gt;?''&lt;br /&gt;
#* It could be, but there is no need.  The &amp;amp;lt;abbr&amp;amp;gt;  element is also preferred as it is better defined.  The &amp;amp;lt;acronym&amp;amp;gt; element, and in particular, the term &amp;quot;acronym&amp;quot; means different things to different people, and thus we are not using it in [[hcalendar|hCalendar]].&lt;br /&gt;
# ''What happens if a browser doesn't support &amp;amp;lt;abbr&amp;amp;gt;?''&lt;br /&gt;
#* Then the human readable contents inside the element are displayed, which is the desirable behavior.&lt;br /&gt;
# ''How is [[hcalendar|hCalendar]] different from xCalendar, i.e. iCalendar XML guidelines submitted as an [http://www.ietf.org/ID.html IETF Internet-Draft]?''&lt;br /&gt;
#* hCalendar and xCalendar are actually very similar in that they are both based on iCalendar standard, RFC2445. However, xCalendar is a way of representing iCalendar files using non-standard XML element names and attributes.  This is inadequate and unwieldly for serving on web pages. xCalendar is still a separate, encapsulated document in the context of the web, that requires yet another namespace. Nobody would ever look at an xCalendar XML file in the context of their ordinary browsing, unless it's XSLTed into something else, e.g. hCalendar. On the other hand, [[hcalendar|hCalendar]] is easily embeddable into normal XHTML web pages, easily stylable with CSS, cleanly separates human presentable date information vs. machine parsable ISO-8601 dates, etc. With hCalendar, calendar and events content appears both to the human user *and* to hCalendar-aware machine implementations, parsers, indexers, etc., on *today's* web.&lt;br /&gt;
# ''Can you provide more precise location data for an hCalendar event such as latitude and longitude?''&lt;br /&gt;
#* Yes, it is possible, by overlaying an [[hcard|hCard]] with the location markup (see [[hcalendar-brainstorming#hCard_locations|the brainstorming on hCard locations]]), e.g. using your lat long example (taking the values as given, someone feel free to fix these to be the real values). The code example(s) are presumed to be inside an element with a class name of &amp;quot;vevent&amp;quot;.  See the [[hcalendar-location-hcard-example]] page for details.  For more discussions of location data, geographic data, and research into current and potential future formats, see the [[location-formats|location formats]] page.&lt;br /&gt;
# ''When transforming an hCalendar to a .ics file, do I have to convert the time to UTC?''&lt;br /&gt;
#* Yes. The iCalendar format does not permit the time to be published with an offset. hCalendars can be published with offsets, because this promotes accuracy, as it can more easily be verified (timezone math is hard), but tools which transform hCalendar to iCalendar must transformat times to UTC.&lt;br /&gt;
# ''How are recurring events represented?''&lt;br /&gt;
#* If you take a look at [http://microformats.org/wiki/hcalendar-examples#Example_3 Example 3], there is a proposed means using an &amp;lt;em&amp;gt;RRULE&amp;lt;/em&amp;gt; property along with a &amp;lt;em&amp;gt;freq&amp;lt;/em&amp;gt; sub-property. It's a start - more brainstorming at [http://microformats.org/wiki/hcalendar-brainstorming#Recurring_Events hcalendar-brainstorming].&lt;br /&gt;
# ''How does one markup just the year as opposed to an entire date? e.g. to represent age, or discussing &amp;quot;the past year&amp;quot; ?&lt;br /&gt;
#* Depends on the context.  If by &amp;quot;the past year&amp;quot;, you mean the past *calendar* year, then mark it up as January 1st through December 31st.  If you mean the past 365 days, then mark it up according to whatever date it is relative to.  Etc.&lt;br /&gt;
# ''Are there any programs of services that convert from iCalendar to hCalender?''&lt;br /&gt;
#*At the moment there are no plans to create a program. There are several issues when converting, mainly HOW the information is represented in HTML. Since you can use just about any element which could the converter choose. This is not to say a converter shouldn't be built, but it is out of the scope of microformats.&lt;br /&gt;
# ''Is the list of possible types for an ADR and TEL case sensitive?''&lt;br /&gt;
#* No, enumerated values are case-INsensitive, therefore Home, home, HOME, etc are all equivalent&lt;br /&gt;
# ''Why won't Outlook import my ics file''&lt;br /&gt;
#* Outlook is picky about some properties. With outlook, UID, DTSTAMP and METHOD are mandatory. Be sure you have marked-up your hCalendar with a class=&amp;quot;uid&amp;quot; and a class=&amp;quot;dtstamp&amp;quot; in a class=&amp;quot;vevent&amp;quot;&lt;br /&gt;
# ''Can I use YYYY-MM-DDThh:mm:ss dates or do I have to use the YYYYMMDDThhmmss format?''&lt;br /&gt;
#* hCalendar specifies [http://en.wikipedia.org/wiki/ISO8601 ISO8601 datetime format], and both examples are valid, you can use with or without hyphens/colons/spaces. Note, however, that both the [http://www.w3.org/TR/NOTE-datetime w3C note] and RFC 3339 recommend the use of the former, extended (delimited) format.&lt;br /&gt;
# ''Do I have to specify detailed time and timezone information?''&lt;br /&gt;
#* Include as much information as necessary, minimally include YYYY-MM-DD&lt;br /&gt;
# ''Why do I have to use a 'T' between the date and time in ISO Dates?''&lt;br /&gt;
#* You can NOT use a white-space character, the 'T' is mandatory to separate the date from the time.&lt;br /&gt;
# ''Why are the root class names &amp;quot;vcalendar&amp;quot; and &amp;quot;vevent&amp;quot; and not &amp;quot;hcalendar&amp;quot;?''&lt;br /&gt;
#* [[hcalendar|hCalendar]] is based on the iCalendar spec (RFC 2445), which itself is based on vCalendar.  The names of objects have remained consistent throughout and are based on the original names from vCalendar.&lt;br /&gt;
# ''How do I mark-up a date-time with the proper timezone?''&lt;br /&gt;
#* There are two ways to do this. First, you can add your timezone offset to the end of your date-time like this: 2006-01-01T12:00:00-0600.  [[http://aa.usno.navy.mil/faq/docs/world_tzones.html See a world timezone offset map here]]. Also, be sure to adjust offset to account for [[http://en.wikipedia.org/wiki/Daylight_saving_time Daylight Saving Time]] for events within applicable dates and locations. The other option is to convert your date-time with a timezone into a UTC date-time. iCalendar requires that times be in UTC, but hCalendar also allows for encoding your date-times as proper ISO date-times with timezone offsets.&lt;br /&gt;
# ''Why does my event end a day earlier than I want?''&lt;br /&gt;
#* DTEND is not inclusive. If you want an event to end on January 2nd, then you will need to set DTEND to 2006-01-03, one day later. This is because the event will END the first second of the date provided, so if you specify 2006-01-02, then that says that the end of the event is at midnight between the 1st and 2nd.&lt;br /&gt;
# ''How do I represent a repeating event in hCalendar?''&lt;br /&gt;
#* See [[hcalendar-brainstorming#Recurring_Events|hCalendar brainstorming: Recurring Events]]&lt;br /&gt;
# ''What is the best way to represent a full address in the Location?''&lt;br /&gt;
#* See [[hcalendar-brainstorming#hCard_locations|hCalendar brainstorming: hCard locations]]&lt;br /&gt;
# ''How do you represent the language of a LOCATION?'' - AKA the language parameter.&lt;br /&gt;
#* Use the (X)HTML &amp;quot;lang&amp;quot; attribute.  See for example [[hcard-authoring#Set_the_lang_when_different|the explanation in hCard authoring of how to use &amp;quot;lang&amp;quot;]].&lt;br /&gt;
# ''Is it possible to represent groups of events?'' - e.g workshops at a conference.&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
{{hcalendar-related-pages}}&lt;/div&gt;</summary>
		<author><name>Beat-boxing</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcalendar-faq&amp;diff=18361</id>
		<title>hcalendar-faq</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcalendar-faq&amp;diff=18361"/>
		<updated>2007-07-14T04:33:09Z</updated>

		<summary type="html">&lt;p&gt;Beat-boxing: /* Q&amp;amp;A */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt; hCalendar FAQ &amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page is for documenting Q&amp;amp;A about [[hcalendar|hCalendar]].  If you have a new question to ask, Please consider first asking your question on the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss] list. New questions and answers should be added to the end of the list.  If you have a new question but not an answer, please add it to [[hcalendar-issues|hCalendar issues]].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;Editing this Page&amp;lt;/h2&amp;gt;&lt;br /&gt;
Please do not use &amp;quot;?&amp;quot; or other punctuation in the headers - it helps to keep the URLs to their fragment identifiers shorter and easier to read, copy/paste etc.  See [[how-to-play]] for more wiki editing guidelines.&lt;br /&gt;
&lt;br /&gt;
== Q&amp;amp;A ==&lt;br /&gt;
&lt;br /&gt;
# ''How do I use a class inside &amp;lt;span class=&amp;quot;vcalendar&amp;quot;&amp;gt; when I don't want the element I use it on to be a property of the calendar?''&lt;br /&gt;
#*Use a class name that isn't a defined iCalendar property name.&lt;br /&gt;
# ''What happens if the class is used both inside and outside &amp;lt;span class=&amp;quot;vcalendar&amp;quot;&amp;gt;?''&lt;br /&gt;
#* That works fine.&lt;br /&gt;
# ''What do I do if I want to add styling to a group of calendar events, especially if the calendar contains dynamic content? ''&lt;br /&gt;
#* You can write style rules that incorporate both the context of said group (say it is in an ordered list with class name &amp;quot;group&amp;quot; for example) and the events, e.g.:&amp;lt;code&amp;gt;ol.group .vevent { /* insert common styling here */ } &amp;lt;/code&amp;gt;&lt;br /&gt;
# ''What do you do if you don't want the calendar or card to be displayed?''&lt;br /&gt;
#* If you don't want the calendar or card to be displayed, why are you publishing it on the Web?&lt;br /&gt;
# ''What if you don't want specific properties to show up?''&lt;br /&gt;
#* You can trivially use CSS to hide (or otherwise alter the display) of certain properties.  E.g. if you want to hide the &amp;quot;location&amp;quot; from all your VEVENTs you would write a rule like this: &amp;lt;code&amp;gt; .vevent .location { display:none } &amp;lt;/code&amp;gt;. This won't, however, keep the properties from being read in the HTML source; or seen by people who don't have CSS enabled; or discovered by search engines or other robots.&lt;br /&gt;
# ''If we use &amp;amp;lt;abbr&amp;amp;gt; title for the ISODate, how do we specify a different tooltip?''&lt;br /&gt;
#* For reasons of metadata transparency and visibility, it is recommended that you DO NOT specify a different tooltip.  However, if in your particular content or application you must, you can do so with a nested span e.g. &amp;lt;code&amp;gt; &amp;lt;abbr title=&amp;quot;20050221&amp;quot;&amp;gt;&amp;lt;span title=&amp;quot;tooltip text&amp;quot;&amp;gt;Feb. 21st&amp;lt;/span&amp;gt;&amp;lt;/abbr&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
# ''Would the use of &amp;amp;lt;acronym&amp;amp;gt; for DTSTART be just as good as &amp;amp;lt;abbr&amp;amp;gt;?''&lt;br /&gt;
#* It could be, but there is no need.  The &amp;amp;lt;abbr&amp;amp;gt;  element is also preferred as it is better defined.  The &amp;amp;lt;acronym&amp;amp;gt; element, and in particular, the term &amp;quot;acronym&amp;quot; means different things to different people, and thus we are not using it in [[hcalendar|hCalendar]].&lt;br /&gt;
# ''What happens if a browser doesn't support &amp;amp;lt;abbr&amp;amp;gt;?''&lt;br /&gt;
#* Then the human readable contents inside the element are displayed, which is the desirable behavior.&lt;br /&gt;
# ''How is [[hcalendar|hCalendar]] different from xCalendar, i.e. iCalendar XML guidelines submitted as an [http://www.ietf.org/ID.html IETF Internet-Draft]?''&lt;br /&gt;
#* hCalendar and xCalendar are actually very similar in that they are both based on iCalendar standard, RFC2445. However, xCalendar is a way of representing iCalendar files using non-standard XML element names and attributes.  This is inadequate and unwieldly for serving on web pages. xCalendar is still a separate, encapsulated document in the context of the web, that requires yet another namespace. Nobody would ever look at an xCalendar XML file in the context of their ordinary browsing, unless it's XSLTed into something else, e.g. hCalendar. On the other hand, [[hcalendar|hCalendar]] is easily embeddable into normal XHTML web pages, easily stylable with CSS, cleanly separates human presentable date information vs. machine parsable ISO-8601 dates, etc. With hCalendar, calendar and events content appears both to the human user *and* to hCalendar-aware machine implementations, parsers, indexers, etc., on *today's* web.&lt;br /&gt;
# ''Can you provide more precise location data for an hCalendar event such as latitude and longitude?''&lt;br /&gt;
#* Yes, it is possible, by overlaying an [[hcard|hCard]] with the location markup (see [[hcalendar-brainstorming#hCard_locations|the brainstorming on hCard locations]]), e.g. using your lat long example (taking the values as given, someone feel free to fix these to be the real values). The code example(s) are presumed to be inside an element with a class name of &amp;quot;vevent&amp;quot;.  See the [[hcalendar-location-hcard-example]] page for details.  For more discussions of location data, geographic data, and research into current and potential future formats, see the [[location-formats|location formats]] page.&lt;br /&gt;
# ''When transforming an hCalendar to a .ics file, do I have to convert the time to UTC?''&lt;br /&gt;
#* Yes. The iCalendar format does not permit the time to be published with an offset. hCalendars can be published with offsets, because this promotes accuracy, as it can more easily be verified (timezone math is hard), but tools which transform hCalendar to iCalendar must transformat times to UTC.&lt;br /&gt;
# ''How are recurring events represented?''&lt;br /&gt;
#* If you take a look at [http://microformats.org/wiki/hcalendar-examples#Example_3 Example 3], there is a proposed means using an &amp;lt;em&amp;gt;RRULE&amp;lt;/em&amp;gt; property along with a &amp;lt;em&amp;gt;freq&amp;lt;/em&amp;gt; sub-property. It's a start - more brainstorming at [http://microformats.org/wiki/hcalendar-brainstorming#Recurring_Events hcalendar-brainstorming].&lt;br /&gt;
# ''How does one markup just the year as opposed to an entire date? e.g. to represent age, or discussing &amp;quot;the past year&amp;quot; ?&lt;br /&gt;
#* Depends on the context.  If by &amp;quot;the past year&amp;quot;, you mean the past *calendar* year, then mark it up as January 1st through December 31st.  If you mean the past 365 days, then mark it up according to whatever date it is relative to.  Etc.&lt;br /&gt;
# ''Are there any programs of services that convert from iCalendar to hCalender?''&lt;br /&gt;
#*At the moment there are no plans to create a program. There are several issues when converting, mainly HOW the information is represented in HTML. Since you can use just about any element which could the converter choose. This is not to say a converter shouldn't be built, but it is out of the scope of microformats.&lt;br /&gt;
# ''Is the list of possible types for an ADR and TEL case sensitive?''&lt;br /&gt;
#* No, enumerated values are case-INsensitive, therefore Home, home, HOME, etc are all equivalent&lt;br /&gt;
# ''Why won't Outlook import my ics file''&lt;br /&gt;
#* Outlook is picky about some properties. With outlook, UID, DTSTAMP and METHOD are mandatory. Be sure you have marked-up your hCalendar with a class=&amp;quot;uid&amp;quot; and a class=&amp;quot;dtstamp&amp;quot; in a class=&amp;quot;vevent&amp;quot;&lt;br /&gt;
# ''Can I use YYYY-MM-DDThh:mm:ss dates or do I have to use the YYYYMMDDThhmmss format?''&lt;br /&gt;
#* hCalendar specifies [http://en.wikipedia.org/wiki/ISO8601 ISO8601 datetime format], and both examples are valid, you can use with or without hyphens/colons/spaces. Note, however, that both the [http://www.w3.org/TR/NOTE-datetime w3C note] and RFC 3339 recommend the use of the former, extended (delimited) format.&lt;br /&gt;
# ''Do I have to specify detailed time and timezone information?''&lt;br /&gt;
#* Include as much information as necessary, minimally include YYYY-MM-DD&lt;br /&gt;
# ''Why do I have to use a 'T' between the date and time in ISO Dates?''&lt;br /&gt;
#* You can NOT use a white-space character, the 'T' is mandatory to separate the date from the time.&lt;br /&gt;
# ''Why are the root class names &amp;quot;vcalendar&amp;quot; and &amp;quot;vevent&amp;quot; and not &amp;quot;hcalendar&amp;quot;?''&lt;br /&gt;
#* [[hcalendar|hCalendar]] is based on the iCalendar spec (RFC 2445), which itself is based on vCalendar.  The names of objects have remained consistent throughout and are based on the original names from vCalendar.&lt;br /&gt;
# ''How do I mark-up a date-time with the proper timezone?''&lt;br /&gt;
#* There are two ways to do this. First, you can add your timezone offset to the end of your date-time like this: 2006-01-01T12:00:00-0600.  [[http://aa.usno.navy.mil/faq/docs/world_tzones.html See a world timezone offset map here]]. Also, be sure to adjust offset to account for [[http://en.wikipedia.org/wiki/Daylight_saving_time Daylight Saving Time]] for events within applicable dates and locations. The other option is to convert your date-time with a timezone into a UTC date-time. iCalendar requires that times be in UTC, but hCalendar also allows for encoding your date-times as proper ISO date-times with timezone offsets.&lt;br /&gt;
# ''Why does my event end a day earlier than I want?''&lt;br /&gt;
#* DTEND is not inclusive. If you want an event to end on January 2nd, then you will need to set DTEND to 2006-01-03, one day later. This is because the event will END the first second of the date provided, so if you specify 2006-01-02, then that says that the end of the event is at midnight between the 1st and 2nd.&lt;br /&gt;
# ''How do I represent a repeating event in hCalendar?''&lt;br /&gt;
#* See [[hcalendar-brainstorming#Recurring_Events|hCalendar brainstorming: Recurring Events]]&lt;br /&gt;
# ''What is the best way to represent a full address in the Location?''&lt;br /&gt;
#* See [[hcalendar-brainstorming#hCard_locations|hCalendar brainstorming: hCard locations]]&lt;br /&gt;
# ''How do you represent the language of a LOCATION?'' - AKA the language parameter.&lt;br /&gt;
#* Use the (X)HTML &amp;quot;lang&amp;quot; attribute.  See for example [[hcard-authoring#Set_the_lang_when_different|the explanation in hCard authoring of how to use &amp;quot;lang&amp;quot;]].&lt;br /&gt;
# ''Is it possible to represent groups of events?'' - e.g workshops at a conference&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
{{hcalendar-related-pages}}&lt;/div&gt;</summary>
		<author><name>Beat-boxing</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcalendar-implementations&amp;diff=18198</id>
		<title>hcalendar-implementations</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcalendar-implementations&amp;diff=18198"/>
		<updated>2007-07-05T10:39:23Z</updated>

		<summary type="html">&lt;p&gt;Beat-boxing: /* Browsing */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt;hCalendar Implementations&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==New Implementations==&lt;br /&gt;
Add new implementations here:&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
==Authoring==&lt;br /&gt;
Implementations you can use to author, create, and publish hCalendar events.&lt;br /&gt;
&lt;br /&gt;
===Web-based Creators===&lt;br /&gt;
;hCalendar Creator : [http://microformats.org/code/hcalendar/creator hCalendar creator] ([[hcalendar-creator-feedback|hCalendar creator feedback]]) - create your own hCalendar events.&lt;br /&gt;
;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.&lt;br /&gt;
&lt;br /&gt;
===Blogging and CMS tools===&lt;br /&gt;
;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] &lt;br /&gt;
&lt;br /&gt;
;Drupal module : [http://hybernaut.com/upcoming-hcal Drupal Upcoming.org syndication module emits hCalendar]&lt;br /&gt;
;MovableType and WordPress plug-ins : [http://structuredblogging.org/formats.php StructuredBlogging] is a set of plugins  [http://structuredblogging.org/structuredblogging-wp-latest.zip for  WordPress] and [http://structuredblogging.org/structuredblogging-wp-latest.zip for MovableType] that supports embedding hCalendar and other microformats in templates and blog posts.&lt;br /&gt;
;Textpattern plug-in : [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].&lt;br /&gt;
;Textpattern plug-in : [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].&lt;br /&gt;
&lt;br /&gt;
===Browser scripts and plug-ins===&lt;br /&gt;
Browser plugins that work with existing authoring tools:&lt;br /&gt;
; 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]).&lt;br /&gt;
; 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.&lt;br /&gt;
; 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.&lt;br /&gt;
&lt;br /&gt;
===Desktop Authoring Tools===&lt;br /&gt;
;Dreamweaver Extension : [http://www.webstandards.org/action/dwtf/microformats/ Extension suite] for Dreamweaver 8 from the [http://webstandards.org/ Web Standards Project].&lt;br /&gt;
;xfy : &lt;br /&gt;
In [https://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations.&lt;br /&gt;
&lt;br /&gt;
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=15&amp;amp;lid=25 hCalendar via RSS] parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.&lt;br /&gt;
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=19&amp;amp;lid=23 hCalendar Marker XVCD] helps to mark up an event information in XHTML document with hCalendar. &lt;br /&gt;
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=15&amp;amp;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.&lt;br /&gt;
&lt;br /&gt;
==Search and Discovery==&lt;br /&gt;
&lt;br /&gt;
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek]. &lt;br /&gt;
* [http://leftlogic.com/info/articles/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].&lt;br /&gt;
&lt;br /&gt;
==Conversion and Import==&lt;br /&gt;
Implementations you can use to importing into a Calendar Application, typically by converting hCalendar to iCalendar/vCalendar.&lt;br /&gt;
&lt;br /&gt;
===Web Services===&lt;br /&gt;
These return iCalendar (.ics) and other calendar formats for easy importing into typical calendar programs or other processing.&lt;br /&gt;
* [http://feeds.technorati.com/events Technorati Events Feed service] uses X2V library to parse hCalendar and return iCalendar (.ics).&lt;br /&gt;
**Note friendly URL, e.g. http://feeds.technorati.com/events/http%3A//microformats.org&lt;br /&gt;
* [http://suda.co.uk/projects/X2V/ X2V] parses hCalendar and produces a .ics (iCalendar) stream.&lt;br /&gt;
**Note: needs to be updated to track changes in the specification as they occur.&lt;br /&gt;
&amp;lt;!-- * [http://lifelint.net/ Life Lint Parser] parses hCalendar and produces .ics, .rdf and debugging information and attempts to be more fully compliant to the iCal standard than previous implementations.  It can be used in the same manner as X2V.  Can output iCal (w optional Outlook 2002 compat), and RDF. OFFLINE SINCE DECEMBER 2006 --&amp;gt;&lt;br /&gt;
* [http://spanningsalesforce.com/ Spanning Salesforce] produces hCalendar-enabled RSS feeds and .ics calendars from Salesforce.com.&lt;br /&gt;
* [http://makedatamakesense.com/myspace/event/ MySpace Events RSS Creator] creates RSS feeds of MySpace events with hCalendar markup.&lt;br /&gt;
&lt;br /&gt;
===Firefox Greasemonkey Plugins===&lt;br /&gt;
* [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)].&lt;br /&gt;
* [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.''&lt;br /&gt;
&lt;br /&gt;
===Aggregators===&lt;br /&gt;
* [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]]&lt;br /&gt;
* [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.&lt;br /&gt;
&lt;br /&gt;
==Browsing==&lt;br /&gt;
Implementations that detect, display and otherwise highlight hCalendar events in pages.&lt;br /&gt;
&lt;br /&gt;
* In [http://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations. &amp;quot;hCalendar via RSS&amp;quot; parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.&lt;br /&gt;
* [http://code.google.com/p/js-hcalendar js-hcalendar] parses hCalendar and produces a displayable HTML table/CSS-based calendar (formerly called JSCalendar).&lt;br /&gt;
&lt;br /&gt;
===Firefox extension===&lt;br /&gt;
*[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.&lt;br /&gt;
*[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 &amp;quot;Add hCalender to Yahoo! Calendar&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
====Pending====&lt;br /&gt;
*[http://reminderfox.mozdev.org/ ReminderFox] have hCalendar import on their &amp;quot;to do &amp;quot; list. &lt;br /&gt;
&lt;br /&gt;
===Flock extension===&lt;br /&gt;
*[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&lt;br /&gt;
&lt;br /&gt;
==Libraries==&lt;br /&gt;
Open source libraries of hCalendar parsers and other related code for building hCalendar implementations.&lt;br /&gt;
; Javascript : [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats simple hCalendar parser] by [http://virtuelvis.com/ Arve Bersvendsen]&lt;br /&gt;
; PHP : &lt;br /&gt;
*[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).&lt;br /&gt;
*[http://enarion.net/phpmicroformats/ phpMicroformats] is a PHP class library that generates microformats for calendar events (hCalendar) and vcards (hCard).&lt;br /&gt;
* [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.&lt;br /&gt;
; Ruby [http://rubyforge.org/projects/uformats/ uformats]: is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]&lt;br /&gt;
; XSLT :&lt;br /&gt;
* X2V is available as an XSLT library&lt;br /&gt;
* [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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
{{hcalendar-related-pages}}&lt;/div&gt;</summary>
		<author><name>Beat-boxing</name></author>
	</entry>
</feed>