 | | Making an RSS FeedHow does RSS syndication work? Say you publish a new web page about a particular topic. You want others interested in that topic to know about it. By listing the page as an "item" in your RSS file, you can have the page appear in front of those who read information using RSS readers or "news aggregators" (explained more in my sidebar article, RSS: Your Gateway To News & Blog Content). RSS also allows people to easily add links to your content within their own web pages. Bloggers are a huge core audience that especially does this.
What does RSS stand for? There's a can of worms. RSS as introduced by Netscape in 1999 then later abandoned in 2001 stood for "Rich Site Summary." Another version of RSS pioneered by UserLand Software stands for "Really Simple Syndication." In yet another version, RSS stands for "RDF Site Summary."
History buffs might be interested that there's been some rivalry over who invented RSS. This is why we have both different names and indeed different "flavors" or versions of RSS. Mark Pilgrim's written an excellent article, What Is RSS, that charts the different versions with recommendations on which to use. I'll also revisit the version choice you'll need to make. But first, let's look more closely at some basics of what goes into any RSS file.
How Easy Is RSS?
I've been exploring RSS because it was time that Search Engine Watch offered its own stories in this manner. I've read several tutorials about making a feed, and they generally suggest that it is easy. They often offer code that you can "cut-and-paste" and link over to specifications that I actually don't find that clear.
For example, the RSS 2.0 specification has an "cloud" element that's optional but which a lay person might still wonder if they should use it. Meanwhile, heaven help the person who stumbles into the RSS 1.0 specification and its complicated RDF syntax.
Sure, making an RSS file IS easy for many. If you understand HTML, you'll probably understand enough to do a cut-and-paste from someone else's RSS file to make your own file. Don't know HTML? Start a blog, because several blogging tools automatically generates RSS files.
As for those non-technical people using WYSIWYG page building tools or personal home page building systems, have faith. Even you can build an RSS file from scratch, as long as you dispense with some of the extra features you probably don't need. We'll go through how to do this below. Later, I'll also mention some tools that will even do some or all of the work for you.
The RSS File
At the heart of an RSS file are "items." No matter what version of RSS you settle on, your file will have to include at least one item. Items are generally web pages that you'd like others to link to. For example, let's say you just created a web page reviewing a new cell phone that's being released. Information about that page would form an item.
To enter your item into the RSS file, you'll need three bits of information:
The title and description of your item need not match exactly the HTML title tag of the web page that the item refers to, nor the meta description tag, assuming you use these (don't know what they are? See my How To Use HTML Tags article). You can write any title and description that you think will describe the page. However, using your page's title and meta description tag certainly makes it easy to copy and paste to build your RSS feed.
Having defined items we want to distribute, we now have to define our site as a "channel." You'll use the same tags as with the items: title, description and link. However, this time the information will be about your entire site, rather than a particular page.
Mind Blowing Options
Everything shown above is the bare basics you need to create a file and start syndicating content from your web site. However, there are additional things you could do.
For example, rather than your entire web site being a "channel," you could actually have different content from within the web site be defined into separate channels. That's something I'm not going to explore in this article, but some of the resources below will guide you through this, when you feel more comfortable.
As hinted at, RSS 2.0 allows you to insert all types of additional information into your feed. It can make your head spin to look at these and decide what to use. The easy answer is, don't bother with anything you don't know. Not every aggregator supports all the options offered. As long as you provide the minimum information suggested above, you should be fine.
Did I Choose The Right RSS Version?
Earlier, I'd mentioned there are different versions of RSS. Even though we entered the bare minimum of information, it turned out that we were able to have a file that was easily considered to be RSS 2.0, the latest version promoted by UserLand and which is widely used.
Indeed, the Syndic8 site reports that the most popular format of RSS by far is RSS 0.91 -- and though we've used RSS 2.0, our file as shown is entirely compatible with RSS 0.91. In short, we're in safe company.
What about that RSS 1.0 version that I said was complicated. Well, it is complicated. However, some people might want to make use of some of the special capabilities that it offers. If you are interested in it, then check out the official specification.
Saving The File
Now that we're done adding to the file, we need to save it. But what name shall we give it? I've looked and not seen any guidance on this. I imagine that's because as long as the file is valid (more below), it probably doesn't matter what it's called.
To make my own decision for Search Engine Watch, I decided to imitate what I saw out at UserLand, which promotes the RSS 2.0 standard that we used. UserLand's example feeds all ended .xml, so let's do the same. As for the first part, that really can be whatever you like. For our example, let's say we just call it feed.xml.
Now that our file is saved, we can place it anywhere we want on our web server. Wecan then put it in the root or home directory.
Validating The File
Now our RSS file is done, but did we do it right? To find out, we need to validate it. Use the aptly named Feed Validator service. Simply enter the address to your RSS file, and you'll be told if everything is OK -- or if there's something wrong you need to fix.
How about a quick preview of how your new feed actually looks? Then pay a visit to Wytheville Community College News Center. Again, enter your feed URL, and you'll see the clickable headlines and story descriptions nicely assembled inside a box.
The service will also generate a JavaScript code that you can post on your site. Anyone copying the JavaScript can automatically have your feed syndicated into their pages -- pretty neat!
Get Syndicated!
Now that your file is validated, you want the world to know about it! To make this happen, visit the RSS directories and search engines listed in the RSS: Your Gateway To News & Blog Content article. They generally offer submission pages, where you can inform them of your feed.
You also want to make sure people who come to your web site see that you provide a feed. It's very common to post a link to the feed somewhere on the home page of a web site. If you have a dedicated news page, you may want to put it there, as well.
You can link to your feed with an ordinary HTML link. However, many sites use a small orange XML icon to link to the feed. I've also seen some sites use blue RSS icon. I could find no standard about using these. So, to be safe, I did all three with Search Engine Watch. Look on the home page, and you'll see how it's done (and help yourself to the icons, if you need them).
Finally, it's good to "ping" one of the major services that track when web logs and RSS content changes. By doing this, you ensure that other sites that monitor these know to check back at your site for more content.
Weblogs.com is one of these major sites. Enter your site's name and the URL of your feed into the manual Ping-Site Form, and it will know you've updated your feed. The Specs page explains how to set up automatic notification.
blo.gs is another major change monitoring site. It is supposed to receive any changes that come from Weblogs.com, so you shouldn't need to notify it separately. However, if you want to be on the safe side, it's easily done. Use the ping form, which also explains how to set up automatic pinging, as well.
Tutorials & Resources
RSS Headline Creator allows you to skip coding and manually choose the number of headlines you'd like to include in your file, up to the 15 maximum allowed. Then a form with boxes that you fill out will be made. Enter the right information, then push the "Make The Code" button. Your RSS file's code will be generated, for you to copy and paste into a text editor and save.
How To Get Your Web Site Content Syndicated is a Dec. 2002 tutorial by Kalena Jordan and Dan Thies from which I drew inspiration to get my own feed going.
Syndic8's How To Section lists a variety of tutorials that discuss how to build RSS files.
Content Syndication with RSS is a book by Ben Hammersley that was just released in March 2003. I haven't read it, but everything I've heard is that it should be excellent.
RSS Resources Directory from UserLand categorizes helpful information related to RSS, in different categories.
|
|
|
|
|
| Information Security: Principles and Practice (Hardcover)
by Mark Stamp |  | As businesses and consumers become more dependent on complex multinational information systems, the need to understand and devise sound information security systems has never been greater. This title takes a practical approach to information security by focusing on real-world examples. While not sidestepping the theory, the emphasis is on developing the skills and knowledge that security and information technology students and professionals need to face their challenges.
Publisher: Wiley-Interscience (October 28, 2005)
Product Dimensions: 9.3 x 6.3 x 1 inches
Paperback: 416 pages | About the Book:
The book is organized around four major themes:- Cryptography: classic cryptosystems, symmetric key cryptography, public key cryptography, hash functions, random numbers, information hiding, and cryptanalysis
- Access control: authentication and authorization, password-based security, ACLs and capabilities, multilevel and multilateral security, covert channels and inference control, BLP and Biba's models, firewalls, and intrusion detection systems
- Protocols: simple authentication protocols, session keys, perfect forward secrecy, timestamps, SSL, IPSec, Kerberos, and GSM
- Software: flaws and malware, buffer overflows, viruses and worms, software reverse engineering, digital rights management, secure software development, and operating systems security
Additional features include numerous figures and tables to illustrate and clarify complex topics, as well as problems-ranging from basic to challenging-to help readers apply their newly developed skills. A solutions manual and a set of classroom-tested PowerPoint(r) slides will assist instructors in their course development. Students and professors in information technology, computer science, and engineering, and professionals working in the field will find this reference most useful to solve their information security issues.
An Instructor's Manual presenting detailed solutions to all the problems in the book is available from the Wiley editorial department. | About the Author:
MARK STAMP, PHD, is Professor of Computer Science, San Jose State University, where he teaches undergraduate and graduate-level information security courses. In addition to his experience gained in private industry and academia, Dr. Stamp has seven years' experience working as a cryptanalyst at the U.S. National Security Agency. | Book Reviews:
"Information Security: Principles and Practice presents information security concepts and practices insightfully in an easily comprehensible style. Although primarily intended as a college course resource, this book will appeal also to many security professionals. Highly recommended." (CHOICE, April 2006)
"The book is well suited for beginners, and contains enough introductory material on a variety of topics." (Computing Reviews.com, January 9, 2006) |
|
|
|
