[microformats-discuss] Evaulating RSS per the microformats principles.

David Janes -- BlogMatrix davidjanes at blogmatrix.com
Mon Aug 15 03:10:58 PDT 2005


HTML [1] provides BLOCKQUOTE and Q to cover this ground, does it not? 
Unfortunately, HTML 4.01 does not provide a "rel" attribute to better 
narrow down the exact context.

<div class="xentry">
  <h3 class="title">title of the post</h3>
   <div class="content">
    <q cite="http://example.org/musings"><a 
href="http://example.org/musings">John Doe</a> muses about a topic of 
intest</q> but, John, you suck.
   </div>
   ...
</div>

[1] http://www.w3.org/TR/html4/struct/text.html#h-9.2.2

Regards, etc...
David
http://www.blogmatrix.com

Michal Migurski wrote:
> Maybe, maybe not - it depends. There's a *ton* of momentum behind  
> serializing periodic content into RSS/Atom/whatever, from podcasts to  
> native OS-level support (see below), so arguing for yet another blog  
> post standard feels somewhat futile to me.
> 
> HOWEVER, I did mention earlier that what was definitely missing from  
> blogs in general was any sort of conversation semantics. I don't see  a 
> mention of this on blog-post-brainstorming[1] or blog-description- 
> format[2], but this seems like a necessity for blog-based, inter-site  
> conversation.
> 
> [1] http://microformats.org/wiki/blog-post-brainstorming
> [2] http://microformats.org/wiki/blog-description-format
> 
> Mail & news both have the In-Reply-To header, whose value looks like  an 
> address. Can a blog post microformat be as simple as this?
> 
> <div class="blog-post">
>     <h3 class="title">title of post</h3>
>     <p class="content">
>         <a href="http://example.org/musings" rel="in-reply-to">John  Doe 
> muses</a> about a topic of interest. I however vehemently  disagree, for 
> many reasons.
>     </p>
>     <a href="http://example.com/ramblings" rel="permanent- 
> link">permanent link</a>.
> </div>
> 
> michal migurski- mike at stamen.com
> 


More information about the microformats-discuss mailing list