Just read Schuyler's thoughts on Web Map API's over at Mapping Hacks and he ends with a query about the next stage of the game for web mapping. I'm pretty sure I know where he's going, which I'm planning on exploring fully here (been planning for awhile, but I'm still not giving up, I promise), but I had a few thoughts at this nice LI Conference hosted by Directions.
The main thought is really quite simple, on how we take an intermediary step to the full on Geospatial Web dreams. It's this:
Yahoo!, Microsoft and Google need to build in GeoRSS output in to their mashup APIs.
At this LI conference, the vendor guys were actually getting quite good talking about GeoRSS, and how they can read it in. Which is sort of interesting to me. But what gets really interesting is when they can output GeoRSS by default. This turns any mashup in to Drive By Data and the essence of Tim O'Rielly's Architecture of Participation (mine's a bit more on top of that) – that users will create things of value simply by doing what they're doing already.
It makes it so I can build a mashup that is just a synthesis of three other mashups, from Yahoo! and Microsoft, since by using their API a hacker would have (perhaps) unknowingly made a GeoRSS feed of the points he was plotting. Right now that's impossible unless the mashuper explicitly make their data available. Many just put it up in a simple xml format already, but by building GeoRSS explicitly in to the mapping engine, it will always happen. Once this gets started, you can start to see what GeoSpatial Search would look like, and these search engine companies can apply what they know best to maps. Not just finding local information, but allowing us to search and sort layers of data that users from all the world are putting up on mashups. Yahoo! is making some traffic feeds and whatnot available as GeoRSS, but they're not yet making it so anyone who makes a mashup has a feed that someone else can attach to, in the way that flickr or del.icio.us does.
And once we make the first step with GeoRSS, then we can start to get WMS and WFS, to combine with the rest of the Geospatial Web, so that we're not in divergent walled gardens, but instead all speak the same language and start to build something much bigger. But even if they just start with GeoRSS then I can just make a datastore in GeoServer that can translate from GeoRSS to the richer display options of WMS and deeper query language possible with WFS.