Attaching the rss.xsl file – just put this in solr/conf/xslt/ and then try

http://localhost:8983/solr/select?q=ipod&wt=xslt&tr=rss.xsl

these seems like a handy little example to me ... anyone see any objections to including this as example/solr/conf/xslt/rss_example.xsl assuming we...

1) add the stock License header
2) change the title to "Example Solr RSS Feed"
3) fill in the main description tag with some text like...
This has been formatted by the sample "rss_example.xsl" transform - use your own XSLT to get a nicer RSS feed
4) eliminate the docpos variable since it isn't used.

+1 for including this. I imagine a lot of people will want this to provide "subscribe to search results for a saved search" type functionality.

What kind of RSS?

-1 unless it is Atom. The nine variants of RSS have some nasty interop problems, even between
those that are supposed to implement the same spec.

Even better, a GData interface returning Atom.

I'm not involved or familiar with the RSS wars but I will say that this is a quick example of getting RSS out of Solr in the easiest possible way. It worked on every single browser and newsreader I tried it on. There's no reason we can't also include an atom_example.xsl as well. I don't understand why you would use GData for this at all, but i am probably out of my league there.

+1 for adding except remove the XSL2.0 references, not worth the confusion, date handling is not necessary for the exampledocs test case.

I wasn't in the RSS wars, either, but I was on the Atom working group. That was a bunch of volunteers making a clean, testable spec for RSS functionality (http://www.ietf.org/rfc/rfc4287). RSS 2.0 has some bad ambiguities, especially around ampersand and entities in titles. The default has changed over the years and clients do different, incompatible things.

GData is just a way to do search result stuff that we would need anyway. It is standard set of URL parameters for query, start-index, and categories, and a few Atom extensions for total results, items per page, and next/previous.

http://code.google.com/apis/gdata/reference.html

Plus there is contrib/gdata-server under Lucene waiting to be used, so there already is gData-something in Luceneland.

As an example, I don't think it matters if this is RSS, Atom, or GData. It just needs to show that you can transform solr results into a "standard" syndication format.

Any real example would need to change the specifics dramatically (unless you really wanted the description to be a list of "features" and link to http://localhost:8983/solr/select?q=id:$

)

As hoss suggests, I think this is good to include as long as the comments make it clear that you need to change stuff to make it 'real' - this may include reformatting to atom or gdata...

Someone else questioned my choice of RSS spec last night. I don't want my tiny Solr contribution to become a political issue! +1 on noting that it's incomplete and will have to be changed for the user's specific scenario. I'll make it Atom.

Adding atom.xsl (replaces rss.xsl)

Changes:

• Added apache header
• Atom, not RSS 2.0

It validates on feedvalidator.org as atom 1.0 except for the link rel=self, since that's on localhost)

+1 on including this in the 1.2 release

i have no interest in format holy wars, and i'm a big fan of well defined standards, but the fact remains that even if "RSS" is ambiguous to feed parsers, the concept isn't ambiguous to people, and the more examples we have for stylizing Solr responses the better ... so i've committed them both with some whitespace cleanup and standardized blurbs about being for example purposes only (matches the HTML example blurb).

Committed revision 541391.