hello peter.
Anyone have any thoughts on this? While it's nice to see that someone was savvy enough about Atom to include it, in the spirit of "being the change..." and all that, it might be a good opportunity for the Atom community to be proactive in getting help to folks who might need it (and perhaps making a pitch for AtomPub if/when some of these agencies want to establish an API).
i think this is an excellent idea. it will not be easy, though, and it might benefit from some coordination for those interested in helping (i would be interested to help, maybe in coordination, and in doing some writing). http://dret.typepad.com/dretblog/atom-landscape.html is my modest attempt to keep track of what's happening in the atom landscape, but there is almost no explanation of what the standards do or propose to do. but it seems to me that certain patterns (such as the recently discussed "tombstone pattern") of using atom will probably be encountered by more and more people, and if there were some good resource that explained what atom did, what atom extensions are available or under discussion, and how to best map collections to atom, that would probably help to increase the quality of the atom feeds being made available.
maybe there is something out there that does exactly that, if that's the case, i would be interested to be pointed to it.
cheers, dret.
