XML Data Feeds - Some Questions

Alpha Blue wrote:

I'm hoping to be processing some XML data feeds directly to college
football stadiums soon and I'm building a plugin for CrossFire
Hardware/Software compatibility.

I assume you're referring to RSS or ATOM when you say "XML data feeds?"
Making this assumption, most feed readers I know of can handle both RSS
and ATOM. You just need to make sure you're providing the feed in the
proper format for the readers that will be used to consume your feeds.

Is there anything special I need to know about providing xml data feeds
with rails as far as user agents, or browser specific information is
concerned? Will one data feed differ from another in any way?

Also there is a way in some browsers (at least Safari) where you can
place a meta tag in the head section that will display the RSS button
in the address bar. At least that's how I think that feature works.

Here is an example form the Apple start page:
<link rel="alternate"
type="application/rss+xml" title="RSS">

Alpha Blue wrote:

This allows you to remove the pre-rendered xml and replace it with your
own tags.

Yes, I thought that might be the case. I know that many people actually
do use ATOM for this purpose rather than a custom XML format. Using a
known representation like ATOM can sometime make the parsing of the data
on the client-side easier by taking advantage of existing parsers. For
example: using an RSS or ATOM feed a client could use any RSS feed
reader to monitor the data feed. That may or may not be useful in your

But, in either case what you showed is how one would use the XML builder
templates. It just depends on wether you want to feed that data as

Thanks for the feedback Robert. I'm implementing that now for the

In case someone else follows this thread, the way to implement type with
xml.builder is by doing the following:

You convert the old syntax:

xml.total_offense team.to_ydspgm

TO the new syntax

xml.total_offense(team.to_ydspgm, :type => "float")

I hope that helps.

I updated what the xml data looks like now:


Alpha Blue wrote:

I updated what the xml data looks like now:


Cool. Now it's clear to the consumer what to expect, rather than having
to treat everything as a string.