From Microformats Wiki
Revision as of 16:58, 6 June 2013 by Barnabywalters (talk | contribs) (Added “see also” section)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

h-example is a microformats2 standard for representing Examples. It builds upon the classic hExample microformat.

Translations: link to each translation as hCard 1.0 does


All properties are optional and are parsed according to the microformats2 parsing specification specification.

  • p-name (was fn) full example name
    • <span class="p-name">Banana #1</span>
  • p-summary (was example-summary) short summary
    • <p class="p-summary">An example of how examples may be exampled</p>
  • p-author h-card (was author) author


Implied examples, if any:

Full example:

<div class="h-example">
  <span class="p-name">An Example Example</span>
  <p>Published <time class="dt-published" datetime="2013-05-02 12:00:00">two days ago</time></p>
  <p class="p-author h-card">Mr. Author</p>
  <img class="u-photo" src="" alt="" />
  <p class="p-summary">An example example showing you how to example</p>
 "type": ["h-example"],
 "properties": {
  "name": ["An Example Example"],
  "published": ["2013-05-02 12:00:00"],
  "author": [{
    "type": ["h-card"],
    "properties": {
     "name": ["Mr. Author"]
    "value": "Mr. Author"
  "photo": [""],
  "summary": ["An example example showing you how to example"]

Examples in the wild

  • List of sites using h-example, with “move to new page if it gets too big” note


What this was based off, why it was created etc.

See Also


Properties first or examples first? returning viewers are most likely to want quick reference to properties, first time viewers are most likely to want an example. Perhaps do as hCard does with the property list => markup 1:1 thing, unless that ends up looking too noisy?


For each property, give:

  • classname e.g. p-name
  • legacy BC classname
  • meaning e.g. The name of the example
  • example value e.g. “An example of an artisanal banana-peeling pattern”
    • full element

Perhaps link to common, shared/implied property classnames (p-name, u-url etc) to their own page? TODO: how to handle properties which probably should be a nested microformat but can also be a plain value? E.G. author:


Ideally all examples will be shown 1:1 with their JSON representation, OR editable with JS to submit it to a parser and show the JSON — this would encourage people to experiment and greater understand the relationship between markup and parsed structure.

  • (perhaps marked up as a test case so the spec page becomes a test suite too)
  • actually, side by side doesn’t work so well, perhaps one after the other or switch between them or just have an external parser provide the JSON repr?