Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Confusion over RSS2.0 Spec

From: "Magnus Henriksson" <magnus.henriksson@--------.---.-------->
To: NULL
Date: 8/4/2004 11:43:00 AM
"Simon Johnson" <simon.johnson@g...> wrote in message
news:f03d8ae0.0408040123.612ec35@p......
> I'm trying to create an RSS 2.0 [1] compliant feed but I'm meeting
> some confusion over the pubDate element.
>
> It clearly states next to the pubDate that the date should be
> formatted in compliance with the specification given in RFC 822. They
> even give the following date as an example:
>
> "Sat, 07 Sep 2002 00:00:01 GMT"
>
> However RFC 822 [2] clearly states that the year portion of the date
> should contain two digits and not four. Which format is RSS 2.0
> compliant. The four digit year or the two digit year?
>
> Cheers,
>
> Simon.
>
> [1] - http://blogs.law.harvard.edu/tech/rss
> [2] - http://asg.web.cmu.edu/rfc/rfc822.html#sec-5

If you read the whole text about pubDate in [1] you will see that it says:

"All date-times in RSS conform to the Date and Time Specification of RFC
822, with the exception that the year may be expressed with two characters
or four characters (four preferred)."

Also, RFC 822 is superseded by RFC 2822 which specifies 4 digits for the
year.



// Magnus




transparent
Print
Mail
Digg
delicious
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent