hcalendar-brainstorming - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:24:15Z

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

← Older revision		Revision as of 16:24, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~ hCalendar Brainstorming ~~</entry-title>~~		{{DISPLAYTITLE: hCalendar Brainstorming }}

	[[to-do]]:		[[to-do]]:

Tantek: name update

2018-06-08T22:53:13Z

name update

← Older revision		Revision as of 22:53, 8 June 2018
Line 352:		Line 352:

	=== how to use with HTML5 ===		=== how to use with HTML5 ===
	Per [http://lists.w3.org/Archives/Public/public-html/2009Jun/0811.html ~~Edward~~ O'Connor's email to public-html]:		Per [http://lists.w3.org/Archives/Public/public-html/2009Jun/0811.html Theresa O'Connor's email to public-html]:
	Add a section in hCalendar 1.0.1 describing how to use hCalendar in [[HTML5]], including optional use of HTML5's <time> element and/or microdata feature(s). Encourage [[HTML5]] to drop the "vevent" predefined microdata vocabulary and reference the updated hCalendar 1.0.1 spec instead. [[User:Tantek\|Tantek]]		Add a section in hCalendar 1.0.1 describing how to use hCalendar in [[HTML5]], including optional use of HTML5's <time> element and/or microdata feature(s). Encourage [[HTML5]] to drop the "vevent" predefined microdata vocabulary and reference the updated hCalendar 1.0.1 spec instead. [[User:Tantek\|Tantek]]

Tantek: /* Repeating Events */ user-conceptual-understanding challenge, via KevinMarks

2015-01-05T00:34:53Z

Repeating Events: user-conceptual-understanding challenge, via KevinMarks

← Older revision		Revision as of 00:34, 5 January 2015
Line 737:		Line 737:
	* https://wiki.mozilla.org/Webapi#Meetings		* https://wiki.mozilla.org/Webapi#Meetings
	* ...		* ...

			Note that repeating events present a user-conceptual-understanding challenge, and likely should be avoided in user interfaces, and thus formats. E.g.
			* http://forum.bodybuilding.com/showthread.php?t=107926751 - discussion (and confusion about) of whether every other day in a week is 3, 3.5, or 4 days.

	== Open Questions ==		== Open Questions ==

Tantek: moved authors section to informative references since it's a historical note from the Technorati wiki, note Repeating Events examples

2012-02-22T19:04:39Z

moved authors section to informative references since it's a historical note from the Technorati wiki, note Repeating Events examples

← Older revision		Revision as of 19:04, 22 February 2012
Line 11:		Line 11:

	If you have a question, please check the [[hcalendar-faq\|hCalendar FAQ]], and ask new questions on the [http://microformats.org/discuss/ mailing lists] first.		If you have a question, please check the [[hcalendar-faq\|hCalendar FAQ]], and ask new questions on the [http://microformats.org/discuss/ mailing lists] first.

	~~== Authors ==~~
	* [http://suda.co.uk/ Brian Suda]
	* [http://tantek.com/log/ Tantek Çelik]

	== hCalendar authoring best practices ==		== hCalendar authoring best practices ==
Line 686:		Line 682:

	== Examples from real world event sites ==		== Examples from real world event sites ==
	''' These should be moved to [[hcalendar-examples-in-wild]]~~'''~~.		''' These should be moved to [[event-examples]]''' with any pre-hCalendar markup noted therein.

			When they add hCalendar markup, copy them to [[hcalendar-examples-in-wild]].

	=== W3C Meetings ===		=== W3C Meetings ===
Line 701:		Line 699:
	=== Laughing Squid ===		=== Laughing Squid ===

	Laughing Squid had the following [http://laughingsquid.com/squidlist/calendar/9584/2005/4/7 multiple ~~occurence~~ event example]:		Laughing Squid had the following [http://laughingsquid.com/squidlist/calendar/9584/2005/4/7 multiple occurrence event example]:

	Thu, Apr 7 : Tu/Wed: 12-4pm Th/Fr/Sat 12-7pm Sun 12-6pm		Thu, Apr 7 : Tu/Wed: 12-4pm Th/Fr/Sat 12-7pm Sun 12-6pm
Line 734:		Line 732:
	With simpler repeating events, or perhaps events which only repeat a day or two, their hCalendar markup may be more illustrative of how to do this in a general way.		With simpler repeating events, or perhaps events which only repeat a day or two, their hCalendar markup may be more illustrative of how to do this in a general way.

			=== Repeating Events ===
			Examples of web pages that discuss or note repeating events which we should figure out how to mark-up in a reliable and accessible way with hCalendar:
			* https://wiki.mozilla.org/Platform#Meetings
			* https://wiki.mozilla.org/Webapi#Meetings
			* ...

	== Open Questions ==		== Open Questions ==
Line 1,071:		Line 1,074:

	=== Informative References ===		=== Informative References ===
	* [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars HTMLForCalendars (FOO camp)] - presented just a few days before this, hopefully these efforts can be ~~combine~~		* [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars HTMLForCalendars (FOO camp)] - presented just a few days before this, hopefully these efforts can be combined

	* [http://www.imc.org/pdi/ Personal Data Interchange (PDI) at the Internet Mail Consortium]		* [http://www.imc.org/pdi/ Personal Data Interchange (PDI) at the Internet Mail Consortium]
Line 1,079:		Line 1,082:
	* [http://www.ietf.org/rfc/rfc2447.txt iMIP RFC2447]		* [http://www.ietf.org/rfc/rfc2447.txt iMIP RFC2447]
	* [http://www.ietf.org/rfc/rfc3283.txt Guide to Internet Calendaring RFC3283]		* [http://www.ietf.org/rfc/rfc3283.txt Guide to Internet Calendaring RFC3283]

			=== Authors ===
			Authors of the original hCalendar brainstorming page on the Technorati wiki which was copied here with the launch of microformats.org 2005-06-20:
			* [http://suda.co.uk/ Brian Suda] ([[User:Brian]])
			* [http://tantek.com/log/ Tantek Çelik] ([[User:Tantek]])
			Authors since 2005-06-20 are reflected by this wiki page's history.

	== Other Implementations/Ideas ==		== Other Implementations/Ideas ==

Tantek: for hCalendar 1.1 and 2

2011-12-04T18:54:28Z

for hCalendar 1.1 and 2

← Older revision		Revision as of 18:54, 4 December 2011
Line 1,056:		Line 1,056:
	** The hCalendar 1.1 draft does not attempt to add anything new to hCalendar (with the exception of [[User:TobyInk/hcalendar-1.1#VTODO_List_XOXO_Minimization\|VTODO lists]], which is effectively an optimisation for quick and easy todo lists rather than proper extension). The hCalendar 1.0 spec is already ''"a 1:1 representation of the aforementioned iCalendar standard, in semantic HTML"'' — implying that all properties in iCalendar are allowed in hCalendar. The 1.1 draft merely ''documents the usage'' of some of the more esoteric properties in iCalendar and how they may be mapped to (X)HTML. (In fact, if anything it ''shrinks'' hCalendar rather than expands it, as it says that the VJOURNAL and VTIMEZONE components of iCalendar are not supported.) [[User:TobyInk\|TobyInk]] 09:22, 1 Sep 2008 (PDT)		** The hCalendar 1.1 draft does not attempt to add anything new to hCalendar (with the exception of [[User:TobyInk/hcalendar-1.1#VTODO_List_XOXO_Minimization\|VTODO lists]], which is effectively an optimisation for quick and easy todo lists rather than proper extension). The hCalendar 1.0 spec is already ''"a 1:1 representation of the aforementioned iCalendar standard, in semantic HTML"'' — implying that all properties in iCalendar are allowed in hCalendar. The 1.1 draft merely ''documents the usage'' of some of the more esoteric properties in iCalendar and how they may be mapped to (X)HTML. (In fact, if anything it ''shrinks'' hCalendar rather than expands it, as it says that the VJOURNAL and VTIMEZONE components of iCalendar are not supported.) [[User:TobyInk\|TobyInk]] 09:22, 1 Sep 2008 (PDT)
	** As it happens, the hCalendar 1.1 draft also acts as rough documentation of how hCalendar is supported in [http://buzzword.org.uk/cognition/ Cognition]. Although Cognition's implementation may vary from the draft in place to place, it is fairly close, and ultimately aims to implement the draft exactly (by improvements to Cognition rather than regressions in the spec!!) This may be useful for other parser programmers wishing to provide a roughly compatible implementation, and those looking for guidance on how to parse iCalendar features which are not covered by the official hCalendar spec. [[User:TobyInk\|TobyInk]] 09:22, 1 Sep 2008 (PDT)		** As it happens, the hCalendar 1.1 draft also acts as rough documentation of how hCalendar is supported in [http://buzzword.org.uk/cognition/ Cognition]. Although Cognition's implementation may vary from the draft in place to place, it is fairly close, and ultimately aims to implement the draft exactly (by improvements to Cognition rather than regressions in the spec!!) This may be useful for other parser programmers wishing to provide a roughly compatible implementation, and those looking for guidance on how to parse iCalendar features which are not covered by the official hCalendar spec. [[User:TobyInk\|TobyInk]] 09:22, 1 Sep 2008 (PDT)

			== for hCalendar 1.1 ==
			* Apply simplifications, fixes from
			** the above, and
			** [http://tools.ietf.org/html/rfc5545 RFC5545 iCal Basic], which drops a lot of the non-event related stuff.

			== for hCalendar 2 ==
			* incorporate hCalendar 1.1 updates/changes into the [[microformats-2]] hCalendar vocabulary

	== References ==		== References ==

Tantek: /* Photos and other attachments */ improve alt text in example

2011-10-26T23:04:37Z

Photos and other attachments: improve alt text in example

← Older revision		Revision as of 23:04, 26 October 2011
Line 305:		Line 305:
	<img src="http://farm1.static.flickr.com/183/411545406_c73ca4e613_t.jpg"		<img src="http://farm1.static.flickr.com/183/411545406_c73ca4e613_t.jpg"
	class="attach"		class="attach"
	alt="~~this photo~~" />		alt="The Wheel of Time" />
	</a>		</a>
	</span>		</span>
Line 320:		Line 320:
	class="attach"		class="attach"
	type="image/jpeg">		type="image/jpeg">
	~~this photo~~</object>		The Wheel of Time</object>
	</a>		</a>
	</span>		</span>

Tantek: /* dtlast */ note resolution of dtend-issue, and capture implied dtend feature from vcp for inclusion in hCalendar 1.1

2010-02-12T08:28:55Z

dtlast: note resolution of dtend-issue, and capture implied dtend feature from vcp for inclusion in hCalendar 1.1

← Older revision		Revision as of 08:28, 12 February 2010
Line 583:		Line 583:
	In any updates/additions to the iCalendar examples translated to hCalendar, make use of the [[value class pattern]] where it's use will improve accessibility.		In any updates/additions to the iCalendar examples translated to hCalendar, make use of the [[value class pattern]] where it's use will improve accessibility.

	== ~~dtlast~~ ==		== inclusive dtend ==
			Now resolved per the [[dtend-issue]]. dtends are now inclusive. The remainder of the section is being kept purely for historical purposes.


	As documented in [[hcalendar-issues]], in practice (e.g. http://barcamp.org ) it appears all too often (thus easy) to make the mistake of assuming a dtend date value is inclusive, and thus the last day of many events is left off. I am proposing a solution (which is a variant of the enddate suggestion which was made for a second version of hCalendar) in an attempt to help this move forward. [[User:Tantek\|Tantek]] 07:46, 1 Sep 2008 (PDT)		As documented in [[hcalendar-issues]], in practice (e.g. http://barcamp.org ) it appears all too often (thus easy) to make the mistake of assuming a dtend date value is inclusive, and thus the last day of many events is left off. I am proposing a solution (which is a variant of the enddate suggestion which was made for a second version of hCalendar) in an attempt to help this move forward. [[User:Tantek\|Tantek]] 07:46, 1 Sep 2008 (PDT)


			Abandoned <span id="dtlast">dtlast</span> brainstorm:

	In short, introduce the syntactic sugar "dtlast", which treats date values as inclusive for the last day of an event. Thus you would markup the last day of an event with "dtlast" - this use of the word "last" in the property name helps provide an easy mnemonic/reminder that it is inclusive. The prefix "dt" is simply a [[naming-convention]] used to indicate that the property is a datetime value.		In short, introduce the syntactic sugar "dtlast", which treats date values as inclusive for the last day of an event. Thus you would markup the last day of an event with "dtlast" - this use of the word "last" in the property name helps provide an easy mnemonic/reminder that it is inclusive. The prefix "dt" is simply a [[naming-convention]] used to indicate that the property is a datetime value.
Line 594:		Line 600:
	<code><nowiki><abbr class="dtend" title="2008-09-08">September 7th, 2008</abbr></nowiki></code>		<code><nowiki><abbr class="dtend" title="2008-09-08">September 7th, 2008</abbr></nowiki></code>

	and		and <span id="previous_enddate_suggestion">previous enddate suggestion</span>

	<code><nowiki><abbr class="dtlast" title="2008-09-07">September 7th, 2008</abbr></nowiki></code>		<code><nowiki><abbr class="dtlast" title="2008-09-07">September 7th, 2008</abbr></nowiki></code>
Line 604:		Line 610:
	Similarly, when generating hCalendar markup from iCalendar or from a database, markup generators may publish "dtlast" for an end day (when time is not provided).		Similarly, when generating hCalendar markup from iCalendar or from a database, markup generators may publish "dtlast" for an end day (when time is not provided).

	~~=== previous enddate suggestion ===~~
	<span id="~~Simplification of date-end~~"></span>		Abandoned <span id="previous_enddate_suggestion">previous enddate suggestion</span>.

	If ever there is an "hCalendar 2" standard, thought should be given to changing the way dtend is handled, where no hour is specified. Currently, we use:		If ever there is an "hCalendar 2" standard, thought should be given to changing the way dtend is handled, where no hour is specified. Currently, we use:

Line 614:		Line 621:
	:<code><nowiki><abbr class="enddate" title="2007-01-31">31 January 2007</abbr></nowiki></code>		:<code><nowiki><abbr class="enddate" title="2007-01-31">31 January 2007</abbr></nowiki></code>

	and making ''parsers'' responsible for converting to "2007-02-01" when exporting as ~~a vCard~~. [[User:AndyMabbett\|Andy Mabbett]] 05:28, 29 Mar 2007 (PDT)		and making ''parsers'' responsible for converting to "2007-02-01" when exporting as iCalendar. [[User:AndyMabbett\|Andy Mabbett]] 05:28, 29 Mar 2007 (PDT)


			Previously was also known as <span id="Simplification_of_date-end">Simplification of date-end</span>.


			== implied dtend ==
			Per [[value-class-pattern#hCalendar_dtend_implied_date]], hCalendar 1.1 should permit implied dtend dates from the dtstart.

	== CSS Styles ==		== CSS Styles ==

Tantek: /* Tabular event calendars */ typo

2009-08-27T04:12:13Z

Tabular event calendars: typo

← Older revision		Revision as of 04:12, 27 August 2009
Line 32:		Line 32:
	*# parse its "headers" attribute as a space separated set of local IDs		*# parse its "headers" attribute as a space separated set of local IDs
	*# find the <code><td></code> and <code><th></code> elements referenced by those IDs (call them header cells) and consider them part of the element being parsed as follows:		*# find the <code><td></code> and <code><th></code> elements referenced by those IDs (call them header cells) and consider them part of the element being parsed as follows:
	*## Treat the header cells as children of the element, ordered by the order of ids in its "headers" attribute, immediately following the last child node (text or element) or the element. (The basic idea is that the content from those header cells is used to construct the VEVENT, but secondary to (AFTER) the content in the data cell itself, so that the data cell can customize/override part of the data in the header, e.g. if the header cell included both start time and location, and the event was being held at a different location).		*## Treat the header cells as children of the element, ordered by the order of ids in its "headers" attribute, immediately following the last child node (text or element) of the element. (The basic idea is that the content from those header cells is used to construct the VEVENT, but secondary to (AFTER) the content in the data cell itself, so that the data cell can customize/override part of the data in the header, e.g. if the header cell included both start time and location, and the event was being held at a different location).

	Real world example in the wild of a tabular event calendar marked up in this fashion:		Real world example in the wild of a tabular event calendar marked up in this fashion:

Tantek: /* how to use with HTML5 */ clarify scope of HTML5/time element write-up for hCalendar 1.0.1

2009-08-12T08:48:03Z

how to use with HTML5: clarify scope of HTML5/time element write-up for hCalendar 1.0.1

← Older revision		Revision as of 08:48, 12 August 2009
Line 357:		Line 357:
	=== how to use with HTML5 ===		=== how to use with HTML5 ===
	Per [http://lists.w3.org/Archives/Public/public-html/2009Jun/0811.html Edward O'Connor's email to public-html]:		Per [http://lists.w3.org/Archives/Public/public-html/2009Jun/0811.html Edward O'Connor's email to public-html]:
	Add a section in hCalendar describing how to use hCalendar in [[HTML5]], including optional use of HTML5's <time> element and microdata feature. Encourage [[HTML5]] to drop the "vevent" predefined microdata vocabulary and reference an updated hCalendar spec instead. [[User:Tantek\|Tantek]]		Add a section in hCalendar 1.0.1 describing how to use hCalendar in [[HTML5]], including optional use of HTML5's <time> element and/or microdata feature(s). Encourage [[HTML5]] to drop the "vevent" predefined microdata vocabulary and reference the updated hCalendar 1.0.1 spec instead. [[User:Tantek\|Tantek]]

	== iCalendar generation best practices ==		== iCalendar generation best practices ==

Tantek: /* Photos and other attachments */ use for marking up event badges and buttons

2009-08-11T12:45:49Z

Photos and other attachments: use for marking up event badges and buttons

← Older revision		Revision as of 12:45, 11 August 2009
Line 346:		Line 346:
	ATTACHMENTS - - An iCalendar object can include references to Uniform		ATTACHMENTS - - An iCalendar object can include references to Uniform
	Resource Locators that can be programmed resources.		Resource Locators that can be programmed resources.

			==== event badges buttons ====
			Events often have small graphics (badges or buttons) which are used to encourage other sites for promotional purposes.

			An hCalendar event can mark up its badge(s) with the "attach" property. Secondary sites that syndicate and republish such events could then automatically retrieve such attachments and use them in the visual appearance of the republication of such events.

	=== update for value class pattern ===		=== update for value class pattern ===