Ok, I've never been to GeoWeb, but it's in Vancouver and I've been told Vancouver is a nice city with great boba (milk tea). So I've proposed a technical session about the current GeoWeb standards (KML, GeoRSS, GeoJSON), and about what I think their future together should entail. I've played around a lot with both these formats over the past few years, written parsers and generators, and now I've got a fairly good sense of what I still need from these formats, both as a developer and a consumer. If this talk is selected, it will give me an excuse to further articulate those needs, and my personal vision. I'd be interested to hear other's opinions about the state of the GeoWeb standards.
Here's the abstract:GeoWeb Standards: How far they've come, How far they need to go
The GeoWeb is growing up rapidly. KML, or Keyhole Markup Language, was invented by Google five years ago and became an OGC standard last year. GeoRSS, an extension of RSS, was invented by Harvard around the same time, and is now a defacto standard. There are now tens of thousands of KML files out there, popular sites like Blogger outputting GeoRSS files, and there are numerous parsers, generators, and validators for both of these formats.
But we're still really in the infancy of being able to truly share and track geo data on the web. We can't subscribe to updates for a KML file with a GeoRSS feed, we can't do CRUD operations on a KML file, we can't settle on a "flavor" of GeoRSS, and more importantly, we can't figure out how these two formats should co-exist in perfect harmony. In this talk, we'll examine the progress the current standards have made and discuss how they could work better with eachother and with the rest of the web - covering topics like syndication, collaboration, searchability, and unification. We'll conclude with suggestions about how the attendees can help.