For web feeds we all know of RSS and Atom, but is that it? Isn’t there a third option?
If not, why? Are RSS and Atom more than qualified to meet today’s demand to distribute information?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
For web feeds we all know of RSS and Atom, but is that it? Isn’t there a third option?
If not, why? Are RSS and Atom more than qualified to meet today’s demand to distribute information?
There are probably hundreds of other options. If not, we could make some up on the spot…
JSON isn’t an uncommon format for syndication. It’s more useful for clients that are implemented entirely in browser-side JavaScript, but JSON is simple enough to use in just about anything if necessary. Here’s one example of a JSON protocol based on Atom.
As for why RSS and Atom are the most common… RSS was the first to really take off. It was very limited, not very strict, and heavily extended to address the limitations – the result being that writing a good client was far more difficult than it should have been. RSS 2.0 didn’t really go far enough to solve these problems, and at least initially it introduced others, and so Atom gained some traction as a comparatively clean, extensible, easy-to-publish, easy-to-process alternative.
With enough sweat and cursing, you can use almost anything to distribute information. Finger and .plan files worked for years…