User:TobyInk/hcalendar-1.1 - Revision history

TobyInk: /* Related-To Links */ clarify linking to UIDs

2010-03-08T22:00:45Z

Related-To Links: clarify linking to UIDs

← Older revision		Revision as of 22:00, 8 March 2010
Line 285:		Line 285:
	==== Related-To Links ====		==== Related-To Links ====

	The value of the related-to property {{must}} be a link, and {{should}} ~~link to~~ another hCalendar event or todo item. If the element with the "related-to" class is <a> or <area>, then it {{may}} take a rel attribute with any of the following values:		The value of the related-to property {{must}} be a link, and {{should}} be the UID of another hCalendar event or todo item (not necessarily on the same page). If the element with the "related-to" class is <a> or <area>, then it {{may}} take a rel attribute with any of the following values:

	* vcalendar-parent		* vcalendar-parent

TobyInk: /* Root Class Name */ Thanks Thomas - fixed.

2009-01-20T22:51:36Z

Root Class Name: Thanks Thomas - fixed.

← Older revision		Revision as of 22:51, 20 January 2009
Line 58:		Line 58:
	The root class name for hCalendar is "vcalendar". An element with a class name of "vcalendar" is itself called an ''hCalendar''.		The root class name for hCalendar is "vcalendar". An element with a class name of "vcalendar" is itself called an ''hCalendar''.

	The root class name for events is "vevent". An element with a class name of "vevent" is itself called an ''hCalendar event''. The root class name for todo items is "vtodo". An element with a class name of "vtodo" is itself called an ''hCalendar todo''. ~~<s>~~The root class name for ~~todo~~ items is "valarm".~~</s>~~ The root class name for ~~todo~~ items is "vfreebusy". An element with a class name of "vfreebusy" is itself called an ''hCalendar freebusy''.		The root class name for events is "vevent". An element with a class name of "vevent" is itself called an ''hCalendar event''. The root class name for todo items is "vtodo". An element with a class name of "vtodo" is itself called an ''hCalendar todo''. The root class name for alarm items is "valarm". An element with a class name of "valarm" is itself called an ''hCalendar alarm''. The root class name for freebusy items is "vfreebusy". An element with a class name of "vfreebusy" is itself called an ''hCalendar freebusy''.

	For authoring convenience, "vevent", "vtodo" and "vfreebusy" are treated as root class names for parsing purposes. If a document contains elements with class names "vevent", "vtodo" or "vfreebusy", but not "vcalendar", the entire document has an implied "vcalendar" context.		For authoring convenience, "vevent", "vtodo" and "vfreebusy" are treated as root class names for parsing purposes. If a document contains elements with class names "vevent", "vtodo" or "vfreebusy", but not "vcalendar", the entire document has an implied "vcalendar" context.

ThomasLoertsch: /* Root Class Name */ soemthings wrong with this sentence

2009-01-20T14:43:34Z

Root Class Name: soemthings wrong with this sentence

← Older revision		Revision as of 14:43, 20 January 2009
Line 58:		Line 58:
	The root class name for hCalendar is "vcalendar". An element with a class name of "vcalendar" is itself called an ''hCalendar''.		The root class name for hCalendar is "vcalendar". An element with a class name of "vcalendar" is itself called an ''hCalendar''.

	The root class name for events is "vevent". An element with a class name of "vevent" is itself called an ''hCalendar event''. The root class name for todo items is "vtodo". An element with a class name of "vtodo" is itself called an ''hCalendar todo''. The root class name for todo items is "valarm". The root class name for todo items is "vfreebusy". An element with a class name of "vfreebusy" is itself called an ''hCalendar freebusy''.		The root class name for events is "vevent". An element with a class name of "vevent" is itself called an ''hCalendar event''. The root class name for todo items is "vtodo". An element with a class name of "vtodo" is itself called an ''hCalendar todo''. <s>The root class name for todo items is "valarm".</s> The root class name for todo items is "vfreebusy". An element with a class name of "vfreebusy" is itself called an ''hCalendar freebusy''.

	For authoring convenience, "vevent", "vtodo" and "vfreebusy" are treated as root class names for parsing purposes. If a document contains elements with class names "vevent", "vtodo" or "vfreebusy", but not "vcalendar", the entire document has an implied "vcalendar" context.		For authoring convenience, "vevent", "vtodo" and "vfreebusy" are treated as root class names for parsing purposes. If a document contains elements with class names "vevent", "vtodo" or "vfreebusy", but not "vcalendar", the entire document has an implied "vcalendar" context.

TobyInk: Clean up for Wiki 2.0

2008-11-24T14:51:26Z

Clean up for Wiki 2.0

← Older revision		Revision as of 14:51, 24 November 2008
Line 1:		Line 1:
	~~(I am aware of the existence of [[hcalendar~~-~~brainstorming]] and [[htask]]~~. ~~This is intended to be more of a formal~~-style document, representing a draft replacement for the current [[hcalendar]] spec, mostly aimed at filling in areas where the current spec is incomplete or ambiguous, rather than adding newly requested functionality.)		<entry-title>hCalendar 1.1</entry-title>

	~~<h1>hCalendar <small>1.1</small></h1>~~
	http://www.boogdesign.com/images/buttons/microformat_hcalendar.png		http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

	'''This is a DRAFT version of an update to the [[hCalendar]] spec.'''		'''This is a DRAFT version of an update to the [[hCalendar]] spec.'''

			(I am aware of the existence of [[hcalendar-brainstorming]] and [[htask]]. This is intended to be more of a formal-style document, representing a draft replacement for the current [[hcalendar]] spec, mostly aimed at filling in areas where the current spec is incomplete or ambiguous, rather than adding newly requested functionality.)

	hCalendar is a simple, open, distributed calendaring and events format, based on the iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), suitable for embedding in HTML or XHTML, Atom, RSS, and arbitrary XML. hCalendar is one of several open [[microformats\|microformat]] standards.		hCalendar is a simple, open, distributed calendaring and events format, based on the iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), suitable for embedding in HTML or XHTML, Atom, RSS, and arbitrary XML. hCalendar is one of several open [[microformats\|microformat]] standards.

AmeerDawood: /* Links */

2008-11-17T23:49:35Z

Links

← Older revision		Revision as of 23:49, 17 November 2008
Line 270:		Line 270:
	# Otherwise, if the element is an <img> element, the "src" attribute is used as the value;		# Otherwise, if the element is an <img> element, the "src" attribute is used as the value;
	# Otherwise, if the element is an <object> element, the "data" attribute is used as the value;		# Otherwise, if the element is an <object> element, the "data" attribute is used as the value;
	# If all else fails, the element is interpreted as if it were a non-link element, with the textual content of the element being treated as the value. If authors rely on this ~~behaviour~~, absolute URLs {{should}} be specified.		# If all else fails, the element is interpreted as if it were a non-link element, with the textual content of the element being treated as the value. If authors rely on this behavior, absolute URLs {{should}} be specified.

	==== UID ====		==== UID ====
Line 279:		Line 279:
	# Otherwise the element with class "uid" is parsed using the procedure described in the previous section on links in general.		# Otherwise the element with class "uid" is parsed using the procedure described in the previous section on links in general.
	# If there is no element with class "uid", then the element bearing the root class name (e.g. "vevent" or "vtodo") is checked. If that element has a fragment identifier (that is, if it has an "id" attribute or is <a name>), then the value of the UID property {{must}} be set to the absolute URL of that fragment.		# If there is no element with class "uid", then the element bearing the root class name (e.g. "vevent" or "vtodo") is checked. If that element has a fragment identifier (that is, if it has an "id" attribute or is <a name>), then the value of the UID property {{must}} be set to the absolute URL of that fragment.
	# If all else fails, an hCalendar parser {{may}} choose to generate its own UID for the item. Reasonable care {{must}} be taken to ensure the uniqueness of this UID. Authors {{should not}} rely on this ~~behaviour~~.		# If all else fails, an hCalendar parser {{may}} choose to generate its own UID for the item. Reasonable care {{must}} be taken to ensure the uniqueness of this UID. Authors {{should not}} rely on this behavior.
	# Otherwise, the item has no UID value.		# Otherwise, the item has no UID value.

TobyInk: /* Property List for hCalendar Alarms */TRIGGER needs more thought

2008-08-18T22:49:09Z

Property List for hCalendar Alarms: TRIGGER needs more thought

← Older revision		Revision as of 22:49, 18 August 2008
Line 222:		Line 222:

	The "ACTION" property is required in RFC 2445, but in hCalendar defaults to "DISPLAY".		The "ACTION" property is required in RFC 2445, but in hCalendar defaults to "DISPLAY".

			{{OpenIssue}} This is an over-simplistic representation of [http://www.kanzaki.com/docs/ical/trigger.html TRIGGER].

	==== Property List for hCalendar Freebusys ====		==== Property List for hCalendar Freebusys ====

TobyInk: /* Property List for hCalendars */

2008-07-15T14:25:35Z

Property List for hCalendars

← Older revision		Revision as of 14:25, 15 July 2008
Line 72:		Line 72:
	** ''vtodo'' (hCalendar todo)*		** ''vtodo'' (hCalendar todo)*
	** ''vfreebusy'' (hCalendar freebusy)*		** ''vfreebusy'' (hCalendar freebusy)*
			** calscale ? [String representing calendar system being used. Default is "GREGORIAN" if not specified.]
			** method ? [Method taken from [http://www.ietf.org/rfc/rfc2446.txt RFC 2446]. Default is "PUBLISH".]

	Although each component of an hCalendar is optional and {{may}} occur more than once, an hCalendar {{should}} contain at least one ~~item~~.		Although each component of an hCalendar is optional and {{may}} occur more than once, an hCalendar {{should}} contain at least one of <code>vevent</code>, <code>vtodo</code> or <code>vfreebusy</code>.

	===== Key =====		===== Key =====

TobyInk: /* Nested hCards */ Rename this section

2008-06-19T14:48:26Z

Nested hCards: Rename this section

← Older revision		Revision as of 14:48, 19 June 2008
Line 391:		Line 391:
	The events and todos are to be parsed as independent items, with properties from the children not being applied to the parent, nor vice versa. The only thing a parser {{may}} infer from the nesting is the RELATED-TO property. However, if the items explicitly specify a "related-to" class, the explicit relation {{must}} override any implied relation.		The events and todos are to be parsed as independent items, with properties from the children not being applied to the parent, nor vice versa. The only thing a parser {{may}} infer from the nesting is the RELATED-TO property. However, if the items explicitly specify a "related-to" class, the explicit relation {{must}} override any implied relation.

	=== ~~Nested hCards~~ ===		<div id="Nested_hCards"></div>

			=== People embedded in hCalendar items ===

	The "attendee", "contact" and "organizer" properties each describe a person. These elements may be treated as [[hcard\|hCards]] even when no class "vcard" is found on the element.		The "attendee", "contact" and "organizer" properties each describe a person. These elements may be treated as [[hcard\|hCards]] even when no class "vcard" is found on the element.

TobyInk: /* VTODO XOXO Minimization */ Change class name for VTODO XOXO minimization

2008-06-19T14:46:03Z

VTODO XOXO Minimization: Change class name for VTODO XOXO minimization

← Older revision		Revision as of 14:46, 19 June 2008
Line 517:		Line 517:
	The [[abbr-design-pattern\|ABBR design pattern]] {{may}} be used within hCalendar, but authors {{should}} take into account potential accessibility issues.		The [[abbr-design-pattern\|ABBR design pattern]] {{may}} be used within hCalendar, but authors {{should}} take into account potential accessibility issues.

	=== VTODO XOXO Minimization ===		=== VTODO List XOXO Minimization ===

	The following minimization is defined for VTODO when used with [[xoxo]]:		The following minimization is defined for VTODO when used with [[xoxo]]:

	<pre><ol class="vtodo xoxo">		<pre><ol class="vtodo-list xoxo">
	<li>Eat breakfast <span class="status">COMPLETED</span></li>		<li>Eat breakfast <span class="status">COMPLETED</span></li>
	<li>		<li>
Line 534:		Line 534:
	</ol></pre>		</ol></pre>

	When class "vtodo" is found on an element with class "xoxo", then each list item corresponds to a todo item. For each item, if no summary is found in, then the entire contents of the item are taken to be the summary. Nested lists correspond to the RELATED property of VTODO with RELTYPE of PARENT/CHILD. An example iCalendar translation of the above XOXO list might be:		When class "vtodo-list" is found on an element with class "xoxo", then each list item corresponds to a todo item. For each item, if no summary is found in, then the entire contents of the item (less any nested lists) are taken to be the summary. Nested lists correspond to the RELATED property of VTODO with RELTYPE of PARENT/CHILD. An example iCalendar translation of the above XOXO list might be:

	<pre>BEGIN:VTODO		<pre>BEGIN:VTODO

TobyInk: /* Nested hCards */ fix link

2008-05-23T21:33:07Z

Nested hCards: fix link

← Older revision		Revision as of 21:33, 23 May 2008
Line 393:		Line 393:
	=== Nested hCards ===		=== Nested hCards ===

	The "attendee", "contact" and "organizer" properties each describe a person. These elements may be treated as [[\|hcard\|hCards]] even when no class "vcard" is found on the element.		The "attendee", "contact" and "organizer" properties each describe a person. These elements may be treated as [[hcard\|hCards]] even when no class "vcard" is found on the element.

	<pre>		<pre>