Scott Hanselman

DasBlog 1.8 will/does produce Atom 1.0 valid documents

July 28, 2005 Comment on this post [8] Posted in DasBlog
Sponsored By

[Valid Atom 1.0]

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 if you care.

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

facebook bluesky subscribe
About   Newsletter
Hosting By
Hosted on Linux using .NET in an Azure App Service
July 28, 2005 13:30
Hi Scott the link goes out to an linux server (case sensitiv K,A,C):

http://www.intertwingly.net/wiki/pie/KnownAtomConsumers

Daniel
July 28, 2005 19:47
> was always marked under "experimental' anyway

Still is?
July 28, 2005 20:08
When will 1.8 be complete? I'm champing at the bit. As always, thanks for your effort.
July 29, 2005 0:25
Good point Sam. I've moved it and put in a 301 Moved so the permalink isn't invalid.
July 29, 2005 8:01
Now if only dasBlog produced valid HTML as well... :)
July 30, 2005 10:36
DasBlog 1.8RC0
http://sourceforge.net/project/showfiles.php?group_id=127624
August 03, 2005 21:49
Ironically, your atom 1.0 feed does not validate, and this is the entry that's breaking validation:

line 253, column 2: Missing textual content

http://feedvalidator.org/check.cgi?url=http%3A%2F%2Fwww.hanselman.com%2Fblog%2FSyndicationService.asmx%2FGetAtom

I believe this was a problem with DasBlog's Atom 0.3 support, I noticed that periodically, I'd get your posts without any content.
August 04, 2005 2:53
Gordon, that is (was) weird. I've fixed it and checked in a change that should handle the case where XHTML isn't cool and instead include a content type="html" chunk.

Comments are closed.

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.