hcalendar-example1-steps - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:24:19Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:24, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~ hCalendar Example 1 Steps ~~</entry-title>~~		{{DISPLAYTITLE: hCalendar Example 1 Steps }}
	http://www.boogdesign.com/images/buttons/microformat_hcalendar.png		http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

Tantek: typos

2011-12-18T02:56:07Z

typos

← Older revision		Revision as of 02:56, 18 December 2011
Line 1:		Line 1:
	<entry-title> hCalendar Example 1 Steps <entry-title>		<entry-title> hCalendar Example 1 Steps </entry-title>
	http://www.boogdesign.com/images/buttons/microformat_hcalendar.png		http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

Line 26:		Line 26:
	<a class="url" href="http://conferences.oreillynet.com/pub/w/40/program.html/">		<a class="url" href="http://conferences.oreillynet.com/pub/w/40/program.html/">
	<span class="summary">Web 2.0 Conference</span></a>:		<span class="summary">Web 2.0 Conference</span></a>:
	<span class="dtstart">2005-10-05</span>-		<span class="dtstart">2005-10-05</span>-
	<span class="dtend">2005-10-07</span>,		<span class="dtend">2005-10-07</span>,
	at the <span class="location">Argent Hotel, San Francisco, CA</span>		at the <span class="location">Argent Hotel, San Francisco, CA</span>
	</div>		</div>
	</source>		</source>

Tantek: entry-toc, incorporate dtend-issue resolution per note, source markup, revert back to original 2005 Web 2.0 example

2011-12-18T02:54:42Z

entry-toc, incorporate dtend-issue resolution per note, source markup, revert back to original 2005 Web 2.0 example

← Older revision		Revision as of 02:54, 18 December 2011
Line 1:		Line 1:
	= hCalendar Example 1 Steps =		<entry-title> hCalendar Example 1 Steps <entry-title>
	http://www.boogdesign.com/images/buttons/microformat_hcalendar.png		http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

	This is a step by step explanation of the first example in the [[hcalendar\|hCalendar]] specification.		This is a step by step explanation of the first example in the [[hcalendar\|hCalendar]] specification.

	~~'''Note: this example derivation needs to be updated to incorporate the [[dtend-issue]] resolution.'''~~

	== Example ==		== Example ==
	Here is a sample event in an iCalendar:		Here is a sample event in an iCalendar:
	<~~pre><nowiki~~>		<source lang=text>
	BEGIN:VCALENDAR		BEGIN:VCALENDAR
	PRODID:-//XYZproduct//EN		PRODID:-//XYZproduct//EN
	VERSION:2.0		VERSION:2.0
	BEGIN:VEVENT		BEGIN:VEVENT
	URL:http://~~www~~.~~web2con~~.com/		URL:http://conferences.oreillynet.com/pub/w/40/program.html
	DTSTART:~~20071017~~		DTSTART:20051005
	DTEND:~~20071020~~		DTEND:20051008
	SUMMARY:Web 2.0 Conference		SUMMARY:Web 2.0 Conference
	LOCATION:Argent Hotel\, San Francisco\, CA		LOCATION:Argent Hotel\, San Francisco\, CA
	END:VEVENT		END:VEVENT
	END:VCALENDAR		END:VCALENDAR
	</~~nowiki></pre~~>		</source>

	and an equivalent event in hCalendar format ~~with various elements optimized appropriately. See [[hcalendar-example1-steps]] for the derivation.~~		and an equivalent event in hCalendar format:

	<~~pre><nowiki~~>		<source lang=html4strict>
	<div class="vevent">		<div class="vevent">
	<a class="url" href="http://~~www~~.~~web2con~~.com/~~">http:~~//~~www~~.~~web2con.com~~/~~</a~~>		<a class="url" href="http://conferences.oreillynet.com/pub/w/40/program.html/">
	<span class="summary">Web 2.0 Conference</span>:		<span class="summary">Web 2.0 Conference</span></a>:
	<span class="dtstart">~~20071017~~</span>-		<span class="dtstart">2005-10-05</span>-
	<span class="dtend">~~20071019~~</span>,		<span class="dtend">2005-10-07</span>,
	at the <span class="location">Argent Hotel, San Francisco, CA</span>		at the <span class="location">Argent Hotel, San Francisco, CA</span>
	</div>		</div>
	</~~nowiki></pre~~>		</source>

	which could be displayed as:		which could be displayed as:

	<div class="vevent">		<div class="vevent">
	<span class="url">http://~~www~~.~~web2con~~.com/</span> ~~<!-- note modified to account for idiosyncrasy of wiki software -->~~		<span class="url" style="display:none"><!-- unfortunately display none'd to account for idiosyncrasy of wiki software, in practice use the example markup above, not this --> http://conferences.oreillynet.com/pub/w/40/program.html/</span>
	<span class="summary">Web 2.0 Conference</span>:		<span class="summary">[http://conferences.oreillynet.com/pub/w/40/program.html/ Web 2.0 Conference]</span>:
	<span class="dtstart">~~20071017~~</span>-		<span class="dtstart">2005-10-05</span>-
	<span class="dtend">~~20071019~~</span>,		<span class="dtend">2005-10-07</span>,
	at the <span class="location">Argent Hotel, San Francisco, CA</span>		at the <span class="location">Argent Hotel, San Francisco, CA</span>
	</div>		</div>
Line 52:		Line 50:
	Note 3: The version information is unnecessary in hCalendar markup directly since the version will be defined by the profile of hCalendar that is used/referred to in the 'profile' attribute of the <head> element.		Note 3: The version information is unnecessary in hCalendar markup directly since the version will be defined by the profile of hCalendar that is used/referred to in the 'profile' attribute of the <head> element.

	Note 4: ISO8601 dates are however not very human friendly~~. Not only that, in the case of the end datetime (DTEND)~~, ~~the date must be specified as a whole day after the last day since [http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769~~.~~html DTEND is exclusive]!~~ In addition, the year is often understood implicitly by humans from the context. Thus this example could be improved by using <abbr> to make the date information more human readable and friendly, e.g.		Note 4: ISO8601 dates without dashes are however not very human friendly, thus we've added dashes. In addition, the year is often understood implicitly by humans from the context. Thus this example could be improved by using <abbr> to make the date information more human readable and friendly, e.g.

	<~~pre><nowiki~~>		<source lang=html4strict>
	<span class="vevent">		<span class="vevent">
	<a class="url" href="http://~~www~~.~~web2con~~.com/~~">http:~~//~~www~~.~~web2con.com~~/~~</a~~>		<a class="url" href="http://conferences.oreillynet.com/pub/w/40/program.html/">
	<span class="summary">Web 2.0 Conference</span>:		<span class="summary">Web 2.0 Conference</span></a>:
	<abbr class="dtstart" title="~~20071017~~">October 17</abbr>-		<abbr class="dtstart" title="2005-10-05">October 5</abbr>-
	<abbr class="dtend" title="~~20071020~~">19</abbr>,		<abbr class="dtend" title="2005-10-07">7</abbr>,
	at the <span class="location">Argent Hotel, San Francisco, CA</span>		at the <span class="location">Argent Hotel, San Francisco, CA</span>
	</span>		</span>
	</~~nowiki></pre~~>		</source>

	which could be displayed as:		which could be displayed as:

	<div class="vevent">		<div class="vevent">
	<span class="url">http://~~www~~.~~web2con~~.com/</span> ~~<!-- note modified to account for idiosyncrasy of wiki software -->~~		<span class="url" style="display:none"><!-- unfortunately display noned to account for idiosyncrasy of wiki software, in practice use the example markup above, not this --> http://conferences.oreillynet.com/pub/w/40/program.html/</span>
	<span class="summary">Web 2.0 Conference</span>:		<span class="summary">[http://conferences.oreillynet.com/pub/w/40/program.html/ Web 2.0 Conference]</span>:
	<abbr class="dtstart" title="~~20071017~~">October 17</abbr>-		<abbr class="dtstart" title="2005-10-05">October 5</abbr>-
	<abbr class="dtend" title="~~20071020~~">19</abbr>,		<abbr class="dtend" title="2005-10-07">7</abbr>,
	at the <span class="location">Argent Hotel, San Francisco, CA</span>		at the <span class="location">Argent Hotel, San Francisco, CA</span>
	</div>		</div>

			Note 5: The iCalendar has DTEND:20051008 (note the '''8''') vs. the hCalendar has the human visible (and actual) end date of 2005-10-07 (note the '''7'''). This is deliberate. In the case of the end datetime in iCalendar (DTEND), the date must be specified as a whole day after the last day since [http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769.html DTEND is exclusive in iCalendar]. This was very confusing for human authors so with microformats we have fixed this to be consistent with human expectations (visible end date is inclusive). See the [[dtend-issue]] for more details on research and resolution.

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

Tantek: needs to be updated to incorporate dtend-issue resolution

2009-11-17T02:17:04Z

needs to be updated to incorporate dtend-issue resolution

← Older revision		Revision as of 02:17, 17 November 2009
Line 3:		Line 3:

	This is a step by step explanation of the first example in the [[hcalendar\|hCalendar]] specification.		This is a step by step explanation of the first example in the [[hcalendar\|hCalendar]] specification.

			'''Note: this example derivation needs to be updated to incorporate the [[dtend-issue]] resolution.'''

	== Example ==		== Example ==

AndyMabbett: button, related pages

2007-03-29T09:24:09Z

button, related pages

← Older revision		Revision as of 09:24, 29 March 2007
Line 1:		Line 1:
	= hCalendar Example 1 Steps =		= hCalendar Example 1 Steps =
			http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

	This is a step by step explanation of the first example in the [[hcalendar\|hCalendar]] specification.		This is a step by step explanation of the first example in the [[hcalendar\|hCalendar]] specification.
Line 71:		Line 72:
	</div>		</div>

	~~Back to the [[~~hcalendar~~]] specification.~~		==Related pages==
			{{hcalendar-related-pages}}

AndyMabbett: fixes

2007-03-29T09:22:03Z

fixes

← Older revision		Revision as of 09:22, 29 March 2007
Line 25:		Line 25:
	<a class="url" href="http://www.web2con.com/">http://www.web2con.com/</a>		<a class="url" href="http://www.web2con.com/">http://www.web2con.com/</a>
	<span class="summary">Web 2.0 Conference</span>:		<span class="summary">Web 2.0 Conference</span>:
	<~~abbr~~ class="dtstart~~" title="2007-12-17~~">~~October 5~~</~~abbr~~>-		<span class="dtstart">20071017</span>-
	<~~abbr~~ class="dtend~~" title="2007-12-20~~">19</~~abbr~~>,		<span class="dtend">20071019</span>,
	at the <span class="location">Argent Hotel, San Francisco, CA</span>		at the <span class="location">Argent Hotel, San Francisco, CA</span>
	</div>		</div>
Line 36:		Line 36:
	<span class="url">http://www.web2con.com/</span> <!-- note modified to account for idiosyncrasy of wiki software -->		<span class="url">http://www.web2con.com/</span> <!-- note modified to account for idiosyncrasy of wiki software -->
	<span class="summary">Web 2.0 Conference</span>:		<span class="summary">Web 2.0 Conference</span>:
	<~~abbr~~ class="dtstart~~" title="2007-12-17~~">~~October 17~~</~~abbr~~>-		<span class="dtstart">20071017</span>-
	<~~abbr~~ class="dtend~~" title="2007-12-20~~">19</~~abbr~~>,		<span class="dtend">20071019</span>,
	at the <span class="location">Argent Hotel, San Francisco, CA</span>		at the <span class="location">Argent Hotel, San Francisco, CA</span>
	</div>		</div>
Line 49:		Line 49:
	Note 3: The version information is unnecessary in hCalendar markup directly since the version will be defined by the profile of hCalendar that is used/referred to in the 'profile' attribute of the <head> element.		Note 3: The version information is unnecessary in hCalendar markup directly since the version will be defined by the profile of hCalendar that is used/referred to in the 'profile' attribute of the <head> element.

	Note 4: ISO8601 dates are however not very human friendly. Not only that, in the case of the end datetime (DTEND), the date must be specified as a whole day after the last day since [http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769.html DTEND is exclusive]! In addition, the year is often understood implicitly by humans from the context. Thus this example could be improved by using <abbr> to make the date information more human readable and friendly, e.g.		Note 4: ISO8601 dates are however not very human friendly. Not only that, in the case of the end datetime (DTEND), the date must be specified as a whole day after the last day since [http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769.html DTEND is exclusive]! In addition, the year is often understood implicitly by humans from the context. Thus this example could be improved by using <abbr> to make the date information more human readable and friendly, e.g.

	<pre><nowiki>		<pre><nowiki>
	<span class="vevent">		<span class="vevent">
	<a class="url" href="http://www.web2con.com/">		<a class="url" href="http://www.web2con.com/">http://www.web2con.com/</a>
	<span class="summary">Web 2.0 Conference</span>:		<span class="summary">Web 2.0 Conference</span>:
	<abbr class="dtstart" title="~~20051005~~">October 5</abbr>-		<abbr class="dtstart" title="20071017">October 17</abbr>-
	<abbr class="dtend" title="~~20051008~~">7</abbr>,		<abbr class="dtend" title="20071020">19</abbr>,
	at the <span class="location">Argent Hotel, San Francisco, CA</span>		at the <span class="location">Argent Hotel, San Francisco, CA</span>
	~~</a>~~
	</span>		</span>
	</nowiki></pre>		</nowiki></pre>
Line 64:		Line 63:
	which could be displayed as:		which could be displayed as:

	[http://www.web2con.com/ Web 2.0 Conference: October 5-7, at the Argent Hotel, San Francisco, CA]		<div class="vevent">
			<span class="url">http://www.web2con.com/</span> <!-- note modified to account for idiosyncrasy of wiki software -->
			<span class="summary">Web 2.0 Conference</span>:
			<abbr class="dtstart" title="20071017">October 17</abbr>-
			<abbr class="dtend" title="20071020">19</abbr>,
			at the <span class="location">Argent Hotel, San Francisco, CA</span>
			</div>

	Back to the [[hcalendar]] specification.		Back to the [[hcalendar]] specification.

AndyMabbett: reflect changes on main hCal page

2007-03-29T09:17:02Z

reflect changes on main hCal page

← Older revision		Revision as of 09:17, 29 March 2007
Line 4:		Line 4:

	== Example ==		== Example ==
	Here is a sample event in iCalendar:		Here is a sample event in an iCalendar:

	<pre><nowiki>		<pre><nowiki>
	BEGIN:VCALENDAR		BEGIN:VCALENDAR
Line 12:		Line 11:
	BEGIN:VEVENT		BEGIN:VEVENT
	URL:http://www.web2con.com/		URL:http://www.web2con.com/
	DTSTART:~~20051005~~		DTSTART:20071017
	DTEND:~~20051008~~		DTEND:20071020
	SUMMARY:Web 2.0 Conference		SUMMARY:Web 2.0 Conference
	LOCATION:Argent Hotel, San Francisco, CA		LOCATION:Argent Hotel\, San Francisco\, CA
	END:VEVENT		END:VEVENT
	END:VCALENDAR		END:VCALENDAR
	</nowiki></pre>		</nowiki></pre>

	and an equivalent in hCalendar:		and an equivalent event in hCalendar format with various elements optimized appropriately. See [[hcalendar-example1-steps]] for the derivation.

	<pre><nowiki>		<pre><nowiki>
	<~~span~~ class="~~vcalendar~~">		<div class="vevent">
	~~<span class="vevent">~~		<a class="url" href="http://www.web2con.com/">http://www.web2con.com/</a>
	<a class="url" href="http://www.web2con.com/">		<span class="summary">Web 2.0 Conference</span>:
	<span class="summary">Web 2.0 Conference</span>:		<abbr class="dtstart" title="2007-12-17">October 5</abbr>-
	<~~span~~ class="dtstart">~~20051005~~</~~span~~>-		<abbr class="dtend" title="2007-12-20">19</abbr>,
	<~~span~~ class="dtend">~~20051008~~</~~span~~>,		at the <span class="location">Argent Hotel, San Francisco, CA</span>
	at the <span class="location">Argent Hotel, San Francisco, CA</span>		</div>
	~~</a~~>
	</~~span>~~
	~~</span~~>
	</nowiki></pre>		</nowiki></pre>

	which could be displayed as:		which could be displayed as:

	[http://www.web2con.com/ Web 2.0 Conference: ~~20051005~~-~~20051007~~, at the Argent Hotel, San Francisco, CA]		<div class="vevent">
			<span class="url">http://www.web2con.com/</span> <!-- note modified to account for idiosyncrasy of wiki software -->
			<span class="summary">Web 2.0 Conference</span>:
			<abbr class="dtstart" title="2007-12-17">October 17</abbr>-
			<abbr class="dtend" title="2007-12-20">19</abbr>,
			at the <span class="location">Argent Hotel, San Francisco, CA</span>
			</div>

			Note that this is a '''live''' hCalendar microformat, which will be found on this page by parsers.

	Note 1: The product information is not necessary since hCalendar is an interchange format. When transforming hCalendar back into iCalendar, the transforming engine should add its own product ID.		Note 1: The product information is not necessary since hCalendar is an interchange format. When transforming hCalendar back into iCalendar, the transforming engine should add its own product ID.

Tantek at 23:59, 10 October 2005

2005-10-10T23:59:13Z

← Older revision		Revision as of 23:59, 10 October 2005
Line 13:		Line 13:
	URL:http://www.web2con.com/		URL:http://www.web2con.com/
	DTSTART:20051005		DTSTART:20051005
	DTEND:~~20051007~~		DTEND:20051008
	SUMMARY:Web 2.0 Conference		SUMMARY:Web 2.0 Conference
	LOCATION:Argent Hotel, San Francisco, CA		LOCATION:Argent Hotel, San Francisco, CA
Line 28:		Line 28:
	<span class="summary">Web 2.0 Conference</span>:		<span class="summary">Web 2.0 Conference</span>:
	<span class="dtstart">20051005</span>-		<span class="dtstart">20051005</span>-
	<span class="dtend">~~20051007~~</span>,		<span class="dtend">20051008</span>,
	at the <span class="location">Argent Hotel, San Francisco, CA</span>		at the <span class="location">Argent Hotel, San Francisco, CA</span>
	</a>		</a>
Line 46:		Line 46:
	Note 3: The version information is unnecessary in hCalendar markup directly since the version will be defined by the profile of hCalendar that is used/referred to in the 'profile' attribute of the <head> element.		Note 3: The version information is unnecessary in hCalendar markup directly since the version will be defined by the profile of hCalendar that is used/referred to in the 'profile' attribute of the <head> element.

	ISO8601 dates are however not very human friendly. In addition, the year is often understood implicitly by humans from the context. Thus this example could be improved by using <abbr> to make the date information more human readable, e.g.		Note 4: ISO8601 dates are however not very human friendly. Not only that, in the case of the end datetime (DTEND), the date must be specified as a whole day after the last day since [http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769.html DTEND is exclusive]! In addition, the year is often understood implicitly by humans from the context. Thus this example could be improved by using <abbr> to make the date information more human readable and friendly, e.g.

	<pre><nowiki>		<pre><nowiki>
Line 53:		Line 53:
	<span class="summary">Web 2.0 Conference</span>:		<span class="summary">Web 2.0 Conference</span>:
	<abbr class="dtstart" title="20051005">October 5</abbr>-		<abbr class="dtstart" title="20051005">October 5</abbr>-
	<abbr class="dtend" title="~~20051007~~">7</abbr>,		<abbr class="dtend" title="20051008">7</abbr>,
	at the <span class="location">Argent Hotel, San Francisco, CA</span>		at the <span class="location">Argent Hotel, San Francisco, CA</span>
	</a>		</a>

Tantek at 17:18, 24 September 2005

2005-09-24T17:18:00Z

← Older revision		Revision as of 17:18, 24 September 2005
Line 1:		Line 1:
	= hCalendar Example 1 Steps =		= hCalendar Example 1 Steps =

	This is a step by step explanation of the first example in the [[hCalendar]] specification.		This is a step by step explanation of the first example in the [[hcalendar\|hCalendar]] specification.

	== Example ==		== Example ==

RyanKing at 21:59, 16 September 2005

2005-09-16T21:59:17Z

← Older revision		Revision as of 21:59, 16 September 2005
Line 64:		Line 64:


	Back to the [[~~hCalendar~~]] specification.		Back to the [[hcalendar]] specification.