Comments on: Correct RSS date format http://tomchikoore.com/2008/02/04/correct-rss-date-format/ Mon, 12 Sep 2011 12:07:13 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Praveena http://tomchikoore.com/2008/02/04/correct-rss-date-format/comment-page-1/#comment-28 Praveena Thu, 26 Jun 2008 12:10:53 +0000 http://tomchikoore.wordpress.com/?p=20#comment-28 Hi , Even i tried to write Feeds for my website (http://exploreneedy.com/). But i am also facing same problem with date time format. Can i write Data time in this: Thu, 26 Jul 2008 13:00:00 -0530 I am confused whats wrong in the above format. Here is my feeds: http://exploreneedy.com/explore-feed.xml Thanks, Hi ,
Even i tried to write Feeds for my website (http://exploreneedy.com/). But i am also facing same problem with date time format.

Can i write Data time in this:
Thu, 26 Jul 2008 13:00:00 -0530

I am confused whats wrong in the above format.

Here is my feeds:

http://exploreneedy.com/explore-feed.xml

Thanks,

]]> By: Elliot http://tomchikoore.com/2008/02/04/correct-rss-date-format/comment-page-1/#comment-26 Elliot Tue, 05 Feb 2008 16:51:55 +0000 http://tomchikoore.wordpress.com/?p=20#comment-26 Dealing with date formats when parsing "RSS/ATOM-in-the-wild" can be a challenging task, due to both the fragmented nature of the RSS/ATOM standards and the variety of date formats one could theoretically expect to find in feeds (RFC 822, W3CDTF, RFC3339, etc.). There's also malformed date formats, time zone abbreviations, and other minor items which can further muddy the date parsing/validation process. When we were building our RSS parsing/serialization engine, dates were probably one of the most tedious validation aspects we ran into (RSS/ATOM extensions and all their potential varying forms being the second). "Really Simple" just isn't really the case if you're parsing feeds -- maybe if you're just subscribing to them! :) Dealing with date formats when parsing “RSS/ATOM-in-the-wild” can be a challenging task, due to both the fragmented nature of the RSS/ATOM standards and the variety of date formats one could theoretically expect to find in feeds (RFC 822, W3CDTF, RFC3339, etc.). There’s also malformed date formats, time zone abbreviations, and other minor items which can further muddy the date parsing/validation process. When we were building our RSS parsing/serialization engine, dates were probably one of the most tedious validation aspects we ran into (RSS/ATOM extensions and all their potential varying forms being the second). “Really Simple” just isn’t really the case if you’re parsing feeds — maybe if you’re just subscribing to them! :)

]]>