Microformats Wiki - User contributions [en]

code-tools

2014-10-04T22:47:57Z

Bcomnes: /* See Also */ Added link to parsers #

<entry-title>Code & Tools</entry-title>
== Code Generators ==
There are a few tools available to help you generate microformatted code:

* [http://microformats.org/code/hcard/creator hCard creator]
* [http://microformats.org/code/hcalendar/creator hCalendar creator]
* [http://microformats.org/code/hreview/creator hReview creator]

The [http://gmpg.org/xfn/creator XFN creator] is a Web-based interface for quickly creating a link with the proper XFN values. It has been translated into the following languages:
* [http://gmpg.org/xfn/creator-fr French] as translated by Serge K. Keller
* [http://gmpg.org/xfn/creator-it Italian] as translated by Serge K. Keller and [http://www.caeciliana.ch/ Cécile Matthey]
* [http://gmpg.org/xfn/creator-es Spanish-Argentina] as translated by [http://ultimorender.com.ar/funkascript/ Manuel Razzari]
* [http://gmpg.org/xfn/creator-nl Dutch] as translated by [http://www.budts.be/weblog Jeroen Budts]
* [http://gmpg.org/xfn/creator-cs Czech] as translated by [http://www.zapisky.info/ Josef Petrák]
* [http://gmpg.org/xfn/creator-ja Japanese] as translated by [http://kidachi.kazuhi.to/ Kazuhito Kidachi]

== Validation Testing Tools ==
{{main|validators}}
You can check how your markup will be parsed by using the [http://waterpigs.co.uk/php-mf2/ php-mf2] tool. It will take markup and show you the JSON interpretation.

If you want to check markup as it is interpreted from your page you can check out the [http://microformat2-node.jit.su/ microformat-node] tool. It will grab your page and show you all found microformats that are supported by the tool.

== See Also ==
* [[browsers]]
* [[search-engines]]
* [[validators]]
* [[microformats2]]
* [[microformats2#Parsers]]

h-geo

2014-10-04T18:56:37Z

Bcomnes: Added parsed JSON to primary example

<entry-title>h-geo</entry-title>
<span class="h-card vcard"><span class="p-name fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>
----
<dfn style="font-style:normal;font-weight:bold">h-geo</dfn> is a simple, open format for publishing [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates. h-geo is one of several open [[microformats|microformat]] draft standards suitable for embedding data in HTML/HTML5.

h-geo is the [[microformats2]] update to [[geo]]. It is most commonly used as part of an [[h-card]] or [[h-event]].

{{cc0-owfa-license}}

== Example ==
Here is a simple h-geo example:

<source lang=html4strict>
<p class="h-geo">
<span class="p-latitude">-27.116667</span>,
<span class="p-longitude">-109.366667</span>
</p>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [
{
"type": [
"h-geo"
],
"properties": {
"latitude": [
"-27.116667"
],
"longitude": [
"-109.366667"
],
"name": [
"-27.116667, -109.366667"
]
}
}
]
}
</source>

=== Get started ===
The class '''<code>h-geo</code>''' is a ''root class name'' that indicates the presence of an h-geo.

'''p-latitude''', '''p-longitude''' and '''p-altitude''' classnames define an element as a ''property'' of the h-geo.

See [[microformats2-parsing]] to learn more about property classnames.

== Properties ==
h-geo properties, inside an element with class '''h-geo''':
* '''<code>p-latitude</code>''' - decimal latitude
* '''<code>p-longitude</code>''' - decimal longitude
* '''<code>p-altitude</code>''' - decimal altitude

All properties are optional.

== Status ==

'''h-geo''' is a microformats.org draft specification. Public discussion on h-geo takes place on [[h-geo-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-new/ microformats-new mailing list].

h-geo is ready to use and implemented in the wild, but for backwards compatibility you should also mark h-geos up with classic [[geo]] classnames.

== Property Details ==

'''p-altitude''' refers to the distance in metres from the nominal sea level along the tangent of the earth’s curve. For more information refer to the [http://en.wikipedia.org/wiki/WGS84 WGS84] specification.

== FAQ ==

'''How should I mark up lat/long coordinates without them looking messy and confusing?'''

Unless your content is targeted at an audience with a high leg authoring '''p-latitude''' and '''p-longitude''' as plain numbers on a webpage may not be the best approach. In addition to this there may be accessibility issues due to the potentially long strings of numbers being read out.

You could present the coordinates in a more human-readable form, retaining the decimal coordinates inside data value attributes:

<source lang=html4strict>
<p class="h-geo">
<data class="p-longitude" value="-27.116667">27° 7′ 0″ S</data>,
<data class="p-latitude" value="-109.366667">109° 22′ 0″ W</data>
</p>
</source>

Alternatively you could not show coordinates at all and simply show a human-readable representation of the location, with the lat/long in value attributes of empty data elements.

== Examples in the Wild ==
* … add any h-geo examples you find in the wild

== Validating ==
{{h-spec-section-validating}}

== Backward Compatibility ==
=== Publisher Compatibility ===
For backward compatibility, you may wish to use classic [[geo]] classnames in addition to the more future-proof h-geo properties, for example:

<source lang=html4strict>
<p class="h-geo geo">
<span class="p-latitude latitude">-27.116667</span>,
<span class="p-longitude longitude">-109.366667</span>
</p>
</source>

=== 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-geo" is found, don't look for an "geo" on the same element.

Compatibility root class name: geo

Properties: (parsed as p- plain text unless otherwise specified)

* latitude
* longitude

== Background ==

h-geo is based on the [http://en.wikipedia.org/wiki/WGS84 WGS84] standard, as well as existing [[geo]] specification, which was extracted from [[hCard]] in order to allow it to be used for applications other than contact information.

== See Also ==
* [[microformats2]]
* [[h-card]] and [[h-event]] often contain h-geo
* [[h-adr]] is used to mark up human-readable structured addresses

[[Category:Draft Specifications]]

h-review

2014-10-04T18:52:16Z

Bcomnes: /* Example */ Added parsed json to primary example

<entry-title>h-review</entry-title>
<span class="h-card vcard"><span class="p-name fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>
----
<dfn style="font-style:normal;font-weight:bold">h-review</dfn> is a simple, open format for publishing reviews on the web. h-review is one of several open [[microformats|microformat]] draft standards suitable for embedding data in HTML/HTML5 on the web.

h-review is the [[microformats2]] update to [[hReview]].

{{cc0-owfa-license}}

== Example ==
Here is a simple review example:

<source lang=html4strict>
<div class="h-review">
<h1 class="p-name">Microformats: is structured data worth it?</h1>

<blockquote>
<a class="p-item h-item" href="http://microformats.org">Microformats</a> are the simplest way to publish structured data on the web.
</blockquote>

<p>
<data class="p-rating" value="5">★★★★★</data>
Published <time class="dt-reviewed" datetime="2013-06-12 12:00:00">12<sup>th</sup> June 2013</time>
by <a class="p-reviewer h-card" href="http://example.com">Joe Bloggs</a>.
</p>

<div class="e-description">
<p>Yes, microformats are undoubtedly great. They are the simplest way to markup structured data in HTML and reap the benefits thereof, including using your web page as your API by automatic conversion to JSON. The alternatives of microdata/schema and RDFa are much more work, require more markup, and are more complicated (harder to get right, more likely to break).</p>
</div>
</div>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [
{
"type": [
"h-review"
],
"properties": {
"name": [
"Microformats: is structured data worth it?"
],
"item": [
{
"value": "Microformats",
"type": [
"h-item"
],
"properties": {
"name": [
"Microformats"
],
"url": [
"http://microformats.org"
]
}
}
],
"rating": [
"5"
],
"reviewed": [
"2013-06-12 12:00:00"
],
"reviewer": [
{
"value": "Joe Bloggs",
"type": [
"h-card"
],
"properties": {
"name": [
"Joe Bloggs"
],
"url": [
"http://example.com"
]
}
}
],
"description": [
{
"value": "Yes, microformats are undoubtedly great. They are the simplest way to markup structured data in HTML and reap the benefits thereof, including using your web page as your API by automatic conversion to JSON. The alternatives of microdata/schema and RDFa are much more work, require more markup, and are more complicated (harder to get right, more likely to break).",
"html": "<p>Yes, microformats are undoubtedly great. They are the simplest way to markup structured data in HTML and reap the benefits thereof, including using your web page as your API by automatic conversion to JSON. The alternatives of microdata/schema and RDFa are much more work, require more markup, and are more complicated (harder to get right, more likely to break).</p>"
}
]
}
}
]
}
</source>

=== Get started ===
The class '''<code>h-review</code>''' is a ''root class name'' that indicates the presence of an h-review.

'''p-name''', '''p-item''', '''p-rating''', '''dt-reviewed''', '''p-reviewer''', '''e-description''' and the other property class names listed below defined elements as ''properties'' of the h-review.

The class '''<code>h-item</code>''' is a ''root class name'' that indicates an embedded '''[[h-item]]''' for the p-item property.

The class '''<code>h-card</code>''' is a ''root class name'' that indicates an embedded '''[[h-card]]''' for the p-reviewer property.

See [[microformats2-parsing]] to learn more about property class names.

== Properties ==
h-review properties, inside an element with class '''h-review''':

* '''<code>p-name</code>''' - name of the review
* '''<code>p-item</code>''' - thing been reviewed, including embedded microformat for e.g. business or person ([[h-card]]), event ([[h-event]]), place ([[h-adr]] or [[h-geo]]), product ([[h-product]]), website, url, or other item ([[h-item]]).
* '''<code>p-reviewer</code>''' - person who authored the review, optionally with an embedded [[h-card]]
* '''<code>dt-reviewed</code>''' - date time of when the review was written
* '''<code>p-rating</code>''' - value from 1-5 indicating a rating for the item (5 best).
* '''<code>p-best</code>''' - define best rating value. can be numerically lower than worst.
* '''<code>p-worst</code>''' - define worst rating value. can be numerically higher than best.
* '''<code>e-description</code>''' - the full text written evaluation and opinion of the reviewer
* '''<code>p-category</code>''' - freeform categories or tags applied to the item by the reviewer
* '''<code>u-url</code>''' - review permalink URL

All properties are optional.

== Status ==
'''h-review''' is a microformats.org draft specification. Public discussion on h-review takes place on [[h-review-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-new/ microformats-new mailing list].

h-review is ready to use and implemented in the wild.

== Property Details ==
(stub, add any property explanations here)

== Examples in the Wild ==
* … add any h-review examples you find in the wild

== Validating ==
{{h-spec-section-validating}}

== Backward Compatiblity ==
=== Publisher Compatibility ===
For backward compatibility, you may wish to use classic [[hReview]] classnames in addition to the more future-proof h-review properties, for example:

<source lang=html4strict>
<div class="h-review hreview">
<h1 class="p-name fn">My great review</h1>
</div>
</source>

=== Parser Compatibility ===
Microformats parsers should detect classic properties and parse them as microformats 2 properties. If an "h-review" is found, don't look for an "hReview" on the same element.

Compatibility root class name: hreview

Properties: (parsed as p- plain text unless otherwise specified)

* <code>summary</code> parse as '''<code>p-name</code>'''
* <code>fn</code> - parse as '''p-name''' of the item being reviewed (p-item h-item p-name)
* <code>photo</code> - parse as '''u-photo''' of the item being reviewed (p-item h-item u-photo)
* <code>url</code> - parse as '''u-url''' of the item being reviewed (p-item h-item u-url)
* <code>reviewer</code> - including compat root vcard in the absence of h-card
* <code>dtreviewed</code> - parse as '''dt-'''
* <code>rating</code>
* <code>best</code>
* <code>worst</code>
* <code>description</code> - parse as '''e-'''
* <code>rel=tag</code> - parse as '''p-category'''
* <code>rel="self bookmark"</code> - parse as '''u-url'''. note that <code>rel</code> attribute value is treated as a space separated set, thus any presence of "self" and "bookmark" within such a set in a rel value is accepted.

Note: The [[hReview]] format has three properties which make use of <code>rel</code> attribute, these are <code>tag</code>, permalink (via the <code>self</code> and <code>bookmark</code> values) and <code>license</code>. Microformats 2 parsers {{should}} map these URLs into the page scoped rel collection.

== Background ==
h-review is based on the existing [[hReview]] specification.

== See Also ==
* [[microformats2]]
* [[h-card]]
* [[h-event]]
* [[h-adr]]
* [[h-geo]]
* [[h-product]] can all be embedded in h-review as the p-item
* [[h-item]] is a minimal microformat in case none of the others suitably represent the item being reviewed

[[Category:Draft Specifications]]

h-resume

2014-10-04T18:50:50Z

Bcomnes: Added parsed JSON to primary example

<entry-title>h-resume</entry-title>
<span class="h-card vcard"><span class="p-name fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>
----
<dfn style="font-style:normal;font-weight:bold">h-resume</dfn> is a simple, open format for publishing resumes and CVs on on the web. h-resume is one of several open [[microformats|microformat]] draft standards suitable for embedding data in HTML/HTML5.

h-resume is the [[microformats2]] update to [[hResume]].

{{cc0-owfa-license}}

== Example ==
Here is a simple resume example:

<source lang=html4strict>
<div class="h-resume">
<span class="p-name">
<a class="p-contact h-card" href="http://example.org">
<img src="http://example.org/photo.png" alt="" />
Joe Bloggs
</a>
resume
</span>

<p class="p-summary">Joe is a top-notch llama farmer with a degree in <span class="p-skill">Llama husbandry</span> and a thirst to produce the finest wool known to man</p>
</div>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [
{
"type": [
"h-resume"
],
"properties": {
"name": [
"Joe Bloggs resume"
],
"contact": [
{
"value": "Joe Bloggs",
"type": [
"h-card"
],
"properties": {
"name": [
"Joe Bloggs"
],
"photo": [
"http://example.org/photo.png"
],
"url": [
"http://example.org"
]
}
}
],
"summary": [
"Joe is a top-notch llama farmer with a degree in Llama husbandry and a thirst to produce the finest wool known to man"
],
"skill": [
"Llama husbandry"
]
}
}
]
}
</source>

=== Get started ===
The class '''<code>h-resume</code>''' is a ''root class name'' that indicates the presence of an h-resume.

See [[microformats2-parsing]] to learn more about property classnames.

== Properties ==
h-resume properties, inside an element with class '''h-resume''':
* '''<code>p-name</code>''' - brief name of the resume
* '''<code>p-summary</code>''' - overview of qualifications and objectives
* '''<code>p-contact</code>''' - current contact info in an <code>[[h-card]]</code>
* '''<code>p-education</code>''' - an education <code>[[h-event]]</code> event, years, embedded <code>[[h-card]]</code> of the school, location. {{main|h-event}} {{main|h-card}}
* '''<code>p-experience</code>''' - a job or other professional experience <code>[[h-event]]</code> event, years, embedded <code>[[h-card]]</code> of the organization, location, job-title. {{main|h-event}} {{main|h-card}}
* '''<code>p-skill</code>''' - a skill or ability, optionally including level and/or duration of experience
* '''<code>p-affiliation</code>''' - an affiliation with an <code>[[h-card]]</code> organization

All properties are optional.

== Status ==

'''h-resume''' is a microformats.org draft specification. Public discussion on h-resume takes place on [[h-resume-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-new/ microformats-new mailing list].

h-resume is ready to use and implemented in the wild, but for backwards compatibility you should also mark h-resumes up with classic [[hResume]] classnames.

== Property Details ==

(stub, add any property explanations here)

'''p-skill''' has a [[hresume-skill-brainstorm|proposed expansion into competency]] with explicit summary, rating and/or duration components. Based on existing real world adoption, we should consider an h-skill vocabulary with p-name, p-rating, and dt-duration properties.

== Examples in the Wild ==
* … add any h-resume examples you find in the wild

== Validating ==
{{h-spec-section-validating}}

== Backward Compatibility ==
=== Publisher Compatibility ===
(stub)
=== Parser Compatibility ===
Microformats parsers {{should}} detect the following root class name and property names. A microformats2 parser may use existing microformats [[parsers]] to extract these properties. If an "h-resume" is found, don't look for an "hresume" on the same element.

compat root class name: <code id="hresume">hresume</code><br/>
properties: (parsed as '''p-''' plain text unless otherwise specified)
* <code>summary</code>
* <code>contact</code> - including compat root <code>vcard</code> in the absence of <code>h-card</code>
* <code>education</code> - including compat root <code>vevent</code> in the absence of <code>h-event</code>
* <code>experience</code> - including compat root <code>vevent</code> in the absence of <code>h-event</code>
* <code>skill</code>
* <code>affiliation</code> - including compat root <code>vcard</code> in the absence of <code>h-card</code>

== Background ==

h-resume is based on the existing [[hResume]] specification.

== See Also ==

* [[microformats2]]
* [[h-card]] and [[h-event]] are both embedded in h-resume
* The [[include-pattern]] is likely to be useful to avoid repeating information in any embedded h-cards
* [[hResume]] is the classic microformat replaced by h-resume

[[Category:Draft Specifications]]

h-recipe

2014-10-04T18:48:08Z

Bcomnes: /* Example */ Added "parsed JSON" above json

<entry-title>h-recipe</entry-title>
<span class="h-card vcard"><span class="p-name fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>
----
<dfn style="font-style:normal;font-weight:bold">h-recipe</dfn> is a simple, open format for publishing recipes on the web. h-recipe is one of several open [[microformats|microformat]] draft standards suitable for embedding data in HTML/HTML5.

h-recipe is the [[microformats2]] update to [[hRecipe]].

{{cc0-owfa-license}}

== Example ==
Here is a simple minimal recipe example:

<source lang=html4strict>
<article class="h-recipe">
<h1 class="p-name">Bagels</h1>

<ul>
<li class="p-ingredient">Flour</li>
<li class="p-ingredient">Sugar</li>
<li class="p-ingredient">Yeast</li>
</ul>

<p>Takes <time class="dt-duration" datetime="1H">1 hour</time>,
serves <data class="p-yield" value="4">four people</data>.</p>

<div class="e-instructions">
<ol>
<li>Start by mixing all the ingredients together.</li>
</ol>
</div>
</article>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [
{
"type": [
"h-recipe"
],
"properties": {
"name": [
"Bagels"
],
"ingredient": [
"Flour",
"Sugar",
"Yeast"
],
"yield": [
"4"
],
"instructions": [
{
"value": "Start by mixing all the ingredients together.",
"html": "<ol> <li>Start by mixing all the ingredients together.</li> </ol>"
}
]
}
}
]
}
</source>

=== Get started ===
The class '''<code>h-recipe</code>''' is a ''root class name'' that indicates the presence of an h-recipe.

'''p-name''', '''e-instructions''', '''p-ingredient''' and the other property classnames listed below define elements as ''properties'' of the h-recipe.

See [[microformats-2-parsing]] to learn more about property classnames.

== Properties ==
h-recipe properties, inside an element with class '''h-recipe''':
* '''<code>p-name</code>''' - the name of the recipe
* '''<code>p-ingredient</code>''' - describes one or more ingredients used in the recipe.
* '''<code>p-yield</code>''' - Specifies the quantity produced by the recipe, like how many persons it satisfyies
* '''<code>e-instructions</code>''' - the method of the recipe.
* '''<code>dt-duration</code>''' - the time it takes to prepare the meal described by the recipe.
* '''<code>u-photo</code>''' - an accompanying image

Experimental properties with wide adoption
* '''<code>p-summary</code>''' - provides a short summary or introduction
* '''<code>p-author</code>''' - person who wrote the recipe, optionally embedded with <code>h-card</code> {{main|h-card}}
* '''<code>dt-published</code>''' - the date the recipe was published
* '''<code>p-nutrition</code>''' - nutritional information like calories, fat, dietary fiber etc.
* ...

== Status ==

'''h-recipe''' is a microformats.org draft specification. Public discussion on h-recipe takes place on [[h-recipe-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-new/ microformats-new mailing list].

h-recipe is ready to use and implemented in the wild, but for backwards compatibility you should also mark h-recipes up with classic [[hRecipe]] classnames.

== Property Details ==

(stub, add any property explanations here)

'''dt-duration''' should be marked up using the [http://developers.whatwg.org/common-microsyntaxes.html#durations duration] microsyntax defined in HTML5. TODO: add more examples

[[hRecipe]] has a number of experimental properties which have real world adoption due to [[Google]] recipe search support of hRecipe. These are: summary, author, published and nutrition.

== Examples in the Wild ==
* … add any h-recipe examples you find in the wild

== Validating ==
{{h-spec-section-validating}}

== Backward Compatibility ==
=== Publisher Compatibility ===
(stub)
=== 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-recipe" is found, don't look for an "hrecipe" on the same element.

compat root class name: <code id="hrecipe">hrecipe</code><br/>
properties: (parsed as '''p-''' plain text unless otherwise specified)
* <code>fn</code> - parse as '''<code>p-name</code>'''
* <code>ingredient</code>
* <code>yield</code>
* <code>instructions</code> - parse as '''e-'''
* <code>duration</code> - parse as '''dt-'''
* <code>photo</code> - parse as '''u-'''
* <code>summary</code>
* <code>author</code> - including compat root <code>vcard</code> in the absence of <code>h-card</code>
* <code>nutrition</code>

== Background ==

h-recipe is based on the existing [[hRecipe]] specification.

== See Also ==

* [[h-recipe-feedback]]
* [[microformats-2]]
* [[h-card]] can be embedded in h-recipe
* [[hRecipe]] is the classic microformat replaced by h-recipe

[[Category:Draft Specifications]]

h-recipe

2014-10-04T18:47:35Z

Bcomnes: Added parsed JSON to primary example

<entry-title>h-recipe</entry-title>
<span class="h-card vcard"><span class="p-name fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>
----
<dfn style="font-style:normal;font-weight:bold">h-recipe</dfn> is a simple, open format for publishing recipes on the web. h-recipe is one of several open [[microformats|microformat]] draft standards suitable for embedding data in HTML/HTML5.

h-recipe is the [[microformats2]] update to [[hRecipe]].

{{cc0-owfa-license}}

== Example ==
Here is a simple minimal recipe example:

<source lang=html4strict>
<article class="h-recipe">
<h1 class="p-name">Bagels</h1>

<ul>
<li class="p-ingredient">Flour</li>
<li class="p-ingredient">Sugar</li>
<li class="p-ingredient">Yeast</li>
</ul>

<p>Takes <time class="dt-duration" datetime="1H">1 hour</time>,
serves <data class="p-yield" value="4">four people</data>.</p>

<div class="e-instructions">
<ol>
<li>Start by mixing all the ingredients together.</li>
</ol>
</div>
</article>
</source>

<source lang=javascript>
{
"items": [
{
"type": [
"h-recipe"
],
"properties": {
"name": [
"Bagels"
],
"ingredient": [
"Flour",
"Sugar",
"Yeast"
],
"yield": [
"4"
],
"instructions": [
{
"value": "Start by mixing all the ingredients together.",
"html": "<ol> <li>Start by mixing all the ingredients together.</li> </ol>"
}
]
}
}
]
}
</source>

=== Get started ===
The class '''<code>h-recipe</code>''' is a ''root class name'' that indicates the presence of an h-recipe.

'''p-name''', '''e-instructions''', '''p-ingredient''' and the other property classnames listed below define elements as ''properties'' of the h-recipe.

See [[microformats-2-parsing]] to learn more about property classnames.

== Properties ==
h-recipe properties, inside an element with class '''h-recipe''':
* '''<code>p-name</code>''' - the name of the recipe
* '''<code>p-ingredient</code>''' - describes one or more ingredients used in the recipe.
* '''<code>p-yield</code>''' - Specifies the quantity produced by the recipe, like how many persons it satisfyies
* '''<code>e-instructions</code>''' - the method of the recipe.
* '''<code>dt-duration</code>''' - the time it takes to prepare the meal described by the recipe.
* '''<code>u-photo</code>''' - an accompanying image

Experimental properties with wide adoption
* '''<code>p-summary</code>''' - provides a short summary or introduction
* '''<code>p-author</code>''' - person who wrote the recipe, optionally embedded with <code>h-card</code> {{main|h-card}}
* '''<code>dt-published</code>''' - the date the recipe was published
* '''<code>p-nutrition</code>''' - nutritional information like calories, fat, dietary fiber etc.
* ...

== Status ==

'''h-recipe''' is a microformats.org draft specification. Public discussion on h-recipe takes place on [[h-recipe-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-new/ microformats-new mailing list].

h-recipe is ready to use and implemented in the wild, but for backwards compatibility you should also mark h-recipes up with classic [[hRecipe]] classnames.

== Property Details ==

(stub, add any property explanations here)

'''dt-duration''' should be marked up using the [http://developers.whatwg.org/common-microsyntaxes.html#durations duration] microsyntax defined in HTML5. TODO: add more examples

[[hRecipe]] has a number of experimental properties which have real world adoption due to [[Google]] recipe search support of hRecipe. These are: summary, author, published and nutrition.

== Examples in the Wild ==
* … add any h-recipe examples you find in the wild

== Validating ==
{{h-spec-section-validating}}

== Backward Compatibility ==
=== Publisher Compatibility ===
(stub)
=== 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-recipe" is found, don't look for an "hrecipe" on the same element.

compat root class name: <code id="hrecipe">hrecipe</code><br/>
properties: (parsed as '''p-''' plain text unless otherwise specified)
* <code>fn</code> - parse as '''<code>p-name</code>'''
* <code>ingredient</code>
* <code>yield</code>
* <code>instructions</code> - parse as '''e-'''
* <code>duration</code> - parse as '''dt-'''
* <code>photo</code> - parse as '''u-'''
* <code>summary</code>
* <code>author</code> - including compat root <code>vcard</code> in the absence of <code>h-card</code>
* <code>nutrition</code>

== Background ==

h-recipe is based on the existing [[hRecipe]] specification.

== See Also ==

* [[h-recipe-feedback]]
* [[microformats-2]]
* [[h-card]] can be embedded in h-recipe
* [[hRecipe]] is the classic microformat replaced by h-recipe

[[Category:Draft Specifications]]

h-product

2014-10-04T18:44:07Z

Bcomnes: /* Example */ Added parsed JSON to primary example

<entry-title>h-product</entry-title>
<span class="h-card vcard"><span class="p-name fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>
----
<dfn style="font-style:normal;font-weight:bold">h-product</dfn> is a simple, open format for publishing product data on the web. h-product is one of several open [[microformats|microformat]] draft standards suitable for embedding data in HTML/HTML5.

h-product is the [[microformats2]] update to [[hProduct]].

{{cc0-owfa-license}}

== Example ==
Here is a simple minimal product example:

<source lang=html4strict>
<div class="h-product">
<h1 class="p-name">Microformats For Dummies</h1>
<img class="u-photo" src="http://example.org/mfd.png" alt="" />
<div class="e-description">
<p>Want to get started using microformats, but intimidated by hyphens and mediawiki? This book contains everything you need to know!</p>
</div>
<p>Yours today for only <data class="p-price" value="20.00">$20.00</data>
from <a class="p-brand h-card" href="http://example.com/acme">ACME Publishing inc.</a>
</p>
</div>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [
{
"type": [
"h-product"
],
"properties": {
"name": [
"Microformats For Dummies"
],
"photo": [
"http://example.org/mfd.png"
],
"description": [
{
"value": "Want to get started using microformats, but intimidated by hyphens and mediawiki? This book contains everything you need to know!",
"html": "<p>Want to get started using microformats, but intimidated by hyphens and mediawiki? This book contains everything you need to know!</p>"
}
],
"price": [
"20.00"
],
"brand": [
{
"value": "ACME Publishing inc.",
"type": [
"h-card"
],
"properties": {
"name": [
"ACME Publishing inc."
],
"url": [
"http://example.com/acme"
]
}
}
]
}
}
]
}
</source>

=== Get started ===
The class '''<code>h-product</code>''' is a ''root class name'' that indicates the presence of an h-product.

'''p-name''', '''p-price''', '''u-photo''' and the other property classnames listed below define elements as ''properties'' of the h-product.

See [[microformats-2-parsing]] to learn more about property classnames.

== Properties ==
h-product properties, inside an element with class '''h-product''':
* '''<code>p-name</code>''' - name of the product
* '''<code>u-photo</code>''' - photo of the product
* '''<code>p-brand</code>''' - manufacturer, can also be embedded <code>h-card</code> {{main|h-card}}
* '''<code>p-category</code>''' - freeform categories or tags applied to the item by the reviewer
* '''<code>e-description</code>'''
* '''<code>u-url</code>''' - URL of the product
* '''<code>u-identifier</code>''' - includes type (e.g. mpn, upc, isbn, issn, sn, vin, sku etc.) and value.
* '''<code>p-review</code>''' - a review of the product, optionally embedded <code>h-review</code> {{main|h-review}}
* '''<code>p-price</code>''' - retail price of the product

== Status ==

'''h-product''' is a microformats.org draft specification. Public discussion on h-product takes place on [[h-product-feedback]] and the #microformats [[irc]] channel on irc.freenode.net.

h-product is ready to use and implemented in the wild, but for backwards compatibility you should also mark h-products up with classic [[hProduct]] classnames.

== Property Details ==

(stub, add any property explanations here)

TODO: u-identifier supposedly “includes type” — how so? URI scheme? Need examples of how to mark up the various different identifier types.

'''price''' was an experimental property which has real world adoption due to [[Google]] and [[Bing]] search support of hProduct. Due to this it has been included in the updated h-product spec.

== Examples in the Wild ==
* Barnaby Walters’ [http://waterpigs.co.uk/notes/new/ posting UI] is marked up with h-product and experimental h-x-app markup so that authorization UIs can provide a better experience whilst authorizing, without having to pre-register apps and upload logos
* … add any h-product examples you find in the wild

== Validating ==
{{h-spec-section-validating}}

== Backward Compatibility ==
=== Publisher Compatibility ===
For backward compatibility, you may wish to use classic [[hProduct]] classnames in addition to the more future-proof h-product properties, for example:

<source lang=html4strict>
<div class="h-product hproduct">
<h1 class="p-name fn">Product Name</h1>
</div>
</source>

=== 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-product" is found, don't look for an "hProduct" on the same element.

Compatibility root class name: hProduct

Properties: (parsed as p- plain text unless otherwise specified)

* <code>fn</code> - parse as '''<code>p-name</code>'''
* <code>photo</code> - parse as '''u-'''
* <code>brand</code>
* <code>category</code>
* <code>description</code>
* <code>identifier</code> - parse as '''u-'''
* <code>url</code> - parse as '''u-'''
* <code>review</code> - including compat root class <code>hreview</code> in the absence of <code>h-review</code>
* <code>price</code>

== Background ==

h-product is based on the existing [[hProduct]] specification.

== See Also ==
* [[h-product-feedback]]
* [[microformats2]]
* [[h-card]] can be embedded in h-product
* [[hProduct]] is the classic microformat replaced by h-product

[[Category:Draft Specifications]]

h-event

2014-10-04T18:41:32Z

Bcomnes: Added parsed JSON to primary example

<entry-title>h-event</entry-title>
<span class="h-event vcard"><span class="p-name fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>
----
<dfn style="font-style:normal;font-weight:bold">h-event</dfn> is a simple, open format for publishing events on the web. h-event is one of several open [[microformats|microformat]] draft standards suitable for embedding data in HTML/HTML5.

h-event is the [[microformats2]] update to [[hCalendar]].

{{cc0-owfa-license}}

== Example ==
Here is a simple event example:

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

Parsed JSON:
<source lang=javascript>
{
"items": [
{
"type": [
"h-event"
],
"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."
]
}
}
]
}
</source>

=== Get started ===
The class '''<code>h-event</code>''' 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]] to learn more about property class names.

== Properties ==
h-event properties, inside an element with class '''h-event''':
* '''<code>p-name</code>''' - event name (or title)
* '''<code>p-summary</code>''' - short summary of the event
* '''<code>dt-start</code>''' - datetime the event starts
* '''<code>dt-end</code>''' - datetime the event ends
* '''<code>dt-duration</code>''' - duration of the event
* '''<code>p-description</code>''' - more detailed description of the event
* '''<code>u-url</code>''' - permalink for the event
* '''<code>p-category</code>''' - event category(ies)/tag(s)
* '''<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-entry spec:
* '''<code>p-attendee</code>''' - a person attending the event, optionally embed [[h-card]]

All properties are optional.

== Status ==
'''h-event''' is a microformats.org draft specification. Public discussion on h-event takes place on [[h-event-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-new/ microformats-new mailing list].

h-event is ready to use and implemented in the wild, but for backwards compatibility you should also mark h-events up as classic [[hCalendar]] events.

== Property Details ==
(stub, to be expanded)

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

<source lang=html4strict>
<p class="p-location h-adr">
<span class="p-street-address">17 Austerstræti</span>
<span class="p-locality">Reykjavík</span>
<span class="p-country-name">Iceland</span>
</p>
</source>

=== Reserved Properties ===
Reserved properties:
* '''<code>p-organizer</code>''' - a person (co-)organizing the event, optionally embed [[h-card]] {{main|h-card}}
** proposed as way to [https://github.com/snarfed/bridgy/issues/275 implement copying an event organizer to Eventbrite]

== Examples in the wild ==
Real world in the wild examples:

* ... add uses of h-event you see in the wild here.
* [http://www.w3.org/conf/ W3Conf 2013] uses h-event for the main event, and h-card for all the speakers and notable attendees. The h-cards make particularly good use of implied name, url, and photo properties.
* [http://tantek.com/ Tantek Çelik] uses h-event on his home page
* [http://tantek.com/presentations/2012/06/microformats microformats.org at 7 years] presentation with h-event
* [http://tantek.com/presentations/2012/06/pdf2012-indieweb.html Rise of the Indie Web hCards] (from Personal Democracy Forum 2012 #pdf12 #pdf2012) has [[microformats2]] h-event and h-card markup
* WebMaker by Mozilla has h-event and h-card on event search (e.g. [https://webmaker.org/en-US/events/near/?lat=45.5234515&lng=-122.6762071 search near Portland Oregon]) and event pages (e.g. [https://webmaker.org/en-US/events/192f56eb9/ IndieWebCamp 2012]).[https://twitter.com/microformats/status/212207925643587585]
* [http://indiewebcamp.com IndieWebCamp] has [[microformats2]] h-event markup with embedded h-cards for the organizers and the location.
* [https://wiki.mozilla.org/Events Mozilla Events] page has [[microformats2]] h-event markup with attendees marked up with h-card.

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

== Validating ==
{{h-spec-section-validating}}

== Backward Compatibility ==
=== Publisher Compatibility ===
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>
<div class="h-event vevent">
<h1 class="p-name summary">Some great event</h1>
</div>
</div>
</source>

=== 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: <code id="vevent">vevent</code><br/>
Properties: (parsed as '''p-''' plain text unless otherwise specified)
* <code>summary</code> - parse as '''<code>p-name</code>'''
* <code>dtstart</code> - parse as '''<code>dt-start</code>'''
* <code>dtend</code> - parse as '''<code>dt-end</code>'''
* <code>duration</code> - parse as '''<code>dt-duration</code>'''
* <code>description</code>
* <code>url</code> - parse as '''u-'''
* <code>category</code>
* <code>location</code> - including compat root <code>vcard</code> in the absence of <code>h-card</code>, and compat root <code>adr</code> in the absence of <code>h-adr</code>
* <code>geo</code> - parse as '''<code>p-location h-geo</code>''' including compat root <code>geo</code>

=== iCalendar Compatibility ===
hCalendar-specific implementations that perform custom display or translation to iCalendar .ics {{should}} prefer <code>p-name</code> over <code>p-summary</code>, and use <code>p-summary</code> value(s) as a fallback if there is no <code>p-name</code>.

== Background ==
This work is based on the existing [[hCalendar]] and [[iCalendar]] specifications.

== Design Principles ==
(stub, expand)

== See Also ==
* [[microformats2]]
* [[microformats2-parsing]]
* [[h-adr]]
* [[h-geo]]
* [[h-card]]
* [[hCalendar]]

[[Category:Draft Specifications]]

h-card

2014-10-04T18:39:39Z

Bcomnes: Added parsed JSON to primary examples

<entry-title>h-card</entry-title>
<span class="h-card vcard"><span class="p-name fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>
----
<dfn style="font-style:normal;font-weight:bold">h-card</dfn> is a simple, open format for publishing people and organisations on the web. h-card is one of several open [[microformats|microformat]] draft standards suitable for embedding data in HTML/HTML5.

h-card is the [[microformats2]] update to [[hCard]].

{{cc0-owfa-license}}

== Example ==
Here is a simple minimal person example:

<source lang=html4strict>
<a class="h-card" href="http://example.com">Joe Bloggs</a>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [
{
"type": [
"h-card"
],
"properties": {
"name": [
"Joe Bloggs"
],
"url": [
"http://example.com"
]
}
}
]
}
</source>

And a slightly more complete example:

<source lang=html4strict>
<p class="h-card">
<img class="u-photo" src="http://example.org/photo.png" alt="" />
<a class="p-name u-url" href="http://example.org">Joe Bloggs</a>
<a class="u-email" href="mailto:joebloggs@example.com">joebloggs@example.com</a>,
<span class="p-street-address">17 Austerstræti</span>
<span class="p-locality">Reykjavík</span>
<span class="p-country-name">Iceland</span>
</p>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [
{
"type": [
"h-card"
],
"properties": {
"photo": [
"http://example.org/photo.png"
],
"name": [
"Joe Bloggs"
],
"url": [
"http://example.org"
],
"email": [
"mailto:joebloggs@example.com"
],
"street-address": [
"17 Austerstræti"
],
"locality": [
"Reykjavík"
],
"country-name": [
"Iceland"
]
}
}
]
}
</source>

=== Get started ===
The class '''<code>h-card</code>''' is a ''root class name'' that indicates the presence of an h-card.

For minimal examples where at most <code>p-name</code>, <code>u-url</code> and <code>u-photo</code> are required (such as the first given above), only the root class name is needed — see [[microformats-2-implied-properties|implied properties]].

For more complex examples, the root class name must be placed on an element which encloses all the desired properties, and then the properties themselves marked up using the classnames given below.

See [[microformats2-parsing]] to learn more about property classnames.

== Properties ==
h-card properties, inside an element with class '''h-card''':
* '''<code>p-name</code>''' - The full/formatted name of the person or organisation
* '''<code>p-honorific-prefix</code>''' - e.g. Mrs., Mr. or Dr.
* '''<code>p-given-name</code>''' - given (often first) name
* '''<code>p-additional-name</code>''' - other/middle name
* '''<code>p-family-name</code>''' - family (often last) name
* '''<code>p-sort-string</code>''' - string to sort by
* '''<code>p-honorific-suffix</code>''' - e.g. Ph.D, Esq.
* '''<code>p-nickname</code>''' - nickname/alias/handle
* '''<code>u-email</code>''' - email address
* '''<code>u-logo</code>'''
* '''<code>u-photo</code>'''
* '''<code>u-url</code>''' - home page
* '''<code>u-uid</code>''' - unique identifier
* '''<code>p-category</code>''' - category/tag
* '''<code>p-adr</code>''' - postal address, optionally embed an [[h-adr]] {{main|h-adr}}
* '''<code>p-post-office-box</code>'''
* '''<code>p-extended-address</code>''' - apartment/suite/room name/number if any
* '''<code>p-street-address</code>''' - street number + name
* '''<code>p-locality</code>''' - city/town/village
* '''<code>p-region</code>''' - state/county/province
* '''<code>p-postal-code</code>''' - postal code, e.g. US ZIP
* '''<code>p-country-name</code>''' - country name
* '''<code>p-label</code>'''
* '''<code>p-geo</code>''' or '''<code>u-geo</code>''', optionally embed an [[h-geo]] {{main|h-geo}}
* '''<code>p-latitude</code>''' - decimal latitude
* '''<code>p-longitude</code>''' - decimal longitude
* '''<code>p-altitude</code>''' - decimal altitude
* '''<code>p-tel</code>''' - telephone number
* '''<code>p-note</code>''' - additional notes
* '''<code>dt-bday</code>''' - birth date
* '''<code>u-key</code>''' - cryptographic public key e.g. SSH or GPG
* '''<code>p-org</code>''' - affiliated organization, optionally embed an [[h-card]]
* '''<code>p-job-title</code>''' - job title, previously 'title' in [[hCard]], disambiguated.
* '''<code>p-role</code>''' - description of role
* '''<code>u-impp</code>''' per RFC 4770, new in vCard4 (RFC6350)
* '''<code>p-sex</code>''' - biological sex, new in vCard4 (RFC6350)
* '''<code>p-gender-identity</code>''' - gender identity, new in vCard4 (RFC6350)
* '''<code>dt-anniversary</code>'''

All properties are optional.

== Status ==
'''h-card''' is a microformats.org draft specification. Public discussion on h-card takes place on [[h-card-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-new/ microformats-new mailing list].

h-card is ready to use and implemented in the wild, but for backwards compatibility you should also mark h-cards up as classic [[hCard]]s.

== Property Details ==
(stub, to be expanded)

=== p-adr ===
<code>p-adr</code> can optionally embed an [[h-adr]] to cluster associated structured address properties. E.g. adding "p-adr" to the example earlier:

<source lang=html4strict>
<div class="h-card">
<p class="p-name">Joe Bloggs</p>
<p class="p-adr h-adr">
<span class="p-street-address">17 Austerstræti</span>
<span class="p-locality">Reykjavík</span>
<span class="p-country-name">Iceland</span>
</p>
</div>
</source>

Q: Why would you use "p-adr" to cluster associated structured address properties?

A: Because if you have more than one structured address, it helps to cluster which properties go with which address, e.g. home vs. work.

=== p-tel ===
Note: use of 'value' within 'p-tel' should be automatically handled by the support of the [[value-class-pattern]]. And for now, the former [[hCard]] 'type' subproperty of 'tel' is dropped/ignored. If there is demonstrable documented need for additional tel types (e.g. fax), we can introduce new flat properties as needed (e.g. p-tel-fax).

=== Reserved properties ===
Reserved properties (not used much, if at all, in practice):

* '''<code>p-organization-name</code>'''
* '''<code>p-organization-unit</code>'''
* '''<code>p-tz</code>''' - timezone offset, e.g. <code><data class="p-tz" value="-0800">PST</data></code>
* '''<code>dt-rev</code>'''

== Examples in the wild ==
Real world in the wild examples:

* ... add uses of h-card you see in the wild here.
* App.net rolled out support for h-card and h-entry on all profile pages and permalink pages as of 2013-08-06 ([https://alpha.app.net/voidfiles example])
* Brett Comnes marks up his posts with h-card ([http://bret.io/2013/06/29/getting-started-with-bower/ example])
* Ben Werdmuller marks up his homepage and posts with h-card [http://werd.io/view/51d5097fbed7ded0633a5956 example])
* Sandeep Shetty marks his homepage and posts up with h-card and h-entry ([sandeep.io/101 example])
* spreadly marks up share permalink pages with minimal h-cards inside h-entry ([http://my.spread.ly/share/51d570bc09e9486562000002 example])
* [http://eschnou.com/ Laurent Eschenauer] marks his homepage profile up using h-card
* [http://tommorris.org/ Tom Morris] marks himself up with h-card as well as venues he’s checked into ([http://tommorris.org/posts/8408 example])
* [http://www.w3.org/conf/ W3Conf 2013] uses h-card for all the event speakers and notable attendees. The h-cards make particularly good use of implied name, url, and photo properties.
* [http://wordpress.org/extend/themes/sempress SemPress] is a WordPress theme that supports h-card, h-feed/h-entry and h-as-*
* [http://the-pastry-box-project.net/ The Pastry Box Project] use h-card markup on their homepage and individual thoughts pages
* Tom Morris uses h-card and [[XFN]] to markup [http://tommorris.org/pages/blogroll his blogroll].
* Aaron Parecki uses h-card to markup both authorship and references to people in his notes permalinks, e.g. [http://aaronparecki.com/2012/230/reply/1 2012/230/reply/1].
* [http://tantek.com/ Tantek Çelik] uses h-card on his home page as well as within [[h-entry]]s on permalink pages to indicate authorship.
* [http://waterpigs.co.uk/ Barnaby Walters] uses h-card on his home page, as well as within h-entries for notes and articles, both to indicate authorship and also when mentioning people within the body of the notes.
* [http://tantek.com/presentations/2012/06/microformats microformats.org at 7 years] presentation with and h-card markup for people and organizations.
* [http://tantek.com/presentations/2012/06/pdf2012-indieweb.html Rise of the Indie Web hCards] (from Personal Democracy Forum 2012 #pdf12 #pdf2012) has [[microformats2]] h-card markup
* WebMaker by Mozilla has [[microformats2]] h-card on event search (e.g. [https://webmaker.org/en-US/events/near/?lat=45.5234515&lng=-122.6762071 search near Portland Oregon]) and event pages (e.g. [https://webmaker.org/en-US/events/192f56eb9/ IndieWebCamp 2012]).[https://twitter.com/microformats/status/212207925643587585]
* WebFWD by Mozilla has [[microformats2]] h-card markup on [https://webfwd.org/about/experts/ experts] and [https://webfwd.org/about/team/ team] pages
* [http://indiewebcamp.com IndieWebCamp] has [[microformats2]] h-event markup with embedded h-cards for the organizers and the location.
* [https://wiki.mozilla.org/Events Mozilla Events] page has [[microformats2]] h-event markup with attendees marked up with h-card.

== Validating ==
* '''[http://indiewebify.waterpigs.co.uk/validate-h-card/ indiewebify.me h-card validator]''' parses [[h-card]] markup and makes suggestions for things to add, with code samples
{{h-spec-section-validating}}

== Backward Compatibility ==
=== Publisher Compatibility ===
For backward compatibility, you may wish to use classic [[hCard]] classnames in addition to the more future-proof h-card properties, for example:

<source lang=html4strict>
<p class="h-card vcard">
<span class="p-name fn">Joe Bloggs</span>,
<span class="p-org org">Awesome Nonprofit</span>
...
</p>
</source>

The class '''<code>vcard</code>''' is a ''backward compatible root class name'' that indicates the presence of an [[hCard]].

'''fn''', '''org''', and all the other backward compatibility hCard property class names are listed below.

=== 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-card" is found, don't look for a "vcard" on the same element.

Compat. root class name: <code id="vcard">vcard</code><br/>
Properties: (parsed as '''p-''' plain text unless otherwise specified)
* <code>fn</code> - parse as '''<code>p-name</code>'''
* <code>honorific-prefix</code>
* <code>given-name</code>
* <code>additional-name</code>
* <code>family-name</code>
* <code>honorific-suffix</code>
* <code>nickname</code>
* <code>email</code> - parse as '''u-'''
* <code>logo</code> - parse as '''u-'''
* <code>photo</code> - parse as '''u-'''
* <code>url</code> - parse as '''u-'''
* <code>uid</code> - parse as '''u-'''
* <code>category</code>
* <code>adr</code> - parse as '''<code>p-adr h-adr</code>''' including compat root class <code>adr</code>
* <code>extended-address</code>
* <code>street-address</code>
* <code>locality</code>
* <code>region</code>
* <code>postal-code</code>
* <code>country-name</code>
* <code>label</code>
* <code>geo</code> - parse as '''<code>p-geo h-geo</code>''' including compat root class <code>geo</code>
* <code>latitude</code>
* <code>longitude</code>
* <code>tel</code>
* <code>note</code>
* <code>bday</code> - parse as '''dt-'''
* <code>key</code> - parse as '''u-'''
* <code>org</code>
* <code>organization-name</code>
* <code>organization-unit</code>
* <code>title</code> - parse as '''p-job-title'''
* <code>role</code>

Reserved: (backward compat properties that parsers {{may}} implement, if they do, they {{must}} implement in this way:
* <code>tz</code>
* <code>rev</code> - parse as '''dt-'''

== Background ==
This work is based on the existing [[hCard]] and [[vcard]] specifications.

== Design Principles ==

(stub, expand)

== See Also ==

* [[microformats2]]
* [[microformats2-parsing]]
* [[h-adr]]
* [[h-geo]]
* [[hCard]]

[[Category:Draft Specifications]]

h-adr

2014-10-04T18:36:01Z

Bcomnes: Added parsed JSON to primary example

<entry-title>h-adr</entry-title>
<span class="h-card vcard"><span class="p-name fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>
----
<dfn style="font-style:normal;font-weight:bold">h-adr</dfn> is a simple, open format for publishing structured locations such as addresses, physical and/or postal. h-adr is one of several open [[microformats|microformat]] draft standards suitable for embedding data in HTML/HTML5 on the web.

h-adr is the [[microformats-2]] update to [[adr]]. It is most commonly used as part of an [[h-card]] or [[h-event]].

{{cc0-owfa-license}}

== Example ==
Here is a simple postal address example:

<source lang=html4strict>
<p class="h-adr">
<span class="p-street-address">17 Austerstræti</span>
<span class="p-locality">Reykjavík</span>
<span class="p-country-name">Iceland</span>
<span class="p-postal-code">107</span>
</p>
</source>

Parsed JSON:

<source lang=javascript>
{
"items": [
{
"type": [
"h-adr"
],
"properties": {
"street-address": [
"17 Austerstræti"
],
"locality": [
"Reykjavík"
],
"country-name": [
"Iceland"
],
"postal-code": [
"107"
],
"name": [
"17 Austerstræti Reykjavík Iceland 107"
]
}
}
]
}
</source>

=== Get started ===
The class '''<code>h-adr</code>''' is a ''root class name'' that indicates the presence of an h-adr.

'''p-street-address''', '''p-locality''', '''p-country-name''', '''p-postal-code''' and all the other h-adr property class names listed below define properties of the h-adr.

See [[microformats-2-parsing]] to learn more about property class names.

== Properties ==
h-adr properties, inside an element with class '''h-adr''':
* '''<code>p-street-address</code>''' - house/apartment number, floor, street name
* '''<code>p-extended-address</code>''' - additional street details
* '''<code>p-post-office-box</code>''' - post office mailbox
* '''<code>p-locality</code>''' - city/town/village
* '''<code>p-region</code>''' - state/county/province
* '''<code>p-postal-code</code>''' - postal code, e.g. ZIP in the US
* '''<code>p-country-name</code>''' - should be full name of country, country code ok
* '''<code>p-label</code>''' - a mailing label, plain text, perhaps with preformatting
* '''<code>p-geo</code>''' (or u-geo with a RFC 5870 geo: URL), optionally embedded [[h-geo]]
* '''<code>p-latitude</code>''' - decimal latitude
* '''<code>p-longitude</code>''' - decimal longitude
* '''<code>p-altitude</code>''' - decimal altitude - new in vCard4 (RFC6350)

All properties are optional.

== Status ==
'''h-adr''' is a microformats.org draft specification. Public discussion on h-adr takes place on [[h-adr-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-new/ microformats-new mailing list].

h-adr is ready to use and implemented in the wild, but for backwards compatibility you should also mark h-adrs up with classic [[adr]] classnames.

== Property Details ==
(stub, add any property explanations here)

== Examples in the Wild ==
* … add any h-adr examples you find in the wild

== Validating ==
{{h-spec-section-validating}}

== Backward Compatiblity ==
=== Publisher Compatibility ===
For backward compatibility, you may wish to use classic [[adr]] classnames in addition to the more future-proof h-adr properties, for example:

<source lang=html4strict>
<p class="h-adr adr">
<span class="p-street-address street-address">123 Main St.</span>,
<span class="p-locality locality">Pleasantville</span>
...
</p>
</source>

The class '''<code>adr</code>''' is a ''backward compatible root class name'' that indicates the presence of an [[adr]].

'''street-address''', '''locality''', and all the other backward compatibility adr property class names are listed below.

=== 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-adr" is found, don't look for an "adr" on the same element.

Compatibility root class name: adr

Properties: (parsed as p- plain text unless otherwise specified)

* post-office-box
* extended-address
* street-address
* locality
* region
* postal-code
* country-name

== FAQ ==
=== What about country codes ===
Q: When marking up an address, can p-country-name be used to markup two letter country codes like "UK"? Or others like 3 letter Olympic country codes?

A: In short yes. You can do:
<source lang=html4strict>
<span class="p-country-name">UK</span>
</source>
However it's better if you mark it up with the <code>abbr</code> element and provide the full name as well, e.g.
<source lang=html4strict>
<abbr class="p-country-name" title="United Kingdom">UK</abbr>
</source>

Consuming applications may interpret any 2-3 character country-name per the table of 2-3 character [http://en.wikipedia.org/wiki/ISO_3166-1#Officially_assigned_code_elements country codes in ISO3166].

== Background ==
h-adr is based on the existing [[adr]] specification, which was extracted from [[hCard]] in order to allow it to be used for applications other than contact information.

== See Also ==
* [[microformats2]]
* [[h-geo]] can be embedded in h-adr
* [[h-card]] and [[h-event]] often contain h-adr

[[Category:Draft Specifications]]

h-item

2014-10-04T18:32:02Z

Bcomnes: Added parsed json to main example

<entry-title>h-item</entry-title>
<span class="h-card vcard"><span class="p-name fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>
----
<dfn style="font-style:normal;font-weight:bold">h-item</dfn> is a simple, open format for publishing details about arbitrary items. h-item is one of several open [[microformats|microformat]] draft standards suitable for embedding data in HTML/HTML5 on the web.

In practice, h-item is almost never used on its own, but rather as the '''p-item''' in an [[h-review]] if the item being reviewed cannot otherwise be represented by either an [[h-card]], [[h-product]], [[h-event]], or other specific microformat.

{{cc0-owfa-license}}

== Example ==
As the only properties defined by h-item are '''p-name''', '''u-url''' and '''u-photo''', in practice only the root class name is ever actually required thanks to [[microformats-2-implied-properties]]. Explicit properties may be needed for unusual markup structures or to represent multiple values, e.g. multiple URLs, photos. etc..

<source lang=html4strict>
<a class="h-item" href="http://example.org/items/1">
<img src="http://example.org/items/1/photo.png" alt="" />
The Item Name
</a>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [
{
"type": [
"h-item"
],
"properties": {
"name": [
"The Item Name"
],
"photo": [
"http://example.org/items/1/photo.png"
],
"url": [
"http://example.org/items/1"
]
}
}
]
}
</source>

== Properties ==
* '''<code>p-name</code>''' - item name
* '''<code>u-url</code>''' - permalink URL
* '''<code>u-photo</code>''' - photo URL

All properties are optional.

== Status ==

'''h-item''' is a microformats.org draft specification. Public discussion on h-item takes place on [[h-item-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-new/ microformats-new mailing list].

== Property Details ==

(stub, add any property explanations here)

== Examples in the Wild ==
* … add any h-item examples you find in the wild

== Validating ==
{{h-spec-section-validating}}

== Background ==
h-item was extracted from the classic [[hReview]] microformat as a way of referring to arbitrary reviewed items which cannot be represented by other microformats but which required a “shell” microformat due to the flat property requirement of microformats 2.

== See Also ==
* [[microformats2]]
* [[h-review]]

[[Category:Draft Specifications]]

h-entry

2014-10-04T18:23:10Z

Bcomnes: /* Example */ Removed rels as we are only parsing a snippet

<entry-title>h-entry</entry-title>
<span class="h-card vcard"><span class="p-name fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>
----
<dfn style="font-style:normal;font-weight:bold">h-entry</dfn> is a simple, open format for episodic or datestamped content on the web. h-entry is often used with content intended to be syndicated, e.g. blog posts. h-entry is one of several open [[microformats|microformat]] draft standards suitable for embedding data in HTML/HTML5.

h-entry is the [[microformats2]] update to [[hAtom]]'s "hentry". For an update to "hfeed" see [[h-feed]].

{{cc0-owfa-license}}

== Example ==
Here is a simple blog post example:

<source lang=html4strict>
<article class="h-entry">
<h1 class="p-name">Microformats are amazing</h1>
<p>Published by <a class="p-author h-card" href="http://example.com">W. Developer</a>
on <time class="dt-published" datetime="2013-06-13 12:00:00">13<sup>th</sup> June 2013</time>

<p class="p-summary">In which I extoll the virtues of using microformats.</p>

<div class="e-content">
<p>Blah blah blah</p>
</div>
</article>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [
{
"type": [
"h-entry"
],
"properties": {
"name": [
"Microformats are amazing"
],
"author": [
{
"value": "W. Developer",
"type": [
"h-card"
],
"properties": {
"name": [
"W. Developer"
],
"url": [
"http://example.com"
]
}
}
],
"published": [
"2013-06-13 12:00:00"
],
"summary": [
"In which I extoll the virtues of using microformats."
],
"content": [
{
"value": "Blah blah blah",
"html": "<p>Blah blah blah</p>"
}
]
}
}
]
}
</source>

=== Get started ===
The class '''<code>h-entry</code>''' is a ''root class name'' that indicates the presence of an h-entry.

'''p-name''', '''p-author''', '''dt-published''' and the other h-entry property classnames listed below define properties of the h-entry.

See [[microformats2-parsing]] to learn more about property classnames.

== Properties ==
h-entry properties, inside an element with class '''h-entry''':
* '''<code>p-name</code>''' - entry name/title
* '''<code>p-summary</code>''' - short entry summary
* '''<code>e-content</code>''' - full content of the entry
* '''<code>dt-published</code>''' - when the entry was published
* '''<code>dt-updated</code>''' - when the entry was updated
* '''<code>p-author</code>''' - who wrote the entry, optionally embedded [[h-card]](s)
* '''<code>p-category</code>''' - entry categories/tags
* '''<code>u-url</code>''' - entry permalink URL
* '''<code>u-uid</code>''' - unique entry ID
* '''<code>p-location</code>''' - location the entry was posted from, optionally embed [[h-card]], [[h-adr]], or [[h-geo]]

The following experimental properties are in use in the wild (published and consumed) but are not yet part of the spec:

* '''<code>p-comment</code>''' - optionally embedded (or nested?) [[h-cite]](s), each of which is a comment on/reply to the parent h-entry. See [[comment-brainstorming]] ([http://waterpigs.co.uk/notes/4V2DjG/ example])
* '''<code>u-syndication</code>''' - URL(s) of syndicated copies of this post. The property equivalent of [[rel-syndication]] ([http://erinjo.is/2014/checked-into-rockit-colabs-23 example])
* '''<code>u-in-reply-to</code>''' - the URL which the h-entry is considered reply to (i.e. doesn’t make sense without context, could show up in comment thread), optionally an embedded [[h-cite]] ([http://indiewebcamp.com/reply-context reply-context]) ([http://waterpigs.co.uk/notes/4V2DjG/ example])
* '''<code>u-like-of</code>''' - the URL which the h-entry is considered a “like” (favorite, star) of. Optionally an embedded [[h-cite]] ([http://barryfrost.com/posts/11 example])
* '''<code>u-repost-of</code>''' - the URL which the h-entry is considered a “repost” of. Optionally an embedded [[h-cite]].
* '''<code>u-photo</code>''' - one or more photos that is/are considered the primary content of the entry, unless there is a <code>p-location h-card</code>, which is still considered a "checkin" (i.e. with a photo). Otherwise the presence of a u-photo means the name of the entry should be interpreted as a caption on the photo, and the summary/content should be interpreted as a description of the photo.

The following properties are proposed additions based on various existing link preview markup conventions which are ''not'' yet commonly used in the wild (Related: [[link-preview-brainstorming]])
* '''<code>u-audio</code>''' - consider special u- parsing rules for <code><audio></code>
* '''<code>u-video</code>''' - consider special u- parsing rules for <code><video></code>

The following interpretation is a proposed addition:
* if the <code>p-location</code> is also an embedded [[h-card]], the entry is treated as a "checkin".

There is a use-case that has no property yet (or used to but it was repurposed in the wild):
* *-* - a representative photo or image for the entry, e.g. primary photo for an article or subject-cropped photo, suitable for use in a [[link-preview]].

All properties are optional.

== Status ==
'''h-entry''' is a microformats.org draft specification. Public discussion on h-entry takes place on [[h-entry-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-new/ microformats-new mailing list].

h-entry is ready to use and implemented in the wild, but for backwards compatibility you should also mark h-entries up as classic [[hAtom]] entries.

== Property Details ==
This section is a stub.
=== p-location ===
'''<code>p-location</code>''' has been re-used from [[h-event]].

== FAQ ==
=== p-name of a note ===
<div class="discussion">
* '''What is the <code>p-name</code> of a [http://indiewebcamp.com/note note]?'''
** A few options, from simplest to most detailed.
*** '''same as the p-content/e-content''' property.
*** '''same as the <code>title</code> element''' on the note permalink post page. When publishing a note on its own permalink post page, the contents of the note are likely abbreviated for the title of the page. The same abbreviation can be used for the p-name.
*** '''first sentence of the p-content/e-content''' property. It may be better for [http://indiewebcamp.com/syndication syndication] and [[link-preview]] purposes to provide just the first sentence of the note as the <code>p-name</code>. Similarly if only a portion of the content is syndicated to other sites, that portion can be marked up as the <code>p-summary</code>.
</div>

=== venue an entry was posted from ===
<div class="discussion">
* '''How do you indicate a named venue where an entry was posted from? Like a restaurant or park.'''
** Use an embedded [[h-card]] microformat on a <code>p-location</code> property value.
</div>
=== address an entry was posted from ===
<div class="discussion">
* '''How do you indicate the address where an entry was posted from? Like a restaurant or park.'''
** If the address is just part of a named venue, see above, use an [[h-card]]
** Otherwise use an embedded [[h-adr]] microformat on a <code>p-location</code> property value.
</div>
=== lat long an entry was posted from ===
<div class="discussion">
* '''How do you indicate the latitude and longitude of where an entry was posted from?'''
** If the location has a name in addition to latitude and longitude, see above, use an [[h-card]]
** Otherwise if there is an address in addition to latitude and longitude, see above, use an [[h-adr]]
** Otherwise use an embedded [[h-geo]] microformat on a <code>p-location</code> property value.
</div>
=== dt-published property and HTML5 time element ===
<div class="discussion">
* '''Does the dt-published property need to be a time element?'''
** The <code>dt-published</code> property should be a <code><time></code> element so that you can take advantage of HTML5's "datetime" property.
** This lets you specify a human-readable date in the value of the attribute, and the ISO8601 machine-readable date in the "datetime" property.
</div>
=== what is the bare minimum list of required properties on an h-entry ===
<div class="discussion">
* What is the bare minimum list of required properties on an h-entry?
** No properties are explicitly required, but in practice a h-entry should have the following properties at a minimum for consumers:
</div>
* <code>name</code> (can be implied)
* <code>url</code> (can be implied)
* <code>published</code>
<div class="discussion">
* What properties should an h-entry have in addition to the bare minimum?
** Beyond the bare minimum, a typical h-entry should have the following as well:
</div>
* <code>content</code> (or <code>summary</code> at least) - especially for structured content. For a plain text note, the content/summary (whichever is used) should be the same as the <code>name</code>, otherwise it will be implied from the text content of the root element.
* <code>name</code> - for explicitly named/titled entries. Otherwise the entry is assumed to be a "title-less" note (like a tweet).
* <code>author</code> - including a nested <code>[[h-card]]</code>

== Examples in the wild ==
Real world in the wild examples:

* ... add uses of h-entry you see in the wild here.
* ind.ie mark up their [https://ind.ie/blog blog] listing and [https://ind.ie/blog/autumn-events-2014/ permalink] pages with h-entry
* David John Mead marks up his profile, blog posts and comments with h-card, h-entry and h-cite on [http://davidjohnmead.com davidjohnmead.com]
* [[User:Brian|Brian Suda]] marks up his blog posts up with h-entry and h-card on [http://optional.is/required/ optional.is]
* Ashton McAllen marks up his blog posts, reposts, comments and likes with h-entry, h-card and h-cite on [http://acegiak.net/ acegiak.net]
* Emma Kuo marks up her blog posts and notes with h-entry and h-card on [http://notenoughneon.com/ notenoughneon.com]
* Scott Jenson marks up his blog posts with h-entry and h-card on [http://jenson.org/ jenson.org]
* Emily McAllen marks up her blog posts with h-entry and h-card on [http://blackwoolholiday.com/ blackwoolholiday.com]
* Ryan Barrett marks up his blog posts, notes, replies and likes with h-entry and h-card on [https://snarfed.org/ snarfed.org]
* Barry Frost marks up his notes with h-entry, h-card and h-cite on [http://barryfrost.com/ barryfrost.com]
* Amber Case marks up her profile, blog posts, replies and notes with h-entry and h-card on [http://caseorganic.com/ caseorganic.com]
* Johannes Ernst marks up his blog posts with h-entry on [http://upon2020.com/blog/ upon2020.com]
* Michiel de Jong marks up his profile and notes with h-entry and h-card on [https://michielbdejong.com/ michielbdejong.com]
* Mike Taylor marks up his profile and blog posts with h-card and h-entry on [https://bear.im/bearlog/ bear.im]
* Erin Jo Ritchey marks up her profile, posts and comments using h-card, h-entry and h-cite with idno on [http://erinjo.is/ erinjo.is]
* Jeena Paradies marks up his profile, blog posts, notes and comments using h-card, h-entry and h-cite on [https://jeena.net/ jeena.net]
* Andy Sylvester marks up his profile, blog posts and comments using h-card and h-entry on [http://andysylvester.com/2014/03/01/howto-setting-up-the-selfoss-feed-reader-with-microformats-support/ andysylvester.com] (note: as of 2014-03-13 using h-entry for comments instead of correct h-cite --[[User:Barnabywalters|bw]] 14:44, 13 March 2014 (UTC))
* Chloe Weil marks up her blog posts with h-entry on [http://chloeweil.com/blog chloeweil.com]
* Christophe Ducamp marks up his blog posts and profile with h-entry and h-card on [http://christopheducamp.com/ christopheducamp.com]
* Glenn Jones marks up his blog posts, notes, replies, profile and comments with h-entry, h-card and h-cite on [http://glennjones.net/ glennjones.net]
* Marcus Povey marks up his blog posts and profile with h-entry and h-card on [http://www.marcus-povey.co.uk/ marcus-povey.co.uk]
* Matthias Pfefferle marks up his blog posts, comments and profile with h-card, h-cite and h-entry on [http://notizblog.org/ notizblog.org]
* Kyle Mahan marks up his profile and notes with h-card and h-entry on [http://kylewm.com/ kylewm.com]
* Okinawan-lyrics marks up his posts with h-entry and h-card ([http://www.okinawan-lyrics.com/ example])
* App.net marks up profile pages and permalink pages with h-entry as of 2013-08-06 ([https://alpha.app.net/voidfiles example])
* The Twitter archive browser UI uses h-entry and h-card internally, unfortunately it’s not exposed as HTML in static files anywhere
* Brett Comnes marks up his posts with h-entry and h-card ([http://bret.io/2013/06/29/getting-started-with-bower/ example])
* Ben Werdmuller marks up his posts with h-card and h-entry, u-in-reply-to and u-like ([http://werd.io/view/51d5097fbed7ded0633a5956 example])
* Sandeep Shetty marks his posts up with h-card and h-entry, as well as draft u-in-reply-to and experimental u-like properties ([http://sandeep.io/101 example])
* spreadly marks up share permalink pages with h-entry, as well as minimal h-cards and experimental p-like properties ([http://my.spread.ly/share/51d570bc09e9486562000002 example])
* Laurent Eschenauer marks up his posts with h-entry ([http://eschnou.com/entry/first-autonomous-flight-of-my-nodecopter-62-24992.html example])
* Tom Morris marks up his posts using h-entry ([http://tommorris.org/posts/8417 example])
* Numerous newer W3C specs, e.g.
** [http://www.w3.org/TR/2013/CR-css3-values-20130404/ CSS Values and Units Module Level 3 - 2013-04-04]
** [http://www.w3.org/TR/2013/CR-css3-conditional-20130404/ CSS Conditional Rules Module Level 3 - 2013-04-04]
** [http://www.w3.org/TR/2013/WD-css3-page-20130314/ CSS Paged Media Module Level 3 - 2013-03-14]
** [http://www.w3.org/TR/2013/WD-css-counter-styles-3-20130221/ CSS Counter Styles Level 3 - 2013-02-21]
* [http://wordpress.org/extend/themes/sempress SemPress] is a WordPress theme that supports h-card, h-feed/h-entry.
* [http://the-pastry-box-project.net/ The Pastry Box Project] use h-card and h-entry markup on their homepage and individual thoughts pages
* Aaron Parecki uses h-entry to mark up notes, e.g. [http://aaronparecki.com/2012/230/reply/1 2012/230/reply/1].
* [http://tantek.com/ Tantek Çelik] uses h-entry on his home page, as well as h-entry on all post permalinks, e.g. [http://tantek.com/2012/243/t1/name-beats-title-modern-use-dubline-core-wrong-uf2 2012-243 post], with [[rel-prev]]/[[rel-next]] (if applicable) to indicate prev/next posts
* [http://waterpigs.co.uk/ Barnaby Walters] uses h-entry on all notes and articles, as well as nested within notes as reply contexts [http://waterpigs.co.uk/notes/1468/ example] and comments [http://waterpigs.co.uk/notes/1482/ example].

== Validating ==
* '''[http://indiewebify.me/validate-h-entry/ indiewebify.me h-entry validator]''' parses [[h-entry]] markup, finds common errors and makes suggestions for things to add, with code samples
* '''[http://shrewdness.waterpigs.co.uk/test/ Shrewdness h-entry/h-feed validator]''' shows how shrewdness interprets+displays h-entries, with original source and interim formats, works for single h-entries and feed pages

{{h-spec-section-validating}}

== Backward Compatibility ==
=== Publisher Compatibility ===
For backward compatibility, you may wish to use classic [[hAtom]] classnames in addition to the more future-proof h-entry properties, for example:

<source lang=html4strict>
<div class="h-entry hentry">
<h1 class="p-name entry-title">My great blog post</h1>
</div>
</source>

=== 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-entry" is found, don't look for an "hentry" on the same element.

Compat root class name: <code id="hentry">hentry</code><br/>
Properties: (parsed as '''p-''' plain text unless otherwise specified):

* <code>entry-title</code> - parse as '''<code>p-name</code>'''
* <code>entry-summary</code> - parse as '''<code>p-summary</code>'''
* <code>entry-content</code> - parse as '''<code>e-content</code>'''
* <code>published</code> - parse as '''dt-'''
* <code>updated</code> - parse as '''dt-'''
* <code>author</code> - including compat root <code>vcard</code> in the absence of <code>h-card</code>
* <code>category</code>

=== Compat FAQ ===
==== What about rel bookmark ====
Also asked as: ''Why use an h-entry u-url u-uid for permalinks when I have [[rel-bookmark|rel=bookmark]]?''

A: tl;dr: use <code>class="u-url u-uid"</code> instead of <code>rel=bookmark</code> for post permalinks because it's simpler (fewer attributes), and works better across contexts (permalink page, recent posts on home page, collection of posts on archive pages).

rel=bookmark was the old [[hAtom]] way of marking up permalinks. Since then two factors have contributed to reducing use of rel inside microformats:
* rel by typically* document scoped in [[HTML5]] - thus making it inappropriate for use in microformats that are aggregated, e.g. a collection of posts on a home page or in monthly archives.
* it is easier to always use class names for properties. When formats use two (or more!) attributes in HTML to specify properties, confusion results in lower data quality (of the markup and thus the stuff that is marked up). Thus per the microformats [[principle]] of [[simplicity]], in [[microformats2]] we only use class names for properties.

<nowiki>*</nowiki> even though rel=bookmark in particular is article-element / sectioning scoped in HTML5[http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#link-type-bookmark], it's a detail that typical authors are not going to remember, and thus it's not good to depend on it for any kind of format.

==== Why rename entry-title entry-summary entry-content ====
The <code>entry-*</code> classnames in classic [[hAtom]] were prefixed as such due to concerns about vocabulary overlap with the title (as in job title, completely separate semantic) property in [[hCard]] and the summary property in [[hCalendar]] (see: [[hatom-faq#Could_hAtom_instead_use_title_content_and_summary|hAtom FAQ]]).

Following the [[simplicity]] principle, in microformats2, the aforementioned vagueness of '''title''' is dealt with by removing it. As '''name''' is now used consistently across all vocabularies as the property which “names” the microformat, it makes sense to use it to mark up the name of a post.

Likewise, adding entry- to '''summary''' doesn’t add any useful information, and in practice there have been no problems with blog post summaries overlapping with entry summaries, so it makes sense to simplify to '''summary'''. The same applies to '''entry-content''' simplified to '''content'''.

See also: [http://krijnhoetmer.nl/irc-logs/microformats/20120830#l-128 2012-08-30 IRC conversation].

== Related Work ==
Work that re-uses or builds upon h-entry:
* [https://mailpile.pagekite.me:8080/p/Open_Message_Format Mailpile Open Message Format] is using h-entry with structured properties, e.g. p-author h-card.

== Background ==
This work is based on the existing [[hAtom]] microformat, and extensive selfdogfooding in the [http://indiewebcamp.com indie web camp] community.

== See Also ==
* [[h-feed]]
* [[microformats2]]
* [[microformats2-parsing]]
* [[h-geo]]
* [[hCard]]

[[Category:Draft Specifications]]

h-entry

2014-10-01T22:11:58Z

Bcomnes: /* Example */ Addded parsed JSON

<entry-title>h-entry</entry-title>
<span class="h-card vcard"><span class="p-name fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>
----
<dfn style="font-style:normal;font-weight:bold">h-entry</dfn> is a simple, open format for episodic or datestamped content on the web. h-entry is often used with content intended to be syndicated, e.g. blog posts. h-entry is one of several open [[microformats|microformat]] draft standards suitable for embedding data in HTML/HTML5.

h-entry is the [[microformats2]] update to [[hAtom]]'s "hentry". For an update to "hfeed" see [[h-feed]].

{{cc0-owfa-license}}

== Example ==
Here is a simple blog post example:

<source lang=html4strict>
<article class="h-entry">
<h1 class="p-name">Microformats are amazing</h1>
<p>Published by <a class="p-author h-card" href="http://example.com">W. Developer</a>
on <time class="dt-published" datetime="2013-06-13 12:00:00">13<sup>th</sup> June 2013</time>

<p class="p-summary">In which I extoll the virtues of using microformats.</p>

<div class="e-content">
<p>Blah blah blah</p>
</div>
</article>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [
{
"type": [
"h-entry"
],
"properties": {
"name": [
"Microformats are amazing"
],
"author": [
{
"value": "W. Developer",
"type": [
"h-card"
],
"properties": {
"name": [
"W. Developer"
],
"url": [
"http://example.com"
]
}
}
],
"published": [
"2013-06-13 12:00:00"
],
"summary": [
"In which I extoll the virtues of using microformats."
],
"content": [
{
"value": "Blah blah blah",
"html": "<p>Blah blah blah</p>"
}
]
}
}
],
"rels": {}
}
</source>

=== Get started ===
The class '''<code>h-entry</code>''' is a ''root class name'' that indicates the presence of an h-entry.

'''p-name''', '''p-author''', '''dt-published''' and the other h-entry property classnames listed below define properties of the h-entry.

See [[microformats2-parsing]] to learn more about property classnames.

== Properties ==
h-entry properties, inside an element with class '''h-entry''':
* '''<code>p-name</code>''' - entry name/title
* '''<code>p-summary</code>''' - short entry summary
* '''<code>e-content</code>''' - full content of the entry
* '''<code>dt-published</code>''' - when the entry was published
* '''<code>dt-updated</code>''' - when the entry was updated
* '''<code>p-author</code>''' - who wrote the entry, optionally embedded [[h-card]](s)
* '''<code>p-category</code>''' - entry categories/tags
* '''<code>u-url</code>''' - entry permalink URL
* '''<code>u-uid</code>''' - unique entry ID
* '''<code>p-location</code>''' - location the entry was posted from, optionally embed [[h-card]], [[h-adr]], or [[h-geo]]

The following experimental properties are in use in the wild (published and consumed) but are not yet part of the spec:

* '''<code>p-comment</code>''' - optionally embedded (or nested?) [[h-cite]](s), each of which is a comment on/reply to the parent h-entry. See [[comment-brainstorming]] ([http://waterpigs.co.uk/notes/4V2DjG/ example])
* '''<code>u-syndication</code>''' - URL(s) of syndicated copies of this post. The property equivalent of [[rel-syndication]] ([http://erinjo.is/2014/checked-into-rockit-colabs-23 example])
* '''<code>u-in-reply-to</code>''' - the URL which the h-entry is considered reply to (i.e. doesn’t make sense without context, could show up in comment thread), optionally an embedded [[h-cite]] ([http://indiewebcamp.com/reply-context reply-context]) ([http://waterpigs.co.uk/notes/4V2DjG/ example])
* '''<code>u-like-of</code>''' - the URL which the h-entry is considered a “like” (favorite, star) of. Optionally an embedded [[h-cite]] ([http://barryfrost.com/posts/11 example])
* '''<code>u-repost-of</code>''' - the URL which the h-entry is considered a “repost” of. Optionally an embedded [[h-cite]].
* '''<code>u-photo</code>''' - one or more photos that is/are considered the primary content of the entry, unless there is a <code>p-location h-card</code>, which is still considered a "checkin" (i.e. with a photo). Otherwise the presence of a u-photo means the name of the entry should be interpreted as a caption on the photo, and the summary/content should be interpreted as a description of the photo.

The following properties are proposed additions based on various existing link preview markup conventions which are ''not'' yet commonly used in the wild (Related: [[link-preview-brainstorming]])
* '''<code>u-audio</code>''' - consider special u- parsing rules for <code><audio></code>
* '''<code>u-video</code>''' - consider special u- parsing rules for <code><video></code>

The following interpretation is a proposed addition:
* if the <code>p-location</code> is also an embedded [[h-card]], the entry is treated as a "checkin".

There is a use-case that has no property yet (or used to but it was repurposed in the wild):
* *-* - a representative photo or image for the entry, e.g. primary photo for an article or subject-cropped photo, suitable for use in a [[link-preview]].

All properties are optional.

== Status ==
'''h-entry''' is a microformats.org draft specification. Public discussion on h-entry takes place on [[h-entry-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-new/ microformats-new mailing list].

h-entry is ready to use and implemented in the wild, but for backwards compatibility you should also mark h-entries up as classic [[hAtom]] entries.

== Property Details ==
This section is a stub.
=== p-location ===
'''<code>p-location</code>''' has been re-used from [[h-event]].

== FAQ ==
=== p-name of a note ===
<div class="discussion">
* '''What is the <code>p-name</code> of a [http://indiewebcamp.com/note note]?'''
** A few options, from simplest to most detailed.
*** '''same as the p-content/e-content''' property.
*** '''same as the <code>title</code> element''' on the note permalink post page. When publishing a note on its own permalink post page, the contents of the note are likely abbreviated for the title of the page. The same abbreviation can be used for the p-name.
*** '''first sentence of the p-content/e-content''' property. It may be better for [http://indiewebcamp.com/syndication syndication] and [[link-preview]] purposes to provide just the first sentence of the note as the <code>p-name</code>. Similarly if only a portion of the content is syndicated to other sites, that portion can be marked up as the <code>p-summary</code>.
</div>

=== venue an entry was posted from ===
<div class="discussion">
* '''How do you indicate a named venue where an entry was posted from? Like a restaurant or park.'''
** Use an embedded [[h-card]] microformat on a <code>p-location</code> property value.
</div>
=== address an entry was posted from ===
<div class="discussion">
* '''How do you indicate the address where an entry was posted from? Like a restaurant or park.'''
** If the address is just part of a named venue, see above, use an [[h-card]]
** Otherwise use an embedded [[h-adr]] microformat on a <code>p-location</code> property value.
</div>
=== lat long an entry was posted from ===
<div class="discussion">
* '''How do you indicate the latitude and longitude of where an entry was posted from?'''
** If the location has a name in addition to latitude and longitude, see above, use an [[h-card]]
** Otherwise if there is an address in addition to latitude and longitude, see above, use an [[h-adr]]
** Otherwise use an embedded [[h-geo]] microformat on a <code>p-location</code> property value.
</div>
=== dt-published property and HTML5 time element ===
<div class="discussion">
* '''Does the dt-published property need to be a time element?'''
** The <code>dt-published</code> property should be a <code><time></code> element so that you can take advantage of HTML5's "datetime" property.
** This lets you specify a human-readable date in the value of the attribute, and the ISO8601 machine-readable date in the "datetime" property.
</div>
=== what is the bare minimum list of required properties on an h-entry ===
<div class="discussion">
* What is the bare minimum list of required properties on an h-entry?
** No properties are explicitly required, but in practice a h-entry should have the following properties at a minimum for consumers:
</div>
* <code>name</code> (can be implied)
* <code>url</code> (can be implied)
* <code>published</code>
<div class="discussion">
* What properties should an h-entry have in addition to the bare minimum?
** Beyond the bare minimum, a typical h-entry should have the following as well:
</div>
* <code>content</code> (or <code>summary</code> at least) - especially for structured content. For a plain text note, the content/summary (whichever is used) should be the same as the <code>name</code>, otherwise it will be implied from the text content of the root element.
* <code>name</code> - for explicitly named/titled entries. Otherwise the entry is assumed to be a "title-less" note (like a tweet).
* <code>author</code> - including a nested <code>[[h-card]]</code>

== Examples in the wild ==
Real world in the wild examples:

* ... add uses of h-entry you see in the wild here.
* ind.ie mark up their [https://ind.ie/blog blog] listing and [https://ind.ie/blog/autumn-events-2014/ permalink] pages with h-entry
* David John Mead marks up his profile, blog posts and comments with h-card, h-entry and h-cite on [http://davidjohnmead.com davidjohnmead.com]
* [[User:Brian|Brian Suda]] marks up his blog posts up with h-entry and h-card on [http://optional.is/required/ optional.is]
* Ashton McAllen marks up his blog posts, reposts, comments and likes with h-entry, h-card and h-cite on [http://acegiak.net/ acegiak.net]
* Emma Kuo marks up her blog posts and notes with h-entry and h-card on [http://notenoughneon.com/ notenoughneon.com]
* Scott Jenson marks up his blog posts with h-entry and h-card on [http://jenson.org/ jenson.org]
* Emily McAllen marks up her blog posts with h-entry and h-card on [http://blackwoolholiday.com/ blackwoolholiday.com]
* Ryan Barrett marks up his blog posts, notes, replies and likes with h-entry and h-card on [https://snarfed.org/ snarfed.org]
* Barry Frost marks up his notes with h-entry, h-card and h-cite on [http://barryfrost.com/ barryfrost.com]
* Amber Case marks up her profile, blog posts, replies and notes with h-entry and h-card on [http://caseorganic.com/ caseorganic.com]
* Johannes Ernst marks up his blog posts with h-entry on [http://upon2020.com/blog/ upon2020.com]
* Michiel de Jong marks up his profile and notes with h-entry and h-card on [https://michielbdejong.com/ michielbdejong.com]
* Mike Taylor marks up his profile and blog posts with h-card and h-entry on [https://bear.im/bearlog/ bear.im]
* Erin Jo Ritchey marks up her profile, posts and comments using h-card, h-entry and h-cite with idno on [http://erinjo.is/ erinjo.is]
* Jeena Paradies marks up his profile, blog posts, notes and comments using h-card, h-entry and h-cite on [https://jeena.net/ jeena.net]
* Andy Sylvester marks up his profile, blog posts and comments using h-card and h-entry on [http://andysylvester.com/2014/03/01/howto-setting-up-the-selfoss-feed-reader-with-microformats-support/ andysylvester.com] (note: as of 2014-03-13 using h-entry for comments instead of correct h-cite --[[User:Barnabywalters|bw]] 14:44, 13 March 2014 (UTC))
* Chloe Weil marks up her blog posts with h-entry on [http://chloeweil.com/blog chloeweil.com]
* Christophe Ducamp marks up his blog posts and profile with h-entry and h-card on [http://christopheducamp.com/ christopheducamp.com]
* Glenn Jones marks up his blog posts, notes, replies, profile and comments with h-entry, h-card and h-cite on [http://glennjones.net/ glennjones.net]
* Marcus Povey marks up his blog posts and profile with h-entry and h-card on [http://www.marcus-povey.co.uk/ marcus-povey.co.uk]
* Matthias Pfefferle marks up his blog posts, comments and profile with h-card, h-cite and h-entry on [http://notizblog.org/ notizblog.org]
* Kyle Mahan marks up his profile and notes with h-card and h-entry on [http://kylewm.com/ kylewm.com]
* Okinawan-lyrics marks up his posts with h-entry and h-card ([http://www.okinawan-lyrics.com/ example])
* App.net marks up profile pages and permalink pages with h-entry as of 2013-08-06 ([https://alpha.app.net/voidfiles example])
* The Twitter archive browser UI uses h-entry and h-card internally, unfortunately it’s not exposed as HTML in static files anywhere
* Brett Comnes marks up his posts with h-entry and h-card ([http://bret.io/2013/06/29/getting-started-with-bower/ example])
* Ben Werdmuller marks up his posts with h-card and h-entry, u-in-reply-to and u-like ([http://werd.io/view/51d5097fbed7ded0633a5956 example])
* Sandeep Shetty marks his posts up with h-card and h-entry, as well as draft u-in-reply-to and experimental u-like properties ([http://sandeep.io/101 example])
* spreadly marks up share permalink pages with h-entry, as well as minimal h-cards and experimental p-like properties ([http://my.spread.ly/share/51d570bc09e9486562000002 example])
* Laurent Eschenauer marks up his posts with h-entry ([http://eschnou.com/entry/first-autonomous-flight-of-my-nodecopter-62-24992.html example])
* Tom Morris marks up his posts using h-entry ([http://tommorris.org/posts/8417 example])
* Numerous newer W3C specs, e.g.
** [http://www.w3.org/TR/2013/CR-css3-values-20130404/ CSS Values and Units Module Level 3 - 2013-04-04]
** [http://www.w3.org/TR/2013/CR-css3-conditional-20130404/ CSS Conditional Rules Module Level 3 - 2013-04-04]
** [http://www.w3.org/TR/2013/WD-css3-page-20130314/ CSS Paged Media Module Level 3 - 2013-03-14]
** [http://www.w3.org/TR/2013/WD-css-counter-styles-3-20130221/ CSS Counter Styles Level 3 - 2013-02-21]
* [http://wordpress.org/extend/themes/sempress SemPress] is a WordPress theme that supports h-card, h-feed/h-entry.
* [http://the-pastry-box-project.net/ The Pastry Box Project] use h-card and h-entry markup on their homepage and individual thoughts pages
* Aaron Parecki uses h-entry to mark up notes, e.g. [http://aaronparecki.com/2012/230/reply/1 2012/230/reply/1].
* [http://tantek.com/ Tantek Çelik] uses h-entry on his home page, as well as h-entry on all post permalinks, e.g. [http://tantek.com/2012/243/t1/name-beats-title-modern-use-dubline-core-wrong-uf2 2012-243 post], with [[rel-prev]]/[[rel-next]] (if applicable) to indicate prev/next posts
* [http://waterpigs.co.uk/ Barnaby Walters] uses h-entry on all notes and articles, as well as nested within notes as reply contexts [http://waterpigs.co.uk/notes/1468/ example] and comments [http://waterpigs.co.uk/notes/1482/ example].

== Validating ==
* '''[http://indiewebify.me/validate-h-entry/ indiewebify.me h-entry validator]''' parses [[h-entry]] markup, finds common errors and makes suggestions for things to add, with code samples
* '''[http://shrewdness.waterpigs.co.uk/test/ Shrewdness h-entry/h-feed validator]''' shows how shrewdness interprets+displays h-entries, with original source and interim formats, works for single h-entries and feed pages

{{h-spec-section-validating}}

== Backward Compatibility ==
=== Publisher Compatibility ===
For backward compatibility, you may wish to use classic [[hAtom]] classnames in addition to the more future-proof h-entry properties, for example:

<source lang=html4strict>
<div class="h-entry hentry">
<h1 class="p-name entry-title">My great blog post</h1>
</div>
</source>

=== 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-entry" is found, don't look for an "hentry" on the same element.

Compat root class name: <code id="hentry">hentry</code><br/>
Properties: (parsed as '''p-''' plain text unless otherwise specified):

* <code>entry-title</code> - parse as '''<code>p-name</code>'''
* <code>entry-summary</code> - parse as '''<code>p-summary</code>'''
* <code>entry-content</code> - parse as '''<code>e-content</code>'''
* <code>published</code> - parse as '''dt-'''
* <code>updated</code> - parse as '''dt-'''
* <code>author</code> - including compat root <code>vcard</code> in the absence of <code>h-card</code>
* <code>category</code>

=== Compat FAQ ===
==== What about rel bookmark ====
Also asked as: ''Why use an h-entry u-url u-uid for permalinks when I have [[rel-bookmark|rel=bookmark]]?''

A: tl;dr: use <code>class="u-url u-uid"</code> instead of <code>rel=bookmark</code> for post permalinks because it's simpler (fewer attributes), and works better across contexts (permalink page, recent posts on home page, collection of posts on archive pages).

rel=bookmark was the old [[hAtom]] way of marking up permalinks. Since then two factors have contributed to reducing use of rel inside microformats:
* rel by typically* document scoped in [[HTML5]] - thus making it inappropriate for use in microformats that are aggregated, e.g. a collection of posts on a home page or in monthly archives.
* it is easier to always use class names for properties. When formats use two (or more!) attributes in HTML to specify properties, confusion results in lower data quality (of the markup and thus the stuff that is marked up). Thus per the microformats [[principle]] of [[simplicity]], in [[microformats2]] we only use class names for properties.

<nowiki>*</nowiki> even though rel=bookmark in particular is article-element / sectioning scoped in HTML5[http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#link-type-bookmark], it's a detail that typical authors are not going to remember, and thus it's not good to depend on it for any kind of format.

==== Why rename entry-title entry-summary entry-content ====
The <code>entry-*</code> classnames in classic [[hAtom]] were prefixed as such due to concerns about vocabulary overlap with the title (as in job title, completely separate semantic) property in [[hCard]] and the summary property in [[hCalendar]] (see: [[hatom-faq#Could_hAtom_instead_use_title_content_and_summary|hAtom FAQ]]).

Following the [[simplicity]] principle, in microformats2, the aforementioned vagueness of '''title''' is dealt with by removing it. As '''name''' is now used consistently across all vocabularies as the property which “names” the microformat, it makes sense to use it to mark up the name of a post.

Likewise, adding entry- to '''summary''' doesn’t add any useful information, and in practice there have been no problems with blog post summaries overlapping with entry summaries, so it makes sense to simplify to '''summary'''. The same applies to '''entry-content''' simplified to '''content'''.

See also: [http://krijnhoetmer.nl/irc-logs/microformats/20120830#l-128 2012-08-30 IRC conversation].

== Related Work ==
Work that re-uses or builds upon h-entry:
* [https://mailpile.pagekite.me:8080/p/Open_Message_Format Mailpile Open Message Format] is using h-entry with structured properties, e.g. p-author h-card.

== Background ==
This work is based on the existing [[hAtom]] microformat, and extensive selfdogfooding in the [http://indiewebcamp.com indie web camp] community.

== See Also ==
* [[h-feed]]
* [[microformats2]]
* [[microformats2-parsing]]
* [[h-geo]]
* [[hCard]]

[[Category:Draft Specifications]]

h-event-brainstorming

2013-10-22T22:53:20Z

Bcomnes: Added my 2 cents

{{stub}}

This page is for documenting ideas for extending and adding to [[h-event]]
__TOC__
== RSVP ==
* [[rsvp]] / [[rsvp-brainstorming]]

== Invitations ==
Many existing event sites on event pages show the list of people invited (e.g. Facebook, Google+).

It makes sense that independent h-event publishers would also want to list people that have been invited.

Use-case: the use case is of course sending notifications of invitations, which could be done with [[webmention]]. Webmention however requires that the "source" page link (in this case the event post permalink) to the "target" page (the person's home page that's being invited).

Some possibilities for markup inside the h-event:
* <code>rel=invitee</code> (directly on the hyperlink to someone being invited, works only on event permalink page)
* <code>u-invitee</code> (directly on the hyperlink to someone being invited, works as an h-event property any place the h-event shows up)
* <code>p-invitee h-card</code> (on the h-card of the invitee, also works as an h-event property any place the h-event shows up)

Then the event invitation/RSVP protocol overall:
* '''A publishes event, invites B & C'''. Person A publishes an event post which explicitly lists invitations to people B & C (hyperlinked) and marks it up accordingly (see above)
* '''A sends webmentions to B & C'''. Person A's site sends webmentions to B & C with the "source" as the event post permalink, and the "target" being their home page (as hyperlinked from the event post).
* '''B & C receive webmention'''. Person B & C's sites receive the webmention, check that the "source" links to the "target", and then provide notification to their users (e.g. perhaps in a recent activity page on their site).
* '''B & C post RSVPs'''. Person B & C's site provide them with a UI to post an [[RSVP]]. They then post [[RSVP]]s replying to the event post specifically noting whether they can attend, maybe, or not.
* '''B & C send webmentions back to A'''. Person B & C's site sends a webmention to Person A's event post, with the "source" being the RSVP reply permalink, and the "target" being the event post.
* '''A receives RSVP webmentions, updates event'''. Person A's site receives the webmention(s), checks to makes sure the "source" links to the "target" on each, and then updates the event post with the RSVPs accordingly.

== Feedback ==
* Looks great to me! From a uF point of view, I think this covers it. Is this treading new ground in terms of sending webmentions without a reply context? I know some people accept webmentions to their root domain, and other do not as of now. --[[User:Bcomnes|Bcomnes]] 22:53, 22 October 2013 (UTC)

== See Also ==
* [[h-event]]
* [[microformats2]]

irc-people

2013-08-15T23:19:56Z

Bcomnes: Added me

A list of [[irc|IRC]] regulars, sorted by nick (with full name optionally in parentheses), and their normal timezones (winter/summer).

* {{irc user|???|Andrew Jaswa|Ajaswa|-0500|}}
* {{irc user|???|Bryan Rieger|BryanRieger|+0000|}}
* {{irc user|???|Chris Cressman|Chris_Cressman|-0500/-0400|}}
* {{irc user|???|Darren Bounds|DBounds|-0500|}}
* {{irc user|???|David Gratton|Ddonat|-0800/-700|}}
* {{irc user|???|Deep Text|DeepText|-0800/-0700|}}
* {{irc user|???|Mark Mansour|MarkNormanFrancis|+0000/+0100|}}
* {{irc user|???|Mark Mansour|Mark_Mansour|+1100|}}
* {{irc user|???|Martin Czura|Maddiin|+0100|}}
* {{irc user|???|Matt Bowen|MattBowen|-0500/-0400|}}
* {{irc user|???|Mattis Manzel|MattisManzel|+0100/+0200|}}
* {{irc user|???|Nater Kane|Naterkane|-0500|}}
* {{irc user|???|Steve Farrell|Smackman|-0800/-0700|}}
* {{irc user|???|Thierry Marianne|Thierrymarianne|+0100/+0200|}}
* {{irc user|???|William Lawrence|Veeliam|-0800/-0700|}}
* {{irc user|adactio|Jeremy Keith|Adactio|+0000|}}
* {{irc user|AdamBallai||Adam_Ballai|-700/-700|}}
* {{irc user|AdamCraven||Adam_Craven|+0000|}}
* {{irc user|Alenonimo||Alenonimo|-0300|}}
* {{irc user|AlexanderGraf||Alexander_Graf|+0100|}}
* {{irc user|aloneone||Tomasino|-0500|}}
* {{irc user|Amanuel||AmanuelTewolde|-0500/-0400|}}
* {{irc user|amette||Amette|+1000|}}
* {{irc user|AmirGuindehi||Amir_Guindehi|+1000|}}
* {{irc user|amodal1||Amodal1|-0500/-0600|}}
* {{irc user|andr3||Andr3|+0000|}}
* {{irc user|AndrewDisley||AndrewDisley|+0000|}}
* {{irc user|Andrii||Andrii_Ponomarov|+0300|}}
* {{irc user|angelogladding||AngeloGladding|-0800/-0700|}}
* {{irc user|anselxyz||AnselHalliburton|-0800/-0700|}}
* {{irc user|Ashe||Ashe_Dryden|-600|}}
* {{irc user|Atamido||Atamido|-0600/-0500|}}
* {{irc user|ax||Axelator|-0700|}}
* {{irc user|Barce||Barce|-0800/-0700|}}
* {{irc user|Baristo||Tyler_Roehmholdt|-0800/-0700|}}
* {{irc user|barnabywalters||BarnabyWalters|+0000|}}
* {{irc user|Belling||Belling|-0800/-0700|}}
* {{irc user|BenjaminCarlyle||BenjaminCarlyle|+1000|}}
* {{irc user|BenWard||Ben_Ward|-0800/-0700|}}
* {{irc user|bergie||HenriBergius|+0200/+0300|}}
* {{irc user|bewest||BenWest|-0800/-0700|}}
* {{irc user|bkdelong||B.K._DeLong|-0500/-0400|}}
* {{irc user|blueace||Robert|+0100|}}
* {{irc user|bluesmoon||BluesMoon|+0530|}}
* {{irc user|BobChao||BobChao|+0800|}}
* {{irc user|BobJonkman||Bob_Jonkman|-0500/-0400|}}
* {{irc user|boblet||Oli|+0900|}}
* {{irc user|boneill||Boneill|+0000|}}
* {{irc user|bret||bcomnes|-0800/-0700|}}
* {{irc user|briansuda||Brian|+0000|}}
* {{irc user|bringo||TimT|-0800/-0700|}}
* {{irc user|Briski||Briski|+0000|}}
* {{irc user|broady||ChrisBroadfoot|+1000|}}
* {{irc user|BryanL||BryanL|-0500/-0400|}}
* {{irc user|Bug-E||Bug-E|+0200|}}
* {{irc user|carlamagpie||CarlaHufstedler|-0500/-0400|}}
* {{irc user|cbarrett||Colin_Barrett|-1000|}}
* {{irc user|cdevroe||ColinDDevroe|-0500/-0600|}}
* {{irc user|cgriego||Cgriego|-0600/-0500|}}
* {{irc user|charles_r||CharlesRoper|0000/+0100|}}
* {{irc user|Charl||Charlvn|+0200/+0200|}}
* {{irc user|ChiefRA||ChiefRA|+0200|}}
* {{irc user|cks||ChristopherStJohn|-0600/-0500|}}
* {{irc user|clioweb||JeremyBoggs|-5000/-4000|}}
* {{irc user|Cloud||Cloud|+0000|}}
* {{irc user|Cognizance||Cognizance|-0800/-0700|}}
* {{irc user|colares||Colares|-0300|}}
* {{irc user|corygwin||CoryGwin|-0500/-0600|}}
* {{irc user|cruster||Cruster|+0200|}}
* {{irc user|csarven||Csarven|-0500/-0400|}}
* {{irc user|ctb||ChrisBrentano|-0800/-0700|}}
* {{irc user|DanC||DanC|-0600/-0500|}}
* {{irc user|DanielBurka||DanielBurka|-0400|}}
* {{irc user|danieljohnlewis||DanielJohnLewis|0000|}}
* {{irc user|danja||DannyAyers|+0100/+0200|}}
* {{irc user|davecardwell||Dave_Cardwell|+0000|}}
* {{irc user|DavidMead||DavidMead|-0400|}}
* {{irc user|davidrussell||DavidRussell|-0600/-0500|}}
* {{irc user|ddfreyne||DenisDefreyne|+0100/+0200|}}
* {{irc user|deanero||DeanEro|-0800/-0700|}}
* {{irc user|DerrickPallas||DerrickPallas|-0800/-0700|}}
* {{irc user|dglazkov||DimitriGlazkov|-0600/-0500|}}
* {{irc user|DiegoBudny||DiegoBudny||}}
* {{irc user|DKerzman||DKerzman|-0600|}}
* {{irc user|dkubb||Dan_Kubb|-0800/-0700|}}
* {{irc user|dotjay||Dotjay|+0000|}}
* {{irc user|dreamisle||Dreamisle|-0500|}}
* {{irc user|DrErnie||DrErnie|-0800/-0700|}}
* {{irc user|drewinthehead||DrewMcLellan|+0000/+0100|}}
* {{irc user|droob||DrewBell|-0600/-0500|}}
* {{irc user|dzach||DimitriosZachariadis|+0200/+0300|}}
* {{irc user|edsu||Ed_Summers|-0500/-0400|}}
* {{irc user|Enric||Enric|-0800/-0700|}}
* {{irc user|epicurious||Epicurious|+0000/+0100|}}
* {{irc user|ethicaljunction||Ket_Majmudar|+0100|}}
* {{irc user|evanpro||Evan|-0500|}}
* {{irc user|ewelker||EdwardWelker|-0500|}}
* {{irc user|e_s_p||Evan|-0500|}}
* {{irc user|factoryjoe||ChrisMessina|-0800/-0700|}}
* {{irc user|Fil||Fil|+0200|}}
* {{irc user|Finke||CFinke|-0700/-0600|}}
* {{irc user|Florian Beer||Azathoth|+1000|}}
* {{irc user|Foundation||FoundAtion|-0800|}}
* {{irc user|frantic0||Francisco_Bernardo|+0100/+0200|}}
* {{irc user|friedcell||MarkoMrdjenovic|+0100/+0200|}}
* {{irc user|garethr||GarethR|+0000/+0100|}}
* {{irc user|georgebrock||GeorgeBrock|+0000/+0100|}}
* {{irc user|German||GermanMartinez|-0500|}}
* {{irc user|glebleu||Guillaume_Lebleu|-0800|}}
* {{irc user|Grantbow||Grantbow|-0800/-0700|}}
* {{irc user|gravitas||ScottRozic|-0500/+0100|}}
* {{irc user|Griffin||Griffin|-0600/-0500|}}
* {{irc user|Guy Fraser||Aubergine10|+0100/+0000|}}
* {{irc user|haibtdt|Bui Thanh Hai|Haibtdt|+????|}}
* {{irc user|HenrichP||HenrichPoehls|+0100|}}
* {{irc user|Hixie||IanHickson|-0800/-0700|}}
* {{irc user|hlb||Hlb|+0800-0700|}}
* {{irc user|hober||EdwardOConnor|-0800/-0700|}}
* {{irc user|ichigo||Ichigo|+1000|}}
* {{irc user|illustir||Alper|+0100|}}
* {{irc user|imdane||Dane|-0600/-0500|}}
* {{irc user|inkbase||Inkbase|-0800/-0700|}}
* {{irc user|iSRAELi||iSRAELi|+0200|}}
* {{irc user|iwaim||IwaiMasaharu|+0900|}}
* {{irc user|IZO||Izo||}}
* {{irc user|Jabz||Jabz|+0000|}}
* {{irc user|JamieKnight||JamieKnight|+1000/0000|}}
* {{irc user|jaymyers||JayMyers|-0600/-0500|}}
* {{irc user|jcgregorio||JoeGregorio||}}
* {{irc user|jcw9||WizardIsHungry|-0500/-0400|}}
* {{irc user|jeffmcneill||JeffMcNeill|-1000|}}
* {{irc user|JesseRodgers||jrodgers|-0500|}}
* {{irc user|jesudas nadar||jesudasjj|+0530|}}
* {{irc user|jimbojw||JimboJW|-0600/-0500|}}
* {{irc user|jkridner||JasonK|-0600/-0500|}}
* {{irc user|JonathanMalek||JonathanMalek|-0800/-0700|}}
* {{irc user|JonathanTNeal||JonathanTNeal|-0800/-0700|}}
* {{irc user|jonnay||Jonathan_Arkell|-0700/0600|}}
* {{irc user|josephholsten||JosephHolsten|-0600/-0500|}}
* {{irc user|julianstahnke||JulianStahnke|+0000|}}
* {{irc user|jurajsivak||Juraj|+0100|}}
* {{irc user|kapowaz||Kapowaz|+0000/+0100|}}
* {{irc user|kerihenare||Keri_Henare|+1200|}}
* {{irc user|kevburnsjr||KevBurnsJr|-0800|}}
* {{irc user|KevinMarks||KevinMarks|-0800/-0700|}}
* {{irc user|kingryan||RyanKing|-0800/-0700|<a href="http://theryanking.com/blog/archives/2006/04/19/office-hours/"> Office hours</a>: Wednesday, 21:00 UTC}}
* {{irc user|Lachy||Lachlan_Hunt|+1000/+1100|}}
* {{irc user|levitation[A]||Levitation|+0200/+0300|}}
* {{irc user|linmic||Linmic|+0800-0700|}}
* {{irc user|Loiseau2nuit||Loiseau2nuit|+0100|}}
* {{irc user|madness||MarkNg|+0000/+0100|}}
* {{irc user|MaryBeth||marybeth|-0500|}}
* {{irc user|mastaYoda||LarsStrojny|+0100|}}
* {{irc user|Matthias Kluth||Groningen|+0100|}}
* {{irc user|McNulty||CiaranMc|+0000/+0100|}}
* {{irc user|MicroAngelo||MicroAngelo|+0000/+0100|}}
* {{irc user|mkaply||MikeKaply|-0600/-0500|}}
* {{irc user|mmc|Michael McCracken|Mike|-0800/-0700|}}
* {{irc user|monkinetic/redmonk||SteveIvy|-0700|}}
* {{irc user|mwte||MWTE|+0000/+0100|}}
* {{irc user|nambor||RobManson|+1000|}}
* {{irc user|NatBat||Natalie_Downe|+0000|}}
* {{irc user|nelix||Nelix|+1000|}}
* {{irc user|neuro||Neuro|+0000/+0100|}}
* {{irc user|niekie||Niekie|+0100/+0200|}}
* {{irc user|ntoll||NTollervey|+0000/+0100|}}
* {{irc user|pawlik||Pawlik|+0100/+0200|}}
* {{irc user|pembertona||Andy_Pemberton|-0500/-0400|}}
* {{irc user|pfefferle||Pfefferle|+0100/+0200|}}
* {{irc user|Phae||Phae|+0000/+0100|}}
* {{irc user|pius|Pius Uzamere|pius|+0500|}}
* {{irc user|pjkix||PJKix|-0800/-700|}}
* {{irc user|plaes||PriitLaes|+0200/+0300|}}
* {{irc user|pnhChris||ChrisCasciano|-0500/-0400|}}
* {{irc user|Politoed||Hugopeixoto|+0000/+0100|}}
* {{irc user|popov||PetarPopov|-0800/-0700|}}
* {{irc user|pseudowish||Lauren_Scime|-0800/-700|}}
* {{irc user|qid||DavidOsolkowski|-0500|}}
* {{irc user|RCanine||RCanine|-0500/-0400|}}
* {{irc user|Remi||Remi|-0500/-0400|}}
* {{irc user|riah||ZachCarter|-0500/-0400|}}
* {{irc user|RobertBachmann||RobertBachmann|+0100/+0200|Office hours: <s>Wednesday, 18:00-20:00 UTC</s>Currently no office hours}}
* {{irc user|RobLinton||RobLinton|-0800/-0700|}}
* {{irc user|Ron Kok||Ronnos|+0000|}}
* {{irc user|Salve||ScottThorpe|-0800/-0700|}}
* {{irc user|samj||SamJohnston|+0100/+0200|}}
* {{irc user|Savell||Savell_Martin|+0000/+0000|}}
* {{irc user|sazbean||SarahWorsham|-0500/-0400|}}
* {{irc user|sebheath||sebheath|-0500/-0400|}}
* {{irc user|shaners||Veganstraightedge|-0800/-0700|}}
* {{irc user|SinDoc||SinDoc|+0100/+0200|}}
* {{irc user|snelle||ScottNelle|-0500/-0400|}}
* {{irc user|Snowden||Dana_Benson|-0800/-0700|}}
* {{irc user|SpikeUK||SpikeUK|+0000/+0100|}}
* {{irc user|steve918||Steven_Osborn|-0700/-0800|}}
* {{irc user|SteveGanz||Steve_Ganz|-0800/-0700|}}
* {{irc user|Stii||Stii|+0200 GMT|}}
* {{irc user|SuperPhly||SuperPhly|-600/-500|}}
* {{irc user|surial||ReinierZ|+0100 GMT|}}
* {{irc user|syedsrahman||SyedSRahman|+0530|}}
* {{irc user|sym||LynX|+0100|or better "lynX" on <a href="http://about.psyc.eu">PSYC</a>}}
* {{irc user|taaz||DavidLehn|-0500/-0400|}}
* {{irc user|tantek||Tantek|-0800/-0700|}}
* {{irc user|tbmartin||tbmartin|-0800/-0700|}}
* {{irc user|theanxy||Wojciech|+0100/+0200|}}
* {{irc user|thejbf||TheJbf|+0100/+0200|}}
* {{irc user|themattharris||themattharris|-0800/-0700|}}
* {{irc user|TheSisb||TheSisb|-0800/-0700|}}
* {{irc user|thomasknoll||Thomasknoll|-0800|}}
* {{irc user|thuddwhirr||thuddwhirr|-0800/-0700|}}
* {{irc user|tl||ThomasLoertsch|+0100/+0200|}}
* {{irc user|tobyink||TobyInk|+0000/+0100|}}
* {{irc user|tommorris||TomMorris|+0000/+0100|}}
* {{irc user|trodrigues||Trodrigues|+0000|}}
* {{irc user|trovster||Trovster|-0800/-0700|}}
* {{irc user|V-I-P||V-I-P|+0100/+0200|}}
* {{irc user|vadania||Vadania|-0600/-0700|}}
* {{irc user|vant||Vant|+0900|}}
* {{irc user|vensilver||venkateswaran|+5.30 GMT|}}
* {{irc user|victor||Victor|+0100/+0200|}}
* {{irc user|VoodooChild||KrissWatt|+0000/+0100|}}
* {{irc user|weborganics||WebOrganics|+0100|}}
* {{irc user|whafro||JacksonWilkinson|-0500/-0400|}}
* {{irc user|WhiskeyM||Richard_Conyard|+0000|}}
* {{irc user|woodss||StevenWoods|+0000 GMT|}}
* {{irc user|xtof_fr||ChristopheDucamp|+0000/+0100|}}
* {{irc user|yakk||Ianloic|-0800/-0700|}}
* {{irc user|zil||PeterHellberg|+0100|}}
* {{irc user|zimbatm||ZimbaTm|+0100|}}
* {{irc user|zkv||Kiryl_Zhybul|+0400|}}

Inactive:
* [[mfbot]] - a bot which logs all edits to this wiki. It appends a number with a '+' or '-' sign, to indicate the number of characters added or removed as a result of the edit.