I will try this again giving a scenario...
Joe Cool, adept coder, releases a project, AlphaBUG, to the web on the
code hosting site, www.attaboy.com. Every time Joe releases a new
update, he also publishes an RSS/Atom article describing. The problem
for Joe, who wants to empower AlphaBUG's
Dude, you are giving me a headache.
On Sat, Nov 22, 2008 at 9:55 AM, David Janes [EMAIL PROTECTED] wrote:
On Sat, Nov 22, 2008 at 9:09 AM, Samuel Richter [EMAIL PROTECTED] wrote:
It seems to me that both hAtom and hDOAP present limitations of a sort
when it comes to providing feeds for
Please excuse me if this is not the appropriate mailing list or if
this has already been discussed (the archives have no search feature.)
It seems that Google Code is using some sort of microformat in their
project feeds. I happened to look at the Atom source for a given
project's update feed
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
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
On Sat, Nov 22, 2008 at 9:09 AM, Samuel Richter [EMAIL PROTECTED] wrote:
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
On [Nov 22], at [ Nov 22] 7:09 , Samuel Richter wrote:
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
