Forum Moderators: open
So until July 1, 2007, the DTDs for RSS 0.9 and 0.91 will be available via my.netscape.com. If you are a software developer, use this time to ensure that your RSS software is capable of displaying RSS feeds even if the DTD is unavailable, or have a backup copy cached locally for your parser to use in the absence of the specified DTD. If you are a content provider, either update your feeds to point to another copy of the DTD, or accept the fact that your feed may not be available through feed readers that don't have a backup plan in the case of a missing DTD.
The RSS 0.91 DTD was being accessed 4 million times a month and AOL/Netscape have simply decided they aren't interested in RSS 0.91 any more and don't want to pick up the tab for hosting the DTD.
The outcome of the DTD deletion is that the thousands of RSS feeds using Netscape's RSS 0.91 will become automatically invalid from July 1st 2007 (including, incidentally, the WebmasterWorld RSS feed). Most RSS readers do not need to access the DTD, but for the few that do it is important to have a plan which covers the DTD deletion. You have a couple of options. If you aren't using the entity references defined in the Netscape DTD, then you can switch your feed to Userland RSS 0.91 or (better) update to RSS 2.0 or Atom. If you absolutely rely on the entity references in your feed content, then you should copy the DTD locally, and change the doctype of your feed to reference your locally-hosted DTD.
Nipping over to Netscape just now to grab a copy of the DTD for 9.01 and reading the DTD header reminded me that for a short while RSS stood for "Rich Site Summary"
Sorry
self-indulgent reminiscance...
back to work now!
It is a shame they can't do a 301 redirect to someone who is willing to hold the DTD, possibly w3c or perhaps a commerical entity who has a major vested interest in the RSS industry.
If you are a software developer, use this time to ensure that your RSS software is capable of displaying RSS feeds even if the DTD is unavailable, or have a backup copy cached locally for your parser to use in the absence of the specified DTD. If you are a content provider, either update your feeds to point to another copy [web.archive.org] of the DTD, or accept the fact that your feed may not be available through feed readers that don't have a backup plan in the case of a missing DTD.
It is interesting that they're advising people to use the archive.org version instead.