View source for h-feed

{{stub}}

'''<dfn>h-feed</dfn>''' 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|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

== Use Cases ==
* Generate an Atom feed
** This seems like a legacy use-case, not sufficient to actually justify h-feed.

* Feed per channel of content - needs a name
** "I will have a feed per tag (channel) so I want to name them." - Sandeep Shetty in #indiewebcamp
** It appears there is some desire to create separate feeds for an indieweb site for separate subsets of content, and name them <em>explicitly</em> accordingly. This presents a need for a container object for the h-entry elements, where the container itself can have a name. This is a potential interesting use-case for an explicit 'h-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 <code>&lt;title&gt;</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 ==
* [[h-entry]]
* [[microformats2]]
* [[hAtom]]