Slashdot Mirror
Netscape Restores RSS DTD, Until July
Randall Bennett writes "RSS 0.91's DTD has been restored to it's rightful location on my.netscape.com, but it'll only stay there till July 1st, 2007. Then, Netscape will remove the DTD, which is loaded four million times each day. Devs, start your caching engines."
Developers who made the mistake to use that external resource in their code most likely don't have the brain resources to adapt until July.
(This is not a troll. Resignation and bitterness, maybe. But not a troll.)
Developers should take the opportunity to move to Atom. In the mean time we could use something as simple as round-robin DNS to share the load or have Mozilla, Google or the internet archive host it. It's a historical document and should reside at a permanent URI.
Netscape Restores RSS DTD, Until July - from the that's-kinda-lame dept.
Two Stargate SG1 Films Announced - from the good-for-them dept.
Linux: x86 Linux Flash Player 9 is Final - from the i-still-hate-flash dept.
Looks like somebody is having a case of the mondays.
(On Wednesday.)
I admit, I am not familiar enough with RSS. However this is a 2.3KB file that is not supposed to change. Why would developers NOT hardcode it into their RSS tools?
Do Or Do Not, There Is No Spoon, There Is Only Zuul. Everything in the above post is probably opinion.
One line blog. I hear that they're called Twitters now.
And any dev who codes his app to check a file like this every day instead of caching it client-side should be smacked oh-my-god-so-frickin-hard.
Richard Dawkins asks this very fundamental question, why reproduce (sexually or asexually) using seeds and embryos? Why not propagate by cuttings and cloning? It happens in nature. Many fern like plants do it. Bananas have been reproducing by new shoots. Then he discusses how harmful mutations too propagage and how going back to the basics and recreating the embryo selects the beneficial mutations and puts a check on deletrious mutations. Books The Selfish Gene, Climbing the Mount Improbable.
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
Great, the entire internet community can rely on one random person's server instead of on one really big corporation's server. That should fix things.
Don't blame me; I'm never given mod points.
One line blog. I hear that they're called Twitters now.
As I replied for the previous Netscape RSS DTD article http://slashdot.org/comments.pl?sid=216818&cid=176 03480, caching DTDs from the network is not the answer if there is the possibility they will not be there in the future:
/ resolver-article.html that helped me out. In addition, if you are using Eclipse with the web tools platform, you can customize the catalog so it resolves DTDs and entities locally. See http://wiki.eclipse.org/index.php/Using_the_XML_Ca talog.
The proper thing to do is for your application to use an XML catalog for resolving entities/URIs and bundle the DTD files with the application. There is a good article at http://xml.apache.org/commons/components/resolver
Uh, if Microsoft could be held liable for bad design, their buildings would already have been burned to the ground, their women stampeded, their cattle raped, the ground sown with salt and the wells poisoned.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
(I tried posting this as a reply to the blog posting, but I'm not getting the confirmation email, so I'll post it here)
From a purely technical standpoint, I agree with your assertion that, for well-baked files like RSS DTDs, clients should not be relying on a file hosted by an arbitrary service.
That being said, please understand that the emotional message you're sending is: "Don't rely on Netscape".
Why?
Back when RSS was first starting out, Netscape's documentation said to use Netscape URLs for the RSS DTDs. Witness this page, published by Netscape, from late 2000:
Now, a shade over six years later, Netscape is saying "Oh, yeah, what we told you to do? Never mind. We're not supporting it any more."
If Netscape/AOL was shutting its doors, that'd be one thing. If the service in question was obviously onerous, that too would be understandable. Or, if Netscape told people "For the love of all that is holy, don't use our URLs for your DTD needs!" from the get-go (based on that document, you didn't), any such reliance would be our own fault.
But, because AOL does not want to serve up two static files, each of which is smaller than the "Netscape Reports" graphic on the netscape.com home page, Netscape is abandoning a service they told people to use.
So what are we to think about Netscape's current services and their long-term usability?
The Busy Coder's Guide to Android Development
But you waited until (UID 633928) to register on Slashdot?
Newbie.
Reality has a liberal bias
For example, globally unique IDs in Atom feeds are often URNs, and hence URIs; but URNs aren't URLs, and you shouldn't need or want to try to connect to something just because it's used as a globally unique identifier in an Atom feed and looks a bit like a URL.
This is relevant because many Internet specifications use URNs (or in the case of HTML, FPIs) as spec identifiers. For instance, XML namespace identifiers are URIs; and while some of them happen to be URLs too, the XML namespace recommendation says:
In the case of RSS 0.91, Netscape wrote the spec, and they used a URL and told people to connect to it to fetch the necessary information to parse the file. They could have used a URN, but I'm guessing they wanted to keep their options open as far as changing the spec on the fly.
(Of course, Dave Winer has a different approach to changing RSS specs on the fly...)
GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
No. This is the perfect example of why a URI is not necessarily supposed to be treated as a URL. http://my.netscape.com/publish/formats/rss-0.91.dt d is just a unique identifier for the RSS DTD. It used to also be hosted there as a convenience, but your software isn't supposed to rely on that.
http://outcampaign.org/