blog-post-brainstorming

Discovered Elements

This section explores the information discovered from blog-post-formats.

Terminology

This section explores the terminology that should used to discuss a blog post microformat. To make it easier to talk about the various different types of teminology, DavidJanes I'm using a XML-like namespace version so we can make statements like atom:entry is roughly equivalent to rss20:feed, atom:feed/atom:link@rel=alternate is roughly equivalent to rss20:channel/rss20:link or atom:author is not equivalent to rss:entry/rss:author (because RSS 2.0 is only the definition of an email address).

Atom Terminology

See here for the spec and [[http://microformats.org/wiki/blog-post-formats#Atom here for analysis].

• atom:feed - (composite) a collection of entries plus information about them
  • atom:author - (composite) the author of a feed (may contain atom:email, atom:name, atom:uri)
  • atom:id - a permament identifier for a feed
  • atom:title - the title of an atom:entry or a atom:feed
  • atom:updated - the last time the feed was updated
  • atom:link@rel=alternate - the home page of a feed
  • atom:link@rel=self - the URI of the feed (where it can be downloaded)
  • atom:entry - (composite) an entry within the feed
    • atom:content - the feed's content
    • atom:summary - a summary of the feed's content

Obstacles

The 'content' problem

The most inconsistent element of blog posts is the content of the post themselves. For example, one webpage may only have a summary of the page, another webpage may contain the first part of the content, with a "More" button to see the rest. These inconsistencies may make it difficult to rationally define (or clarify) a set of microformat elements to achieve blog-post-feed-equivalence.

Header Tag for Entry Title?

--Bryan 14:55, 14 Aug 2005 (PDT)

Many weblog CMSes allow for concurrent publishing of entries in the following ways:

• multiple entries on a page (an "Index," monthly archive, category archive, etc. see Example)
• one entry on a page (see Example)

Early attempts at blog-post-formats have set the title of the blog post to use the h3 tag.

At least where individual entry pages are concerned (and possible including indexes and archives), I recommend using h1 for the entry title, given that the entry is by far the most important chunk of information on the page, and it's what we'd want search engines to recognize as such. In the case where the h1 was used for the site title, fears about "losing" this information should be allayed by simply including the site name in the title tag, after the title of the article / entry / post.

Whether an h3 or h1 is used is irrelevant, the semantics will be applied with classnames. This is a non-issue. --RyanKing 22:35, 18 Aug 2005 (PDT)

Possible Uses

This section is to describe possible applications for a blog post microformat

See Also

• blog-post-formats