posted on Thursday, July 28, 2005 9:23 AM
by
paul
Getting ATOM
Ever since the the IETF Atom syndication format specification has been declared ready for implementation (more), the demand for Atom 1.0 support by the Feed Validator has been high.
As progress on implementing the Atom 1.0 test cases has reached the point where the feed validator is rarely outright misleading any more, it is time for a wider exposure. At this point, the Feed Validator will accept bug reports on Atom 1.0 support
Particularly be on the look out for the following:
- Errors being reported as warnings, and vice versa
- Additional places where warnings would be helpful
- Unclear or confusing advice
As always, feel free to join us on the feedvalidator-users discussion list.
After a small bit of work today, DasBlog 1.8 will (does) produce valid Atom 1.0 feeds. This is response to the bakededness of Atom 1.0 and Sam's desire to deprecate 0.3. DasBlog won't produce Atom 0.3 anymore (it was always marked under "experimental' anyway) so when you upgrade to 1.8 your Atom feed will upgrade automatically.
We do, as always, produce valid RSS 2.0 and now Atom 1.0. Here's a list of known Atom 1.0 consumers
Atomic RSS
Suppose you’re generating an RSS feed, or you’re thinking about generating an RSS feed, and you’re wondering how Atom fits into the picture. The future of technology is hard to predict, but there’s a good way to hedge your bets. You can generate an RSS feed and, by following a few simple rules, be really sure that there’s a 100%-equivalent Atom 1.0 feed, so that if you’re generating both, they’ll be in sync, and if you need to switch back and forth, it’s just a matter of changing a few strings. Let’s call this future-proofed flavor “Atomic RSS”. It turns out that using Atomic RSS is a Good Thing anyhow, because it will help software in general and news aggregators in particular produce better results.
ATOM is
getting traction and gaining momentum, hope to see
DotNetJunkies upgrade to
ATOM 1.0 real soon!