Skip to the Main Content

Note:These pages make extensive use of the latest XHTML and CSS Standards. They ought to look great in any standards-compliant modern browser. Unfortunately, they will probably look horrible in older browsers, like Netscape 4.x and IE 4.x. Moreover, many posts use MathML, which is, currently only supported in Mozilla. My best suggestion (and you will thank me when surfing an ever-increasing number of sites on the web which have been crafted to use the new standards) is to upgrade to the latest version of your browser. If that's not possible, consider moving to the Standards-compliant and open-source Mozilla browser.

July 22, 2005

Atom 1.0

The Atom Specification has been finalized. And Sam Ruby has asked that people migrate away from Atom 0.3 to the final Atom 1.0. Using Niels Leenheer’s very nice guide to upgrading, it took maybe 5 minutes to upgrade my Atom feed from 0.3 to 1.0.

If you’re using the old feed, be forewarned that it will go away at some point in the not-too-distant future. Once you’ve upgraded your aggregator software to a version that supports Atom 1.0. (NetNewswire 2.0.1, for instance, already supports Atom 1.0), point you aggregator at the new feed instead. The same holds for the feeds at the String Coffee Table.

Posted by distler at July 22, 2005 2:26 PM

TrackBack URL for this Entry:   http://golem.ph.utexas.edu/cgi-bin/MT-3.0/dxy-tb.fcgi/614

4 Comments & 0 Trackbacks

Re: Atom 1.0

Aren’t you planning on redirecting the old to the new feed?

Posted by: Henrik Lied on July 22, 2005 5:44 PM | Permalink | Reply to this

Redirection

That’s probably what I will do.

The main point is that — for those who don’t upgrade their clients — the feed will break sometime in the near future.

That remains true whether it goes 410 (permanently gone), 301 (moved permanently) or gets silently redirected to the new URL.

Posted by: Jacques Distler on July 22, 2005 6:13 PM | Permalink | PGP Sig | Reply to this

Re: Atom 1.0

I committed a few more checks into the feedvalidator. These changes should be online by the morning. Two of these checks will affect your feed, specifically:

  • your title type=”xhml” needs an xhtml:div, or to be changed to another type.
  • you have a summary with type=”text” which is expressed as CDATA and contains a reference to the eacute entity. This likely should be type=”html”.

Finally, something just to be aware of. I will ultimately add checks to ensure that dc:subject and atom:category elements don’t appear inside the same element (which takes precedence?). This does not appear that it will affect your feed.

Posted by: Sam Ruby on July 22, 2005 8:26 PM | Permalink | Reply to this

Personalized Service!

  • your title type="xhml" needs an xhtml:div, or to be changed to another type.

Changed to html. I think that works best.

  • you have a summary with type="text" which is expressed as CDATA and contains a reference to the eacute entity. This likely should be type="html".

Forgot to filter the summary to convert named entities to NCRs. Fixed.

Thanks for the feedback, Sam. If you turned up any more problems, please let me know.

Posted by: Jacques Distler on July 22, 2005 9:15 PM | Permalink | PGP Sig | Reply to this

Post a New Comment