A open, flexible Facebook-style API for Apps would be awesome.  Imagine the community building the next generation office platform.

Right now, developers outside of Google can write Gadgets that live on the outside layout areas of GMail. Google developers have done some interesting things with Labs – I use the easy to find "Mark as Read" button / gadget.  However, if trusted development teams in the community, and developers at companies adopting Google Apps, had complete access to everything – including the interface, Apps would meet the challenge set forth to it by Microsoft Office (and its powerful friend, VBA).  A fully programmable cloud-based office suite.

Related Blogs

• Related Blogs on cloud computing
• Ten Key Reasons for Enterprise to Choose Cloud Computing
• Auto-scaling cloud computing and Denial of Service attacks « Wille …

• Related Blogs on google apps
• Google blog News – Google Apps: Labs Go Live in Google Apps Accounts

• Related Blogs on mashups
• Mashups « Empasize on Learning
• 19 Handy Twitter Mashups and Tools | Design And Marketing Blog …
• The Aggro1 Experience | FREE Music Mashups, cutups and bastard pop …
• Culture Bully’s Favorite Mashups of 2007

This looks really cool.  I hope it is not all for naught.  Anyone using it?  Have any examples? Please post them!

The support forum has few active topics. But I think there is potential here, even if Yahoo doesn’t exist in the same form 3 or 6 months from now.  I don’t think Microsoft would shut this stuff down.

YQL looks really neat and is a popular topic.  YQL seems like a highlight of this offering.

“Geokit is a Rails plugin for building location-based apps. It provides geocoding, location finders, and distance calculation in one cohesive package. If you have any tables with latitude/longitude columns in your database, or if you every wanted to easily query for “all the stores within a 50 mile radius,” then GeoKit is for you”

It is fantastic. Here is some sample code:

include GeoKit::Geocoders
   def get_location( location )
      loc = MultiGeocoder.geocode( location )   # ask GeoKit to find your city
      return loc
    end
 
    def calculate
     start_city = get_location("Hoboken NJ")
     end_city = get_location("Los Angeles CA")
     distance = start_city.distance_to( dest )
     #thats it!  really?? yes.
    end

What is Geonames

Geonames is a public location database / web service API that allows you to search and reverse lookup geography and location information, such as city names and towns, longitude/latitude, etc.

The excellent Geonames Gem for Ruby provides an easy to use interface into the geonames web service.

Why use geonames? I’ve found it extremely useful for finding “nearby” locations as well as cities/counties/subdivisions within another area. For example, look at the following call:

http://ws.geonames.org/search?q=NJ&maxRows=20

Viola! All the cities and location features in NJ. The real power in geonames (which you don’t necessarily get with geokit) is the ability to restrict searches based on FCL and FCODE designators.

For example, some locations from geonames might these elements attached to them:

<fcl>P</fcl><fcode>PPL</fcode>

What do these codes mean?

FCL and FCODE represent “feature codes.” A complete list of feature codes can be found here.

You can do neat things with feature codes. Witness:

“Geonames?”Yes, Ed

“New Jersey has over 127 miles of beachfront and another 83 miles of bayshore. Where are all of these beaches??”

Ed, I am not a person, just an XML web service. You’ll have to ask me a different way.

“Ok, how about this: http://ws.geonames.org/search?q=NJ&featureClass=T&featureCode=BCH”

Yumm.

More geonames; simple latitude / longitude lookup:
http://ws.geonames.org/postalCodeSearch?postalcode=10012&country=US

gives us the longitude and latitude for a zip code in Manhattan.

It is a great tool when you don’t want to have a local database with geography information. Put memcached in front of the calls, and you’ll have a zippy, small-footprint mashup in no time.