h-event - Revision history

GRegorLove: /* Examples in the wild */ IA link for 68 middle St example

2026-02-24T00:57:44Z

Examples in the wild: IA link for 68 middle St example

← Older revision		Revision as of 00:57, 24 February 2026
Line 137:		Line 137:
	** has additional property from [[h-entry]]: <code>dt-published</code>		** has additional property from [[h-entry]]: <code>dt-published</code>
	* https://oauth.net/events/ has a list of h-event marked up events relating to OAuth, both future and past		* https://oauth.net/events/ has a list of h-event marked up events relating to OAuth, both future and past
	* http://68middle.st/events ~~has~~ events marked up in h-event		* [https://web.archive.org/web/20191231175256/http://68middle.st/events 68middle.st/events (archived)] had events marked up in h-event
	* [https://www.gov.uk/government/publications/open-standards-for-government/exchange-of-calendar-events gov.uk] mentions that iCalendar can be translated into h-event microformats in their "Exchange of calendar events" guidance.		* [https://www.gov.uk/government/publications/open-standards-for-government/exchange-of-calendar-events gov.uk] mentions that iCalendar can be translated into h-event microformats in their "Exchange of calendar events" guidance.
	<blockquote>You can map events to and from iCalendar from other formats, such as h-event.</blockquote>		<blockquote>You can map events to and from iCalendar from other formats, such as h-event.</blockquote>

GRegorLove: s///

2023-07-26T21:18:23Z

s/<source>/<syntaxhighlight>/

← Older revision		Revision as of 21:18, 26 July 2023
Line 21:		Line 21:
	Here is a simple event example:		Here is a simple event example:

	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<div class="h-event">		<div class="h-event">
	<h1 class="p-name">Microformats Meetup</h1>		<h1 class="p-name">Microformats Meetup</h1>
Line 30:		Line 30:
	<p class="p-summary">Get together and discuss all things microformats-related.</p>		<p class="p-summary">Get together and discuss all things microformats-related.</p>
	</div>		</div>
	</~~source~~>		</syntaxhighlight>

	Parsed JSON:		Parsed JSON:
	<~~source~~ lang=~~javascript~~>		<syntaxhighlight lang="json">
	{		{
	"items": [		"items": [
Line 60:		Line 60:
	]		]
	}		}
	</~~source~~>		</syntaxhighlight>

	=== Get started ===		=== Get started ===
Line 110:		Line 110:
	<code>p-location</code> is typically a physical address, optionally marked up with [[h-adr]], for example:		<code>p-location</code> is typically a physical address, optionally marked up with [[h-adr]], for example:

	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<p class="p-location h-adr">		<p class="p-location h-adr">
	<span class="p-street-address">17 Austerstræti</span>		<span class="p-street-address">17 Austerstræti</span>
Line 116:		Line 116:
	<span class="p-country-name">Iceland</span>		<span class="p-country-name">Iceland</span>
	</p>		</p>
	</~~source~~>		</syntaxhighlight>

	=== Reserved Properties ===		=== Reserved Properties ===
Line 157:		Line 157:
	For backward compatibility, you may wish to use classic [[hCalendar]] classnames in addition to the more future-proof h-event properties, for example:		For backward compatibility, you may wish to use classic [[hCalendar]] classnames in addition to the more future-proof h-event properties, for example:

	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<div class="h-event vevent">		<div class="h-event vevent">
	<h1 class="p-name summary">Some great event</h1>		<h1 class="p-name summary">Some great event</h1>
	</div>		</div>
	</div>		</div>
	</~~source~~>		</syntaxhighlight>

	=== Parser Compatibility ===		=== Parser Compatibility ===

Tantek: editorial: float TOC right like h-card

2023-06-30T23:15:12Z

editorial: float TOC right like h-card

← Older revision		Revision as of 23:15, 30 June 2023
Line 16:		Line 16:
	;License		;License
	: {{cc0-owfa-license}}		: {{cc0-owfa-license}}
	__TOC__		<span style="float:right">__TOC__</span>

	== Example ==		== Example ==

JamesGallagher: /* Examples in the wild */

2022-09-18T20:44:15Z

Examples in the wild

← Older revision		Revision as of 20:44, 18 September 2022
Line 139:		Line 139:
	* http://68middle.st/events has events marked up in h-event		* http://68middle.st/events has events marked up in h-event
	* [https://www.gov.uk/government/publications/open-standards-for-government/exchange-of-calendar-events gov.uk] mentions that iCalendar can be translated into h-event microformats in their "Exchange of calendar events" guidance.		* [https://www.gov.uk/government/publications/open-standards-for-government/exchange-of-calendar-events gov.uk] mentions that iCalendar can be translated into h-event microformats in their "Exchange of calendar events" guidance.
	** <blockquote>You can map events to and from iCalendar from other formats, such as h-event.</blockquote>		<blockquote>You can map events to and from iCalendar from other formats, such as h-event.</blockquote>

	See [[microformats2#Examples_in_the_wild\|microformats2 examples in the wild]] for more		See [[microformats2#Examples_in_the_wild\|microformats2 examples in the wild]] for more

JamesGallagher: Add gov.uk example to h-event page

2022-09-18T20:44:04Z

Add gov.uk example to h-event page

← Older revision		Revision as of 20:44, 18 September 2022
Line 138:		Line 138:
	* https://oauth.net/events/ has a list of h-event marked up events relating to OAuth, both future and past		* https://oauth.net/events/ has a list of h-event marked up events relating to OAuth, both future and past
	* http://68middle.st/events has events marked up in h-event		* http://68middle.st/events has events marked up in h-event
			* [https://www.gov.uk/government/publications/open-standards-for-government/exchange-of-calendar-events gov.uk] mentions that iCalendar can be translated into h-event microformats in their "Exchange of calendar events" guidance.
			** <blockquote>You can map events to and from iCalendar from other formats, such as h-event.</blockquote>

	See [[microformats2#Examples_in_the_wild\|microformats2 examples in the wild]] for more		See [[microformats2#Examples_in_the_wild\|microformats2 examples in the wild]] for more

Dshanske: /* Experimental Properties */

2021-08-20T04:52:35Z

Experimental Properties

← Older revision		Revision as of 04:52, 20 August 2021
Line 96:		Line 96:
	** I don't understand this. p-attendee is supposed to represent a person, e.g. an [[h-card]]. How would it having that be an [[h-entry]] make sense and work (from a publishing and consuming code perspective)? This proposed extension to p-attendee may be worth its own issue as well. [[User:Tantek\|Tantek]] 01:10, 28 February 2017 (UTC)		** I don't understand this. p-attendee is supposed to represent a person, e.g. an [[h-card]]. How would it having that be an [[h-entry]] make sense and work (from a publishing and consuming code perspective)? This proposed extension to p-attendee may be worth its own issue as well. [[User:Tantek\|Tantek]] 01:10, 28 February 2017 (UTC)
	</div>		</div>
	* '''<code>p-organizer</code>''' - a person organizing an event, optionally embedded [[h-card]]. Used in Indieweb events, but not consumed.		* '''<code>p-organizer</code>''' - a person organizing an event, optionally embedded [[h-card]]. Used in Indieweb events, but not consumed. https://github.com/microformats/h-event/issues/10
	* '''<code>u-rsvp</code>''' - similar to the proposed u-comment on h-entry, this would be the proposed property to mark up displayed RSVPs on an h-event. https://github.com/microformats/h-event/issues/9		* '''<code>u-rsvp</code>''' - similar to the proposed u-comment on h-entry, this would be the proposed property to mark up displayed RSVPs on an h-event. https://github.com/microformats/h-event/issues/9

Dshanske: /* Properties */

2021-08-20T04:52:13Z

Properties

← Older revision		Revision as of 04:52, 20 August 2021
Line 83:		Line 83:
	* '''<code>p-location</code>''' - where the event takes place, optionally embedded [[h-card]], [[h-adr]], or [[h-geo]]		* '''<code>p-location</code>''' - where the event takes place, optionally embedded [[h-card]], [[h-adr]], or [[h-geo]]

	Experimental properties currently in use in the wild but not (yet) part of the ~~official~~ h-event spec:		All properties are optional.

			=== Experimental Properties ===

			These properties are currently in use in the wild but not (yet) part of the draft h-event spec:

	* '''<code>p-attendee</code>''' - a person attending the event, optionally embed [[h-card]]		* '''<code>p-attendee</code>''' - a person attending the event, optionally embed [[h-card]]
	<div class="discussion">		<div class="discussion">
Line 91:		Line 96:
	** I don't understand this. p-attendee is supposed to represent a person, e.g. an [[h-card]]. How would it having that be an [[h-entry]] make sense and work (from a publishing and consuming code perspective)? This proposed extension to p-attendee may be worth its own issue as well. [[User:Tantek\|Tantek]] 01:10, 28 February 2017 (UTC)		** I don't understand this. p-attendee is supposed to represent a person, e.g. an [[h-card]]. How would it having that be an [[h-entry]] make sense and work (from a publishing and consuming code perspective)? This proposed extension to p-attendee may be worth its own issue as well. [[User:Tantek\|Tantek]] 01:10, 28 February 2017 (UTC)
	</div>		</div>
			* '''<code>p-organizer</code>''' - a person organizing an event, optionally embedded [[h-card]]. Used in Indieweb events, but not consumed.
	~~All properties are optional~~.		* '''<code>u-rsvp</code>''' - similar to the proposed u-comment on h-entry, this would be the proposed property to mark up displayed RSVPs on an h-event. https://github.com/microformats/h-event/issues/9

	== Status ==		== Status ==

Tantek: Advance the spec issue / blocker

2021-06-21T18:30:08Z

Advance the spec issue / blocker

← Older revision		Revision as of 18:30, 21 June 2021
Line 9:		Line 9:
	:[https://github.com/microformats/h-event/issues Open Issues]		:[https://github.com/microformats/h-event/issues Open Issues]
	:[[IRC]]		:[[IRC]]
			:Advance the spec by contributing to a consensus in [https://github.com/microformats/h-event/issues/1 issue: adopt same change control as h-entry]
	<div class="p-author h-card vcard">		<div class="p-author h-card vcard">
	;<span class="p-role role">Editor</span>		;<span class="p-role role">Editor</span>

Tantek: feedback is on issues, no longer on wiki for h-event

2021-06-21T18:27:14Z

feedback is on issues, no longer on wiki for h-event

← Older revision		Revision as of 18:27, 21 June 2021
Line 5:		Line 5:

	;<span id="status">Status</span>		;<span id="status">Status</span>
	:This is a '''Living Specification''' yet mature enough to encourage additional implementations and [[h-event-issues\|feedback]].		:This is a '''Living Specification''' yet mature enough to encourage additional implementations and [https://github.com/microformats/h-event/issues feedback].
	;<span id="participate">Participate</span>		;<span id="participate">Participate</span>
	:[https://github.com/microformats/h-event/issues Open Issues]		:[https://github.com/microformats/h-event/issues Open Issues]

Tantek: editorial: fragments for status and participate, dedup IRC line

2021-06-21T18:21:02Z

editorial: fragments for status and participate, dedup IRC line

← Older revision		Revision as of 18:21, 21 June 2021
Line 4:		Line 4:
	h-event is the [[microformats2]] update to [[hCalendar]].		h-event is the [[microformats2]] update to [[hCalendar]].

	;<span id="~~Status~~">Status</span>		;<span id="status">Status</span>
	:This is a '''Living Specification''' yet mature enough to encourage additional implementations and [[h-event-issues\|feedback]].		:This is a '''Living Specification''' yet mature enough to encourage additional implementations and [[h-event-issues\|feedback]].
	;Participate		;<span id="participate">Participate</span>
	:[https://github.com/microformats/h-event/issues Open Issues]		:[https://github.com/microformats/h-event/issues Open Issues]
	:[[IRC]~~]: [irc://irc.freenode.net/microformats #microformats on Freenode~~]		:[[IRC]]
	<div class="p-author h-card vcard">		<div class="p-author h-card vcard">
	;<span class="p-role role">Editor</span>		;<span class="p-role role">Editor</span>