I just uploaded an opml file into Google Base. I wonder what will happen. It'll take an hour to get published.
It didn't say I could upload an opml file, but then it didn't say I couldn't. I don't think it will work.
Anyway, if it turns up, it'll be here somewhere: http://www.google.com/base/a/alexbarnett
Now the RSS bit is interesting. The RSS 2.0 file allows extention against their namepace. This allows data entry via RSS.
<title>HR Analyst - Mountain View </title>
<description> We have an immediate need for an experienced analytical HR professional.
The ideal candidate has a proven record of developing analytical frameworks to make
fact-based decisions. </description>
<g:location>1600 Amphitheatre Parkway, Mountain View, CA, 94043, USA</g:location>
I need to sleep, hopefully some interesting RSS / XML / Atom experiments to wake up to in the morning...let me know.
Update: Bill Burham nails it:
"Once the feed gets inside Google the fun is just beginning. Most commentators have been underwhelmed by Google Base because they don't see the big deal of Google Base entires showing up as part of free text search. What these commentators miss, is that Google isn't gathering all this structured data just so they can regurgitate it piece-meal via unstructured queries, they are gathering all this data so that they can build the world's largest XML database.
"...As for RSS, Google Base represents a kind of Confirmation. With Google's endorsement, RSS has now graduated from a rather obscure content syndication standard to the exautled status of the web's default standard for data integration. Google's endorsement should in turn push other competitors to adopt RSS as their data transport format and process of choice. This adoption will in turn force many of the infrastructure software vendors to enhance their products so that they can easily consume and produce RSS-based messages which in turn will further cement the standard. At its highest level, Google's adoption of RSS represents a further trimph of REST-based SOA architectures over the traditional RPC architecture being advanced by many software vendors. Once again, short and simple wins over long and complex."