h-item: Difference between revisions
(Category:Draft Specifications) |
(All properties are optional.) |
||
Line 17: | Line 17: | ||
== Properties == | == Properties == | ||
* '''<code>p-name</code>''' - item name | * '''<code>p-name</code>''' - item name | ||
* '''<code>u-url</code>''' - permalink URL | * '''<code>u-url</code>''' - permalink URL | ||
* '''<code>u-photo</code>''' - photo URL | * '''<code>u-photo</code>''' - photo URL | ||
All properties are optional. | |||
== Status == | == Status == |
Revision as of 09:01, 23 June 2013
<entry-title>h-item</entry-title> Tantek Çelik (Editor)
h-item is a simple, open format for publishing details about arbitrary items. h-item is one of several open 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.
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..
<a class="h-item" href="http://example.org/items/1">
<img src="http://example.org/items/1/photo.png" alt="" />
The Item Name
</a>
Properties
p-name
- item nameu-url
- permalink URLu-photo
- 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 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
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.