h-feed: Difference between revisions
Jump to navigation
Jump to search
(→Examples in the wild: props) |
(Parsing with fallback) |
||
| Line 19: | Line 19: | ||
* http://tantek.com/ uses h-feed with p-name and p-author properties and child h-entry posts. | * http://tantek.com/ uses h-feed with p-name and p-author properties and child h-entry posts. | ||
* ... | * ... | ||
== Parsing == | |||
When parsing a page for an h-feed, do so per [[microformats2]]. | |||
Fallback: | |||
If there is no explicit "h-feed" element, implementations may: | |||
* Treat the <code><title></code> of the page as the p-name | |||
* Use http://indiewebcamp.com/authorship to discover authorship of posts. | |||
* Treat top level h-entry elements as items in the feed. | |||
== See Also == | == See Also == | ||
Revision as of 18:25, 28 June 2013
This article is a stub. You can help the microformats.org wiki by expanding it.
h-feed is a microformats2 experiment with a top level feed object to contain h-entry posts.
From experience with hAtom, it's not clear that there's actually a need (use-case) for a top level feed, but for those that wish to experiment with it, here it is.
root class name: h-feed
properties:
- p-name - name of the feed
- p-author - author of the feed, optionally embed an h-card Main article: h-card
- u-url - URL of the feed
- u-photo - representative photo / icon for the feed
children:
- nested h-entry objects representing the items of the feed
Examples in the wild
- http://tantek.com/ uses h-feed with p-name and p-author properties and child h-entry posts.
- ...
Parsing
When parsing a page for an h-feed, do so per microformats2.
Fallback:
If there is no explicit "h-feed" element, implementations may:
- Treat the
<title>of the page as the p-name - Use http://indiewebcamp.com/authorship to discover authorship of posts.
- Treat top level h-entry elements as items in the feed.