From Microformats Wiki
Jump to navigation Jump to search

h-event is a simple, open format for events on the web. h-event is often used with both event listings and individual event pages. h-event is one of several open microformat draft standards suitable for embedding data in HTML.

h-event is the microformats2 update to hCalendar 1.0.

This is a Living Specification yet mature enough to encourage additional implementations and feedback.
Open Issues
#microformats on freenode: #microformats on Freenode
Tantek Çelik
Per CC0, to the extent possible under law, the editors have waived all copyright and related or neighboring rights to this work. In addition, as of 2020-08-25, the editors have made this specification available under the Open Web Foundation Agreement Version 1.0.


Here is a simple event example:

<div class="h-event">
  <h1 class="p-name">Microformats Meetuph1>
    <time class="dt-start" datetime="2013-06-30 12:00">30<sup>thsup> June 2013, 12:00time>
    to <time class="dt-end" datetime="2013-06-30 18:00">18:00time>
    at <span class="p-location">Some bar in SFspan>p>
  <p class="p-summary">Get together and discuss all things microformats-related.p>

Parsed JSON:

  "items": [
      "type": [
      "properties": {
        "name": [
          "Microformats Meetup"
        "start": [
          "2013-06-30 12:00:00"
        "end": [
          "2013-06-30 18:00:00"
        "location": [
          "Some bar in SF"
        "summary": [
          "Get together and discuss all things microformats-related."

Get started

The class h-event is a root class name that indicates the presence of an h-event.

p-name, dt-start, dt-end, p-location, p-summary, and the other h-event property class names listed below define properties of the h-event.

See microformats2 parsing specification to learn more about property class names.


h-event properties, inside an element with class h-event:

  • p-name - event name (or title)
  • p-summary - short summary of the event
  • dt-start - datetime the event starts
  • dt-end - datetime the event ends
  • dt-duration - duration of the event
  • p-description - more detailed description of the event
  • u-url - permalink for the event
  • p-category - event category(ies)/tag(s)
  • p-location - 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:

  • p-attendee - a person attending the event, optionally embed h-card
  • This draft has not been updated in almost 2 years. During this period, h-entry p-rsvp has been standardised, thus making it robust and mature enough for the addition. I guess it's about time to unlabel p-attendee as experimental.
    • I've filed https://github.com/microformats/h-event/issues/2 to track advancing this draft as a whole. Let's do that with the existing draft before discussing p-attendee in particular. And rather than guessing, take a look at the vocabulary maturity levels in h-entry and perhaps help evaluate (in another issue) p-attendee according to those criteria. Tantek 01:10, 28 February 2017 (UTC)
  • I would also suggest to extend expected value to h-entry, so that, while the personal info can be preserved, the attendee can also support p-rsvp property of h-entry.
    • 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. Tantek 01:10, 28 February 2017 (UTC)

All properties are optional.


h-event is a microformats.org draft specification. Public discussion on h-event takes place on the #microformats channel on irc.freenode.net (view recent discussions), and specific issues may be filed on GitHub.

h-event is ready to use and implemented in the wild. For backwards compatibility you should also mark up top-level h-events as classic hCalendar 1.0 events.

Property Details

(stub, to be expanded)


p-location is typically a physical address, optionally marked up with h-adr, for example:

<p class="p-location h-adr">
  <span class="p-street-address">17 Austerstrætispan>
  <span class="p-locality">Reykjavíkspan>
  <span class="p-country-name">Icelandspan>

Reserved Properties

Reserved properties:

Examples in the wild

Real world in the wild examples:

See microformats2 examples in the wild for more


Main article: microformats validators

Test and validate microformats2 markup in general with:


Software implementations that publish or consume h-event, including themes, plugins, or extensions:

When adding an implementation, please provide and link to its home page and open source repo if any.

Backward Compatibility

Publisher Compatibility

For backward compatibility, you may wish to use classic hCalendar 1.0 classnames in addition to the more future-proof h-event properties, for example:

<div class="h-event vevent">
  <h1 class="p-name summary">Some great eventh1>

Parser Compatibility

Microformats parsers SHOULD detect classic properties only if a classic root class name is found and parse them as microformats2 properties.

If an "h-event" is found, don't look for a "vevent" on the same element.

Compat root class name: vevent
Properties: (parsed as p- plain text unless otherwise specified)

  • summary - parse as p-name
  • dtstart - parse as dt-start
  • dtend - parse as dt-end
  • duration - parse as dt-duration
  • description
  • url - parse as u-
  • category
  • location - including compat root vcard in the absence of h-card, and compat root adr in the absence of h-adr
  • geo - parse as p-location h-geo including compat root geo

iCalendar Compatibility

hCalendar-specific implementations that perform custom display or translation to iCalendar .ics SHOULD prefer p-name over p-summary, and use p-summary value(s) as a fallback if there is no p-name.


This work is based on the existing hCalendar 1.0 and iCalendar RFC 2445 specifications.

Design Principles

(stub, expand)

See Also