By my read, today is August 46th or thereabouts, which I guess
early August, so I’ve gone ahead and made the
Feed Validator issue
deprecation warnings whenever it encounters Atom 0.3 feeds
(example). No other code changes were made. Feeds
that worked yesterday with any given combination of tools should
work exactly the same way today.
From here on out, changes to the Feed Validator will be made
with wanton disregard to the impact of validation of Atom 0.3
feeds. By the end of the year, the plan is still to remove
support for Atom 0.3 entirely.
Glad to see the Ophelia doesn’t seem to be impacting you too badly.
So Google has blog search. Summary: It’s fast, it’s reasonably complete, it’s stripped-down in the typical Google style, the result ranking needs work, the time window is way too deep. They’re also providing feeds, which is good, but the feeds are...
Robert, this is the Internet, the land where betas last forever, and all feed formats are above average.
More seriously, yes, while there are a few unimplemented tests and undoubtedly are some bugs in outlying areas, we are well beyond the point where I expect that there are large classes of valid feeds being marked invalid or invalid feeds being marked valid.
Given that Atom 0.3 is now deprecated, I’ve finally gotten around to creating an Atom 1.0 feed for this blog. Yay! MovableType users might be interested in my Atom 1.0 template. Just replace “Josh Staiger” inside the rights element of the feed with...
Je maintenais jusqu’à présent un fil de nouvelles au format Atom 0.3, bien que celui-ci soit deprecated depuis quelques temps déjà. La raison principale était le mauvais support du format officiel Atom 1.0 dans certains lecteurs de nouvelles, dont...
"Atom Publishing Protocol" and "Atom API": not synonyms
Back in 2003 there was a lot of buzz surrounding the (then new) Atom syndication format and its sister, the Atom API. Mark Pilgrim published an article about the API on XML.com, it was implemented in some high-profile applications (including...