Content Syndication With RSS
The first three chapters are primarily discussing the multiplicity of RSS standards. While with some other technologies it might seem a bit excessive, remember that RSS is a forked project with the forks at this moment bearing little resemblance to one another. The abbreviations even have different abbreviations - RSS means Really Simple Syndication if you are using RSS 0.91 or RSS 0.92, that was developed by Dave Winer. RSS means RDF Site Summary if the version you're using RSS 1.0. The development credits in this case go to RSS DEV team. To confuse you even more, the RSS 2.0 standard is deciphered as... correct, Really Simple Syndication again.
Hence chapter 4 discusses Winer's implementation (simplistic and user-friendly), while chapter 6 focuses on RSS 1.0 (RDF-compliant and data-architect-friendly), and chapter 8 talks about RSS 2.0 (improved RSS 0.9x). Chapter 4 is available online as a PDF file. Section 4.4 is recommended for those interested in promoting their RSS feeds as it provides pretty good reference to meta data.
Chapter 9 is perhaps of special interest to Web developers and administrators out there. It presents several code samples to properly parse RSS and present the result in readable HTML. The examples include (a) parsing with XML::Simple in Perl, (b) parsing with Perl regular expressions, (c) parsing with XML::Simple and sending the headlines to cell phones via WWW::SMS, (d) parsing via XSLT transformation. Python, PHP and ASP folks might feel left out due to the abundance of Perl examples, but if you got so far in the book, you can probably apply the regular expressions example or search for appropriate support for RSS format in your preferred language.
Going beyond the standard itself, RSS directories, aggregators and readers are discussed. Author makes a distinction between the last two by classifying Meerkat-like services into aggregators and desktop or Web applications designed to present the information to the user into readers. The chapter also provides information about Syndic8, its API, and describes the feed registration process. OReilly's Meerkat is also discussed in chapter, together with reference table for its API (you can make Meerkat generate HTML or RSS news headlines on certain topic or using certain keywords by providing a right query to its Web interface).
The book is quite a smooth read for a text describing the details of data specification. The chapters are informative and the book is not overloaded with useless information just to increase the page count. The tips are quite useful for someone, who is knew to the field and answers some questions not covered by standards (e.g., how often should you request an RSS feed, what to do if you're being screen-scraped, etc.)
I like the way the author divided the chapters into RSS 0.9x/2.0 and RSS 1.0 and kept two worlds apart. Most of the time you probably won't be interested in developing a feed to support both standards, but would like to focus just on one. The examples in Perl are perfect with me, although for someone new to Perl or programming in general those examples with abundant regular expressions might look a bit convoluted. Kudos to the author for not expanding on the topic, like many do, and providing an example of a script for RSS manipulation in every possible language out there.
What's missing? I wish more pages were dedicated to desktop RSS readers. FeedReader, HotSheet, Syndirella, Beaver and SharpReader are excellent end user applications currently gaining some popularity among those who'd prefer to browse the favorite headlines at a glance, instead of going to a dozen of sites every morning. To be fair, there's a huge list of readers in Appendix, and some applications mentioned above only came around in the last few months, which was probably after the book hit the press. Some sites also didn't make it into the book. I like DailyRotation and FreshNews that borrow from Meerkat's versatility and provide their own feed portal.
Overall, the book is a pretty good developer's guide to RSS standard. Accompanied with helpful illustrations and numerous tips it's an excellent resource for those unfamiliar with RSS and a helpful reference for those who have been doing Web syndication for a while.
You can purchase Content Syndication With RSS from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
As both an aggregator and provider of content, I can safely say an entire book need not be devoted to the subject. Maybe a pamphlet. I guarantee this book is 90% fluff.
I think the ability to easily transfer information in real time is just going to grow with time, this is not a fast fad.
Go calculate something!
Am I the only one who likes to view website/blog entries in their original context (where relevant) -- i.e. on the webpage where it was published -- even if it means I have a really long "links" list?
Presentation isn't everything, but it matters.
Joe
http://www.joegrossberg.com
When is /. going to use the RSS standard instead of its current PITA XML format?
Here's the problem I have with content syndication/RSS.
It is difficult for a non-professional or non-techie to implement someone else's feed on their site.
I have content that is updated all day long and there are probably hundreds (at a minimum) of users that would love to add my content to their site via an RSS feed. And it would drive a lot of people to my site, too.
Unfortunately, HTML is about as limited as most of these people get. A lot of them probably aren't even that far along - most likely using WYSIWYG HTML editors.
All the RDF/RSS feed grabbers/users that I have seen are fairly involved perl (or other language) scripts that require a nice chunk of work on the webmaster's side.
Until people can implement my feed on their site with no more difficulty than copying and pasting a few lines of pre-generated code, then it's useless.
Here's Slashdot's current RSS page:
h dot.org0 0:00
1 050
c 1050
1 050
0 50
Slashdot
http://slashdot.org/
News for nerds, stuff that matters
en-us
Copyright 1997-2001, OSDN
2003-04-21T16:33:48+00:00
OSDN
pater@slas
Technology
hourly
1
1970-01-01T00:00+
Your Headline Reader Has Been Banned
http://slashdot.org/faq/accounts.shtml#ac
Your RSS reader is abusing the Slashdot server. You are requesting pages more often than our terms of service allow. Please see the FAQ link for more information, and if you email us, include your IPID MD5: 2be13864b6e87d2ec6b4701261c83663.
You May Only Load Headlines Every 30 Minutes
http://slashdot.org/faq/accounts.shtml#a
Your RSS reader is abusing the Slashdot server. You are requesting pages more often than our terms of service allow. Please see the FAQ link for more information, and if you email us, include your IPID MD5: 2be13864b6e87d2ec6b4701261c83663.
In 72 Hours, Your Ban Will Be Lifted
http://slashdot.org/faq/accounts.shtml#ac
Your RSS reader is abusing the Slashdot server. You are requesting pages more often than our terms of service allow. Please see the FAQ link for more information, and if you email us, include your IPID MD5: 2be13864b6e87d2ec6b4701261c83663.
Do Not Bother Contacting Us For 72 Hours
http://slashdot.org/faq/accounts.shtml#ac1
Your RSS reader is abusing the Slashdot server. You are requesting pages more often than our terms of service allow. Please see the FAQ link for more information, and if you email us, include your IPID MD5: 2be13864b6e87d2ec6b4701261c83663.
So apparently we've not only succeeded in slashdotting Slashdot, we've gotten Slashdot to give us multiple duplicate posts! WE WIN!
Someone you trust is one of us.
How are sites that offer a Semantic Web interface such as RSS supposed to bring in revenue? They can't rely on advertising because the machines that browse the Semantic Web cannot be trusted to deliver advertising to a human eyeball.
Will I retire or break 10K?
Slashdot has been blocking my rss aggregator for about 2 weeks -- despite the fact that my aggregator is set to every 4 hours. The sad thing is I didn't really care because the RSS summaries were pretty crap. Not putting the full article summary (which in most cases is the article) is bad, Stopping in the middle of a sentence to do it is really bad...
I am not a number! I am a man! And don't you
It seems like this would be a good way for major news outlets to draw traffic to their sites - if I could put a brief RSS generated bit of info on one of my web pages, people might click the link and go to the other web sites. So why can't I find any RSS feeds for major news sites like CNN and such?
Making an RSS feed is easy - I want to have RSS feeds of other more interesting sites avaiable to put in my own web pages. And that would benefit everyone, no?
Password protected feeds add real value to RSS for obvious reasons. You won't always want everyone to read your feeds
Diarist.com offers a HTTP Password protected RSS feed here. http://rsstest.diarist.com/
As I write this... There are only two RSS clients which can read it's passworded feeds.
1. NewsGator
2. A beta version of FeedReader
Free Web based FTP
Cheers,
Mike
www.jmagar.com
-
I've noticed that with most blogs, the content is actually placed into the RSS (HTML tags and all in some cases). Some of the bigger sites that offer feeds (/., News.com, etc.) provide a headline and then maybe a 40 character summary.
/.'s case, I'm consuimng the headlines via an aggregator, but all I'm seeing is a link and the article headline. I still go to the site to read the full content and the comments, so I'm still seeing the banner ads and such.
In
The key is putting limited information, so you can draw the user to the site if you're trying to generate revenu from your content. Then, you better hope the internal link referenced in the feed has some advertising.
-- jimmycarter
Mail? Put "slashdot" in the subject to pass the spam filters.
Just to let you know: Full featured RSS support ist scheduled for KDE 3.2. See http://dot.kde.org/1049415292/ for more information.
This will include a RSS dcop service providing a powerful XML-RPC interface to www.syndic8.com, a new RSS konqueror sidebar and a rewritten knewsticker.
Currently everything is still under development but already quite useful (if you know how to deal with dcop...). Let's hope we will have everything finished before KDE 3.2.
I needed one which didn't use a database, but only flatfiles. It took me a while to find them but here is what I've found:
CafeRSS The one I'm using rigth now. Really easy.
OnyxRSS More powerful, uses the XML parsing fetures of PHP
Rippy Another one, I just don't know.
Have fun!
quake74