feed-brainstorming: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(draft)
 
(previous efforts)
Line 6: Line 6:


This page is for documenting [[brainstorming]] proposals based on analysis of real world [[feed-examples]] and previous [[feed-formats]].
This page is for documenting [[brainstorming]] proposals based on analysis of real world [[feed-examples]] and previous [[feed-formats]].
== previous efforts ==
* [[blog-description-brainstorming]]
* [[blog-description-format-brainstorming]]


== h-feed ==
== h-feed ==

Revision as of 21:24, 3 October 2012

This article is a stub. You can help the microformats.org wiki by expanding it.

<entry-title>feed brainstorming</entry-title>

Part of the feed microformat development effort per the process.

This page is for documenting brainstorming proposals based on analysis of real world feed-examples and previous feed-formats.

previous efforts

h-feed

In microformats2 simply using a root class name like class="h-feed" on an element that contains all the h-entry elements would be sufficient to create a feed microformat object that can be parsed with all the h-entry elements as children.

root class name: h-feed

example:

<div class="h-feed">
...
  <div class="h-entry"> ... entry 1 and properties ... </div>
  <div class="h-entry"> ... entry 2 and properties ... </div>
...
</div>

Serves as a way of containing separate sets of related/grouped/sequential h-entry elements on a single page. With HTML ID attributes on the h-feed elements, tools can reference different feeds on the same page and operate on them individually or collectively.

see also

next steps

  • try the brainstorming proposal(s) on real world content and gather experience/feedback from doing so
  • with experience and rough consensus, write-up a simple/minimal h-feed microformats similar and perhaps adjacent to the documentation of the h-entry microformat.