It seems to me that both hAtom and hDOAP present limitations of a sort when it comes to providing feeds for software updates. On the one hand with hAtom, you have a generic microformat with no way of identifying any content beyond it merely being feed content and with hDOAP, you have no mechanism for providing update information. Do you see the gap I'm trying to show?
-Sam On Sat, Nov 22, 2008 at 4:59 AM, Toby A Inkster <[EMAIL PROTECTED]> wrote: > If you're talking about their use of class="ot-logmessage" etc, then no, > that isn't a Microformat[1]. > > It looks to me like the reason those particular classes are present in the > project updates Atom feed is that the feed is generated by the same code > that generates the project updates HTML file, where these classes seems to > be mainly present as hooks for CSS and Javascript. > > If you're looking for a way to markup feeds, then use hAtom[2]. If you're > looking for a way to markup software projects, then perhaps you should look > at hDOAP[3]. > > ____ > 1. http://microformats.org/wiki/Category:Specifications > http://microformats.org/wiki/Category:Draft_Specifications > 2. http://microformats.org/wiki/hAtom > 3. http://purl.org/stuff/hdoap/profile > > -- > Toby A Inkster > <mailto:[EMAIL PROTECTED]> > <http://tobyinkster.co.uk> > > > > _______________________________________________ > microformats-discuss mailing list > microformats-discuss@microformats.org > http://microformats.org/mailman/listinfo/microformats-discuss > _______________________________________________ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss