The ''h-entry'' marks up a post: a note, an article, ...

h-entry

The following is literally copied from the respective microformats.org webpage

p-name:
entry name/title
p-summary:
short entry summary
e-content:
full content of the entry
dt-published:
when the entry was published
dt-updated:
when the entry was updated
p-author:
who wrote the entry, optionally embedded h-card(s)
p-category:
entry categories/tags
u-url:
entry permalink URL
u-uid:
universally unique identifier, typically canonical entry URL
p-location:
location the entry was posted from, optionally embed h-card, h-adr, or h-geo
u-syndication:
URL(s) of syndicated copies of this post. The property equivalent of rel-syndication (example)
u-in-reply-to:
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 (reply-context) (example)
p-rsvp:
(enum, use element or value-class-pattern)

h-entry vs. hentry (hAtom)

microformats.org recommends to mark up both with version 1 and version 2 tags. The following table shows the correspondence between the two standards.

h-entry tag hentry tag
p-name entry-title
p-summary entry-summary
e-content entry-content
dt-published published
dt-updated updated
p-author author
u-url bookmark
p-category n.a., see rel="tag"
u-uid
p-location
u-syndication
u-in-reply-to
p-rsvp